Okay, let's do sudo ipa. You don't really need sudo. But hey, I'm doing it automatically and doesn't hurt.
I have my ENS160 which is in the state of UP.
And what else do we see? It's dynamically assigned. That means that there's a DHCP server behind it.
And this is the inetv4 address.
It also has an inetv6 address which is the ipv6 address. But as I
told you before, that is not really something that is used a lot.
So to verify that we can reach out to google.com I use ping google.com and
that's all. I'm not going to check my hostname resolution and my routing table.
I would only do that if pingongoogle.com is giving me a failure because then you want to know what's going on, right?
And the option is that you get hostname could not be resolved. So let's do
a ping on something that doesn't exist. Then you can see the error message.
Here you see the error message name or service not known. That means typically that it's not available in DNS.
And if that happens for a server that should be available, well then the next test would be to ping 8.8.8.8.
Everybody on the planet is using it. It's a Google DNS server,
it's very much available and use it as a connectivity test.
If you can ping 8.8.8.8 and you cannot ping DNS names, at least
you know that the problem is DNS related and not routing related.
Next SS Tul which is showing services currently offered on
my system. No need to do sudo for that.
Now when I want to do NMAP the then I do need sudo nmap and let's do sudo NMAP on localhost.
Now funny thing is that when we use sudo NMAP on localhost it's only
scanning some of the most common ports and that's why it doesn't find everything.
NMAP has a ton of options. Go explore them if you want
to learn more about all the rich possibilities of this utility.