[Fixed] Bridged networking 5.2.0 issues (#17186)

[socratis]

@MasterAnt,
This doesn't sound right. First of all, 5.1.18 is way too old for the latest Win10 update, so, let's get this out of the discussion. You need to update.

Second, did you uninstall VirtualBox before re-installing it while doing all the version testing?

Third, did you install VirtualBox with the Run-as-Administrator method? Please take a look at this post from this thread for the "proper" way of installing VirtualBox.

Fourth, do you have an issue specifically with a Bridged to WiFi adapter? This is what this thread and the ticket are dealing with, not general networking problems.

Fifth, how did you test your internet connectivity? Did you get an IP address? Which one? Can you run "ping 8.8.8.8" successfully? Can you run "ping google.com" successfully?

[vdave]

Just confirming (as one of the reporters) that with build 118475, bridged network via a USB Wifi adapter works for me, the guest now can access the Internet.

[socratis]

A similar issue affecting Windows hosts when there is no options selected in the WiFi card properties, except the "VirtualBox NDIS6 Bridged Networking Driver", has been split and got it's own topic: 5.2.0 Bridged fails w/ only VBox Bridged Driver selected.

[Jinganglishi]

Dear Support, I am facing the same issue.

Please find relevant information below:

Host: Win10 64bit Version 10.0.15063 Build 15063
Guests: Win7 64bit version 6.1.7601 Service Pack 1 Build 7601, Win10 64 bit version 10.0.15063 Build 15063, Win Server 64bit 2008 R2 Service Pack 1 version 6.1.7601 Build 7601
VirtualBox: 5.2.0 r118431 (Qt5.6.2)
Network: Bridged network: Wired works, wireless does not
Previously: Worked on 5.1.28 r117968 (Qt5.6.2). When downgraded back to 5.1.30 r118389 (Qt5.6.2) wireless works again.
Other programs: respectively Avast 17.7.2314 Build 17.7.3660.226, Windows Defender Suite engine version 1.1.14306.0, none

[Ludwik]

Problem solved only after to downgrade to VirtualBox-5.1.30-118389!

[BONappetite]

I have the exact same issue

Host: Win10-64bit (SP1, build 1709)
Guest: Win10-64bit (SP1, build 1709)
VirtualBox: 5.2.0 r118431(Qt5.6.2)
Network: Wireless, fails with bridged and works with NAT
Previously: Worked on VirtualBox 5.1.30
Other programs: Pretty much as plain as they come.

[rickygai]

rickygai

Host: Windows 10 Pro x64 [Version 10.0.15063]
Guest: a) Windows 7 Pro N x64 SP1 [Version 6.1.7601], b) Windows Server 2016 x64 [Version 10.0.14393]
VirtualBox: 5.1.30, 5.2.0, 5.2.1 (r119001)
Network: Host computer was using WIFI connection at DLINK DIR-510L router (home) and TP-LINK-MR3420-3G4G router (office)
Previously: Working with 5.1.28 and 5.1.30
Other programs: Windows Defender ( Windows default )

REMARK:

From internet survey, DLINK DIR-510L router not supporting wireless bridge.
Meanwhile, TP-LINK-MR3420 did support wireless bridge.

I needs to double confirm if physical router wireless bridge features does affects Virtualbox bridged adapter function.

Please advise.

[fyah]

Is it solved in 5.2.2 ?
It is not clearly mentioned in the changelog....
https://www.virtualbox.org/wiki/Changelog#2

[socratis]

@fyah
Yes it's fixed, since the intermediate builds, as you can clearly see at the beginning of this thread. Not every fix gets mentioned in the Changelog necessarily, although in this case I think that they should have definitely mention it. That was a major one and if someone relies solely on the Changelog, this one could have been missed...

[BoogieBug]

I'm running 5.2.2 and it seem the problem still there.

On the first boot after installing the guest OS, it works perfectly. I can get the address from DHCP and
the everything work smoothly. However, after a few hours, the bridged network cannot send or receive
any data from/to the outside world.

The work around is shutting down the guest OS and change the Adapter Type of the guest OS' in the
network configuration panel to 'other' (what every type except the current one) and restart the guest OS.

This might be not a practical approach since I have to reboot the guest after few hours of usage, but it
let me continue my work.

[socratis]

On the first boot after installing the guest OS, it works perfectly.

Then it's not the same bug/issue. Since the original problem was clearly identified and fixed, I'm going to lock this thread. I don't want it to become a honeypot for everything Bridged-over-WiFi related.

@BoogieBug
Please open a new thread, clearly describing your host, guest and VirtualBox version. Use the complete version numbers (including the build numbers) to identify your software:

• "OSX" isn't enough, "OSX 10.9.5 build 13f1911" is much better.
• "Win10" isn't enough, "Win10 1607, build 14393.969" is much better.
• "Ubuntu" isn't enough, "Ubuntu 16.04, 4.4.0-59-generic #80-Ubuntu SMP" is much better.
• "The latest VirtualBox" isn't enough, "VirtualBox 5.1.22 r115126" is much better.

And a complete log from a full run of the VM, from start to shutdown:

• Start the VM from cold-boot (not from a paused or saved state) / Observe error / Shutdown the VM.
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response (see the "Upload attachment" tab below the reply form).

But please do it in a new thread.