Ticket #11031 (new defect)
'Bridged Networking' on host vlan interfaces does not work
|Reported by:||nocternal||Owned by:|
I have searched the forums, and looked on the internet... and this seems to be a regression in the 4.2.0 release. Downgrading back to 4.1.22 on the same kernel resolves the issue.
I am on gentoo 64-bit, running gentoo-sources-3.6.0. Same results on 3.5.4
I have a vm-host with several 1q vlan interfaces on it. I then bind my VM's to a particular interface using the 'Bridge Adapter'. The VM's are vlan-agnostic.
The symptom I have on VB 4.2.0 is that none of my VM's have network access. As soon as I switch to NAT on the VM's everything works fine. Downgrading to 4.1.22 on the same kernel restores network access for the 'Bridge Adapter'.
daffy TAZ6 # cat /proc/net/vlan/config VLAN Dev name | VLAN ID Name-Type: VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD eth0.10 | 10 | eth0 eth0.11 | 11 | eth0 eth0.12 | 12 | eth0 eth0.13 | 13 | eth0 eth0.14 | 14 | eth0 eth0.20 | 20 | eth0 eth0.25 | 25 | eth0
My VM-HOST network layout:
[ROUTER]====1Q-TRUNK===[VM HOST] eth0.10--bridged--VM1, VM2, VM3.... eth0.11--bridged--VM6, VM7, VM8 eth0.12--bridged--VM4 eth0.13 eth0.14--bridged--VM5 eth0.20 eth0.25
The ROUTER and VM-HOST have the VM's MAC address in their arp tables. The VM itself only has the VM-HOST's MAC address - but not the ROUTER's. The VM can communicate with the VM-HOST but not anything else on the same L2 vlan. All other devices on the same L2 vlan have VM's MAC address (after a ping, say) but the VM never has any of the other hosts in it's arp table. Seems like packets destined to the VM never make it past the VM-HOST. I don't see any odd kernel events.
This is the forum post I started prior to this bug - https://forums.virtualbox.org/viewtopic.php?f=7&t=51886
I can attach all the details here if need be.