xref: /freebsd/sbin/ping/ping.8 (revision 87569f75a91f298c52a71823c04d41cf53c88889)
1.\" Copyright (c) 1985, 1991, 1993
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 4. Neither the name of the University nor the names of its contributors
13.\"    may be used to endorse or promote products derived from this software
14.\"    without specific prior written permission.
15.\"
16.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
26.\" SUCH DAMAGE.
27.\"
28.\"     @(#)ping.8	8.2 (Berkeley) 12/11/93
29.\" $FreeBSD$
30.\"
31.Dd August 15, 2005
32.Dt PING 8
33.Os
34.Sh NAME
35.Nm ping
36.Nd send
37.Tn ICMP ECHO_REQUEST
38packets to network hosts
39.Sh SYNOPSIS
40.Nm
41.Op Fl AaDdfnoQqRrv
42.Op Fl c Ar count
43.Op Fl G Ar sweepmaxsize
44.Op Fl g Ar sweepminsize
45.Op Fl h Ar sweepincrsize
46.Op Fl i Ar wait
47.Op Fl l Ar preload
48.Op Fl M Cm mask | time
49.Op Fl m Ar ttl
50.Op Fl P Ar policy
51.Op Fl p Ar pattern
52.Op Fl S Ar src_addr
53.Op Fl s Ar packetsize
54.Op Fl t Ar timeout
55.Op Fl z Ar tos
56.Ar host
57.Nm
58.Op Fl AaDdfLnoQqRrv
59.Op Fl c Ar count
60.Op Fl I Ar iface
61.Op Fl i Ar wait
62.Op Fl l Ar preload
63.Op Fl M Cm mask | time
64.Op Fl m Ar ttl
65.Op Fl P Ar policy
66.Op Fl p Ar pattern
67.Op Fl S Ar src_addr
68.Op Fl s Ar packetsize
69.Op Fl T Ar ttl
70.Op Fl t Ar timeout
71.Op Fl z Ar tos
72.Ar mcast-group
73.Sh DESCRIPTION
74The
75.Nm
76utility uses the
77.Tn ICMP
78.No protocol Ap s mandatory
79.Tn ECHO_REQUEST
80datagram to elicit an
81.Tn ICMP ECHO_RESPONSE
82from a host or gateway.
83.Tn ECHO_REQUEST
84datagrams
85.Pq Dq pings
86have an IP and
87.Tn ICMP
88header, followed by a
89.Dq struct timeval
90and then an arbitrary number of
91.Dq pad
92bytes used to fill out the packet.
93The options are as follows:
94.Bl -tag -width indent
95.It Fl A
96Audible.
97Output a bell
98.Tn ( ASCII
990x07)
100character when no packet is received before the next packet
101is transmitted.
102To cater for round-trip times that are longer than the interval
103between transmissions, further missing packets cause a bell only
104if the maximum number of unreceived packets has increased.
105.It Fl a
106Audible.
107Include a bell
108.Tn ( ASCII
1090x07)
110character in the output when any packet is received.
111This option is ignored
112if other format options are present.
113.It Fl c Ar count
114Stop after sending
115(and receiving)
116.Ar count
117.Tn ECHO_RESPONSE
118packets.
119If this option is not specified,
120.Nm
121will operate until interrupted.
122If this option is specified in conjunction with ping sweeps,
123each sweep will consist of
124.Ar count
125packets.
126.It Fl D
127Set the Don't Fragment bit.
128.It Fl d
129Set the
130.Dv SO_DEBUG
131option on the socket being used.
132.It Fl f
133Flood ping.
134Outputs packets as fast as they come back or one hundred times per second,
135whichever is more.
136For every
137.Tn ECHO_REQUEST
138sent a period
139.Dq .\&
140is printed, while for every
141.Tn ECHO_REPLY
142received a backspace is printed.
143This provides a rapid display of how many packets are being dropped.
144Only the super-user may use this option.
145.Bf -emphasis
146This can be very hard on a network and should be used with caution.
147.Ef
148.It Fl G Ar sweepmaxsize
149Specify the maximum size of
150.Tn ICMP
151payload when sending sweeping pings.
152This option is required for ping sweeps.
153.It Fl g Ar sweepminsize
154Specify the size of
155.Tn ICMP
156payload to start with when sending sweeping pings.
157The default value is 0.
158.It Fl h Ar sweepincrsize
159Specify the number of bytes to increment the size of
160.Tn ICMP
161payload after
162each sweep when sending sweeping pings.
163The default value is 1.
164.It Fl I Ar iface
165Source multicast packets with the given interface address.
166This flag only applies if the ping destination is a multicast address.
167.It Fl i Ar wait
168Wait
169.Ar wait
170seconds
171.Em between sending each packet .
172The default is to wait for one second between each packet.
173The wait time may be fractional, but only the super-user may specify
174values less than 1 second.
175This option is incompatible with the
176.Fl f
177option.
178.It Fl L
179Suppress loopback of multicast packets.
180This flag only applies if the ping destination is a multicast address.
181.It Fl l Ar preload
182If
183.Ar preload
184is specified,
185.Nm
186sends that many packets as fast as possible before falling into its normal
187mode of behavior.
188Only the super-user may use this option.
189.It Fl M Cm mask | time
190Use
191.Dv ICMP_MASKREQ
192or
193.Dv ICMP_TSTAMP
194instead of
195.Dv ICMP_ECHO .
196For
197.Cm mask ,
198print the netmask of the remote machine.
199Set the
200.Va net.inet.icmp.maskrepl
201MIB variable to enable
202.Dv ICMP_MASKREPLY .
203For
204.Cm time ,
205print the origination, reception and transmission timestamps.
206.It Fl m Ar ttl
207Set the IP Time To Live for outgoing packets.
208If not specified, the kernel uses the value of the
209.Va net.inet.ip.ttl
210MIB variable.
211.It Fl n
212Numeric output only.
213No attempt will be made to lookup symbolic names for host addresses.
214.It Fl o
215Exit successfully after receiving one reply packet.
216.It Fl P Ar policy
217.Ar policy
218specifies IPsec policy for the ping session.
219For details please refer to
220.Xr ipsec 4
221and
222.Xr ipsec_set_policy 3 .
223.It Fl p Ar pattern
224You may specify up to 16
225.Dq pad
226bytes to fill out the packet you send.
227This is useful for diagnosing data-dependent problems in a network.
228For example,
229.Dq Li \-p ff
230will cause the sent packet to be filled with all
231ones.
232.It Fl Q
233Somewhat quiet output.
234.No Don Ap t
235display ICMP error messages that are in response to our query messages.
236Originally, the
237.Fl v
238flag was required to display such errors, but
239.Fl v
240displays all ICMP error messages.
241On a busy machine, this output can be overbearing.
242Without the
243.Fl Q
244flag,
245.Nm
246prints out any ICMP error messages caused by its own ECHO_REQUEST
247messages.
248.It Fl q
249Quiet output.
250Nothing is displayed except the summary lines at startup time and
251when finished.
252.It Fl R
253Record route.
254Includes the
255.Tn RECORD_ROUTE
256option in the
257.Tn ECHO_REQUEST
258packet and displays
259the route buffer on returned packets.
260Note that the IP header is only large enough for nine such routes;
261the
262.Xr traceroute 8
263command is usually better at determining the route packets take to a
264particular destination.
265If more routes come back than should, such as due to an illegal spoofed
266packet, ping will print the route list and then truncate it at the correct
267spot.
268Many hosts ignore or discard the
269.Tn RECORD_ROUTE
270option.
271.It Fl r
272Bypass the normal routing tables and send directly to a host on an attached
273network.
274If the host is not on a directly-attached network, an error is returned.
275This option can be used to ping a local host through an interface
276that has no route through it
277(e.g., after the interface was dropped by
278.Xr routed 8 ) .
279.It Fl S Ar src_addr
280Use the following IP address as the source address in outgoing packets.
281On hosts with more than one IP address, this option can be used to
282force the source address to be something other than the IP address
283of the interface the probe packet is sent on.
284If the IP address
285is not one of this machine's interface addresses, an error is
286returned and nothing is sent.
287.It Fl s Ar packetsize
288Specify the number of data bytes to be sent.
289The default is 56, which translates into 64
290.Tn ICMP
291data bytes when combined
292with the 8 bytes of
293.Tn ICMP
294header data.
295Only the super-user may specify values more than default.
296This option cannot be used with ping sweeps.
297.It Fl T Ar ttl
298Set the IP Time To Live for multicasted packets.
299This flag only applies if the ping destination is a multicast address.
300.It Fl t Ar timeout
301Specify a timeout, in seconds, before ping exits regardless of how
302many packets have been received.
303.It Fl v
304Verbose output.
305.Tn ICMP
306packets other than
307.Tn ECHO_RESPONSE
308that are received are listed.
309.It Fl z Ar tos
310Use the specified type of service.
311.El
312.Pp
313When using
314.Nm
315for fault isolation, it should first be run on the local host, to verify
316that the local network interface is up and running.
317Then, hosts and gateways further and further away should be
318.Dq pinged .
319Round-trip times and packet loss statistics are computed.
320If duplicate packets are received, they are not included in the packet
321loss calculation, although the round trip time of these packets is used
322in calculating the round-trip time statistics.
323When the specified number of packets have been sent
324(and received)
325or if the program is terminated with a
326.Dv SIGINT ,
327a brief summary is displayed, showing the number of packets sent and
328received, and the minimum, mean, maximum, and standard deviation of
329the round-trip times.
330.Pp
331If
332.Nm
333receives a
334.Dv SIGINFO
335(see the
336.Cm status
337argument for
338.Xr stty 1 )
339signal, the current number of packets sent and received, and the
340minimum, mean, and maximum of the round-trip times will be written to
341the standard error output.
342.Pp
343This program is intended for use in network testing, measurement and
344management.
345Because of the load it can impose on the network, it is unwise to use
346.Nm
347during normal operations or from automated scripts.
348.Sh ICMP PACKET DETAILS
349An IP header without options is 20 bytes.
350An
351.Tn ICMP
352.Tn ECHO_REQUEST
353packet contains an additional 8 bytes worth of
354.Tn ICMP
355header followed by an arbitrary amount of data.
356When a
357.Ar packetsize
358is given, this indicated the size of this extra piece of data
359(the default is 56).
360Thus the amount of data received inside of an IP packet of type
361.Tn ICMP
362.Tn ECHO_REPLY
363will always be 8 bytes more than the requested data space
364(the
365.Tn ICMP
366header).
367.Pp
368If the data space is at least eight bytes large,
369.Nm
370uses the first eight bytes of this space to include a timestamp which
371it uses in the computation of round trip times.
372If less than eight bytes of pad are specified, no round trip times are
373given.
374.Sh DUPLICATE AND DAMAGED PACKETS
375The
376.Nm
377utility will report duplicate and damaged packets.
378Duplicate packets should never occur when pinging a unicast address,
379and seem to be caused by
380inappropriate link-level retransmissions.
381Duplicates may occur in many situations and are rarely
382(if ever)
383a good sign, although the presence of low levels of duplicates may not
384always be cause for alarm.
385Duplicates are expected when pinging a broadcast or multicast address,
386since they are not really duplicates but replies from different hosts
387to the same request.
388.Pp
389Damaged packets are obviously serious cause for alarm and often
390indicate broken hardware somewhere in the
391.Nm
392packet's path (in the network or in the hosts).
393.Sh TRYING DIFFERENT DATA PATTERNS
394The
395(inter)network
396layer should never treat packets differently depending on the data
397contained in the data portion.
398Unfortunately, data-dependent problems have been known to sneak into
399networks and remain undetected for long periods of time.
400In many cases the particular pattern that will have problems is something
401that does not have sufficient
402.Dq transitions ,
403such as all ones or all zeros, or a pattern right at the edge, such as
404almost all zeros.
405It is not
406necessarily enough to specify a data pattern of all zeros (for example)
407on the command line because the pattern that is of interest is
408at the data link level, and the relationship between what you type and
409what the controllers transmit can be complicated.
410.Pp
411This means that if you have a data-dependent problem you will probably
412have to do a lot of testing to find it.
413If you are lucky, you may manage to find a file that either
414cannot
415be sent across your network or that takes much longer to transfer than
416other similar length files.
417You can then examine this file for repeated patterns that you can test
418using the
419.Fl p
420option of
421.Nm .
422.Sh TTL DETAILS
423The
424.Tn TTL
425value of an IP packet represents the maximum number of IP routers
426that the packet can go through before being thrown away.
427In current practice you can expect each router in the Internet to decrement
428the
429.Tn TTL
430field by exactly one.
431.Pp
432The
433.Tn TCP/IP
434specification recommends setting the
435.Tn TTL
436field for
437.Tn IP
438packets to 64, but many systems use smaller values
439.No ( Bx 4.3
440uses 30,
441.Bx 4.2
442used 15).
443.Pp
444The maximum possible value of this field is 255, and most
445.Ux
446systems set
447the
448.Tn TTL
449field of
450.Tn ICMP ECHO_REQUEST
451packets to 255.
452This is why you will find you can
453.Dq ping
454some hosts, but not reach them with
455.Xr telnet 1
456or
457.Xr ftp 1 .
458.Pp
459In normal operation
460.Nm
461prints the ttl value from the packet it receives.
462When a remote system receives a ping packet, it can do one of three things
463with the
464.Tn TTL
465field in its response:
466.Bl -bullet
467.It
468Not change it; this is what
469.Bx
470systems did before the
471.Bx 4.3 tahoe
472release.
473In this case the
474.Tn TTL
475value in the received packet will be 255 minus the
476number of routers in the round-trip path.
477.It
478Set it to 255; this is what current
479.Bx
480systems do.
481In this case the
482.Tn TTL
483value in the received packet will be 255 minus the
484number of routers in the path
485.Em from
486the remote system
487.Em to
488the
489.Nm Ns Em ing
490host.
491.It
492Set it to some other value.
493Some machines use the same value for
494.Tn ICMP
495packets that they use for
496.Tn TCP
497packets, for example either 30 or 60.
498Others may use completely wild values.
499.El
500.Sh RETURN VALUES
501The
502.Nm
503utility returns an exit status of zero if at least one response was
504heard from the specified
505.Ar host ;
506a status of two if the transmission was successful but no responses
507were received; or another value
508(from
509.In sysexits.h )
510if an error occurred.
511.Sh SEE ALSO
512.Xr netstat 1 ,
513.Xr ifconfig 8 ,
514.Xr routed 8 ,
515.Xr traceroute 8
516.Sh HISTORY
517The
518.Nm
519utility appeared in
520.Bx 4.3 .
521.Sh AUTHORS
522The original
523.Nm
524utility was written by
525.An Mike Muuss
526while at the US Army Ballistics
527Research Laboratory.
528.Sh BUGS
529Many Hosts and Gateways ignore the
530.Tn RECORD_ROUTE
531option.
532.Pp
533The maximum IP header length is too small for options like
534.Tn RECORD_ROUTE
535to be completely useful.
536.No There Ap s
537not much that can be done about this, however.
538.Pp
539Flood pinging is not recommended in general, and flood pinging the
540broadcast address should only be done under very controlled conditions.
541.Pp
542The
543.Fl v
544option is not worth much on busy hosts.
545