virtualbox.org

Hello people,

my Host is Fedora 31 fully updated with several vlan subinterfaces configured + Windows 10 as a Guest inside latest VirtualBox with all Extensions and Guest additions installed. I can see and select vlan interface for bridge in VM's settings, but no network appears in VM. NAT set up works perfectly as well as general network access on host via vlan interface. All three Intel virtual NICs were tried - no help.

Any help or suggestion would be very appreciated.

Regards.

Try opening the PDF of the Virtualbox manual, in the Virtualbox installation folder. Search for 'vlan' there's a couple things mentioned, but I have never set up a vlan nor am I skilled on Linux (I'm a Windows guy). There may be something pertinent in the manual.

Also, Bridged doesn't always work over Wi-Fi.

Further, Bridged might work if the Vlan stuff were removed. (Not what you want, I see, but it's worth a try to see if Bridged works directly to the host's Ethernet card.)

scottgus1 wrote:Try opening the PDF of the Virtualbox manual, in the Virtualbox installation folder. Search for 'vlan' there's a couple things mentioned, but I have never set up a vlan nor am I skilled on Linux (I'm a Windows guy). There may be something pertinent in the manual.

Also, Bridged doesn't always work over Wi-Fi.

Further, Bridged might work if the Vlan stuff were removed. (Not what you want, I see, but it's worth a try to see if Bridged works directly to the host's Ethernet card.)

Thanks for pointing thos doc. Nothing helpful on the issue, but in general pretty interesting. It is not about wifi but wired connection. Of course I tried that - via untagged connection bridge works like a charm.

Up. Same on Kubuntu 19.10... Still not resolved or explained.

Same thing happening here. I am running FreeBSD 12.1-RELEASE #0 r354387M (Xigmanas 12.1.0.4 - Ingva (revision 7091) Full) on my host, which runs Virtual Box 5.2.34 (133883). I have a couple of VM's (Win7 x64, Win10 x64) running with GuestAdditions 5.2.34. Using a bridged adapter on my VM's (em0), the network in the guest continuously drops out. Host network access remains unaffected. Using the guest Windows troubleshooter it detects no access to the gateway, resets the adapter, and everything works for between 5-60 seconds, then I lose the network again (i.e. little yellow badge over network icon, suggesting no access to network). Before the dropout I can browse the LAN, connect to shares, browse the internet. But it only stays live for under a minute, and then drops out again. Changing from Bridged to NAT, the guest works flawlessly, solid and stable connection to both LAN and internet .. unfortunately NAT introduces restrictions that I cannot live with.
Anyone know what the heck is going on here? This previously worked (with older version of Xigmanas which I assume uses older version of VirtualBox).

Ok, have now tested this on a Debian (Buster) amd64 guest. The adapter set in Bridged mode seems a lot more stable than Win10 guest but still unusable. The second I try and copy anything across the LAN the applications start to die on the guest (file browser, qBittorrent, everything accessing the adapter in anger, including network mounts, etc). Using NAT, it's solid as a rock except I cannot use both my VPN and access my LAN simultaneously .. again, a deal-breaker for me (unless I download to my VM with VPN enabled, then disconnect VPN to copy to my LAN .. way too hard). At the moment I am investigating using NAT + Host-Only to circumvent the broken Bridged mode .. not looking promising. I can look into downgrading VirtualBox (as Bridged used to be solid) but it means downgrading Xigmanas too, a right royal pain .. and I'm unsure how far back I need to go in the downgrade process.

@Timski: The "Supported Hosts" list : https://www.virtualbox.org/manual/ch01. ... tossupport doesn't show FreeBSD. You might want to try in the Unsupported Hosts subforum.

@TulipB, If the manual doesn't have anything definitely allowing or disallowing your setup, it could be that the devs don't know something is broken or they didn't program for it. Try IRC, mailing list, or the bug tracker: https://www.virtualbox.org/wiki/Community

scottgus1 wrote:@TulipB, If the manual doesn't have anything definitely allowing or disallowing your setup, it could be that the devs don't know something is broken or they didn't program for it. Try IRC, mailing list, or the bug tracker: https://www.virtualbox.org/wiki/Community

Posted a bug. No reaction so far.

TulipB wrote:No reaction so far.

Quite likely. The devs are rather busy.
<voice='Yoda'> “Patience you must have my young padawan.” </voice>