From: Ido Schimmel <idosch@nvidia.com>
To: "Linus Lüssing" <linus.luessing@c0d3.blue>
Cc: netdev@vger.kernel.org, bridge@lists.linux.dev,
Nikolay Aleksandrov <razor@blackwall.org>
Subject: Re: [PATCH iproute2-next] bridge: mcast: add mcast_active_v4 / mcast_active_v6 output
Date: Sun, 8 Feb 2026 18:13:45 +0200 [thread overview]
Message-ID: <20260208161345.GO154003@shredder> (raw)
In-Reply-To: <20260206023704.4839-1-linus.luessing@c0d3.blue>
On Fri, Feb 06, 2026 at 03:37:04AM +0100, Linus Lüssing wrote:
> Add output for the mcast_active_v4 and mcast_active_v6 states. If their
> output is 1 then IGMP/MLD snooping is applied to multicast payload
> traffic of their according protocol family. This is the case when:
>
> * the bridge interface is up
> * multicast snooping is enabled
> * an IGMP/MLD querier is present
> * for own IPv6 MLD querier: an IPv6 address is configured on the bridge
>
> Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>
> ---
> bridge/vlan.c | 10 ++++++++++
> include/uapi/linux/if_bridge.h | 2 ++
> include/uapi/linux/if_link.h | 2 ++
Code looks fine, but note that David asks to split the uAPI header
changes to a separate patch as a hint for him to sync the headers. See
commit a3ec2778576b ("Update kernel headers") for example.
> ip/iplink_bridge.c | 12 ++++++++++++
> 4 files changed, 26 insertions(+)
prev parent reply other threads:[~2026-02-08 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 2:37 [PATCH iproute2-next] bridge: mcast: add mcast_active_v4 / mcast_active_v6 output Linus Lüssing
2026-02-08 16:13 ` Ido Schimmel [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=20260208161345.GO154003@shredder \
--to=idosch@nvidia.com \
--cc=bridge@lists.linux.dev \
--cc=linus.luessing@c0d3.blue \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.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.