|MPING(1)||General Commands Manual||MPING(1)|
mpingaspires to be an easy to use and script friendly program with support for both IPv4 and IPv6. Similar to the standard ping(1) program, but unlike it, the response to multicast ping is sent by another
mping. It can be used to verify intended IGMP/MLD snooping functionality in any layer-2 bridges (switches), as well as verify forwarding of multicast in static (
SMCRoute) or dynamic (
pim6sd) multicast routing setups. By default,
mpingstarts in receiver mode, joining group 220.127.116.11, and for each received UDP packet from the sender, it is looped back. For unicast ping, this is handled by the TCP/IP stack. To run in sender mode, use the
-scommand line option. Remember to adjust the TTL value if you are in a routed setup, and to set the multicast interface with
-iIFNAME, otherwise the unicast routing table is used by the kernel to select the outbound interface, which often is not what you want.
mpingcurrently only supports any-source multicast, ASM (*,G).
mpingdoes not create or send IGMP/MLD frames directly. Instead, it asks the kernel for groups from a specific interface, which is then converted to the IGMPv2/MLDv1 join messages, or IGMPv3/MLDv2 membership reports by the kernel. /proc/sys/net/ipv4/conf/eth0/force_igmp_version. E.g., to change
echo 2 | sudo tee /proc/sys/net/ipv4/conf/eth0/force_igmp_version
mpinghas two modes of operation available. The default is to exit after COUNT number of packets have been sent. The other mode is to wait for COUNT packets to be recived. See
-woption, below, for more information.
-cCOUNT replies. If COUNT replies are received before the deadline,
|May 12, 2022||Debian|