Changes between Version 1 and Version 2 of Ticket #5415, comment 3
- Timestamp:
- Jan 14, 2013 1:46:44 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #5415, comment 3
v1 v2 5 5 6 6 Using tcpdump on host's VLAN interface, I see the ARP request from the guest, and the ARP reply from a machine on the network (that has passed the HP switch), but the ARP reply is never dumped by tcpdump on the guest OS' VLAN interface. 7 eth0 on the host sees one untagged VLAN's traffic, and several tagged VLANs without any problems. (So it's not a "clean" trunk, one VLAN is sent untagged.) 7 8 8 9 If I instead bridge host OS' VLAN interface (such as eth0:100) to guest OS' second NIC (eth1), then I can configure eth1 in the guest and have perfect communication. Ie, the guest OS talks to the VLAN on eth1 as were it untagged. This is the fallback/workaround solution I'm using now in production. (I just pray I won't ever need to use more than 8 VLANs in a guest OS.)
