Date: Thu, 4 Sep 2025 13:22:49 +0200 From: Ronald Klop <ronald-lists@klop.ws> To: net@freebsd.org Cc: Lexi Winter <ivy@freebsd.org> Subject: Re: bridge new vlan and iftagged "none" Message-ID: <1a91faca-69ef-410d-95ad-2d371c84f759@klop.ws> In-Reply-To: <aLlvcpTEz4oZVQEe@amaryllis.le-fay.org> References: <481902534.1074.1756977663370@localhost> <aLlvcpTEz4oZVQEe@amaryllis.le-fay.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Op 04-09-2025 om 12:52 schreef Lexi Winter: > hi Roland, > > Ronald Klop: >> member: epair4a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> >> port 15 priority 128 path cost 2000 vlan protocol 802.1q > > based on this configuration, epair4a should neither accept nor send any > traffic. When I saw my mail again I realized that I copy-pasted the bridge config with VLANFILTER enabled. That didn't match with the case I wrote about. So with VLANFILTER enabled epair4a didn't receive/send any traffic as expected. But genet0 didn't receive anything either so little happened on the machine. :-) With VLANFILTER disabled epair4a did receive traffic and also broadcasts on vlan 3. I don't know if this is expected. Interestingly, with VLANFILTER disabled the "untagged 3" interfaces also saw broadcast traffic which was not destined for vlan 3. >> epair4a still receives all traffic, so also traffic for vlan 3. > > however, it seems like there's an issue filtering outgoing traffic from > the host itself. could you please try the attached patch and see if it > makes any difference? With the story above is the patch still needed? I will test anyway to see what happens. It is a RPI4, so compiling is a bit slow. Regards, Ronald.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1a91faca-69ef-410d-95ad-2d371c84f759>