From: Joachim Wiberg <troglobit@gmail.com>
To: Nikolay Aleksandrov <razor@blackwall.org>, netdev@vger.kernel.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH iproute2-next 1/2] bridge: support for controlling flooding of broadcast per port
Date: Wed, 09 Mar 2022 07:14:26 +0100 [thread overview]
Message-ID: <878rtjabzx.fsf@gmail.com> (raw)
In-Reply-To: <70f81f09-0b18-43c2-206d-c31c518dab4d@blackwall.org>
On Tue, Mar 08, 2022 at 18:11, Nikolay Aleksandrov <razor@blackwall.org> wrote:
> On 08/03/2022 15:29, Joachim Wiberg wrote:
>> Add per-port support for controlling flooding of broadcast traffic.
>> Similar to unicast and multcast flooding that already exist.
> Nice, thanks for adding this. Please also update ip/iplink_bridge_slave.c and the
> respective docs with the bcast flag, it already supports the other two.
Aha, there are knobs and levers over there too! OK, will do :-)
/J
next prev parent reply other threads:[~2022-03-09 6:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 13:29 [PATCH iproute2-next 0/2] bridge: support for controlling broadcast flooding per port Joachim Wiberg
2022-03-08 13:29 ` [PATCH iproute2-next 1/2] bridge: support for controlling flooding of broadcast " Joachim Wiberg
2022-03-08 16:11 ` Nikolay Aleksandrov
2022-03-09 6:14 ` Joachim Wiberg [this message]
2022-03-08 13:29 ` [PATCH iproute2-next 2/2] man: document new bcast_flood config/query support for bridge ports Joachim Wiberg
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=878rtjabzx.fsf@gmail.com \
--to=troglobit@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=stephen@networkplumber.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 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).