VB 4.2.0: Bridged Networking and host vlan interfaces...
Posted: 3. Oct 2012, 09:26
I'm having an odd problem when upgrading to VB 4.2.0. I have several 1Q VLAN interfaces on my VB host server. I use the bridge adapter to connect to each VM to a particular VLAN interface on the host server (depending on where the VM's should be in the network). With this method the VM guests are VLAN-agnostic.
After the upgrade to 4.2.0 none of my VM's have network connectivity when using the Bridged Network adapter. When I switch to the NAT adapter everything works fine. Down grading back to VB 4.1.22 also restores the bridged adapter functionality. I don't see any error message in the VBox.log of any of the VM's... and the kernel messages show each interface going into promiscous mode as VM's are attached.
I know this kind of setup is not the norm - but has anyone else experienced this? I've google'd and searched these forums, tried the IRC channel... no hits yet.
I should note my system summary:
Gentoo 64-bit running on kernel's gentoo-sources-3.5.4 and -3.6.0. As mentioned downgrading to VB-4.1.22 restores network so I don't think it's anything on the gentoo/kernel side.
After the upgrade to 4.2.0 none of my VM's have network connectivity when using the Bridged Network adapter. When I switch to the NAT adapter everything works fine. Down grading back to VB 4.1.22 also restores the bridged adapter functionality. I don't see any error message in the VBox.log of any of the VM's... and the kernel messages show each interface going into promiscous mode as VM's are attached.
Code: Select all
vboxdrv: Found 6 processor cores.
vboxdrv: fAsync=0 offMin=0x9dd offMax=0xb840
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 4.2.0 (interface 0x001a0004).
device eth0.10 entered promiscuous mode
device eth0 entered promiscuous mode
device eth0.12 entered promiscuous mode
device eth0.13 entered promiscuous mode
I should note my system summary:
Gentoo 64-bit running on kernel's gentoo-sources-3.5.4 and -3.6.0. As mentioned downgrading to VB-4.1.22 restores network so I don't think it's anything on the gentoo/kernel side.