[Fixed] Bridged networking 5.2.0 issues (#17186)

[chinacjt]

add some information:
hosts: windows 7 SP1 with latest Server packs
client:(windows server 2003 SP2 OR windows 10 Pro 1703)
My wireless cards :intel centrino(R) Advanced-N 6205
Previously: Working with 5.1.30
Other programs: chrome 62.0.3202.62

[ci4ic4]

In my case the behaviour is similar on all the guests, but I test it first with NetBSD-current amd64 and FreeBSD 11.1. There are also some CentOS, Fedora, Ubuntu, Windows/XP, Windows Server/Next clients, together with internal firewalls running OpenBSD, OpnSense and OpenWRT. Most use the standard Intel 82540EM workstation card emulation, but some of the clients, mainly the BSDs, use virtio-net.

I think it is unlikely the client matters in this case.

I can also say that from within the guest tcpdump shows the broadcast traffic on the wireless network, so it is not a complete break. It behaves very similarly to a problem I am having running Xen 4.6 on a NetBSD-current DOM0, whereby if the interface in use is wired, it works fine; on (at least some) wireless interfaces, I see only broadcast traffic.

[mx325]

What's your host version? Win10 64bit Version 10.0.14393 Build 14393

What's your guest version? Win7 32bit version 6.1.7601 Service Pack 1 Build 7601

What's your VirtualBox version? 5.2.0 r118431 (Qt5.6.2)

What method are you using to connect? Wired or wireless (WiFi)? Can you try with both? Wired works, wireless does not

Did this setup used to work previously? Does it work if you downgrade your VirtualBox? To which version? Worked on 5.1.28 r117968 (Qt5.6.2). When downgraded back to 5.1.28 r117968 (Qt5.6.2) it works on wireless again.

Do you have any 3rd party apps installed? McAfee enterprise 8.8.0.1804

[socratis]

Thank you @ci4ic4, @chinacjt and @mx325 for adding your information.

Funny thing? There was not a ticket open for this, so I went ahead and created a new one; #17186: Bridged over WiFi networking: no IP assigned on Win hosts, with a variety of guests/WiFi cards.

I pointed the ticket to this discussion and this discussion to the ticket. I'm going to be updating both the thread and the ticket with any changes. I will let you know if the developers prefer the list of affected users/setups here or in the ticket.

[yefkov]

Me too.

yefkov

• 1. Host: Windows 10 Home 1709 Build 16299.19 x64
  2. Guest: a) Windows XP Home (SP3, build 2600) x86, b) Windows 7 Pro (SP1, build 7601) x64
  3. VirtualBox: 5.2.0
  4. Network: Wireless fails with 5.2.0, works with 5.1.28. Wireless use DHCP, not static IPs. GUEST can connect with the HOST only. Wireless card: Intel(R) Dual Band Wireless-AC 7265
  5. Previously: Working with 5.1.28 and 5.1.30
  6. Other programs: Dr.Web antivirus

I have just downgraded back to 5.1.30. Bridged networking with wireless adapter is working again.

[socratis]

Thanks @yefkov, I added your info as well...

I have a couple of questions:

1. What's the IP that your guest gets, if it gets one? Mine for example gets an IP in the 169.254.x.x range, which is a self assigned IP. That's a clear indication of a communication failure.
2. Some of you are saying that you can connect to the HOST. Can you please explain how is that possible? What do you mean by that? I really hope you don't mean the Shared Folders.

[yefkov]

Hi, socratis.
Sorry for ambiguity. My LAN is 192.168.0.0/24. Guests are getting IP address through APIPA and thus cannot communicate with the host. But if I set in guest OS static IP address from the range of my LAN the guest can ping the host. But ONLY host. The rest of the network is not available for guest and vice versa.

[nelsonhf]

Same issue here

