https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292759
--- Comment #10 from [email protected] --- (In reply to Zhenlei Huang from comment #7) > Well if_bridge(4) does not register vlan_config event, hence unable to pass > correct VLAN IDs to the bridge members those has IFCAP_VLAN_HWFILTER enabled. > Disabling the IFCAP_VLAN_HWFILTER capability of member interface can be a > rescue, > since it makes the member interface into *promiscuous* mode for tagged > packets. hm ... in face after any reconfiguration - if_bridge knows set of VLANs for each member port: # ifconfig bridge0 bridge0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1504 description: igb0 options=10<VLAN_HWTAGGING> ether 58:9c:fc:10:3f:e4 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 bridge flags=1<VLANFILTER> member: epair3a flags=943<LEARNING,DISCOVER,PRIVATE,AUTOEDGE,AUTOPTP> port 16 priority 128 path cost 2000 vlan protocol 802.1q untagged 20 tagged 1 member: epair1a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> port 9 priority 128 path cost 2000 vlan protocol 802.1q untagged 1 member: epair2a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> port 12 priority 128 path cost 2000 vlan protocol 802.1q untagged 20 member: igb0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> port 1 priority 128 path cost 55 vlan protocol 802.1q untagged 1 tagged 20 groups: bridge nd6 options=9<PERFORMNUD,IFDISABLED> The only "issue" here is who calling whom and when? -- You are receiving this mail because: You are the assignee for the bug.
