Date: Wed, 2 Aug 2017 19:07:34 -0300 From: Mario Lobo <lobo@bsd.com.br> To: freebsd-questions@freebsd.org Subject: Re: VirtualBox bridged networking stopped working after upgrading host to 11.1 RELEASE Message-ID: <20170802190734.3f95f36e@Papi> In-Reply-To: <20170802211628.1e40814f@curlew> References: <20170802211628.1e40814f@curlew>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2 Aug 2017 21:16:28 +0100 Mike Clarke <jmc-freebsd2@milibyte.co.uk> wrote: > 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: > > Starting dhclient. > 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 > interface: ............................. > > 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. > Hi; I recently upgraded from 11.0 to 11.1 FreeBSD Papi 11.1-STABLE FreeBSD 11.1-STABLE #0 r321652: Sat Jul 29 and immediately sfter, I recompiled vbox (5.1.26) and have no network issues whatsoever (bridge,NAT,whatever..) with any guest OS type. I believe you should try ports instead of packages. Maybe is a RELEASE thing? -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170802190734.3f95f36e>