[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <867da5viak.fsf@gmail.com>
Date: Tue, 08 Feb 2022 10:06:43 +0100
From: Hans Schultz <schultz.hans@...il.com>
To: Andrew Lunn <andrew@...n.ch>, Ido Schimmel <idosch@...sch.org>
Cc: Hans Schultz <schultz.hans@...il.com>, davem@...emloft.net,
kuba@...nel.org, netdev@...r.kernel.org,
Roopa Prabhu <roopa@...dia.com>,
Nikolay Aleksandrov <nikolay@...dia.com>,
linux-kernel@...r.kernel.org, bridge@...ts.linux-foundation.org
Subject: Re: [PATCH net-next 1/4] net: bridge: Add support for bridge port
in locked mode
On mån, feb 07, 2022 at 14:53, Andrew Lunn <andrew@...n.ch> wrote:
>> > + if (p->flags & BR_PORT_LOCKED) {
>> > + fdb_entry = br_fdb_find_rcu(br, eth_hdr(skb)->h_source, vid);
>> > + if (!(fdb_entry && fdb_entry->dst == p))
>> > + goto drop;
>>
>> I'm not familiar with 802.1X so I have some questions:
>
> Me neither.
>
>>
>> 1. Do we need to differentiate between no FDB entry and an FDB entry
>> pointing to a different port than we expect?
>
> And extending that question, a static vs a dynamic entry?
>
> Andrew
The question is - if there is an fdb entry or not - for the specific client
mac address behind the locked port in the bridge associated with the
respective locked port and vlan taken into consideration.
Normally you would have learning disabled, or from a fresh start if a port
is locked, it will not learn on incoming from that port, so you need to
add the fdb entry from user-space. In the common case you will want to
use static entries and remember the master flag for the entry to go to
the bridge module.
Powered by blists - more mailing lists