Congratulations!
Look at this.
You've received the yellow warning that we're at the end of this module,
a module where we've introduced the network analysis
tools that we have available to us,
as well as the troubleshooting course in general.
We've looked at how we can get statistics about our network
card for drop packets with ip ‑s and link,
we've seen that nload could be used to see the bandwidth that
we're achieving on our network interface cards,
we can take a look at the configured options on our network card to
make sure that we're using the most efficient option,
we've seen how we can use resolvectl,
which is available on our Ubuntu system but not on our AlmaLinux system,
to manage our DNS settings.
But of course we've got our traditional tools such as dig and
getent and hosts to manage the entries as well.
We've seen the shortened IP addresses, such as ping 1.1,
to test connectivity to our outside world,
and we've seen how we can ping our default gateway for internal
connectivity using a little bit of a command‑line hack.
Using nmap we're able to port scan to see which ports are open on a system,
but that can be very useful when we have disabled ICMP pings to our systems.
But there you go.
We're at the end of this module,
a module I really hope you've taken a lot from and you're ready to move on
to the next module where we're going to be taking a look at troubleshooting memory and CPU issues within our Linux systems.