dual tagged traffic not forwarded from bridge_if to em0

[dotOne]

All,

I'm running some bhyve VM's that are all connected to em0, a dedicated interface not having an IP address.
Each of these VM's have two vlans configured.
Traffic from these vlan's is forwarded nicely with the tag through the tap interface and the bridge to the physical interface em0.

However, these are lab testing machines and they are sometimes used to generate 802.1ad (QinQ) traffic.
When running a tcpdump on the tap interface or on the bridge is can see the double tagged frames but the traffic is not showing on the physical interface that is attached to the bridge as well.
Any idea how to solve this?

# ifconfig bridge2
bridge2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 02:f3:ed:90:ad:02
nd6 options=1<PERFORMNUD>
groups: bridge
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: em0 flags=102<DISCOVER,AUTOPTP>
ifmaxaddr 0 port 3 priority 128 path cost 20000
member: tap5 flags=102<DISCOVER,AUTOPTP>
ifmaxaddr 0 port 16 priority 128 path cost 2000000


TCPdump on tap interface
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on tap5, link-type EN10MB (Ethernet), capture size 262144 bytes
15:30:03.561550 00:aa:bb:bb:10:02 > 00:aa:03:ff:ff:60, ethertype 802.1Q (0x8100), length 1414: vlan 1002, p 0, ethertype 802.1Q, vlan 2400, p 0, ethertype IPv4, ...
15:30:03.662367 00:aa:bb:bb:10:02 > 00:aa:03:ff:ff:60, ethertype 802.1Q (0x8100), length 127: vlan 1002, p 0, ethertype 802.1Q, vlan 2200, p 0, ethertype IPv4, ...
15:30:03.762598 00:aa:bb:bb:10:02 > 00:aa:03:ff:ff:60, ethertype 802.1Q (0x8100), length 1301: vlan 1002, p 0, ethertype 802.1Q, vlan 2300, p 0, ethertype IPv4, ...

TCPdump on bridge interface
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on bridge2, link-type EN10MB (Ethernet), capture size 262144 bytes
15:32:46.381604 00:aa:bb:bb:10:02 > 00:aa:03:ff:ff:60, ethertype 802.1Q (0x8100), length 127: vlan 1002, p 0, ethertype 802.1Q, vlan 2200, p 0, ethertype IPv4, ...
15:32:46.481947 00:aa:bb:bb:10:02 > 00:aa:03:ff:ff:60, ethertype 802.1Q (0x8100), length 1301: vlan 1002, p 0, ethertype 802.1Q, vlan 2300, p 0, ethertype IPv4, ...
15:32:46.582585 00:aa:bb:bb:10:02 > 00:aa:03:ff:ff:60, ethertype 802.1Q (0x8100), length 1414: vlan 1002, p 0, ethertype 802.1Q, vlan 2400, p 0, ethertype IPv4, ...

TCPdump on physical interface
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on em0, link-type EN10MB (Ethernet), capture size 262144 bytes

 

[dlavigne]

There are a couple of open bug tickets wrt VMs with laggs or vlans which are targetted for the next major version.