fping
fping is a ping like program which uses the Internet Control Message Protocol (ICMP) echo request to determine if a host is up. fping is different from ping in that you can specify any number of hosts on the command line, or specify a file containing the lists of hosts to ping . Instead of trying one host until it timeouts or replies, fping will send out a ping packet and move on to the next host in a round-robin fashion. If a host replies, it is noted and removed from the list of hosts to check. If a host does not respond within a certain time limit and/or retry limit it will be considered unreachable.
Unlike ping , fping is meant to be used in scripts and its output is easy to parse. It is often used as a probe for packet loss and round-trip time in SmokePing.
fping version 3
The original fping was written by Roland Schemers in 1992, and stopped being updated in 2002. In December 2011, David Schweikert decided to take up maintainership of fping , and increased the major release number to 3, mainly to reflect the change of maintainer. Changes from earlier versions include:
- integration of all Debian patches, including IPv6 support (2.4b2-to-ipv6-16)
- an optimized main loop that is claimed to bring performance close to the theoretical maximum
- patches to improve SmokePing compatibility
The Web site location has changed to fping.org , and the source is now maintained on GitHub.
Since July 2013, there is also a Mailing List, which will be used to announce new releases.
Examples
Simple example of usage:
# fping -c 3 -s www.man.poznan.pl www.google.pl
www.google.pl : [0], 96 bytes, 8.81 ms (8.81 avg, 0% loss)
www.man.poznan.pl : [0], 96 bytes, 37.7 ms (37.7 avg, 0% loss)
www.google.pl : [1], 96 bytes, 8.80 ms (8.80 avg, 0% loss)
www.man.poznan.pl : [1], 96 bytes, 37.5 ms (37.6 avg, 0% loss)
www.google.pl : [2], 96 bytes, 8.76 ms (8.79 avg, 0% loss)
www.man.poznan.pl : [2], 96 bytes, 37.5 ms (37.6 avg, 0% loss)
www.man.poznan.pl : xmt/rcv/%loss = 3/3/0%, min/avg/max = 37.5/37.6/37.7
www.google.pl : xmt/rcv/%loss = 3/3/0%, min/avg/max = 8.76/8.79/8.81
2 targets
2 alive
0 unreachable
0 unknown addresses
0 timeouts (waiting for response)
6 ICMP Echos sent
6 ICMP Echo Replies received
0 other ICMP received
8.76 ms (min round trip time)
23.1 ms (avg round trip time)
37.7 ms (max round trip time)
2.039 sec (elapsed real time)
IPv6 Support
Jeroen Massar has added IPv6 support to fping . This has been implemented as a compile-time variant, so that there are separate fping (for IPv4) and fping6 (for IPv6) binaries. The IPv6 patch has been partially integrated into the fping version on www.fping.com as of release "2.4b2_to-ipv6" (thus also integrated in fping 3.0). Unfortunately his modifications to the build routine seem to have been lost in the integration, so that the fping.com version only installs the IPv6 version as fping . Jeroen's original version doesn't have this problem, and can be downloaded from his IPv6 Web page.
ICMP Sequence Number handling
Older versions of fping used the Sequence Number field in ICMP ECHO requests in a peculiar way: it used a different sequence number for each destination host, but used the same sequence number for all requests to a specific host. There have been reports of specific systems that suppress (or rate-limit) ICMP ECHO requests with repeated sequence numbers, which causes high loss rates reported from tools that use fping , such as SmokePing. Another issue is that fping could not distinguish a perfect link from one that drops every other packet and that duplicates every other.
Newer fping versions such as 3.0 or 2.4.2b2_to (on Debian GNU/Linux) include a change to sequence number handling attributed to Stephan Fuhrmann. These versions increment sequence numbers for every probe sent, which should solve both of these problems.
References
- Fping Web site, http://fping.org/
fpingsource on GitHub, https://github.com/schweikert/fping
– Main.BartoszBelter - 2005-07-14 - 2005-07-26
– Main.SimonLeinen - 2008-05-19 - 2013-07-26