VirtualBox bridged networking stopped working after upgrading host to 11.1 RELEASE
jmc-freebsd2 at milibyte.co.uk
Wed Aug 2 20:22:30 UTC 2017
I've been running Windows and FreeBSD VirtualBox guests with bridged
networking without problems until I upgraded my host from 11.0 to 11.1.
None of the guest systems are able to access the network since the
upgrade. The Windows guests are not very forthcoming with useful error
messages but the FreeBSD 11.0 guest shows the following while booting:
DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
add host 127.0.0.1: gateway lo0 fib 0: route already in table
add host ::1: gateway lo0 fib 0: route already in table
add net fe80::: gateway ::1
add net ff02::: gateway ::1
add net ::ffff:0.0.0.0: gateway ::1
add net ::0.0.0.0: gateway ::1
Waiting 30s for the default route
It appears to be a problem with the virtual network interface rather
than DHCP because I've tried editing /etc/rc.conf on the FreeBSD guest
to turn off DHCP and provide an IP address and default root. When I do
this the boot messages look OK and ifconfig and netstat show that the
address and default route have been set up OK but any attempts to
access the network just time out.
The problem appears to be specific to 11.1 because when I revert to
11.0 the bridged networking works fine.
As a temporary workaround I can use networking with VirtualBox if I
switch to NAT instead of bridged but I need to find a way of going
back to using the bridged connection so I can use the "correct" IP
addresses for the guests.
More information about the freebsd-questions