From: Stephen Hemminger <stephen@networkplumber.org>
To: Fabian Pfitzner <f.pfitzner@pengutronix.de>
Cc: netdev@vger.kernel.org, entwicklung@pengutronix.de,
dsahern@gmail.com, roopa@nvidia.com, razor@blackwall.org,
bridge@lists.linux-foundation.org
Subject: Re: [PATCH v2 iproute] bridge: dump mcast querier state
Date: Wed, 30 Oct 2024 17:41:40 -0700 [thread overview]
Message-ID: <20241030174140.4ef77885@hermes.local> (raw)
In-Reply-To: <20241030222136.3395120-1-f.pfitzner@pengutronix.de>
On Wed, 30 Oct 2024 23:21:36 +0100
Fabian Pfitzner <f.pfitzner@pengutronix.de> wrote:
> Kernel support for dumping the multicast querier state was added in this
> commit [1]. As some people might be interested to get this information
> from userspace, this commit implements the necessary changes to show it
> via
>
> ip -d link show [dev]
>
> 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/linux/kernel/git/torvalds/linux.git/commit/?id=c7fa1d9b1fb179375e889ff076a1566ecc997bfc
>
> Signed-off-by: Fabian Pfitzner <f.pfitzner@pengutronix.de>
Use print_color_string for printing addresses; to be consistent with other code
next prev parent reply other threads:[~2024-10-31 0:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 22:21 [PATCH v2 iproute] bridge: dump mcast querier state Fabian Pfitzner
2024-10-31 0:41 ` Stephen Hemminger [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-30 8:46 Fabian Pfitzner
2024-10-30 15:23 ` Stephen Hemminger
2024-10-30 15:29 ` Nikolay Aleksandrov
2024-10-30 22:10 ` Fabian Pfitzner
2024-10-31 8:44 ` 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=20241030174140.4ef77885@hermes.local \
--to=stephen@networkplumber.org \
--cc=bridge@lists.linux-foundation.org \
--cc=dsahern@gmail.com \
--cc=entwicklung@pengutronix.de \
--cc=f.pfitzner@pengutronix.de \
--cc=netdev@vger.kernel.org \
--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).