|-4||Force the use of IPv4.|
|-6||Force the use of IPv6.|
|-c count||Send (and receive) count ICMP packets, then stop and exit.|
|-i interval||Send one ICMP packet (per host) each interval seconds. This can be a floating-point number to specify sub-second precision.|
|-t ttl||Set the IP Time to Live to ttl. This must be a number between (and including) 1 and 255. If omitted, the value 64 is used.|
|-I address||Set the source address to use. You may either specify an IP number or a hostname. You cannot pass the interface name, as you can with GNUs ping(8) - use the -D option for that purpose.|
|-D interface name||Set the outgoing network device to use.|
Instead of specifying hostnames on the command line, read them from
filename. If filename is -, read from STDIN.
If oping is installed with the SetUID-bit, it will set the effective UID to the real UID before opening the file. In the special (but common) case that oping is owned by the super-user (UID 0), this means that privileges are temporarily dropped before opening the file, in order to prevent users from reading arbitrary files on the system.
If your system doesnt provide saved set-user IDs (this was an optional feature before POSIX 2001), the behavior is different because it is not possible to temporarily drop privileges. The alternative behavior is: If the real user ID (as returned by getuid(2)) and the effective user ID (as returned by geteuid(2)) differ, the only argument allowed for this option is - (i.e. standard input).
Specify the Quality of Service (QoS) for outgoing packets. This is a
somewhat tricky option, since the meaning of the bits in the IPv4 header has
been revised several times.
The currently recommended method is Differentiated Services which is used in IPv6 headers as well. There are shortcuts for various predefined per-hop behaviors (PHBs):
The old definition of the same bits in the IPv4 header was as Type of Service (ToS) field, specified in RFC 1349. It defined four possible values which have appropriate aliases. Please note that this use of the bits is deprecated and the meaning is limited to IPv4!
Alternatively, you can also specify the byte manually. You can use either a decimal number (0-255), a hexadecimal number (0x00-0xff) or an octal number (00-0377) using the usual 0x and 0 prefixes for hexadecimal and octal respectively.
The printed lines will contain information about the QoS field of received packets if either a non-standard QoS setting was used on outgoing packets or if the QoS byte of incoming packets is not zero. In other words, the QoS information is omitted if both, the outgoing and the incoming QoS bytes are zero. The received byte is always interpreted as Differentiated Services Code Point (DSCP) and Explicit Congestion Notification (ECN), even if the deprecated Type of Service (ToS) aliases were used to specify the bits of outgoing packets.
|-u|-U||noping only -u forces UTF-8 output, -U disables UTF-8 output. If neither is given, the codeset is automatically determined from the locale.|
noping only Selects the graph to display.
|-P percent||Configures the latency percentile to report. percent must be a number between zero and 100, exclusively in both cases. In general, defaults to 95. If -c is given and a number less than 20, this would be the same as the maximum. In this case the default is chosen so that it excludes the maximum, e.g. if -c 5 is given, the default is 80. The calculated percentile is based on the last 900 packets (15 minutes with the default interval).|
If any hosts have a drop rate higher than percent, where percent is a
number between zero and 100 inclusively, exit with a non-zero exit status.
Since it is not possible to have a higher drop rate than 100%, passing this
limit will effectively disable the feature (the default). Setting the option to
zero means that the exit status will only be zero if all replies for all
hosts have been received.
The exit status will indicate the number of hosts with more than percent packets lost, up to a number of 255 failing hosts.
If supported by the terminal, noping will highlight the round-trip times (RTT) using the colors green, yellow and red. Green signals RTTs that are in the expected range, yellow marks moderately unusual times and times that differ a lot from the expected value are printed in red.
The information used to categorize round-trip times is the percentile. RTTs in the 80th percentile are considered to be normal and are printed in green. RTTs within the 95th percentile are considered moderately unusual and are printed in yellow. RTTs above that are considered to be unusual and are printed in red.
ping(8), <http://www.fping.com/>, liboping(3)
liboping is written by Florian octo Forster <ff at octo.it>. Its homepage can be found at <http://verplant.org/liboping/>.
Copyright (c) 2005-2011 by Florian octo Forster.