From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Ido Schimmel <idosch@nvidia.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bridge@lists.linux-foundation.org"
<bridge@lists.linux-foundation.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"edumazet@google.com" <edumazet@google.com>,
"roopa@nvidia.com" <roopa@nvidia.com>,
"razor@blackwall.org" <razor@blackwall.org>,
"netdev@kapio-technology.com" <netdev@kapio-technology.com>,
"mlxsw@nvidia.com" <mlxsw@nvidia.com>
Subject: Re: [PATCH net-next 2/2] selftests: forwarding: Add MAC Authentication Bypass (MAB) test cases
Date: Thu, 3 Nov 2022 23:15:05 +0000 [thread overview]
Message-ID: <20221103231505.7ftg2zcfoa7rzwtw@skbuf> (raw)
In-Reply-To: <20221101193922.2125323-3-idosch@nvidia.com> <20221101193922.2125323-3-idosch@nvidia.com>
On Tue, Nov 01, 2022 at 09:39:22PM +0200, Ido Schimmel wrote:
> From: "Hans J. Schultz" <netdev@kapio-technology.com>
>
> Add four test cases to verify MAB functionality:
>
> * Verify that a locked FDB entry can be generated by the bridge,
> preventing a host from communicating via the bridge. Test that user
> space can clear the "locked" flag by replacing the entry, thereby
> authenticating the host and allowing it to communicate via the bridge.
>
> * Test that an entry cannot roam to a locked port, but that it can roam
> to an unlocked port.
>
> * Test that MAB can only be enabled on a port that is both locked and
> has learning enabled.
>
> * Test that locked FDB entries are flushed from a port when MAB is
> disabled.
>
> Signed-off-by: Hans J. Schultz <netdev@kapio-technology.com>
> Signed-off-by: Ido Schimmel <idosch@nvidia.com>
> ---
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
next prev parent reply other threads:[~2022-11-03 23:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 19:39 [PATCH net-next 0/2] bridge: Add MAC Authentication Bypass (MAB) support Ido Schimmel
2022-11-01 19:39 ` [PATCH net-next 1/2] " Ido Schimmel
2022-11-02 13:16 ` Nikolay Aleksandrov
2022-11-03 23:18 ` Vladimir Oltean
2022-11-04 11:23 ` netdev
2022-11-04 13:11 ` Vladimir Oltean
2022-11-01 19:39 ` [PATCH net-next 2/2] selftests: forwarding: Add MAC Authentication Bypass (MAB) test cases Ido Schimmel
2022-11-02 13:17 ` Nikolay Aleksandrov
2022-11-03 23:15 ` Vladimir Oltean [this message]
2022-11-04 5:00 ` [PATCH net-next 0/2] bridge: Add MAC Authentication Bypass (MAB) support patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221103231505.7ftg2zcfoa7rzwtw@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@kapio-technology.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox