Difference: FpingTool (1 vs. 9)

Revision 92013-07-26 - SimonLeinen

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

fping

Line: 16 to 16
  The Web site location has changed to fping.org, and the source is now maintained on GitHub.
Added:
>
>
Since July 2013, there is also a Mailing List, which will be used to announce new releases.
 

Examples

Simple example of usage:
Line: 61 to 63
 
Deleted:
<
<
-- BartoszBelter - 26 Jul 2005 - 14 Jul 2005
-- SimonLeinen - 19 May 2008 - 08 Jan 2012
 \ No newline at end of file
Added:
>
>
-- BartoszBelter - 2005-07-14 - 2005-07-26
-- SimonLeinen - 2008-05-19 - 2013-07-26
 \ No newline at end of file

Revision 82012-01-08 - SimonLeinen

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

fping

Line: 10 to 10
  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:
Changed:
<
<
  • integration of all Debian patches (2.4b2-to-ipv6-16)
>
>
  • 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
Line: 48 to 48
 

IPv6 Support

Changed:
<
<
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". 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.
>
>
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

Line: 62 to 62
 

-- BartoszBelter - 26 Jul 2005 - 14 Jul 2005

Changed:
<
<
-- SimonLeinen - 19 May 2008 - 04 Jan 2012
>
>
-- SimonLeinen - 19 May 2008 - 08 Jan 2012
 \ No newline at end of file

Revision 72012-01-04 - SimonLeinen

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

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.

Changed:
<
<
Unlike ping, fping is meant to be used in scripts and its output is easy to parse.
>
>
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

Line: 52 to 52
 

ICMP Sequence Number handling

Changed:
<
<
Current versions of fping uses the Sequence Number field in ICMP ECHO requests in a peculiar way. RFC 792 explains that the sequence number can be used to match responses to requests. Therefore it would make sense to use different sequence numbers for different ECHO requests to the same host - responses from different hosts can be disambiguated easily by looking at the source address. Instead, fping uses a different sequence number for each destination host, but uses the same sequence number for all requests to a specific hosts. For example, fping -c 3 hostA hostB would send the following ICMP packets
>
>
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.
 
Changed:
<
<
ICMP ECHO -> hostA, seq# 0
ICMP ECHO -> hostB, seq# 1
ICMP ECHO -> hostA, seq# 0
ICMP ECHO -> hostB, seq# 1
ICMP ECHO -> hostA, seq# 0
ICMP ECHO -> hostB, seq# 1

instead of, e.g.

ICMP ECHO -> hostA, seq# 0
ICMP ECHO -> hostB, seq# 0
ICMP ECHO -> hostA, seq# 1
ICMP ECHO -> hostB, seq# 1
ICMP ECHO -> hostA, seq# 2
ICMP ECHO -> hostB, seq# 2

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 cannot 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

Line: 82 to 62
 

-- BartoszBelter - 26 Jul 2005 - 14 Jul 2005

Deleted:
<
<
-- SimonLeinen - 19 May 2008 - 02 Jan 2012
 \ No newline at end of file
Added:
>
>
-- SimonLeinen - 19 May 2008 - 04 Jan 2012

Revision 62012-01-04 - SimonLeinen

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

fping

Line: 20 to 20
 Simple example of usage:

# fping -c 3 -s www.man.poznan.pl www.google.pl
Changed:
<
<
www.man.poznan.pl : [0], 84 bytes, 1.44 ms (1.44 avg, 0% loss) www.google.pl : [0], 84 bytes, 126 ms (126 avg, 0% loss) www.man.poznan.pl : [1], 84 bytes, 1.12 ms (1.28 avg, 0% loss) www.google.pl : [1], 84 bytes, 126 ms (126 avg, 0% loss) www.man.poznan.pl : [2], 84 bytes, 2.18 ms (1.58 avg, 0% loss) www.google.pl : [2], 84 bytes, 126 ms (126 avg, 0% loss)
>
>
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)
 
Changed:
<
<
www.man.poznan.pl : xmt/rcv/%loss = 3/3/0%, min/avg/max = 1.12/1.58/2.18 www.google.pl : xmt/rcv/%loss = 3/3/0%, min/avg/max = 126/126/126
>
>
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
Line: 40 to 40
  6 ICMP Echo Replies received 0 other ICMP received
Changed:
<
<
1.12 ms (min round trip time) 64.0 ms (avg round trip time) 126 ms (max round trip time) 2.548 sec (elapsed real time)
>
>
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

Revision 52012-01-02 - SimonLeinen

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

fping

Line: 6 to 6
  Unlike ping, fping is meant to be used in scripts and its output is easy to parse.
