From owner-freebsd-questions@freebsd.org Wed Aug 2 20:22:30 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2BBC8DB3A59 for ; Wed, 2 Aug 2017 20:22:30 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from outmx-028.london.gridhost.co.uk (outmx-028.london.gridhost.co.uk [95.142.156.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E9F42764BF for ; Wed, 2 Aug 2017 20:22:29 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from curlew.milibyte.co.uk (unknown [82.71.56.121]) (Authenticated sender: mailpool@milibyte.co.uk) by outmx-028.london.gridhost.co.uk (Postfix) with ESMTPA id 158A820C3372D for ; Wed, 2 Aug 2017 21:09:45 +0100 (BST) Received: from [192.168.1.13] (helo=curlew) by curlew.milibyte.co.uk with esmtp (Exim 4.89) (envelope-from ) id 1dd04C-0000n8-D9 for freebsd-questions@freebsd.org; Wed, 02 Aug 2017 21:16:28 +0100 Date: Wed, 2 Aug 2017 21:16:28 +0100 From: Mike Clarke To: freebsd-questions@freebsd.org Message-ID: <20170802211628.1e40814f@curlew> X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; amd64-portbld-freebsd11.0) MIME-Version: 1.0 X-SA-Exim-Connect-IP: 192.168.1.13 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on curlew.lan X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 Subject: VirtualBox bridged networking stopped working after upgrading host to 11.1 RELEASE Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on curlew.milibyte.co.uk) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Aug 2017 20:22:30 -0000 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. -- Mike Clarke