From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 72707418C0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 85A32418BE MIME-Version: 1.0 Date: Fri, 21 Oct 2022 08:47:42 +0200 From: netdev@kapio-technology.com In-Reply-To: <20221020225719.l5iw6vndmm7gvjo3@skbuf> References: <20221018165619.134535-1-netdev@kapio-technology.com> <20221018165619.134535-1-netdev@kapio-technology.com> <20221018165619.134535-11-netdev@kapio-technology.com> <20221018165619.134535-11-netdev@kapio-technology.com> <20221020132538.reirrskemcjwih2m@skbuf> <2565c09bb95d69142522c3c3bcaa599e@kapio-technology.com> <20221020225719.l5iw6vndmm7gvjo3@skbuf> Message-ID: <82d23b100b8d2c9e4647b8a134d5cbbf@kapio-technology.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Bridge] [PATCH v8 net-next 10/12] net: dsa: mv88e6xxx: mac-auth/MAB implementation List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vladimir Oltean Cc: Andrew Lunn , Alexandre Belloni , Nikolay Aleksandrov , Kurt Kanzenbach , Eric Dumazet , linux-kselftest@vger.kernel.org, Joachim Wiberg , Shuah Khan , Ivan Vecera , Florian Fainelli , Daniel Borkmann , Ido Schimmel , bridge@lists.linux-foundation.org, Russell King , linux-arm-kernel@lists.infradead.org, Roopa Prabhu , kuba@kernel.org, Paolo Abeni , Vivien Didelot , Woojung Huh , Landen Chao , Jiri Pirko , Amit Cohen , Christian Marangi , Hauke Mehrtens , Hans Schultz , Sean Wang , DENG Qingfang , Claudiu Manoil , linux-mediatek@lists.infradead.org, Matthias Brugger , Yuwei Wang , Petr Machata , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Florent Fourcot , UNGLinuxDriver@microchip.com, davem@davemloft.net On 2022-10-21 00:57, Vladimir Oltean wrote: > On Thu, Oct 20, 2022 at 10:20:50PM +0200, netdev@kapio-technology.com > wrote: >> In general locked ports block traffic from a host based on if there is >> a >> FDB entry or not. In the non-offloaded case, there is only CPU >> assisted >> learning, so the normal learning mechanism has to be disabled as any >> learned entry will open the port for the learned MAC,vlan. > > Does it have to be that way? Why can't BR_LEARNING on a BR_PORT_LOCKED > cause the learned FDB entries to have BR_FDB_LOCKED, and everything > would be ok in that case (the port will not be opened for the learned > MAC/VLAN)? > I suppose you are right that basing it solely on BR_FDB_LOCKED is possible. The question is then maybe if the common case where you don't need learned entries for the scheme to work, e.g. with EAPOL link local packets, requires less CPU load to work and is cleaner than if using BR_FDB_LOCKED entries? >> Thus learning is off for locked ports, which of course includes MAB. >> >> So the 'learning' is based on authorizing MAC,vlan addresses, which >> is done by userspace daemons, e.g. hostapd or what could be called >> mabd.