[Bug 238198] [if_ix] and [if_bridge] and [vlan] not playing well

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238198

            Bug ID: 238198
           Summary: [if_ix] and [if_bridge] and [vlan] not playing well
           Product: Base System
           Version: 12.0-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs at FreeBSD.org
          Reporter: dgilbert at eicat.ca

Created attachment 204676
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=204676&action=edit
tcpdump -nvi ix0.221

Not sure if pr_208910 is related, but this is definately different

Summary:

Traffic through a vm -> bridge -> vlan -> ix doesn't return.  tcpdump at ix0
shows both pings, tcpdump at ix0.221 shows only outbound direction of pings.

vlan.pcap is a tcpdump of ix0.221
port.pcap is a tcpdump of ix0

System is 12.0-p4 and here's the bridge config:

bridge2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: vm-lan221
        ether 02:df:71:71:45:02
        id 00:bd:a8:26:5b:00 priority 32768 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
        root id 00:bd:a8:26:5b:00 priority 32768 ifcost 0 port 0
        member: tap0 flags=167<LEARNING,DISCOVER,STP,EDGE,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 12 priority 128 path cost 2000000 proto rstp
                role designated state forwarding
        member: ix0.221 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 7 priority 128 path cost 55
        groups: bridge vm-switch viid-c15cb@
        nd6 options=1<PERFORMNUD>

ix0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu
1500    
options=e53bbb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,WOL_UCAST,WOL_MCAST,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
        ether a0:36:9f:17:ba:10
        inet 192.168.110.3 netmask 0xffffff00 broadcast 192.168.110.255
        inet6 fe80::a236:9fff:fe17:ba10%ix0 prefixlen 64 scopeid 0x1
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

ix0.221: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0
mtu 1500
        options=200001<RXCSUM,RXCSUM_IPV6>
        ether a0:36:9f:17:ba:10
        inet 66.96.20.34 netmask 0xffffffe0 broadcast 66.96.20.63
        inet 66.96.20.35 netmask 0xffffffe0 broadcast 66.96.20.63
        inet6 fe80::a236:9fff:fe17:ba10%ix0.221 prefixlen 64 scopeid 0x7
        inet6 2001:1928:1::34 prefixlen 64
        inet6 2001:1928:1::35 prefixlen 64
        groups: vlan
        vlan: 221 vlanpcp: 0 parent interface: ix0
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

tap0 is obviously the VM in question.  Bridge2 does "know" the mac addresses
... but the broacast packets (for ARP) do make it through.

[1:4:304]root at run:~> ifconfig bridge2 addr
00:04:4b:2b:92:6c Vlan1 ix0.221 0 flags=0<>
58:9c:fc:01:d4:67 Vlan1 tap0 1200 flags=0<>
00:00:aa:ae:e1:31 Vlan1 ix0.221 1168 flags=0<>
00:c0:b7:2c:43:c5 Vlan1 ix0.221 789 flags=0<>
a0:36:9f:17:bb:0c Vlan1 ix0.221 1156 flags=0<>
f0:9f:c2:0a:dd:0c Vlan1 ix0.221 1170 flags=0<>
00:04:4b:47:9b:dc Vlan1 ix0.221 1195 flags=0<>
b4:fb:e4:80:48:0e Vlan1 ix0.221 1142 flags=0<>
00:12:3f:41:72:fd Vlan1 ix0.221 1200 flags=0<>
10:7b:44:92:e8:fd Vlan1 ix0.221 1200 flags=0<>

-- 
You are receiving this mail because:
You are the assignee for the bug.