From: David Ahern <dsahern@gmail.com>
To: Nikolay Aleksandrov <razor@blackwall.org>, netdev@vger.kernel.org
Cc: roopa@nvidia.com, Nikolay Aleksandrov <nikolay@nvidia.com>
Subject: Re: [PATCH iproute2-next 0/6] bridge: mdb: add support for IGMPv3/MLDv2 attributes
Date: Sun, 11 Oct 2020 20:08:19 -0600 [thread overview]
Message-ID: <05f5cd5c-6dd8-a153-64ed-03b1d850d5d5@gmail.com> (raw)
In-Reply-To: <20201008135024.1515468-1-razor@blackwall.org>
On 10/8/20 6:50 AM, Nikolay Aleksandrov wrote:
> From: Nikolay Aleksandrov <nikolay@nvidia.com>
>
> Hi,
> This set adds support for IGMPv3/MLDv2 attributes, they're mostly
> read-only at the moment. The only new "set" option is the source address
> for S,G entries. It is added in patch 01 (see the patch commit message for
> an example). Patch 02 shows a missing flag (fast_leave) for
> completeness, then patch 03 shows the new IGMPv3/MLDv2 flags:
> added_by_star_ex and blocked. Patches 04-06 show the new extra
> information about the entry's state when IGMPv3/MLDv2 are enabled. That
> includes its filter mode (include/exclude), source list with timers and
> origin protocol (currently only static/kernel), in order to show the new
> information the user must use "-d"/show_details.
> Here's the output of a few IGMPv3 entries:
> dev bridge port ens12 grp 239.0.0.1 src 20.21.22.23 temp filter_mode include proto kernel blocked 0.00
> dev bridge port ens12 grp 239.0.0.1 src 8.9.10.11 temp filter_mode include proto kernel blocked 0.00
> dev bridge port ens12 grp 239.0.0.1 src 1.2.3.1 temp filter_mode include proto kernel blocked 0.00
> dev bridge port ens12 grp 239.0.0.1 temp filter_mode exclude source_list 20.21.22.23/0.00,8.9.10.11/0.00,1.2.3.1/0.00 proto kernel 26.65
>
applied to iproute2-next. Thanks, Nik
prev parent reply other threads:[~2020-10-12 2:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 13:50 [PATCH iproute2-next 0/6] bridge: mdb: add support for IGMPv3/MLDv2 attributes Nikolay Aleksandrov
2020-10-08 13:50 ` [PATCH iproute2-next 1/6] bridge: mdb: add support for source address Nikolay Aleksandrov
2020-10-08 13:50 ` [PATCH iproute2-next 2/6] bridge: mdb: print fast_leave flag Nikolay Aleksandrov
2020-10-08 13:50 ` [PATCH iproute2-next 3/6] bridge: mdb: show igmpv3/mldv2 flags Nikolay Aleksandrov
2020-10-08 13:50 ` [PATCH iproute2-next 4/6] bridge: mdb: print filter mode when available Nikolay Aleksandrov
2020-10-08 13:50 ` [PATCH iproute2-next 5/6] bridge: mdb: print source list " Nikolay Aleksandrov
2020-10-08 13:50 ` [PATCH iproute2-next 6/6] bridge: mdb: print protocol " Nikolay Aleksandrov
2020-10-12 2:08 ` David Ahern [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=05f5cd5c-6dd8-a153-64ed-03b1d850d5d5@gmail.com \
--to=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.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;
as well as URLs for NNTP newsgroup(s).