Has anyone noticed issues with #vSphere Customization Specification and #Ubuntu 17.10 (GNU/Linux 4.13.0-25-generic x86_64) – Now that the network settings are located in:
/etc/netplan/01-netcfg.yaml, I’m back to manually updating IP information (Server Naming still works).
Although the traditional
/etc/network/interfaces reflects the information provided by the customization process, the host still acquires a DHCP issued address. After some digging I was able to find out that this information was no longer being referenced and is now being pulled from:
Here are the IP configuration details
# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto ens160 #iface ens160 inet dhcp iface ens160 inet static address 10.200.255.6 netmask 255.255.255.0 network 10.200.255.0 broadcast 10.0.255.255 gateway 10.200.255.1 dns-nameservers 10.200.255.1
# This file describes the network interfaces available on your system # For more information, see netplan(5). network: version: 2 renderer: networkd ethernets: ens160: dhcp4: no addresses: [10.200.255.6/24] gateway4: 10.200.255.1 nameservers: addresses: [126.96.36.199,188.8.131.52]