Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to bridge vmware workstation's VM NIC to tap interface on host that includes 802.1q/tagged (vlan) traffic. Somehow vmware bridging strips 802.1q header and all traffic gets to VM untagged. When running tcpdump on tap interface on host I see 802.1q headers, but when running tcpdump on VM's NIC inside vmware I don't. If I create two VMs inside vmware workstation, both bridged to same host NIC/tap interface - tagged(vlan) traffic is working between them, but not with outside world (host). I am running vmware workstation 9.0.2 build-1031769 on linux, kernel 3.10.11. Is this normal behaviors for vmware workstation? Is there any other workaround to get 802.1q traffic in VMs?

share|improve this question
up vote 0 down vote accepted

Found three workarounds

  1. Patching vmnet modules (not working always) - see
  2. Use GRE tunnel with 'gretap' - see / in guest VM you might have problems combing VLANs
  3. Use openvswitch on host and guest VM and crate GRE tunnel between both openvswitches (best option so far if you can run openvswitch in guest VM)
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.