[Bug 292759] [igb] vlanhwfilter silently does not work with bridge with VLANs
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 28 Jan 2026 15:44:12 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292759 --- Comment #7 from Zhenlei Huang <zlei@FreeBSD.org> --- (In reply to Aleksandr Fedorov from comment #5) The report by vova, now fix that: # ifconfig igb1 -vlanhwfilter # ping -c1 192.168.20.1 PING 192.168.20.1 (192.168.20.1): 56 data bytes 64 bytes from 192.168.20.1: icmp_seq=0 ttl=64 time=0.473 ms --- 192.168.20.1 ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.473/0.473/0.473/0.000 ms >>> now it works drive me to think about the implementation of vlan over if_bridge(4). Currently on configuring the vid ( VLAN ID ), the vlan_config event handler is invoked to let the drivers, obviously has the IFCAP_VLAN_HWFILTER capability, to program hardware / firmware's vlan filters. The mismatched tagged packets will all be silently dropped by the hardware. 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. I'm CCing Lexi to see if she's working on that. -- You are receiving this mail because: You are the assignee for the bug.