VirtualBox

Ticket #14558 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

VirtuaBox bridged adapter "merges" bridged interfaces of the same hardware => Fixed in SVN

Reported by: EPinci Owned by:
Priority: major Component: network
Version: VirtualBox 5.0.4 Keywords: Win10
Cc: Guest type: all
Host type: Windows

Description

Runing VBox 5.0.4 on Win10 RTM on a system with an Intel 82574L dual NIC. First NIC is disconnected, second NIC is the one in use as per below:

PS C:\WINDOWS\system32> Get-NetAdapter | FT Name, InterfaceDescription, InterfaceIndex, Status

Name                         InterfaceDescription                       InterfaceIndex Status
----                         --------------------                       -------------- ------
Ethernet 2                   Intel(R) 82574L Gigabit Network Connection              7 Up
Clavister                    SSL VPN TAP-Win32 Adapter V9                            9 Disconnected
VirtualBox Host-Only Network VirtualBox Host-Only Ethernet Adapter #2                8 Up
Ethernet                     Intel(R) 82574L Gigabit Network Connection             10 Disconnected

Note that both Ethernet and Ethernet 2 have the same Descriptor. Description (AKA Device name) is not user configurable and defined by the OS. I believe Win8 used to mark the second one with an "# 2" but Win10 does not.

Per similar tickets, I checked NetADP6 and NetLWF driver version and running status with "sc query". "VBoxManage list bridgedifs" correctly identifies the Ethernet NIC *all with same Name and VBoxNetworkName* per below:

PS C:\Program Files\Oracle\VirtualBox> .\VBoxManage.exe list bridgedifs
Name:            Intel(R) 82574L Gigabit Network Connection
GUID:            943906a2-b8b3-4bdd-ad8b-ba4a836d51bf
DHCP:            Disabled
IPAddress:       192.168.1.5
NetworkMask:     255.255.255.0
IPV6Address:     fd9a:1c10:4d81:0001:20e4:d222:4c89:d809
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 00:30:48:bc:e9:56
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-Intel(R) 82574L Gigabit Network Connection

Name:            SSL VPN TAP-Win32 Adapter V9
GUID:            e5e56055-88c4-4a8a-a8c8-c2820776956c
DHCP:            Disabled
IPAddress:       1.1.1.1
NetworkMask:     15.0.0.0
IPV6Address:     fe80:0000:0000:0000:2189:4efc:410a:7bab
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 00:ff:e5:e5:60:55
MediumType:      Ethernet
Status:          Down
VBoxNetworkName: HostInterfaceNetworking-SSL VPN TAP-Win32 Adapter V9

Name:            Intel(R) 82574L Gigabit Network Connection
GUID:            f3c6f150-12ed-42f1-8a2a-21ff92c253de
DHCP:            Enabled
IPAddress:       169.254.11.85
NetworkMask:     15.0.0.0
IPV6Address:     fe80:0000:0000:0000:18f7:ac18:9661:0b55
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 00:30:48:bc:e9:57
MediumType:      Ethernet
Status:          Down
VBoxNetworkName: HostInterfaceNetworking-Intel(R) 82574L Gigabit Network Connection

As result, the interface dropdown in the virtual machine shows *two* availble bridged interfaces:

  • Intel(R) 82574L Gigabit Network Connection
  • SSL VPN TAP-Win32 Adapter V9

And VBox effectively binds the VM interface to the first adapter with the name, in my case the disconnected one. There's no way to select the other working interface as used to be with Win8.

Note that this behavior is shown only after the first reboot post-installation. For some baffling reasons, right after the installation of VBox, before the first reboot, I can see and use three NICs in the VM Network configuration dropdown and actually use the right one (# 2) until the first reboot. After the first reboot the # 2 adapter disappear and the VM errors out on start due to missing network adapter and I can bind it only to the wrong VM.

Attachments

VBoxSVC.log Download (9.5 KB) - added by EPinci 2 years ago.

Change History

Changed 2 years ago by EPinci

comment:1 Changed 2 years ago by EPinci

Furthermore, I might add that probably the UI dropdown should show the interface name (significant for the user that names it in the OS according to his own needs) rather than the device name that might be duplicate for multi-NIC adapters.

comment:2 Changed 2 years ago by aleksey

Could you please try build 102928? Please provide VBoxSVC.log if the problem still present.

comment:3 Changed 2 years ago by aleksey

  • Summary changed from VirtuaBox bridged adapter "merges" bridged interfaces of the same hardware to VirtuaBox bridged adapter "merges" bridged interfaces of the same hardware => Fixed in SVN

comment:4 Changed 2 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Fix is part of VBox 5.0.12.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use