I am using a virtual machine within virtual box 5.2.18 within Ubuntu 18.04.2. I have two network adapters, one is the default nat (10.0.2.0/24) and the other is a host-only adapter, which means it can only communicate with other virtual machines within the same subnet (in my case 192.168.99.1/24; dhcp server: 192.168.99.100; dhcp pool .101-.254).
I've removed the cloud-init package, I've also removed the cloud network config in /etc/netplan and I've created the following file in /etc/netplan/config.yml:
Code:
network:
renderer: networkd
version: 2
ethernets:
enp0s3:
dhcp4: yes
enp0s8:
dhcp4: yes
The problem is that during the booting process, I get this message:
Code:
A start job is running for Wait for Network to be Configured
which lasts around 2 minutes.
Everything works just fine when the system has booted, I have access to the internet, although I do get a message that it failed to connect to
https://changelogs.ubuntu.com and that I should check my internet connection.
Related messages found in syslog:
Code:
[Tue Feb 26 14:08:00 2019] e1000 0000:00:08.0 enp0s8: renamed from eth1
[Tue Feb 26 14:08:00 2019] e1000 0000:00:03.0 enp0s3: renamed from eth0
Feb 26 14:08:07 reverseproxy kernel: [ 7.504798] IPv6: ADDRCONF(NETDEV_UP): enp0s8: link is not ready
Feb 26 14:08:07 reverseproxy kernel: [ 7.515006] e1000: enp0s8 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Feb 26 14:08:07 reverseproxy kernel: [ 7.515527] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s8: link becomes ready
Feb 26 14:08:07 reverseproxy kernel: [ 7.523682] IPv6: ADDRCONF(NETDEV_UP): enp0s3: link is not ready
Feb 26 14:08:07 reverseproxy kernel: [ 7.532122] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Feb 26 14:08:07 reverseproxy kernel: [ 7.537654] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s3: link becomes ready
Feb 26 14:08:07 reverseproxy systemd-networkd[666]: enp0s3: Link is not managed by us
Feb 26 14:08:07 reverseproxy systemd-networkd[666]: lo: Link is not managed by us
Feb 26 14:08:07 reverseproxy systemd-networkd[666]: enp0s8: IPv6 successfully enabled
Feb 26 14:08:07 reverseproxy systemd[1]: Starting Network Name Resolution...
Feb 26 14:08:07 reverseproxy systemd[1]: Starting Wait for Network to be Configured...
Feb 26 14:08:07 reverseproxy systemd-networkd[666]: lo: Link is not managed by us
Feb 26 14:08:07 reverseproxy systemd-networkd[666]: enp0s3: IPv6 successfully enabled
Feb 26 14:08:07 reverseproxy systemd-networkd[666]: enp0s8: Gained carrier
Feb 26 14:08:07 reverseproxy systemd-networkd[666]: enp0s8: DHCPv4 address 192.168.99.101/24
Feb 26 14:08:07 reverseproxy systemd-networkd[666]: enp0s3: Gained carrier
Feb 26 14:08:07 reverseproxy systemd-networkd[666]: enp0s3: DHCPv4 address 10.0.2.4/24 via 10.0.2.2
Feb 26 14:08:07 reverseproxy systemd-networkd[666]: enp0s8: DHCP: No routes received from DHCP server: No data available
Feb 26 14:08:08 reverseproxy systemd-networkd[666]: enp0s8: Gained IPv6LL
Feb 26 14:08:09 reverseproxy systemd-networkd[666]: enp0s3: Gained IPv6LL
Feb 26 14:08:09 reverseproxy systemd-networkd[666]: enp0s3: Configured
Feb 26 14:08:09 reverseproxy systemd-networkd-wait-online[690]: managing: enp0s3
Feb 26 14:08:09 reverseproxy systemd-networkd-wait-online[690]: ignoring: lo
