From: Stephen Hemminger <stephen@networkplumber.org>
To: Nikolay Aleksandrov <nikolay@nvidia.com>
Cc: Felix Fietkau <nbd@nbd.name>, <netdev@vger.kernel.org>
Subject: Re: [RFC 1/2] net: bridge: add knob for filtering rx/tx BPDU packets on a port
Date: Fri, 11 Feb 2022 09:01:47 -0800 [thread overview]
Message-ID: <20220211090147.3db33a58@hermes.local> (raw)
In-Reply-To: <d4f1f9b1-6e8e-d21d-603f-7a0889e33a78@nvidia.com>
On Thu, 10 Feb 2022 16:55:40 +0200
Nikolay Aleksandrov <nikolay@nvidia.com> wrote:
> On 10/02/2022 16:24, Felix Fietkau wrote:
> > Some devices (e.g. wireless APs) can't have devices behind them be part of
> > a bridge topology with redundant links, due to address limitations.
> > Additionally, broadcast traffic on these devices is somewhat expensive, due to
> > the low data rate and wakeups of clients in powersave mode.
> > This knob can be used to ensure that BPDU packets are never sent or forwarded
> > to/from these devices
> >
> > Signed-off-by: Felix Fietkau <nbd@nbd.name>
> > ---
> > include/linux/if_bridge.h | 1 +
> > include/uapi/linux/if_link.h | 1 +
> > net/bridge/br_forward.c | 5 +++++
> > net/bridge/br_input.c | 2 ++
> > net/bridge/br_netlink.c | 6 +++++-
> > net/bridge/br_stp_bpdu.c | 9 +++++++--
> > net/core/rtnetlink.c | 4 +++-
> > 7 files changed, 24 insertions(+), 4 deletions(-)
> >
>
> Why can't netfilter or tc be used to filter these frames?
>
>
It could but this looks better.
BPDU filter matches what other hardware switch vendors offer and
has the benefit of not adding another layer of complexity into
user configurations.
Adding one rule into a complex firewall or starting to have to
configure tc is a mess.
prev parent reply other threads:[~2022-02-11 17:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 14:24 [RFC 1/2] net: bridge: add knob for filtering rx/tx BPDU packets on a port Felix Fietkau
2022-02-10 14:24 ` [RFC 2/2] net: bridge: add a software fast-path implementation Felix Fietkau
2022-02-10 15:02 ` Nikolay Aleksandrov
2022-02-10 16:53 ` Felix Fietkau
2022-02-11 8:50 ` Nikolay Aleksandrov
2022-03-28 15:15 ` Felix Fietkau
2022-03-28 18:20 ` Nikolay Aleksandrov
2022-03-29 11:07 ` Felix Fietkau
2022-02-10 14:55 ` [RFC 1/2] net: bridge: add knob for filtering rx/tx BPDU packets on a port Nikolay Aleksandrov
2022-02-10 16:06 ` Felix Fietkau
2022-02-11 8:16 ` Nikolay Aleksandrov
2022-02-11 17:01 ` Stephen Hemminger [this message]
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=20220211090147.3db33a58@hermes.local \
--to=stephen@networkplumber.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=nikolay@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;
as well as URLs for NNTP newsgroup(s).