We've just installed an Ubuntu 17.10 server, and during the installation, it was assigned the IP address
We've now reserved the IP address
192.168.50.107 on the DHCP server.
netplan configuration was a surprise and, in my opinion,
/etc/network/interfaces made a lot more sense to do.
Every time the server reboots, it sets the IP address to
192.168.50.84, and it doesn't seem to ask the DHCP for an IP address.
If we execute:
sudo dhclient -r; sudo dhclient
The server gets the intended IP address (
192.168.50.107) from the DHCP.
So, what is wrong with
netplan? Why doesn't it ask for the IP address on boot or a network restart?
On every boot we get this line in the logs:
Mar 6 18:48:08 blues-web-proxy systemd-networkd: eth0: DHCPv4 address 192.168.50.84/24 via 192.168.50.140
Thanks for the replies.
We didn't do any configuration, the installation process only asked if it needed to use a proxy server or not - replied no.
# This file describes the network interfaces available on your system # For more information, see netplan(5). network: version: 2 renderer: networkd ethernets: eth0: dhcp4: yes
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # Generated by debian-installer. # The loopback interface auto lo iface lo inet loopback
127.0.0.1 localhost 127.0.1.1 blues-web-proxy.bluescreen.local blues-web-proxy # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters