[PATCH net-next 2/2] net: dsa: mt7530: add support for bridge port isolation
Matthias Schiffer
mschiffer at universe-factory.net
Sun Jun 16 09:35:25 PDT 2024
On 16/06/2024 17:35, Andrew Lunn wrote:
>> As far as I can tell, the rules are:
>>
>> - non-isolated ports can communicate with every port
>> - isolated ports can't communicate with other isolated ports
>> - communication is symmetric
>
> It is a bit more subtle than that.
>
> By default, all ports should be isolated. They can exchange packets
> with the CPU port, but nothing else. This goes back to the model of
> switches just look like a bunch of netdev interfaces. By default,
> linux netdev interfaces are standalone. You need to add a bridge
> before packets can flow between ports.
>
> Once you add a bridge, ports within that bridge can exchange
> packets. However, there can be multiple bridges. So a port needs to be
> isolated from ports in another bridge, but non-isolated to ports
> within the same bridge.
>
> Andrew
Right, I was talking about ports in the same bridge (which is already
handled as expected by the mt7530 driver, just the option to set the
isolation flag for individual bridge ports was unsupported).
Matthias
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20240616/780349f8/attachment.sig>
More information about the linux-arm-kernel
mailing list