From: Nikolay Aleksandrov <nikolay@nvidia.com>
To: 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: Thu, 10 Feb 2022 16:55:40 +0200 [thread overview]
Message-ID: <d4f1f9b1-6e8e-d21d-603f-7a0889e33a78@nvidia.com> (raw)
In-Reply-To: <20220210142401.4912-1-nbd@nbd.name>
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?
next prev parent reply other threads:[~2022-02-10 14:55 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 ` Nikolay Aleksandrov [this message]
2022-02-10 16:06 ` [RFC 1/2] net: bridge: add knob for filtering rx/tx BPDU packets on a port Felix Fietkau
2022-02-11 8:16 ` Nikolay Aleksandrov
2022-02-11 17:01 ` Stephen Hemminger
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=d4f1f9b1-6e8e-d21d-603f-7a0889e33a78@nvidia.com \
--to=nikolay@nvidia.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.