VirtualBox

Ticket #7094 (new defect)

Opened 4 years ago

Last modified 2 years ago

VirtualBox kills network connectivity if VLAN tagging enabled on Realtek NIC

Reported by: viro Owned by:
Priority: major Component: network/hostif
Version: VirtualBox 3.2.6 Keywords:
Cc: Guest type: other
Host type: Windows

Description

If VLAN tagging is enabled on the Realtek network card of a system with VirtualBox installed, and the "VirtualBox Bridged Network Driver" is bound to that network card (the default behavior), no network access is possible. The only remedy is to either disable VLAN tagging or unbind the "VirtualBox Bridged Network Driver" and reboot the system. The former is no remedy, because we use VLAN tagging (to the desktop) in our environment. The latter remedy obviously means no network access for VirtualBox. It would be nice if this issue could be fixed, as Microsoft HyperV does not suffer from this problem, and I'd much rather use VirtualBox.

Steps to reproduce:

1. Install the appropriate full Realtek NIC driver from http://www.realtek.com
/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false
2. Install VirtualBox on a system with a "Realtek PCIe GBE Family Controller"
3. Open the Network Connection Control Panel
4. Right-click "local Area Connection" and choose "Properties"
5. Click Configure
6. Click Advanced
7. Under the "Propery:" list, select "Priority & VLAN" then, under the "Value:" list, select "Priority & VLAN Enabled"
8. Click Start --> All Programs --> Realtek --> Diagnostic Utility --> Realtek Ethernet Diagnostic Utility
9. Select "Realtek PCIe GBE Family Controller" from the list on the left
10 Click "VLAN" (from the middle column)
11. Click "Add" and enter a VLAN ID (for a VLAN that actually exists on your network) and press <ENTER>
12. Confirm adding of the VLAN and close the Realtek utility
13. Check to see if you still have network connectivity.  If you do, reboot.
14. You should not longer have network connectivity.
15. Open "local Area Connection Properties"
16. Uncheck "VirtualBox Bridged Network Driver" and click "OK".  Reboot
17. Now you should have network connectivity.

This problem is happening on a system with the following characteristics;

- Windows 7 64-bit
- Realtek Realtek PCIe Gigabit Etherenet NIC
- Virtual Box 3.2.x

Change History

comment:1 Changed 4 years ago by fgp

I am not certain the problem is virtualbox or the realtek vlan driver. I have the same setup version 3.2.8 and win7 64bit. My vlan connection does not come up ever. I cannot determine if is a virtualbox or a driver problem.

comment:2 Changed 4 years ago by fgp

I take it back, it is clearly the virtualbox driver. I disabled "Virtualbox bridge network driver" from the nic and suddenly all vlans came up.

comment:3 Changed 2 years ago by Technologov

A possible solution for your problem is described in Wish #6057

-Technologov

comment:4 Changed 2 years ago by viro

Unfortunately, that would not be a solution, as I shouldn't have to choose between having a properly functioning networking stack and running VirtualBox. Microsoft Virtual PC does not have this problem. Since all my other software and drivers are compatible with each other, and it's only when the VirtualBox bridge network driver enters that picture that things fall apart, this is VirtualBox's problem to fix. Notifications about incompatibilities resolve nothing.

I know the VirtualBox team can fix these issues, if they try, because they've recently fixed similar issues where VirtualBox was not playing nice with third-party USB filter drivers.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use