Date: Sat, 06 Sep 2025 06:54:50 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 289326] bridge(4): VLAN subinterfaces on one member block tagged traffic on others Message-ID: <bug-289326-7501-D2hJ4t0fRn@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-289326-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-289326-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289326 Lexi Winter <ivy@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ivy@FreeBSD.org --- Comment #3 from Lexi Winter <ivy@FreeBSD.org> --- the intended behaviour here is that if a physical interface has a vlan(4) configured and is also in a bridge, all tagged traffic received on that interface goes to if_vlan, not if_bridge. the previous behaviour depended on matching the destination MAC address of each frame to decide whether it should be handled by vlan(4) or bridge(4), which meant it would "work" in some configurations but not others in a non-obvious way; in particular, traffic on the same interface for the same VLAN ID could be delivered to either vlan(4) or bridge(4) depending on its destination address. in 15.0, the right way to do this is to put the interface in the bridge, then configure the vlan subinterface on the bridge instead of the physical interface: ifconfig bridge0 create addm oce3 ifconfig bridge0.2 create now bridge0.2 will receive traffic on the bridge (from any interface) with vlan id 2. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-289326-7501-D2hJ4t0fRn>