[Fixed] Bridged networking 5.2.0 issues (#17186)

Discussions related to using VirtualBox on Windows hosts.

[Fixed] Bridged networking 5.2.0 issues (#17186)

Postby mgmcomm » 19. Oct 2017, 00:29


Related ticket #17186: "Bridged over WiFi networking: no IP assigned on Win hosts, with a variety of guests/WiFi cards". CLOSED AS FIXED.

Updating to 5.2.1 r118475 (or more recent) from the test builds (https://www.virtualbox.org/wiki/Testbuilds) fixes the problem.


I was using VirtualBox 5.1.28 before and was successfully using bridged adaptor and DHCP on my home router to access the internet on a Windows 10 host running a FreeBSD 11 guest. Today when I restarted Virtual box I got a message stating an upgrade was available so I downloaded and installed and rebooted the host. Now bridged adaptor setting no longer works but other modes like NAT do work. I have tried several troubleshooting options such as different options for promiscuous mode and completely disabling the built-in windows firewall program. Right now I seem unable to get the bridged adapter to connect to the internet. Freebsd reports seeing the cable connected but no traffic is allowed to pass through.

I could not find any other posts related this issue in regards to this version of the software which is probably due to this release only just coming out. I do not have the time or patience to troubleshoot as I need to get back on my previous project so I downgraded back to 5.1.28 and my bridged setting works again. This post is an FYI that there might be a bug and my to detail experience and steps I took to solve it in case this information might be of use to others who have the same issue. I will try upgrading again on release beyond 5.2.0.
Last edited by socratis on 25. Oct 2017, 00:02, edited 1 time in total.
Reason: Marked as [Fixed].
mgmcomm
 
Posts: 1
Joined: 18. Oct 2017, 23:55

Re: bridged networking 5.2.0 issues

Postby Martin » 19. Oct 2017, 08:39

Did you install the update using "run as administrator"?
Martin
Volunteer
 
Posts: 2144
Joined: 30. May 2007, 18:05
Primary OS: Fedora other
VBox Version: PUEL
Guest OSses: XP, Win7, Linux, OS/2

Re: bridged networking 5.2.0 issues

Postby Calvin Liu » 19. Oct 2017, 10:30

I also uncountered the same problem,only using version 5.1.30!!!
Calvin Liu
 
Posts: 1
Joined: 19. Oct 2017, 10:28

Re: bridged networking 5.2.0 issues

Postby chinacjt » 19. Oct 2017, 11:52

I have same problem.
chinacjt
 
Posts: 16
Joined: 22. Aug 2012, 07:38

Re: bridged networking 5.2.0 issues

Postby N0YB » 19. Oct 2017, 12:27

Ditto

VirtualBox 5.2.0 + Extensions Pack (installed and run from actual administrator account)

Host:
Windows 8.1 Pro
Broadcom 802.11n Network Adapter
VirtualBox NDIS6 Bridged Networking Driver

Guest:
FreeBSD 11.1 (64-bit)
Bridged Adapter
Broadcom 802.11n Network Adapter
DHCP client

Rolled back to 5.1.28 where it works fine.
N0YB
 
Posts: 37
Joined: 20. Sep 2012, 18:55

Re: bridged networking 5.2.0 issues

Postby socratis » 19. Oct 2017, 17:52

Please follow the steps below. If there is a failure, please state exactly which step failed:

  1. Uninstall VirtualBox. Your VMs are going to be untouched. Reboot.

  2. You may want to clean up your registry and/or filesystem at this point. CCleaner is a freeware utility that could help you. Mind the installation, it comes with "offers" from 3rd parties, known as "bundleware". Also, check out Device Cleanup program that helps you to remove any unused devices from your computer.

  3. Download (if you haven't already) the latest VirtualBox and its matching ExtPack. Store them in a common location, i.e. not on "Desktop", or "Documents", but to "Public/Downloads" for example.

  4. Locate the downloaded file in Windows Explorer. Right-click on the installer and select "Run-as-Administrator", even if you are the administrator. At the end of the installation, choose to "Start Oracle VM VirtualBox". Do not worry if your VMs do not show up.

  5. If you're going to install the ExtPack, go to File » Preferences » Extensions. Click on the icon with the orange, down-pointing arrow on the right. Select the ExtPack from the previous steps.

  6. Quit VirtualBox. Re-start VirtualBox as you would normally, i.e. from the Desktop shortcut or the Start menu.

  7. Update the Guest Additions (GAs) in your guest(s), if the GAs are available for a specific guest.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 22095
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: bridged networking 5.2.0 issues

Postby vdbvdb » 19. Oct 2017, 22:47

I have same problem after Windows update with Virtual Box 5.1.28, Virtual Box 5.2.0-RC1 and 5.2.0 (release).
All steps listed above already executed.

Host: Windows 10 Pro 1703 Build 15063.674 x64
Network: 192.168.1.130/24 @ Realtek RTL8723AE Wireless LAN 802.11n PCI-E NIC

Guest: FreeBSD 11.1 amd64
Network: bridged on RTL8723AE , 192.168.1.131/24

After winUpdate the GUEST can connect within the master HOST only. No one from 192.168.1.1/24 can connect to the GUEST and the GUEST cannot connect to 192.168.1.1/24 except master HOST.
But as I can see in tcpdump and wireshark : all packets are successfully forwarded into the guest, but nothing forwarded from guest to network.

Maybe you want some tcpdump logs or something else?
Sorry for my English.

P.S. this problem affects only with wireless NICs.
There is no problems with Ethernet NICs.
vdbvdb
 
Posts: 2
Joined: 19. Oct 2017, 21:54

Re: bridged networking 5.2.0 issues

Postby ci4ic4 » 19. Oct 2017, 23:45

Another "Me too". I tried carefully the suggestions above - which were obvious anyway - and the bridged networking did not work using 5.2. At the end I reinstalled 5.1.30 and all was OK.

By the way I posted the same on a different thread in the same forum and my message disappeared.

This is on an HP Envy 17 laptop, which has been running VirtualBox since the day it was purchased more than 16 months ago.
ci4ic4
 
Posts: 18
Joined: 16. Jun 2009, 12:55
Primary OS: OpenSolaris 11
VBox Version: PUEL
Guest OSses: Windows Server 2008 R2, Windows 7, OpenSolaris

Re: bridged networking 5.2.0 issues

Postby vdave » 20. Oct 2017, 00:03

Just another +1. With VirtualBox 5.2.0 on host Windows 10 17017 (Fast ring pre-release), the guest system (Ubuntu 17.04, 64-bit) could only connect to the host, but nothing else (not even my router's config page at 192.168.1.1). I could not find any related logs in either VirtualBox's logs or the Windows event log, it seems that packets disappear inside VirtualBox's "virtual" network adapter on the host. Switching back to 5.1.28 solved the issue immediately.
Additional info: The VM was configured with bridged networking targeting a Linksys WUSB6300 USB Wifi adapter (that's the active network connection for the host machine).
vdave
 
Posts: 2
Joined: 19. Oct 2017, 23:59

Re: bridged networking 5.2.0 issues

Postby vdbvdb » 20. Oct 2017, 00:12

Guys! Please let's specify the NIC type (WiFi/FDDI/ethernet/token-ring etc) and Windows build.
vdbvdb
 
Posts: 2
Joined: 19. Oct 2017, 21:54

Re: bridged networking 5.2.0 issues

Postby ci4ic4 » 20. Oct 2017, 01:10

The relevant bits from systeminfo follow:
---
Code: Select all   Expand viewCollapse view
OS Name:                   Microsoft Windows 10 Home
OS Version:                10.0.16299 N/A Build 16299
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Organization:   HP
Original Install Date:     17/10/2017, 19:27:34
System Boot Time:          19/10/2017, 21:04:03
System Manufacturer:       HP
System Model:              HP ENVY Notebook
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 94 Stepping 3 GenuineIntel ~2601 Mhz
BIOS Version:              Insyde F.36, 25/07/2016
Windows Directory:         C:\WINDOWS
System Directory:          C:\WINDOWS\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             en-gb;English (United Kingdom)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC+00:00) Dublin, Edinburgh, Lisbon, London
Total Physical Memory:     16,221 MB
Available Physical Memory: 6,565 MB
Virtual Memory: Max Size:  21,085 MB
Virtual Memory: Available: 8,934 MB
Virtual Memory: In Use:    12,151 MB
Page File Location(s):     C:\pagefile.sys
Hotfix(s):                 2 Hotfix(s) Installed.
                           [01]: KB4049179
                           [02]: KB4043961
Network Card(s):           4 NIC(s) Installed.
                           [01]: VirtualBox Host-Only Ethernet Adapter
                                 Connection Name: VirtualBox Host-Only Network
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 192.168.56.1
                                 [02]: fe80::4122:b623:442b:45d9
                           [02]: Intel(R) Dual Band Wireless-AC 7265
                                 Connection Name: WiFi
                                 DHCP Enabled:    Yes
                                 DHCP Server:     192.168.0.1
                                 IP address(es)
                                 [01]: 192.168.0.35
                                 [02]: fe80::c9bc:aa3:3a5:b78e
                           [03]: Realtek PCIe GBE Family Controller
                                 Connection Name: Ethernet 2
                                 Status:          Media disconnected
                           [04]: Bluetooth Device (Personal Area Network)
                                 Connection Name: Bluetooth Network Connection
                                 Status:          Media disconnected
Hyper-V Requirements:      VM Monitor Mode Extensions: Yes
                           Virtualization Enabled In Firmware: Yes
                           Second Level Address Translation: Yes
                           Data Execution Prevention Available: Yes
ci4ic4
 
Posts: 18
Joined: 16. Jun 2009, 12:55
Primary OS: OpenSolaris 11
VBox Version: PUEL
Guest OSses: Windows Server 2008 R2, Windows 7, OpenSolaris

Re: bridged networking 5.2.0 issues

Postby BillG » 20. Oct 2017, 05:56

vdbvdb has narrowed it down to wireless network cards. I certainly don't have any problems with Ethernet NICs. Let's now try to see whether it is all wireless cards or only some of them.

Instead of "me too" please supply Windows build and wireless network card type as he suggested.
Bill
BillG
Volunteer
 
Posts: 4054
Joined: 19. Sep 2009, 04:44
Location: Sydney, Australia
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows 7,8,Server

Re: bridged networking 5.2.0 issues

Postby socratis » 20. Oct 2017, 07:01

First of all, I've got to say that I tried it on 3 hosts; Win7-32bit (SP1, build 7601), Win7-64bit (SP1, build 7601) and Win10-64bit (1607, build 14393.1198). Actually it's the same computer doing a triple boot. The guest in all the cases was a WinXP-32bit (SP3, build 2600). I had no problems getting an IP and a complete network connection with a wired connection, which means that the filters are working (at least in my three hosts). When I refer to a "complete network connection", the tests to establish that were:
  1. Get a valid IP, verify it with the command "ipconfig",
  2. Ping the default gateway,
  3. Success with the command "ping 8.8.8.8" and
  4. Success with the command "ping google.com".
Another thing to keep in mind is the title of the thread: "bridged networking 5.2.0 issues". If you have problems with another version, do NOT dump it here. Either find an appropriate thread, or start a new one. If this becomes widespread, messages that do NOT deal with 5.2.0 explicitly, will end up in the trashcan. With no undelete and no warning.

Let's try and find the common denominator. So, I'll need all of you to revisit this thread and fill in the following information:

  1. What's your host version? Full and complete details please."Win10" isn't enough, "Win10 1607, build 14393.969" is much better.

  2. What's your guest version? Full and complete details please. "Ubuntu" isn't enough, "Ubuntu 16.04, 4.4.0-59-generic #80-Ubuntu SMP" is much better.

  3. What's your VirtualBox version? Full and complete details please. "The latest" is not enough, "VirtualBox 5.2.0 r118431 (Qt5.6.3)" is much better.

  4. What method are you using to connect? Wired or wireless (WiFi)? Can you try with both?

  5. Did this setup used to work previously? Does it work if you downgrade your VirtualBox? To which version?

  6. Do you have any 3rd party apps installed? Firewalls, antivirus, protection suites, monitoring, throttling, or any low level programs installed? List them.

I'll collect what has been posted so far and update this post, which I will be updating as more information becomes available. I'll start here with my setup and you can use this as a template:

socratis
  1. Host: a) Win7-32bit (SP1, build 7601), b) Win7-64bit (SP1, build 7601) and c) Win10-64bit (1607, build 14393.1198)
  2. Guest: WinXP-32bit (SP3, build 2600)
  3. VirtualBox: 5.2.0 r118431, 5.1.30 r118389, 5.1.28 r117968
  4. 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.
  5. 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.
  6. Other programs: Windows Defender, the built-in Windows antivirus only, default firewall settings (just enabled it and forgot about it). No additional services/programs/drivers. Pretty much as plain as they come.

N0YB
  1. Host: Windows 8.1 Pro
  2. Guest: FreeBSD 11.1 (64-bit)
  3. VirtualBox: 5.2.0 r118431
  4. Network: Wireless with DHCP
  5. Previously: Working with 5.1.28
  6. Other programs: ???

vdbvdb
  1. Host: Windows 10 Pro 1703 Build 15063.674 x64
  2. Guest: FreeBSD 11.1 amd64
  3. VirtualBox: 5.1.28, 5.2.0-RC1 and 5.2.0
  4. Network: Wireless. GUEST can connect with the HOST only
  5. Previously: Working with 5.1.28
  6. Other programs: ???

vdave
  1. Host: Windows 10 17017 (Fast ring pre-release)
  2. Guest: Ubuntu 17.04, 64-bit
  3. VirtualBox: 5.2.0
  4. Network: Wireless. GUEST can connect with the HOST only
  5. Previously: ???
  6. Other programs: ???

ci4ic4
  1. Host: Microsoft Windows 10 Home 10.0.16299 N/A Build 16299
  2. Guest: NetBSD-current amd64, FreeBSD 11.1, CentOS, Fedora, Ubuntu, Windows/XP, Windows Server/Next clients, together with internal firewalls running OpenBSD, OpnSense and OpenWRT.
  3. VirtualBox: 5.2.0
  4. Network: Wireless.
  5. Previously: 5.1.30
  6. Other programs: ???

chinacjt
  1. Host: Windows 7 SP1 with latest Server packs
  2. Guest: Windows server 2003 SP2, Windows 10 Pro 1703
  3. VirtualBox: 5.2.0
  4. Network: Wireless.
  5. Previously: 5.1.30
  6. Other programs: ???

mx325
  1. Host: Win10 64bit Version 10.0.14393 Build 14393
  2. Guest: Win7 32bit version 6.1.7601 Service Pack 1 Build 7601
  3. VirtualBox: 5.2.0 r118431 (Qt5.6.2)
  4. Network: Wired works, wireless does not
  5. Previously: 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.
  6. Other programs: McAfee enterprise 8.8.0.1804

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
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 22095
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: bridged networking 5.2.0 issues

Postby rickygai » 20. Oct 2017, 09:45

Microsoft Windows 10 Pro x64 [Version 10.0.15063]
Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz
DDR3 16GB
NVIDIA GeForce GTX 660M

Me too encountered the same issues today on bridged network using VirtualBox 5.2.0, already do a clean uninstall and reinstall and the guest OS reported:
1. subnet mask is set to 255.255.0.0
2. IP address is not assigned by the physical router pre-configured.

Please advise.
rickygai
 
Posts: 19
Joined: 22. Apr 2009, 05:00
Primary OS: MS Windows other
VBox Version: OSE other
Guest OSses: Microsoft Windows

Re: bridged networking 5.2.0 issues

Postby socratis » 20. Oct 2017, 10:54

Did you even read the thread? I asked for a specific list of information, not another me too. And "please advice"? Advice you for what exactly? Do you see anyone having the solution and not sharing? No you don't.

Please provide the detailed information I asked for. I'm going to edit my post (the one just above yours) and make it in bold red. Maybe someone will notice. If we don't help the developers, there's not going to be enough help...
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 22095
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Next

Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: No registered users and 40 guests