Host: Windows 8.1 Home Single Language 64bit (6.3.9600)
Guests: Win10 Pro v1703 64bit, Ubuntu 17.04 64bit, Ubuntu Server 14.04.5 32bit, Endian Firewall 3.2.4 64bit
VirtualBox: 5.2.0 r118431
Network: Wireless @ Qualcomm Atheros AR9285 Wireless Network Adapter. Guests with static IP can ping only the host.
Previously: Working with 5.1.30
Other programs: Comodo Internet Security Premium 10 (10.0.1.6294)

If the guest is configured with DHCP, no IP is received from the DHCP server. If the guest is configured with a static IP, it can ping the host but not the DHCP server or any other IP in the host wireless network. I have another VirtualBox 5.2.0 host running on a desktop Windows 7 SP1 Pro but with wired network and no problems whatsover.

Going back to 5.1.30 for now...

Regards,
Nelson.

[easermatti]

Same here.
Host: Windows 10 Pro (x64) version 10.0.16299 Build 16299
Guest: Linux Centos 6.9 x64
Virtualbox: 5.2.0 118431
Network: Fails with Intel Centrino Wireless-N 2230 -adapter, driver 15.18.0.1, Provider Intel Corporation. Works with Realtek PCIe GBE Family Controller. Static ip.
Other: F-Secure SAFE. Turning off protection didn't help

[Lees]

Hello,

I reinstalled VirtualBox-5.1.28-117968-Win.exe after the new version failed to connect to the Internet. The old version works fine.

Host: Windows 7 Ultimate
Guest: Linux Ubuntu 16.04
Virtualbox: VirtualBox-5.2.0-118431-Win.exe
Network: Broadcom 802.11n wireless adapter
Static ip.

Others:
- Guest can ping to host and vice versa.
- I followed the instruction in this thread, failed.
- Tried to tweak the settings in bridged adapter and NAT, played with diff IP addresses. Tried many settings, failed.
- Uninstalled, then re-installed same version, tweaked again. Failed again.
- Gave up after 6 hours trying.

[fyah]

Hello,

Exact same here.

Host: Win7-64bit (SP1, build 7601)
Guest: Win7-64bit (SP1, build 7601)
VirtualBox: 5.2.0 r118431, 5.1.30 r118389, 5.1.28 r117968
Network: Wired works, always worked in the past. Wireless fails with 5.2.0, works with 5.1.30 and 5.1.28. Both wired and wireless use DHCP, not static IPs.
Previously: Working since VirtualBox 4.0.0, all the intermediate versions and several development/beta builds. Nothing really has changed over the years, except the addition of the Win10-64 host.
Other programs: Symantec Endpoint protection

Thanks !

[Wouaf]

Hello,

Same problem for me.

Host: Win10 Enterprise 64bit 1703 / 15063.674
Guest: Win10 Enterprise 64bit 1703 / 15063.674
VirtualBox: 5.2.0 r118431
Network: Wireless Intel(R) Dual Band Wireless-N 7265
Previously: Working
Other programs: Windows Defender

Thanks !

[hi5dao]

windows 10 10.0.16299.19

virtual box 5.2.0

Bridged networking not working ,,,,,change virtual box 5.1.30,,,ok!



today，I have to install vmvare to check problem,,,,,,,,,,,,,,all day!

[hi5dao]

Hello,

Same problem for me.

Host: Win10 Enterprise 64bit 1703 / 15063.674
Guest: Win10 Enterprise 64bit 1703 / 15063.674
VirtualBox: 5.2.0 r118431
Network: Wireless Intel(R) Dual Band Wireless-N 7265
Previously: Working
Other programs: Windows Defender

Thanks !

change 5.1.30 !!!

[aleksey-vb]

This is a regression caused by introduction of HostNetworkInterface::Wireless flag. The fix will be included into the next maintenance release. Build 118475 (or more recent) is available for testing at https://www.virtualbox.org/wiki/Testbuilds in 'Development snapshots' section. Sorry for inconveniences.