Fundamental Networking Commands

This how-to will acquaint you with the basic tools used to setup and establish networking on Ubuntu.

Lecture Slides

Do you know how to decipher a manual page? Here’s how.


  • ip

  • hostname

  • arp

  • route

  • ss

  • netplan


  • /etc/netplan

  • /etc/hosts

  • /etc/hostname

Essential IP Information

The ip command is a multi-purpose tool for setting and viewing IP parameters. To determine the current configuration of Ethernet devices on your system run the command:

$ ip addr 
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc fq_codel state UP group default qlen 1000
    link/ether 0e:77:ef:6e:a6:9d brd ff:ff:ff:ff:ff:ff
    inet brd scope global dynamic eth0
       valid_lft 2113sec preferred_lft 2113sec
    inet6 2600:1f18:1d35:8f01:9ed0:1196:552d:ee37/128 scope global dynamic noprefixroute 
       valid_lft 422sec preferred_lft 122sec
    inet6 fe80::c77:efff:fe6e:a69d/64 scope link 
       valid_lft forever preferred_lft forever

You can use ip to set a temporary IP address on an interface but that’s risky on a VM! Changes made using ip immediately take effect but do not survive a reboot. In order to have changes stick after a reboot you must alter some configuration files on the system. On older Ubuntu the configuration file is /etc/network/interfaces. Here’s an example:

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto ens192
iface ens192 inet static 

iface ens192 inet6 static 
    address 2607:f380:80f:f192::10
    netmask 64

More recent versions of Ubuntu use Netplan. Netplan is a tool that works on many different Linuxes. It generates the configuration that’s right for the Linux you’re using. Here’s the an example of the Netplan configuration on your VM:

            dhcp4: true
            dhcp6: true
                macaddress: 0e:77:ef:6e:a6:9d
            set-name: eth0
    version: 2

Making changes to the file does not immediately change the network interfaces. When you want to change your IP address settings the procedure is:

  1. Edit the Netplan configuration

  2. Run netplan try to test the configuration

  3. If you can still see the prompt you’re done. If not you have to wait and fix your settings.

Setting your Hostname

When you install Ubuntu the installer asks you to give a hostname. You can change those later if you wish. You can alter your host name using the hostname command. Hostname with no arguments prints the current hostname:

$ hostname

You can set the hostname too:

$ sudo hostname newname

The change isn’t permanent. If you want to make the change permanent you must put your new hostname into the /etc/hostname file. It’s very important that you also make sure your hostname is listed in /etc/hosts. If it’s not you will see funny errors when you run the sudo command. The hosts file is discussed in the next section.

The Hosts File

Before there was such a thing as DNS every hostname of every computer on the entire Internet was listed in a file /etc/hosts. A copy of that file was placed on every computer and someone was responsible for keeping it maintained. That system has obvious problems with scale but instead of being replaced, DNS just adds a layer on top of it. Your /etc/hosts file is still a piece configuration. Even Microsoft Windows has a hosts file it’s located in C:\Windows\System32\drivers\etc\hosts. Here’s an example of a hosts file from your VMs:  localhost  ubuntu-server

# The following lines are desirable for IPv6 capable hosts
::1   ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

The hosts file is where the special name “localhost” gets its meaning. Also, by adding the name of your computer to the hosts file Linux ensures you’ll be able to refer to your computer by name even if it doesn’t have a DNS entry. The hosts file takes precedence over DNS so if you place a host name in there Linux will use it without question. Be careful when you do that because it can cause some very hard to find problems.

ARP and ND

In order to function all hosts need a neighbor table and a routing table. This section introduces the commands in Linux that can view and alter those tables. You can view the neighbor table with the following command.

ip neigh


You will need to be root to run the latter two commands. I strongly suggest avoiding them unless you’re sure of what you’re doing. Altering the routing table is often required when you want to manually establish a Linux computer on the network. You can display the routing table with either of the two commands:

ip route  
ip -6 route

You can use those commands to determine what (if any) default gateway you have set. If you need to establish a default gateway use the following commands:

ip route add default via <ipv4-address>
ip -6 route add default via <ipv6-address> dev <device>


ip route add default via
ip -6 route add default via fe80::f831:1 dev ens192

The reason that the IPv6 version needs the additional “dev” argument is that in IPv6 routers are most often reached through link-local addresses. Linux would not know which Ethernet device to send the packet to without you telling it. You can also add static routes but that’s beyond the scope of this article.


Nameservers are configured using the file /etc/resolv.conf. The file is almost as old as Unix and has a very simple format. Here’s an example:


The file tells Linux where to find nameservers and what domain to search when a user enters a hostname without a domain name (e.g. opus instead of On Ubuntu the file also comes with this warning:


On modern Linuxes DNS lookups are handled by Systemd. Look closely at /etc/resolv.conf and you’ll see that the loopback address is used. If you want to determine what DNS servers your VM uses you have to issue this command:

$ systemd-resolve --status

Network Status

When debugging it’s important to know what network connections are currently being maintained by your computer. This can help you spot configuration problems quickly and painlessly. The ss command is a Swiss Army knife command that will tell you almost anything you want to know about Linux’s network. We won’t use all of its functionality in class but it’s important to know these formulations of the command:

Shows the current TCP connections:

ss -ntp

Shows what servers are listening for INBOUND connections on TCP (remember this!):

ss -lntp

Shows what programs have UDP sockets open:

ss -nup

Shows what programs have listening UDP sockets open:

ss -lnup

I expect you to have these commands committed to memory! A good admin should know them by heart.