[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7057e5e0-c42b-4ae5-a709-61c6938a0316@6wind.com>
Date: Wed, 4 Dec 2024 15:17:05 +0100
From: Nicolas Dichtel <nicolas.dichtel@...nd.com>
To: Yuyang Huang <yuyanghuang@...gle.com>
Cc: "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, Simon Horman <horms@...nel.org>,
David Ahern <dsahern@...nel.org>, roopa@...ulusnetworks.com,
jiri@...nulli.us, stephen@...workplumber.org, jimictw@...gle.com,
prohr@...gle.com, liuhangbin@...il.com, andrew@...n.ch,
netdev@...r.kernel.org, Maciej Żenczykowski
<maze@...gle.com>, Lorenzo Colitti <lorenzo@...gle.com>
Subject: Re: [PATCH iproute2-next, v3 2/2] iproute2: add 'ip monitor mcaddr'
support
Le 04/12/2024 à 15:02, Yuyang Huang a écrit :
> Enhanced the 'ip monitor' command to track changes in IPv4 and IPv6
> multicast addresses. This update allows the command to listen for
> events related to multicast address additions and deletions by
> registering to the newly introduced RTNLGRP_IPV4_MCADDR and
> RTNLGRP_IPV6_MCADDR netlink groups.
>
> This patch depends on the kernel patch that adds RTNLGRP_IPV4_MCADDR
> and RTNLGRP_IPV6_MCADDR being merged first.
>
> Here is an example usage:
>
> root@...-x86-64:/# ip monitor mcaddr
Note that 'ip maddr' (see 'man ip-maddress') already exists. Using 'mcaddr' for
'ip monitor' is confusing.
You could also update man/man8/ip-monitor.8
Regards,
Nicolas
Powered by blists - more mailing lists