Hello, and welcome to this presentation from Pluralsight. My name is
Andrew Mallett, and I'm here as your instructor to help guide you
through this module where we'll we take a look at Managing Linux
Network Configuration. Now we're going to work through taking a look
at the ip command,
the Swiss Army Knife of gaining information about your network.
And in networking with Linux, we're going to take a look at how we
can configure networking in RHEL with NetworkManager, in openSUSE
using Wicked, and in Ubuntu using Netplan.
Yes, we suddenly move away from standardization and what we've become used to
with systemd and taking a look at how we're quite different with our network
configurations when working in Linux. We'll take a look at host name resolution
and some of the tools that we can use with that, including dig. We'll be taking
a look at how we can control which resources are used in name resolution, so
our nssswitch.conf, as well as looking at DNS entries and how we can configure
the DNS servers with our different networking tools across our distributions.
Finally,
we're going to be taking a look at monitoring network traffic, so we can
get a better understanding of why things are happening the way they are on
our network. And even using the command line,
there's plenty of tools available for us to go through and
investigate what's happening on our network. Now,
as we've already mentioned, we are a long way from standardizing our
persistent networking configuration. In Alma Linux, which is based around
Red Hat Enterprise Linux, we use the NetworkManager. When we're working
with openSUSE, we are using Wicked when we're working with servers. And on
Ubuntu 20.04, we are working with Netplan, so a long way from what we've
seen with our systemd and the standardization improvements we have in that
environment.
But don't worry, we don't need to stress too much.
No,
we don't. At least reading our networking is standardized by using the
command ip. The one command can pretty much do everything for us from looking at the IP address to looking at our route table.