{"id":63043,"date":"2022-06-22T09:42:52","date_gmt":"2022-06-22T08:42:52","guid":{"rendered":"https:\/\/www.bleuanus.nl\/?p=63043"},"modified":"2022-06-22T09:43:55","modified_gmt":"2022-06-22T08:43:55","slug":"how-to-configure-static-ip-address-on-ubuntu-20-04","status":"publish","type":"post","link":"https:\/\/www.bleuanus.nl\/index.php\/2022\/06\/22\/how-to-configure-static-ip-address-on-ubuntu-20-04\/","title":{"rendered":"How to Configure Static IP Address on Ubuntu 20.04"},"content":{"rendered":"\n

Typically, in most network configurations, the IP address is assigned dynamically by the router DHCP server. Setting a static IP address may be required in different situations, such as configuring port forwarding or running a media server<\/a> .<\/p>\n\n\n\n

Configuring Static IP address using DHCP<\/h2>\n\n\n\n

The easiest and recommended way to assign a static IP address to a device on your LAN is to configure a Static DHCP on your router. Static DHCP or DHCP reservation is a feature found on most routers which makes the DHCP server to automatically assign the same IP address to a specific network device, each time the device requests an address from the DHCP server. This works by assigning a static IP to the device\u2019s unique MAC address.<\/p>\n\n\n\n

The steps for configuring a DHCP reservation vary from router to router. Consult the vendor\u2019s documentation for more information.<\/p>\n\n\n\n

Netplan<\/h2>\n\n\n\n

Ubuntu 17.10 and later uses Netplan<\/a> as the default network management tool. The previous Ubuntu versions<\/a> were using ifconfig<\/code><\/a> and its configuration file \/etc\/network\/interfaces<\/code> to configure the network.<\/p>\n\n\n\n

Netplan configuration files are written in YAML syntax with a .yaml<\/code> file extension. To configure a network interface with Netplan, you need to create a YAML<\/a> description for the interface, and Netplan will generate the required configuration files for the chosen renderer tool.<\/p>\n\n\n\n

Netplan supports two renderers, NetworkManager and Systemd-networkd. NetworkManager is mostly used on Desktop machines, while the Systemd-networkd is used on servers without a GUI.<\/p>\n\n\n\n

Configuring Static IP address on Ubuntu Server<\/h2>\n\n\n\n

On Ubuntu 20.04, the system identifies network interfaces using \u2018predictable network interface names\u2019.<\/p>\n\n\n\n

The first step toward setting up a static IP address is identifying the name of the ethernet interface you want to configure. To do so, use the ip link<\/code><\/a> command, as shown below:<\/p>\n\n\n\n

ip link<\/code><\/pre>\n\n\n\n
The command prints a list of all the available network interfaces. In this example, the name of the interface is ens3<\/code>:<\/p>\n\n\n\n
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000\n    link\/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00\n2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000\n    link\/ether 08:00:27:6c:13:63 brd ff:ff:ff:ff:ff:ff\n<\/code><\/pre>\n\n\n\n
Netplan configuration files are stored in the \/etc\/netplan<\/code> directory. You\u2019ll probably find one or more YAML files in this directory. The name of the file may differ from setup to setup. Usually, the file is named either 01-netcfg.yaml<\/code>, 50-cloud-init.yaml<\/code>, or NN_interfaceName.yaml<\/code>, but in your system it may be different.<\/p>\n\n\n\n
If your Ubuntu cloud instance is provisioned with cloud-init, you\u2019ll need to disable it. To do so create the following file:<\/p>\n\n\n\n
sudo nano \/etc\/cloud\/cloud.cfg.d\/99-disable-network-config.cfg<\/code><\/pre>\n\n\n\n
\/etc\/cloud\/cloud.cfg.d\/99-disable-network-config.cfg<\/p>\n\n\n\n
network<\/strong>: {config<\/strong>: disabled}\n<\/code><\/pre>\n\n\n\n
Copy<\/p>\n\n\n\n
To assign a static IP address on the network interface, open the YAML configuration file with your text editor<\/a> :<\/p>\n\n\n\n
sudo nano \/etc\/netplan\/01-netcfg.yaml<\/code><\/pre>\n\n\n\n
\/etc\/netplan\/01-netcfg.yaml<\/p>\n\n\n\n
network<\/strong>:\n  version<\/strong>: 2\n  renderer<\/strong>: networkd\n  ethernets<\/strong>:\n    ens3<\/strong>:\n      dhcp4<\/strong>: yes<\/strong>\n<\/code><\/pre>\n\n\n\n
Copy<\/p>\n\n\n\n
Before changing the configuration, let\u2019s explain the code in a short.<\/p>\n\n\n\n
Each Netplan Yaml file starts with the network<\/code> key that has at least two required elements. The first required element is the version of the network configuration format, and the second one is the device type. The device type can be ethernets<\/code>, bonds<\/code>, bridges<\/code>, or vlans<\/code>.<\/p>\n\n\n\n
The configuration above also has a line that shows the renderer<\/code> type. Out of the box, if you installed Ubuntu in server mode, the renderer is configured to use networkd<\/code> as the back end.<\/p>\n\n\n\n
Under the device\u2019s type (ethernets<\/code>), you can specify one or more network interfaces. In this example, we have only one interface ens3<\/code> that is configured to obtain IP addressing from a DHCP server dhcp4: yes<\/code>.<\/p>\n\n\n\n
To assign a static IP address to ens3<\/code> interface, edit the file as follows:<\/p>\n\n\n\n
  • Set DHCP to dhcp4: no<\/code>.<\/li>
  • Specify the static IP address. Under addresses:<\/code> you can add one or more IPv4 or IPv6 IP addresses that will be assigned to the network interface.<\/li>
  • Specify the gateway.<\/li>
  • Under nameservers<\/code>, set the IP addresses of the nameservers.<\/li><\/ul>\n\n\n\n
    \/etc\/netplan\/01-netcfg.yaml<\/p>\n\n\n\n
    network<\/strong>:\n  version<\/strong>: 2\n  renderer<\/strong>: networkd\n  ethernets<\/strong>:\n    ens3<\/strong>:\n      dhcp4<\/strong>: no<\/strong>\n      addresses<\/strong>:\n        - 192.168.121.221\/24\n      gateway4<\/strong>: 192.168.121.1\n      nameservers<\/strong>:\n          addresses<\/strong>: [8.8.8.8, 1.1.1.1]<\/code><\/pre>\n\n\n\n
    Copy<\/p>\n\n\n\n
    When editing Yaml files, make sure you follow the YAML code indent standards. If the syntax is not correct, the changes will not be applied.<\/p>\n\n\n\n
    Once done, save the file and apply the changes by running the following command:<\/p>\n\n\n\n
    sudo netplan apply<\/code><\/pre>\n\n\n\n
    Verify the changes by typing:<\/p>\n\n\n\n
    ip addr show dev ens3<\/code><\/pre>\n\n\n\n
    2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000\n    link\/ether 08:00:27:6c:13:63 brd ff:ff:ff:ff:ff:ff\n    inet 192.168.121.221\/24 brd 192.168.121.255 scope global dynamic ens3\n       valid_lft 3575sec preferred_lft 3575sec\n    inet6 fe80::5054:ff:feb0:f500\/64 scope link \n       valid_lft forever preferred_lft forever\n<\/code><\/pre>\n\n\n\n
    That\u2019s it! You have assigned a static IP to your Ubuntu server.<\/p>\n\n\n\n
    <\/p>\n","protected":false},"excerpt":{"rendered":"
    Typically, in most network configurations, the IP address is assigned dynamically by the router DHCP server. Setting a static IP address may be required in different situations, such as configuring port forwarding or running a media server . Configuring Static IP address using DHCP The easiest and recommended way to assign a static IP address to a […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[10],"class_list":["post-63043","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-dhcp"],"_links":{"self":[{"href":"https:\/\/www.bleuanus.nl\/index.php\/wp-json\/wp\/v2\/posts\/63043","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.bleuanus.nl\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bleuanus.nl\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bleuanus.nl\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bleuanus.nl\/index.php\/wp-json\/wp\/v2\/comments?post=63043"}],"version-history":[{"count":1,"href":"https:\/\/www.bleuanus.nl\/index.php\/wp-json\/wp\/v2\/posts\/63043\/revisions"}],"predecessor-version":[{"id":63044,"href":"https:\/\/www.bleuanus.nl\/index.php\/wp-json\/wp\/v2\/posts\/63043\/revisions\/63044"}],"wp:attachment":[{"href":"https:\/\/www.bleuanus.nl\/index.php\/wp-json\/wp\/v2\/media?parent=63043"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bleuanus.nl\/index.php\/wp-json\/wp\/v2\/categories?post=63043"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bleuanus.nl\/index.php\/wp-json\/wp\/v2\/tags?post=63043"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}