Bridged Network requires IPv4 enabled?

[yaplej]

So as of installing VirtualBox 5.0.8 r103449 I can only bridge to network interfaces that have IPv4 enabled on them. Why is that? I specifically use a dedicated NIC to bridge to and don't want to have any IP protocols enabled on it.

[dataKEKS]

See Ticket #14578 for details on the same bug.

It seems that some posts of the following topic are connected with this issue: No bridged mode with 5.0.4 on Windows 7.

[yaplej]

Yep that explains it.

[diamond_D]

I did two major upgrades today. Upgraded from VBox 4 to the current build (v.5.0.8 r103449) and also upgraded my OS from Windows 7 to Windows 10.

I had two Linux MINT VM's running on bridged networking to dedicated NICs. Now only one is working. It seems like VBox networking can only see one physical NIC. Any suggestions on what I need to do to get this fixed?

Roll back to VBox 4? Will it work fine on Windows 10?

...or do I need to roll back my OS?

[LastWord]

Test build 104375 (with filename VirtualBox-5.0.51-104375-Win.exe) solved the issue with bridged networking for me. See Ticket #14578 ("Unable to select network adaptor that has TCP/IP disabled.") for details.
I tested this build on Windows 10 host and it works.

[dataKEKS]

Works fine for me on Windows 10 Pro x64 on an HP z400 with OnBoard Broadcom NIC and an Intel Pro1000PT DualPort NIC. Now the onboard NIC is for OS only again and the Intel NICs for test networks in other ip ranges. Right now i ony miss one thine: Expansion Pack for USB and PXE Support?

Best regards
Norbert