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