Opened 13 years ago
Last modified 11 years ago
#8769 new defect
VLAN tagged packets mangled on bridged adapter
| Reported by: | Kevin Otte | Owned by: | |
|---|---|---|---|
| Component: | network/hostif | Version: | VirtualBox 4.0.6 |
| Keywords: | vlan network bridge | Cc: | |
| Guest type: | other | Host type: | Linux |
Description
A guest that is bridged to a physical adapter on which VLAN tagged packets (ethertype 0x8100) are received, the packets arrive in the guest without the VLAN tag.
I will attach a Wireshark packet decode of a frame as seen from the host and the guest for review.
Attachments (3)
Change History (14)
by , 13 years ago
| Attachment: | vbox-tshark-wire.txt added |
|---|
comment:1 by , 13 years ago
I am also seeing this behavior when using a Host-only adapter that is a member of a Linux bridge.
comment:2 by , 13 years ago
| Component: | network → network/hostif |
|---|
comment:4 by , 13 years ago
I don't recall if I ever tried this under 3.2. Unfortunately I can't backrev this machine to test it out.
comment:5 by , 13 years ago
Not 100% clear to me what the configuration of the NIC is. Is the card on the host configured to receive packets with a certain VLAN tag?
If it is then I'd say it's expected behavior (of the host OS) to strip the VLAN tag before it reaches the bridge.
comment:7 by , 13 years ago
I just tested with version 4.0.12 r72916 and am still seeing the problem.
VLAN tagging is functioning correctly to the OS, and I can use the Bridged adapter to a VLAN tagged interface (eg: eth0.2). My suspicion is something in the vbox filter code is mangling the packet before it gets passed to the guest.
What log(s) do you need to see?
comment:8 by , 13 years ago
After much tinkering, I seem to have found the problem. If any of the guests are set to use the Paravirtualized Network driver, this behavior is seen. If the guests are all configured to use something else (Intel, PCNet), then everything behaves correctly.
comment:9 by , 13 years ago
My apologies, I spoke to soon. I just experienced the behavior with two Intel guests. Back to the drawing board.
comment:10 by , 13 years ago
Please attach VBox.log from Logs subfolder located in VM folder. The same log can also be accessed via Machine->Show Log... menu item.
Packet as seen on the wire at the host