xref: /freebsd/sbin/ping/ping.8 (revision 3642298923e528d795e3a30ec165d2b469e28b40)
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. The default value is 1.
163.It Fl I Ar iface
164Source multicast packets with the given interface address.
165This flag only applies if the ping destination is a multicast address.
166.It Fl i Ar wait
167Wait
168.Ar wait
169seconds
170.Em between sending each packet .
171The default is to wait for one second between each packet.
172The wait time may be fractional, but only the super-user may specify
173values less than 1 second.
174This option is incompatible with the
175.Fl f
176option.
177.It Fl L
178Suppress loopback of multicast packets.
179This flag only applies if the ping destination is a multicast address.
180.It Fl l Ar preload
181If
182.Ar preload
183is specified,
184.Nm
185sends that many packets as fast as possible before falling into its normal
186mode of behavior.
187Only the super-user may use this option.
188.It Fl M Cm mask | time
189Use
190.Dv ICMP_MASKREQ
191or
192.Dv ICMP_TSTAMP
193instead of
194.Dv ICMP_ECHO .
195For
196.Cm mask ,
197print the netmask of the remote machine.
198Set the
199.Va net.inet.icmp.maskrepl
200MIB variable to enable
201.Dv ICMP_MASKREPLY .
202For
203.Cm time ,
204print the origination, reception and transmission timestamps.
205.It Fl m Ar ttl
206Set the IP Time To Live for outgoing packets.
207If not specified, the kernel uses the value of the
208.Va net.inet.ip.ttl
209MIB variable.
210.It Fl n
211Numeric output only.
212No attempt will be made to lookup symbolic names for host addresses.
213.It Fl o
214Exit successfully after receiving one reply packet.
215.It Fl P Ar policy
216.Ar policy
217specifies IPsec policy for the ping session.
218For details please refer to
219.Xr ipsec 4
220and
221.Xr ipsec_set_policy 3 .
222.It Fl p Ar pattern
223You may specify up to 16
224.Dq pad
225bytes to fill out the packet you send.
226This is useful for diagnosing data-dependent problems in a network.
227For example,
228.Dq Li \-p ff
229will cause the sent packet to be filled with all
230ones.
231.It Fl Q
232Somewhat quiet output.
233.No Don Ap t
234display ICMP error messages that are in response to our query messages.
235Originally, the
236.Fl v
237flag was required to display such errors, but
238.Fl v
239displays all ICMP error messages.
240On a busy machine, this output can be overbearing.
241Without the
242.Fl Q
243flag,
244.Nm
245prints out any ICMP error messages caused by its own ECHO_REQUEST
246messages.
247.It Fl q
248Quiet output.
249Nothing is displayed except the summary lines at startup time and
250when finished.
251.It Fl R
252Record route.
253Includes the
254.Tn RECORD_ROUTE
255option in the
256.Tn ECHO_REQUEST
257packet and displays
258the route buffer on returned packets.
259Note that the IP header is only large enough for nine such routes;
260the
261.Xr traceroute 8
262command is usually better at determining the route packets take to a
263particular destination.
264If more routes come back than should, such as due to an illegal spoofed
265packet, ping will print the route list and then truncate it at the correct
266spot.
267Many hosts ignore or discard the
268.Tn RECORD_ROUTE
269option.
270.It Fl r
271Bypass the normal routing tables and send directly to a host on an attached
272network.
273If the host is not on a directly-attached network, an error is returned.
274This option can be used to ping a local host through an interface
275that has no route through it
276(e.g., after the interface was dropped by
277.Xr routed 8 ) .
278.It Fl S Ar src_addr
279Use the following IP address as the source address in outgoing packets.
280On hosts with more than one IP address, this option can be used to
281force the source address to be something other than the IP address
282of the interface the probe packet is sent on.
283If the IP address
284is not one of this machine's interface addresses, an error is
285returned and nothing is sent.
286.It Fl s Ar packetsize
287Specify the number of data bytes to be sent.
288The default is 56, which translates into 64
289.Tn ICMP
290data bytes when combined
291with the 8 bytes of
292.Tn ICMP
293header data.
294Only the super-user may specify values more than default.
295This option cannot be used with ping sweeps.
296.It Fl T Ar ttl
297Set the IP Time To Live for multicasted packets.
298This flag only applies if the ping destination is a multicast address.
299.It Fl t Ar timeout
300Specify a timeout, in seconds, before ping exits regardless of how
301many packets have been received.
302.It Fl v
303Verbose output.
304.Tn ICMP
305packets other than
306.Tn ECHO_RESPONSE
307that are received are listed.
308.It Fl z Ar tos
309Use the specified type of service.
310.El
311.Pp
312When using
313.Nm
314for fault isolation, it should first be run on the local host, to verify
315that the local network interface is up and running.
316Then, hosts and gateways further and further away should be
317.Dq pinged .
318Round-trip times and packet loss statistics are computed.
319If duplicate packets are received, they are not included in the packet
320loss calculation, although the round trip time of these packets is used
321in calculating the round-trip time statistics.
322When the specified number of packets have been sent
323(and received)
324or if the program is terminated with a
325.Dv SIGINT ,
326a brief summary is displayed, showing the number of packets sent and
327received, and the minimum, mean, maximum, and standard deviation of
328the round-trip times.
329.Pp
330If
331.Nm
332receives a
333.Dv SIGINFO
334(see the
335.Cm status
336argument for
337.Xr stty 1 )
338signal, the current number of packets sent and received, and the
339minimum, mean, and maximum of the round-trip times will be written to
340the standard error output.
341.Pp
342This program is intended for use in network testing, measurement and
343management.
344Because of the load it can impose on the network, it is unwise to use
345.Nm
346during normal operations or from automated scripts.
347.Sh ICMP PACKET DETAILS
348An IP header without options is 20 bytes.
349An
350.Tn ICMP
351.Tn ECHO_REQUEST
352packet contains an additional 8 bytes worth of
353.Tn ICMP
354header followed by an arbitrary amount of data.
355When a
356.Ar packetsize
357is given, this indicated the size of this extra piece of data
358(the default is 56).
359Thus the amount of data received inside of an IP packet of type
360.Tn ICMP
361.Tn ECHO_REPLY
362will always be 8 bytes more than the requested data space
363(the
364.Tn ICMP
365header).
366.Pp
367If the data space is at least eight bytes large,
368.Nm
369uses the first eight bytes of this space to include a timestamp which
370it uses in the computation of round trip times.
371If less than eight bytes of pad are specified, no round trip times are
372given.
373.Sh DUPLICATE AND DAMAGED PACKETS
374The
375.Nm
376utility will report duplicate and damaged packets.
377Duplicate packets should never occur when pinging a unicast address,
378and seem to be caused by
379inappropriate link-level retransmissions.
380Duplicates may occur in many situations and are rarely
381(if ever)
382a good sign, although the presence of low levels of duplicates may not
383always be cause for alarm.
384Duplicates are expected when pinging a broadcast or multicast address,
385since they are not really duplicates but replies from different hosts
386to the same request.
387.Pp
388Damaged packets are obviously serious cause for alarm and often
389indicate broken hardware somewhere in the
390.Nm
391packet's path (in the network or in the hosts).
392.Sh TRYING DIFFERENT DATA PATTERNS
393The
394(inter)network
395layer should never treat packets differently depending on the data
396contained in the data portion.
397Unfortunately, data-dependent problems have been known to sneak into
398networks and remain undetected for long periods of time.
399In many cases the particular pattern that will have problems is something
400that does not have sufficient
401.Dq transitions ,
402such as all ones or all zeros, or a pattern right at the edge, such as
403almost all zeros.
404It is not
405necessarily enough to specify a data pattern of all zeros (for example)
406on the command line because the pattern that is of interest is
407at the data link level, and the relationship between what you type and
408what the controllers transmit can be complicated.
409.Pp
410This means that if you have a data-dependent problem you will probably
411have to do a lot of testing to find it.
412If you are lucky, you may manage to find a file that either
413cannot
414be sent across your network or that takes much longer to transfer than
415other similar length files.
416You can then examine this file for repeated patterns that you can test
417using the
418.Fl p
419option of
420.Nm .
421.Sh TTL DETAILS
422The
423.Tn TTL
424value of an IP packet represents the maximum number of IP routers
425that the packet can go through before being thrown away.
426In current practice you can expect each router in the Internet to decrement
427the
428.Tn TTL
429field by exactly one.
430.Pp
431The
432.Tn TCP/IP
433specification recommends setting the
434.Tn TTL
435field for
436.Tn IP
437packets to 64, but many systems use smaller values
438.No ( Bx 4.3
439uses 30,
440.Bx 4.2
441used 15).
442.Pp
443The maximum possible value of this field is 255, and most
444.Ux
445systems set
446the
447.Tn TTL
448field of
449.Tn ICMP ECHO_REQUEST
450packets to 255.
451This is why you will find you can
452.Dq ping
453some hosts, but not reach them with
454.Xr telnet 1
455or
456.Xr ftp 1 .
457.Pp
458In normal operation
459.Nm
460prints the ttl value from the packet it receives.
461When a remote system receives a ping packet, it can do one of three things
462with the
463.Tn TTL
464field in its response:
465.Bl -bullet
466.It
467Not change it; this is what
468.Bx
469systems did before the
470.Bx 4.3 tahoe
471release.
472In this case the
473.Tn TTL
474value in the received packet will be 255 minus the
475number of routers in the round-trip path.
476.It
477Set it to 255; this is what current
478.Bx
479systems do.
480In this case the
481.Tn TTL
482value in the received packet will be 255 minus the
483number of routers in the path
484.Em from
485the remote system
486.Em to
487the
488.Nm Ns Em ing
489host.
490.It
491Set it to some other value.
492Some machines use the same value for
493.Tn ICMP
494packets that they use for
495.Tn TCP
496packets, for example either 30 or 60.
497Others may use completely wild values.
498.El
499.Sh RETURN VALUES
500The
501.Nm
502utility returns an exit status of zero if at least one response was
503heard from the specified
504.Ar host ;
505a status of two if the transmission was successful but no responses
506were received; or another value
507(from
508.In sysexits.h )
509if an error occurred.
510.Sh SEE ALSO
511.Xr netstat 1 ,
512.Xr ifconfig 8 ,
513.Xr routed 8 ,
514.Xr traceroute 8
515.Sh HISTORY
516The
517.Nm
518utility appeared in
519.Bx 4.3 .
520.Sh AUTHORS
521The original
522.Nm
523utility was written by
524.An Mike Muuss
525while at the US Army Ballistics
526Research Laboratory.
527.Sh BUGS
528Many Hosts and Gateways ignore the
529.Tn RECORD_ROUTE
530option.
531.Pp
532The maximum IP header length is too small for options like
533.Tn RECORD_ROUTE
534to be completely useful.
535.No There Ap s
536not much that can be done about this, however.
537.Pp
538Flood pinging is not recommended in general, and flood pinging the
539broadcast address should only be done under very controlled conditions.
540.Pp
541The
542.Fl v
543option is not worth much on busy hosts.
544