Ethernet Bridge development
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <razor@blackwall.org>
To: Fabian Pfitzner <f.pfitzner@pengutronix.de>, netdev@vger.kernel.org
Cc: dsahern@gmail.com, idosch@nvidia.com,
	bridge@lists.linux-foundation.org, entwicklung@pengutronix.de
Subject: Re: [PATCH iproute2-next v5 2/3] bridge: dump mcast querier per vlan
Date: Tue, 24 Jun 2025 15:40:29 +0300	[thread overview]
Message-ID: <ef528c8e-9931-4746-b72f-31110fc3aebe@blackwall.org> (raw)
In-Reply-To: <20250623093316.1215970-3-f.pfitzner@pengutronix.de>

On 6/23/25 12:33, Fabian Pfitzner wrote:
> Dump the multicast querier state per vlan.
> This commit is almost identical to [1].
> 
> The querier state can be seen with:
> 
> bridge -d vlan global
> 
> The options for vlan filtering and vlan mcast snooping have to be enabled
> in order to see the output:
> 
> ip link set [dev] type bridge mcast_vlan_snooping 1 vlan_filtering 1
> 
> The querier state shows the following information for IPv4 and IPv6
> respectively:
> 
> 1) The ip address of the current querier in the network. This could be
>    ourselves or an external querier.
> 2) The port on which the querier was seen
> 3) Querier timeout in seconds
> 
> [1] https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=16aa4494d7fc6543e5e92beb2ce01648b79f8fa2
> 
> Signed-off-by: Fabian Pfitzner <f.pfitzner@pengutronix.de>
> ---
>  bridge/vlan.c | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/bridge/vlan.c b/bridge/vlan.c
> index 14b8475d..3c240207 100644
> --- a/bridge/vlan.c
> +++ b/bridge/vlan.c
> @@ -852,6 +852,11 @@ static void print_vlan_global_opts(struct rtattr *a, int ifindex)
>  		print_uint(PRINT_ANY, "mcast_querier", "mcast_querier %u ",
>  			   rta_getattr_u8(vattr));
>  	}
> +	if (vtb[BRIDGE_VLANDB_GOPTS_MCAST_QUERIER_STATE]) {
> +		struct rtattr *attr = vtb[BRIDGE_VLANDB_GOPTS_MCAST_QUERIER_STATE];
> +
> +		bridge_print_mcast_querier_state(attr);
> +	}
>  	if (vtb[BRIDGE_VLANDB_GOPTS_MCAST_IGMP_VERSION]) {
>  		vattr = vtb[BRIDGE_VLANDB_GOPTS_MCAST_IGMP_VERSION];
>  		print_uint(PRINT_ANY, "mcast_igmp_version",
> --
> 2.39.5
> 

Acked-by: Nikolay Aleksandrov <razor@blackwall.org>


  parent reply	other threads:[~2025-06-24 12:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-23  9:33 [PATCH iproute2-next v5 0/3] bridge: dump mcast querier state per vlan Fabian Pfitzner
2025-06-23  9:33 ` [PATCH iproute2-next v5 1/3] bridge: move mcast querier dumping code into a shared function Fabian Pfitzner
2025-06-24 11:55   ` Ido Schimmel
2025-06-24 12:40   ` Nikolay Aleksandrov
2025-06-23  9:33 ` [PATCH iproute2-next v5 2/3] bridge: dump mcast querier per vlan Fabian Pfitzner
2025-06-24 11:57   ` Ido Schimmel
2025-06-24 12:40   ` Nikolay Aleksandrov [this message]
2025-06-23  9:33 ` [PATCH iproute2-next v5 3/3] bridge: refactor bridge mcast querier function Fabian Pfitzner
2025-06-24 12:01   ` Ido Schimmel
2025-06-24 12:41   ` Nikolay Aleksandrov

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=ef528c8e-9931-4746-b72f-31110fc3aebe@blackwall.org \
    --to=razor@blackwall.org \
    --cc=bridge@lists.linux-foundation.org \
    --cc=dsahern@gmail.com \
    --cc=entwicklung@pengutronix.de \
    --cc=f.pfitzner@pengutronix.de \
    --cc=idosch@nvidia.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox