NAME
mcping —
Ping one more more hosts using
ICMP or TCP
SYNOPSIS
| mcping |
[-c count]
[-i
interface]
[-n]
[-p -pps]
[-q]
[-t
-seconds] host(s) |
DESCRIPTION
mcping pings one or more hosts using ICMP or TCP. It uses raw
sockets and pcap, and hence requires escalated privileges (root).
Optional arguments:
- -c count
- Specify the number of packets
to send to each host.
- -i interface
- Specify the interface (by
name) on which to listen for responses.
- -n
- Do not perform DNS
lookups.
- -p pps
- Specify an overall packet
rate, in packets/second. The default is 1.
- -q
- Quiet mode. Do not print each
received packet, only print the final result.
- -t seconds
- Specify a round trip timeout,
in seconds. Responses that take longer than seconds will be
considered dropped. The default is 5 seconds.
Required arguments:
- host(s)
- Specify the destination
host(s). To use ICMP, just use the hostnames, e.g. foo.bar.com. To
use TCP, append a colon and the port number, e.g.
foo.bar.com:80.
EXAMPLES
Ping 192.168.169.2 using TCP on port 80, 192.168.168.1 using TCP port 22 and
192.168.168.4 using ICMP.
# mcping -p 10 -c 5 192.168.168.2:80 192.168.168.1:22 192.168.168.4
192.168.168.1:22 0.053 ms
192.168.168.2:80 0.116 ms
192.168.168.4 0.539 ms
192.168.168.1:22 0.047 ms
192.168.168.2:80 0.116 ms
192.168.168.4 0.394 ms
192.168.168.1:22 0.184 ms
192.168.168.2:80 0.114 ms
192.168.168.4 0.445 ms
192.168.168.1:22 0.113 ms
192.168.168.2:80 0.114 ms
192.168.168.4 0.422 ms
192.168.168.1:22 0.179 ms
192.168.168.2:80 0.119 ms
192.168.168.4 0.389 ms
--- 192.168.168.2:80 ping statistics ---
5 packets sent, 5 packets received, 0% packet loss
--- 192.168.168.1:22 ping statistics ---
5 packets sent, 5 packets received, 0% packet loss
--- 192.168.168.4 ping statistics ---
5 packets sent, 5 packets received, 0% packet loss
SEE ALSO
Manpage Index
AUTHORS
Copyright (c) 2016 Daniel W. McRobb
dwm@mcplex.net
CAVEATS
mcping(1) does not have the
smarts to open the correct interface for the loopback address. Also, since it
opens a single pcap device, it's not able to receive responses on more than
one interface. This makes it mostly useless on multihomed hosts. This may
change in the future.