Added:
>
>

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 (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.

Examples

 Simple example of usage:

# fping -c 3 -s www.man.poznan.pl www.google.pl
Line: 67 to 78
 

References

Changed:
<
<
>
>
  -- BartoszBelter - 26 Jul 2005 - 14 Jul 2005
Deleted:
<
<
-- SimonLeinen - 19 May 2008
 \ No newline at end of file
Added:
>
>
-- SimonLeinen - 19 May 2008 - 02 Jan 2012
 \ No newline at end of file

Revision 42008-05-19 - SimonLeinen

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

fping

Line: 8 to 8
  Simple example of usage:
Changed:
<
<

# fping -c 3 -s www.man.poznan.pl www.google.pl
>
>
# fping -c 3 -s www.man.poznan.pl www.google.pl
 www.man.poznan.pl : [0], 84 bytes, 1.44 ms (1.44 avg, 0% loss) www.google.pl : [0], 84 bytes, 126 ms (126 avg, 0% loss) www.man.poznan.pl : [1], 84 bytes, 1.12 ms (1.28 avg, 0% loss)
Line: 43 to 39
  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". 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.
Added:
>
>

ICMP Sequence Number handling

Current versions of fping uses the Sequence Number field in ICMP ECHO requests in a peculiar way. RFC 792 explains that the sequence number can be used to match responses to requests. Therefore it would make sense to use different sequence numbers for different ECHO requests to the same host - responses from different hosts can be disambiguated easily by looking at the source address. Instead, fping uses a different sequence number for each destination host, but uses the same sequence number for all requests to a specific hosts. For example, fping -c 3 hostA hostB would send the following ICMP packets

ICMP ECHO -> hostA, seq# 0
ICMP ECHO -> hostB, seq# 1
ICMP ECHO -> hostA, seq# 0
ICMP ECHO -> hostB, seq# 1
ICMP ECHO -> hostA, seq# 0
ICMP ECHO -> hostB, seq# 1

instead of, e.g.

ICMP ECHO -> hostA, seq# 0
ICMP ECHO -> hostB, seq# 0
ICMP ECHO -> hostA, seq# 1
ICMP ECHO -> hostB, seq# 1
ICMP ECHO -> hostA, seq# 2
ICMP ECHO -> hostB, seq# 2

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 cannot distinguish a perfect link from one that drops every other packet and that duplicates every other.

 

References

Changed:
<
<
-- BartoszBelter - 26 Jul 2005 - 14 Jul 2005
>
>
-- BartoszBelter - 26 Jul 2005 - 14 Jul 2005
-- SimonLeinen - 19 May 2008
 \ No newline at end of file

Revision 32006-09-13 - SimonLeinen

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

fping

Changed:
<
<
_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.
>
>
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.
 
Changed:
<
<
Unlike ping, fping is meant to be used in scripts and its output is easy to parse.

For more information please refer to http://www.fping.com.

>
>
Unlike ping, fping is meant to be used in scripts and its output is easy to parse.
  Simple example of usage:
Line: 41 to 39
 
Added:
>
>

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". 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.

 

References

Revision 22006-05-22 - SimonLeinen

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

fping

Line: 45 to 45
 
Changed:
<
<
-- OrlaMcGann - 26 Jul 2005 - 14 Jul 2005
>
>
-- BartoszBelter - 26 Jul 2005 - 14 Jul 2005
 

Revision 12006-03-29 - SimonLeinen

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="WebHome"

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.

For more information please refer to http://www.fping.com.

Simple example of usage:


# fping -c 3 -s www.man.poznan.pl www.google.pl
www.man.poznan.pl : [0], 84 bytes, 1.44 ms (1.44 avg, 0% loss)
www.google.pl     : [0], 84 bytes, 126 ms (126 avg, 0% loss)
www.man.poznan.pl : [1], 84 bytes, 1.12 ms (1.28 avg, 0% loss)
www.google.pl     : [1], 84 bytes, 126 ms (126 avg, 0% loss)
www.man.poznan.pl : [2], 84 bytes, 2.18 ms (1.58 avg, 0% loss)
www.google.pl     : [2], 84 bytes, 126 ms (126 avg, 0% loss)

www.man.poznan.pl : xmt/rcv/%loss = 3/3/0%, min/avg/max = 1.12/1.58/2.18
www.google.pl     : xmt/rcv/%loss = 3/3/0%, min/avg/max = 126/126/126

       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

 1.12 ms (min round trip time)
 64.0 ms (avg round trip time)
 126 ms (max round trip time)
        2.548 sec (elapsed real time)

References

-- OrlaMcGann - 26 Jul 2005 - 14 Jul 2005

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2004-2009 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.