VirtualBox Bridged Adapter Not Getting IP – Fixes That Work

1. The Host Adapter Isn't Actually Bridged Properly

This is the one I see most often. You think you've selected the right physical NIC in VirtualBox's bridged settings, but it's actually hitting a virtual adapter or a disabled interface. The result? Your guest sends DHCP requests into the void.

How to check: On the host (Windows/Linux), run ipconfig /all or ip a. Look for the physical NIC that's actually connected to your router or switch. It'll have a valid IP (like 192.168.1.x) and show a gateway. That's the one you need.

Now go to the VM settings in VirtualBox: Network > Adapter 1 > Attached to: Bridged Adapter > Name. Pick that exact physical NIC. Not "Wi-Fi" if you're on Ethernet. Not "VirtualBox Host-Only Network." I've seen people pick the wrong one because both show up. Don't guess.

Why this happens

Windows 10/11 sometimes creates a "VirtualBox NDIS6 Bridged Networking Driver" filter on the wrong adapter. If you installed VirtualBox after a Windows update, the filter might bind to a hidden virtual adapter instead. Re-run the installer and choose "Repair" – that binds it correctly.

After that, restart the VM. If it still doesn't get an IP, try ipconfig /release then ipconfig /renew inside the guest. If it grabs an IP now, you're done.

2. The MAC Address Filter or Promiscuous Mode Is Blocking DHCP

This one's more subtle. VirtualBox's bridged adapter uses a unique MAC for the guest. If your physical network has port security (like MAC filtering on the switch or router), the guest's MAC won't match the host's – and DHCP gets dropped.

The fix is simple: Set the guest's MAC address to the same as the host's. In VirtualBox settings, go to Network > Adapter 1 > Advanced > MAC Address. Click the plus icon to generate a new one, or manually type the host's MAC (from ipconfig /all – Physical Address).

I don't love this approach because it can confuse the router (two devices with the same MAC). But it's a quick test. If it works, you know the issue is MAC filtering. Better solution: turn off MAC filtering on your router/switch, or add the guest's MAC to an allowed list.

Promiscuous mode gotcha

In the same Advanced tab, you'll see "Promiscuous Mode." Set it to "Allow All" for bridged adapters. Some routers refuse DHCP unless they see the VM can receive traffic from any MAC. I've had this bite me on TP-Link and Netgear consumer routers. Leave it on "Allow All" permanently for bridged VMs.

3. Windows Firewall or Antivirus Is Blocking DHCP Traffic

This one's rarer but I've seen it enough. Windows Firewall (or third-party AV like Norton, McAfee, or Bitdefender) can block DHCP – UDP ports 67 and 68 – on the VirtualBox bridge.

Quick test: Temporarily disable Windows Firewall (all profiles). Restart the VM. If it gets an IP, the firewall's the problem.

Permanent fix: Don't leave the firewall off. Instead, open an admin PowerShell and run:

New-NetFirewallRule -DisplayName "Allow VirtualBox DHCP Bridged" -Direction Inbound -Protocol UDP -LocalPort 67,68 -Action Allow
New-NetFirewallRule -DisplayName "Allow VirtualBox DHCP Bridged Out" -Direction Outbound -Protocol UDP -LocalPort 67,68 -Action Allow

Same for the outbound rule. Then re-enable the firewall. Test again.

If you've got third-party AV, check its network protection settings. Norton and Bitdefender both have a "Network Threat Protection" feature that can kill DHCP. You'll need to add an exception for the VirtualBox network adapters in the AV's settings.

Quick-Reference Summary Table

Try these in order. Nine times out of ten, the first fix does it. The third one's a pain but you'll only hit it once per machine.