Ticket #5652 (new defect)
Bridge network driver breaks host network DHCP
|Reported by:||rmoore2@…||Owned by:|
Installing VirtualBox with the bridge network driver installed prevents the host machine from getting DHCP responses. However, this issue only comes up after I reboot the host computer. Here are the steps:
- Install VirtualBox. Install completes successfully. VMs run properly and can access the network. Host networking works properly. I can release my DHCP lease and acquire a new one successfully.
- Reboot the host computer. Host is now unable to get DHCP responses and thus the IPv4 stack is not configured properly. Interestingly, IPv6 is working properly. The host is able to automatically configure its IPv6 address.
- Uninstall VirtualBox. As soon as VB is uninstalled, the host gets the DHCP response and IPv4 works again.
I've had this issue since VB 3.0.10 at least. I did not have the issue in 3.0.2. I didn't install any versions between them.
Host is running Windows 7 Ultimate 64-bit. It is an upgrade from Vista Ultimate 64-bit. I had the same issue in Vista as well. Several guests including Gentoo Linux and FreeBSD. Although it doesn't appear to be a guest issue.
If I don't install the Bridge Network driver, I don't see the DHCP problem. I did have Juniper Networks VPN installed. I un-installed it, but it didn't help the problem. I don't know if the un-install left any lingering drivers behind though.
I see from the DHCP server logs that the server is getting the DHCP query and is sending a response. But the Windows box is clearly not getting the response. Including 'ipconfig' output.