VB 4.2.0: Bridged Networking and host vlan interfaces...

Discussions related to using VirtualBox on Linux hosts.

VB 4.2.0: Bridged Networking and host vlan interfaces...

Postby nocternal » 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.

Code: Select all   Expand viewCollapse view
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 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.
nocternal
 
Posts: 3
Joined: 3. Oct 2012, 09:13

Re: VB 4.2.0: Bridged Networking and host vlan interfaces...

Postby GuillaumeT » 3. Oct 2012, 15:00

the same problem on F17 x64
GuillaumeT
 
Posts: 1
Joined: 3. Oct 2012, 14:57

Re: VB 4.2.0: Bridged Networking and host vlan interfaces...

Postby michaelnorris0 » 4. Oct 2012, 02:13

i am getting the same problem while running win xp pack on VM. I am using Virtual Box 4.2.0 ,Selecting Bridged Adaptor keeps the network connectivity to limited.and when i used NAT ,it worked pretty fine.
What do you think why this problem is? Do i need to use some old version of virtual box?and yes i downloaded the Virtual box 4.1.20 from official website of its.
Will Bridged Adapter work fine on some old version of VB?
well i am downloading VB 4.1.20 to see if the bridged adaptor will work or not?
michaelnorris0
 
Posts: 1
Joined: 4. Oct 2012, 02:05

Re: VB 4.2.0: Bridged Networking and host vlan interfaces...

Postby nocternal » 4. Oct 2012, 23:53

I have done some more testing with VB 4.2.0.

First, here's my interfaces:
Code: Select all   Expand viewCollapse view
daffy ~ # 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


Here's my VLAN settings (I'm showing one here... they all look the same):
Code: Select all   Expand viewCollapse view
daffy ~ # cat /proc/net/vlan/eth0.10
eth0.10  VID: 10         REORDER_HDR: 1  dev->priv_flags: 1
         total frames received       953569
          total bytes received    827045052
      Broadcast/Multicast Rcvd          300

      total frames transmitted      2614142
       total bytes transmitted   2796452747
Device: eth0
INGRESS priority mappings: 0:0  1:0  2:0  3:0  4:0  5:0  6:0 7:0
 EGRESS priority mappings:


Here's a quick diagram of the network-path between the VM and my Router (the VM's default gateway):
Code: Select all   Expand viewCollapse view
[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


So here's my findings:
The router has the MAC address of the VM in it's arp tables, as does the VB HOST. The VM itself, however does not have the Router in it's ARP table. The VM *DOES* have the VM HOST mac address and I can ping/ssh to the VM HOST from the VM's... but not anything past that. This means, from my cursory review, that somehow the VB Bridge Adapter is dropping/filtering/mangling a packet that is destined to the VM's. This makes sense (that the VM can communicate with the VM HOST as switching to 'NAT adapter' works).
nocternal
 
Posts: 3
Joined: 3. Oct 2012, 09:13

Re: VB 4.2.0: Bridged Networking and host vlan interfaces...

Postby Perryg » 5. Oct 2012, 00:01

This being the case you should open a ticket at bugtracker
Perryg
Site Moderator
 
Posts: 25942
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX - Other

Re: VB 4.2.0: Bridged Networking and host vlan interfaces...

Postby nocternal » 5. Oct 2012, 00:12

Thanks,

I've been considering that... but I didn't want to burden them without cause. I figured I'd post something here first, in case there was a simple fix or change. I agree - it looks like a bug (or significant change from 4.1.x) in that just downgrading works perfectly everytime.

I will open a bug later tonight and file an update here as well it if gets and traction in the bugtracker.
nocternal
 
Posts: 3
Joined: 3. Oct 2012, 09:13

Re: VB 4.2.0: Bridged Networking and host vlan interfaces...

Postby Perryg » 5. Oct 2012, 00:22

If as stated in your original post the symptoms are not in a previous version then that and of itself is a regression and deserving a ticket.
Perryg
Site Moderator
 
Posts: 25942
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX - Other


Return to VirtualBox on Linux Hosts

Who is online

Users browsing this forum: No registered users and 14 guests