On Tue, Aug 16, 2022 at 09:51:32AM +0200, netdev@kapio-technology.com wrote:

On 2022-08-10 09:21, Ido Schimmel wrote:

quoted

quoted

quoted

1. It discards packets with matching DMAC, regardless of ingress port. I
read the document [1] you linked to in a different reply and could not
find anything against this approach, so this might be fine or at least
not very significant.

Note that this means that "locked" entries need to be notified to device
drivers so that they will install a matching entry in the HW FDB.

I just want to be completely sure as what should be done in version 5 with
locked entries from the bridge, as - if I should implement it so that they
are sent to all the drivers, and the drivers then ignore them if they don't
need to take action? (for the mv88e6xxx driver, it does not need them and
can ignore but other drivers might need.)

Yes, I think that would be best. At least when mlxsw starts supporting
MAB it will need to program the locked entry as an FDB with discard
action.

To be clear, I'm aware that all drivers other than mv88e6xxx currently
forbid a port from being locked, making it unlikely that they will
receive such notifications, but if you do it now then we will not need
more changes in the bridge when other drivers gain support for
802.1X/MAB.