Debian Codegraph @

upstream/debian-unstable/man8/ping.8

raw
1 '\" t
2 .TH "PING" "8" "" "iputils 20250605" "iputils"
3 .\" -----------------------------------------------------------------
4 .\" * Define some portability stuff
5 .\" -----------------------------------------------------------------
6 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7 .\" http://bugs.debian.org/507673
8 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
9 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10 .ie \n(.g .ds Aq \(aq
11 .el .ds Aq '
12 .\" -----------------------------------------------------------------
13 .\" * set default formatting
14 .\" -----------------------------------------------------------------
15 .\" disable hyphenation
16 .nh
17 .\" disable justification (adjust text to left margin only)
18 .ad l
19 .\" -----------------------------------------------------------------
20 .\" * MAIN CONTENT STARTS HERE *
21 .\" -----------------------------------------------------------------
22 .SH "NAME"
23 ping \- send ICMP ECHO_REQUEST to network hosts
24 .SH "SYNOPSIS"
25 .HP \w'\fBping\fR\ 'u
26 \fBping\fR [\fB\-aAbBdCDfhHLnOqrRUvV346\fR] [\fB\-c\ \fR\fB\fIcount\fR\fR] [\fB\-e\ \fR\fB\fIidentifier\fR\fR] [\fB\-F\ \fR\fB\fIflowlabel\fR\fR] [\fB\-i\ \fR\fB\fIinterval\fR\fR] [\fB\-I\ \fR\fB\fIinterface\fR\fR] [\fB\-l\ \fR\fB\fIpreload\fR\fR] [\fB\-m\ \fR\fB\fImark\fR\fR] [\fB\-M\ \fR\fB\fIpmtudisc_option\fR\fR] [\fB\-N\ \fR\fB\fInodeinfo_option\fR\fR] [\fB\-w\ \fR\fB\fIdeadline\fR\fR] [\fB\-W\ \fR\fB\fItimeout\fR\fR] [\fB\-p\ \fR\fB\fIpattern\fR\fR] [\fB\-Q\ \fR\fB\fItos\fR\fR] [\fB\-s\ \fR\fB\fIpacketsize\fR\fR] [\fB\-S\ \fR\fB\fIsndbuf\fR\fR] [\fB\-t\ \fR\fB\fIttl\fR\fR] [\fB\-T\ \fR\fB\fItimestamp\ option\fR\fR] [hop\&.\&.\&.] {destination}
27 .SH "DESCRIPTION"
28 .PP
29 \fBping\fR
30 uses the ICMP protocol\*(Aqs mandatory ECHO_REQUEST datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway\&. ECHO_REQUEST datagrams (\(lqpings\(rq) have an IP and ICMP header, followed by a struct timeval and then an arbitrary number of \(lqpad\(rq bytes used to fill out the packet\&.
31 .PP
32 \fBping\fR
33 works with both IPv4 and IPv6\&. Using only one of them explicitly can be enforced by specifying
34 \fB\-4\fR
35 or
36 \fB\-6\fR\&.
37 .PP
38 \fBping\fR
39 can also send IPv6 Node Information Queries (RFC4620)\&. Intermediate
40 \fIhop\fRs may not be allowed, because IPv6 source routing was deprecated (RFC5095)\&.
41 .SH "OPTIONS"
42 .PP
43 \fB\-3\fR
44 .RS 4
45 RTT precision (do not round up the result time)\&.
46 .RE
47 .PP
48 \fB\-4\fR
49 .RS 4
50 Use IPv4 only\&.
51 .RE
52 .PP
53 \fB\-6\fR
54 .RS 4
55 Use IPv6 only\&.
56 .RE
57 .PP
58 \fB\-a\fR
59 .RS 4
60 Audible ping\&.
61 .RE
62 .PP
63 \fB\-A\fR
64 .RS 4
65 Adaptive ping\&. Interpacket interval adapts to round\-trip time, so that effectively not more than one (or more, if preload is set) unanswered probe is present in the network\&. The default interval is 2 ms, for more info see option
66 \fB\-i\fR\&. On networks with low RTT this mode is essentially equivalent to flood mode\&.
67 .RE
68 .PP
69 \fB\-b\fR
70 .RS 4
71 Allow pinging a broadcast address\&.
72 .RE
73 .PP
74 \fB\-B\fR
75 .RS 4
76 Do not allow
77 \fBping\fR
78 to change source address of probes\&. The address is bound to one selected when
79 \fBping\fR
80 starts\&.
81 .RE
82 .PP
83 \fB\-c\fR \fIcount\fR
84 .RS 4
85 Stop after sending
86 \fIcount\fR
87 ECHO_REQUEST packets\&. With
88 \fIdeadline\fR
89 option,
90 \fBping\fR
91 waits for
92 \fIcount\fR
93 ECHO_REPLY packets, until the timeout expires\&.
94 .RE
95 .PP
96 \fB\-C\fR
97 .RS 4
98 Call connect() syscall on socket creation\&.
99 .RE
100 .PP
101 \fB\-d\fR
102 .RS 4
103 Set the SO_DEBUG option on the socket being used\&. Essentially, this socket option is not used by Linux kernel\&.
104 .RE
105 .PP
106 \fB\-D\fR
107 .RS 4
108 Print timestamp (unix time + microseconds as in gettimeofday) before each line\&.
109 .RE
110 .PP
111 \fB\-e\fR \fIidentifier\fR
112 .RS 4
113 Set the identification field of ECHO_REQUEST\&. Value 0 implies using
114 \fIraw socket\fR
115 (not supported on
116 \fIICMP datagram socket\fR)\&. The value of the field may be printed with
117 \fB\-v\fR
118 option\&.
119 .RE
120 .PP
121 \fB\-f\fR
122 .RS 4
123 Flood ping\&. For every ECHO_REQUEST sent a period \(lq\&.\(rq is printed, while for every ECHO_REPLY received a backspace is printed\&. This provides a rapid display of how many packets are being dropped\&. If interval is not given, it sets interval to zero and outputs packets as fast as they come back or one hundred times per second, whichever is more\&. Only the super\-user may use this option with zero interval\&.
124 .RE
125 .PP
126 \fB\-F\fR \fIflow label\fR
127 .RS 4
128 IPv6 only\&. Allocate and set 20 bit flow label (in hex) on echo request packets\&. If value is zero, kernel allocates random flow label\&.
129 .RE
130 .PP
131 \fB\-h\fR
132 .RS 4
133 Show help\&.
134 .RE
135 .PP
136 \fB\-H\fR
137 .RS 4
138 Force DNS name resolution for the output\&. Useful for numeric destination, or
139 \fB\-f\fR
140 option, which by default do not perform it\&. It can also help to workaround DNS resolution problems\&. Override previously defined
141 \fB\-n\fR
142 option\&. See also
143 \fIIPUTILS_PING_PTR_LOOKUP\fR
144 environment variable\&.
145 .RE
146 .PP
147 \fB\-i\fR \fIinterval\fR
148 .RS 4
149 Wait
150 \fIinterval\fR
151 seconds between sending each packet\&. Real number allowed with dot as a decimal separator (regardless locale setup)\&. The default is to wait for one second between each packet normally, or not to wait in flood mode\&. Only super\-user may set interval to values less than 2 ms\&. Broadcast and multicast ping have even higher limitation for regular user: minimum is 1 sec\&.
152 .RE
153 .PP
154 \fB\-I\fR \fIinterface\fR
155 .RS 4
156 \fIinterface\fR
157 is either an address, an interface name or a VRF name\&. If
158 \fIinterface\fR
159 is an address, it sets source address to specified interface address\&. If
160 \fIinterface\fR
161 is an interface name, it sets source interface to specified interface\&. If
162 \fIinterface\fR
163 is a VRF name, each packet is routed using the corresponding routing table; in this case, the
164 \fB\-I\fR
165 option can be repeated to specify a source address\&. NOTE: For IPv6, when doing ping to a link\-local scope address, link specification (by the \*(Aq%\*(Aq\-notation in
166 \fIdestination\fR, or by this option) can be used but it is no longer required\&.
167 .RE
168 .PP
169 \fB\-l\fR \fIpreload\fR
170 .RS 4
171 If
172 \fIpreload\fR
173 is specified,
174 \fBping\fR
175 sends that many packets not waiting for reply\&. Only the super\-user may select preload more than 3\&.
176 .RE
177 .PP
178 \fB\-L\fR
179 .RS 4
180 Suppress loopback of multicast packets\&. This flag only applies if the ping destination is a multicast address\&.
181 .RE
182 .PP
183 \fB\-m\fR \fImark\fR
184 .RS 4
185 use
186 \fImark\fR
187 to tag the packets going out\&. This is useful for variety of reasons within the kernel such as using policy routing to select specific outbound processing\&. CAP_NET_ADMIN or CAP_NET_RAW (since Linux 5\&.17) capability is required, see
188 \fBsocket\fR(7)\&.
189 .RE
190 .PP
191 \fB\-M\fR \fIpmtudisc_opt\fR
192 .RS 4
193 Select Path MTU Discovery strategy\&.
194 \fIpmtudisc_option\fR
195 may be either
196 \fIdo\fR
197 (set DF flag but subject to PMTU checks by kernel, packets too large will be rejected),
198 \fIwant\fR
199 (do PMTU discovery, fragment locally when packet size is large),
200 \fIprobe\fR
201 (set DF flag and bypass PMTU checks, useful for probing), or
202 \fIdont\fR
203 (do not set DF flag)\&.
204 .RE
205 .PP
206 \fB\-N\fR \fInodeinfo_option\fR
207 .RS 4
208 IPv6 only\&. Send IPv6 Node Information Queries (RFC4620), instead of Echo Request\&. CAP_NET_RAW capability is required\&.
209 .PP
210 \fBhelp\fR
211 .RS 4
212 Show help for NI support\&.
213 .RE
214 .PP
215 \fBname\fR
216 .RS 4
217 Queries for Node Names\&.
218 .RE
219 .PP
220 \fBipv6\fR
221 .RS 4
222 Queries for IPv6 Addresses\&. There are several IPv6 specific flags\&.
223 .PP
224 \fBipv6\-global\fR
225 .RS 4
226 Request IPv6 global\-scope addresses\&.
227 .RE
228 .PP
229 \fBipv6\-sitelocal\fR
230 .RS 4
231 Request IPv6 site\-local addresses\&.
232 .RE
233 .PP
234 \fBipv6\-linklocal\fR
235 .RS 4
236 Request IPv6 link\-local addresses\&.
237 .RE
238 .PP
239 \fBipv6\-all\fR
240 .RS 4
241 Request IPv6 addresses on other interfaces\&.
242 .RE
243 .RE
244 .PP
245 \fBipv4\fR
246 .RS 4
247 Queries for IPv4 Addresses\&. There is one IPv4 specific flag\&.
248 .PP
249 \fBipv4\-all\fR
250 .RS 4
251 Request IPv4 addresses on other interfaces\&.
252 .RE
253 .RE
254 .PP
255 \fBsubject\-ipv6=\fR\fIipv6addr\fR
256 .RS 4
257 IPv6 subject address\&.
258 .RE
259 .PP
260 \fBsubject\-ipv4=\fR\fIipv4addr\fR
261 .RS 4
262 IPv4 subject address\&.
263 .RE
264 .PP
265 \fBsubject\-name=\fR\fInodename\fR
266 .RS 4
267 Subject name\&. If it contains more than one dot, fully\-qualified domain name is assumed\&.
268 .RE
269 .PP
270 \fBsubject\-fqdn=\fR\fInodename\fR
271 .RS 4
272 Subject name\&. Fully\-qualified domain name is always assumed\&.
273 .RE
274 .RE
275 .PP
276 \fB\-n\fR
277 .RS 4
278 Numeric output only\&. No attempt will be made to lookup symbolic names for host addresses (no reverse DNS resolution)\&. This is the default for numeric destination or
279 \fB\-f\fR
280 option\&. Override previously defined
281 \fB\-H\fR
282 option\&. See also
283 \fIIPUTILS_PING_PTR_LOOKUP\fR
284 environment variable\&.
285 .RE
286 .PP
287 \fB\-O\fR
288 .RS 4
289 Report outstanding ICMP ECHO reply before sending next packet\&. This is useful together with the timestamp
290 \fB\-D\fR
291 to log output to a diagnostic file and search for missing answers\&.
292 .RE
293 .PP
294 \fB\-p\fR \fIpattern\fR
295 .RS 4
296 You may specify up to 16 \(lqpad\(rq bytes to fill out the packet you send\&. This is useful for diagnosing data\-dependent problems in a network\&. For example,
297 \fB\-p ff\fR
298 will cause the sent packet to be filled with all ones\&.
299 .RE
300 .PP
301 \fB\-q\fR
302 .RS 4
303 Quiet output\&. Nothing is displayed except the summary lines at startup time and when finished\&.
304 .RE
305 .PP
306 \fB\-Q\fR \fItos\fR
307 .RS 4
308 Set Quality of Service \-related bits in ICMP datagrams\&.
309 \fItos\fR
310 can be decimal (\fBping\fR
311 only) or hex number\&.
312 .sp
313 In RFC2474, these fields are interpreted as 8\-bit Differentiated Services (DS), consisting of: bits 0\-1 (2 lowest bits) of separate data, and bits 2\-7 (highest 6 bits) of Differentiated Services Codepoint (DSCP)\&. In RFC2481 and RFC3168, bits 0\-1 are used for ECN\&.
314 .sp
315 Historically (RFC1349, obsoleted by RFC2474), these were interpreted as: bit 0 (lowest bit) for reserved (currently being redefined as congestion control), 1\-4 for Type of Service and bits 5\-7 (highest bits) for Precedence\&.
316 .RE
317 .PP
318 \fB\-r\fR
319 .RS 4
320 Bypass the normal routing tables and send directly to a host on an attached interface\&. If the host is not on a directly\-attached network, an error is returned\&. This option can be used to ping a local host through an interface that has no route through it provided the option
321 \fB\-I\fR
322 is also used\&.
323 .RE
324 .PP
325 \fB\-R\fR
326 .RS 4
327 \fBping\fR
328 only\&. Record route\&. Includes the RECORD_ROUTE option in the ECHO_REQUEST packet and displays the route buffer on returned packets\&. Note that the IP header is only large enough for nine such routes\&. Many hosts ignore or discard this option\&.
329 .RE
330 .PP
331 \fB\-s\fR \fIpacketsize\fR
332 .RS 4
333 Specifies the number of data bytes to be sent\&. The default is 56, which translates into 64 ICMP data bytes when combined with the 8 bytes of ICMP header data\&. The maximum allowed value is 65507 for IPv4 (65467 when
334 \fB\-R\fR
335 or
336 \fB\-T\fR
337 or Intermediate
338 \fIhop\fRs) or 65527 for IPv6, but most systems limit this to a smaller, system\-dependent number\&.
339 .RE
340 .PP
341 \fB\-S\fR \fIsndbuf\fR
342 .RS 4
343 Set socket sndbuf\&. If not specified, it is selected to buffer not more than one packet\&.
344 .RE
345 .PP
346 \fB\-t\fR \fIttl\fR
347 .RS 4
348 \fBping\fR
349 only\&. Set the IP Time to Live\&.
350 .RE
351 .PP
352 \fB\-T\fR \fItimestamp option\fR
353 .RS 4
354 Set special IP timestamp options\&.
355 \fItimestamp option\fR
356 may be either
357 \fItsonly\fR
358 (only timestamps),
359 \fItsandaddr\fR
360 (timestamps and addresses) or
361 \fItsprespec host1 [host2 [host3 [host4]]]\fR
362 (timestamp prespecified hops)\&.
363 .RE
364 .PP
365 \fB\-U\fR
366 .RS 4
367 Print full user\-to\-user latency (the old behaviour)\&. Normally
368 \fBping\fR
369 prints network round trip time, which can be different f\&.e\&. due to DNS failures\&.
370 .RE
371 .PP
372 \fB\-v\fR
373 .RS 4
374 Verbose output\&. Do not suppress DUP replies when pinging multicast address\&.
375 .RE
376 .PP
377 \fB\-V\fR
378 .RS 4
379 Show version and exit\&.
380 .RE
381 .PP
382 \fB\-w\fR \fIdeadline\fR
383 .RS 4
384 Specify a timeout, in seconds, before
385 \fBping\fR
386 exits regardless of how many packets have been sent or received\&. In this case
387 \fBping\fR
388 does not stop after
389 \fIcount\fR
390 packet are sent, it waits either for
391 \fIdeadline\fR
392 expire or until
393 \fIcount\fR
394 probes are answered or for some error notification from network\&.
395 .RE
396 .PP
397 \fB\-W\fR \fItimeout\fR
398 .RS 4
399 Time to wait for a response, in seconds\&. The option affects only timeout in absence of any responses, otherwise
400 \fBping\fR
401 waits for two RTTs\&. Real number allowed with dot as a decimal separator (regardless locale setup)\&. 0 means infinite timeout\&.
402 .RE
403 .PP
404 When using
405 \fBping\fR
406 for fault isolation, it should first be run on the local host, to verify that the local network interface is up and running\&. Then, hosts and gateways further and further away should be \(lqpinged\(rq\&. Round\-trip times and packet loss statistics are computed\&. If duplicate packets are received, they are not included in the packet loss calculation, although the round trip time of these packets is used in calculating the minimum/average/maximum/mdev round\-trip time numbers\&.
407 .PP
408 Population standard deviation (mdev), essentially an average of how far each ping RTT is from the mean RTT\&. The higher mdev is, the more variable the RTT is (over time)\&. With a high RTT variability, you will have speed issues with bulk transfers (they will take longer than is strictly speaking necessary, as the variability will eventually cause the sender to wait for ACKs) and you will have middling to poor VoIP quality\&.
409 .PP
410 When the specified number of packets have been sent (and received) or if the program is terminated with a SIGINT, a brief summary is displayed\&. Shorter current statistics can be obtained without termination of process with signal SIGQUIT\&.
411 .PP
412 This program is intended for use in network testing, measurement and management\&. Because of the load it can impose on the network, it is unwise to use
413 \fBping\fR
414 during normal operations or from automated scripts\&.
415 .SH "ENVIRONMENT"
416 .PP
417 \fIIPUTILS_PING_PTR_LOOKUP\fR
418 environment variable set to 0 disable reverse DNS resolution (PTR lookup) by default\&. It will be overrided by
419 \fB\-H\fR
420 or
421 \fB\-n\fR
422 option\&.
423 .SH "EXIT STATUS"
424 .PP
425 If
426 \fBping\fR
427 does not receive any reply packets at all it will exit with code 1\&. If a packet
428 \fIcount\fR
429 and
430 \fIdeadline\fR
431 are both specified, and fewer than
432 \fIcount\fR
433 packets are received by the time the
434 \fIdeadline\fR
435 has arrived, it will also exit with code 1\&. On other error it exits with code 2\&. Otherwise it exits with code 0\&. This makes it possible to use the exit code to see if a host is alive or not\&.
436 .SH "IPV6 LINK\-LOCAL DESTINATIONS"
437 .PP
438 For IPv6, when the destination address has link\-local scope and
439 \fBping\fR
440 is using
441 \fIICMP datagram sockets\fR, the output interface must be specified\&. When
442 \fBping\fR
443 is using
444 \fIraw sockets\fR, it is not strictly necessary to specify the output interface but it should be done to avoid ambiguity when there are multiple possible output interfaces\&.
445 .PP
446 There are two ways to specify the output interface:
447 .PP
448 \(bu using the \fI% notation\fR
449 .RS 4
450 The destination address is postfixed with
451 \fI%\fR
452 and the output interface name or ifindex, for example:
453 .sp
454 \fBping fe80::5054:ff:fe70:67bc%eth0\fR
455 .sp
456 \fBping fe80::5054:ff:fe70:67bc%2\fR
457 .RE
458 .PP
459 \(bu using the \fI\-I option\fR
460 .RS 4
461 When using
462 \fIICMP datagram sockets\fR, this method is supported since the following kernel versions: 5\&.17, 5\&.15\&.19, 5\&.10\&.96, 5\&.4\&.176, 4\&.19\&.228, 4\&.14\&.265\&. Also it is not supported on musl libc\&.
463 .RE
464 .SH "ICMP PACKET DETAILS"
465 .PP
466 An IP header without options is 20 bytes\&. An ICMP ECHO_REQUEST packet contains an additional 8 bytes worth of ICMP header followed by an arbitrary amount of data\&. When a
467 \fIpacketsize\fR
468 is given, this indicates the size of this extra piece of data (the default is 56)\&. Thus the amount of data received inside of an IP packet of type ICMP ECHO_REPLY will always be 8 bytes more than the requested data space (the ICMP header)\&.
469 .PP
470 If the data space is at least of size of struct timeval
471 \fBping\fR
472 uses the beginning bytes of this space to include a timestamp which it uses in the computation of round trip times\&. If the data space is shorter, no round trip times are given\&.
473 .SH "DUPLICATE AND DAMAGED PACKETS"
474 .PP
475 \fBping\fR
476 will report duplicate and damaged packets\&. Duplicate packets should never occur, and seem to be caused by inappropriate link\-level retransmissions\&. Duplicates may occur in many situations and are rarely (if ever) a good sign, although the presence of low levels of duplicates may not always be cause for alarm\&.
477 .PP
478 Damaged packets are obviously serious cause for alarm and often indicate broken hardware somewhere in the
479 \fBping\fR
480 packet\*(Aqs path (in the network or in the hosts)\&.
481 .SH "ID COLLISIONS"
482 .PP
483 Unlike TCP and UDP, which use port to uniquely identify the recipient to deliver data, ICMP uses identifier field (ID) for identification\&. Therefore, if on the same machine, at the same time, two ping processes use the same ID, echo reply can be delivered to a wrong recipient\&. This is a known problem due to the limited size of the 16\-bit ID field\&. That is a historical limitation of the protocol that cannot be fixed at the moment unless we encode an ID into the ping packet payload\&.
484 \fBping\fR
485 prints
486 \fIDIFFERENT ADDRESS\fR
487 error and packet loss is negative\&.
488 .PP
489 \fBping\fR
490 uses PID to get unique number\&. The default value of
491 \fI/proc/sys/kernel/pid_max\fR
492 is 32768\&. On the systems that use ping heavily and with
493 \fIpid_max\fR
494 greater than 65535 collisions are bound to happen\&.
495 .SH "TRYING DIFFERENT DATA PATTERNS"
496 .PP
497 The (inter)network layer should never treat packets differently depending on the data contained in the data portion\&. Unfortunately, data\-dependent problems have been known to sneak into networks and remain undetected for long periods of time\&. In many cases the particular pattern that will have problems is something that doesn\*(Aqt have sufficient \(lqtransitions\(rq, such as all ones or all zeros, or a pattern right at the edge, such as almost all zeros\&. It isn\*(Aqt necessarily enough to specify a data pattern of all zeros (for example) on the command line because the pattern that is of interest is at the data link level, and the relationship between what you type and what the controllers transmit can be complicated\&.
498 .PP
499 This means that if you have a data\-dependent problem you will probably have to do a lot of testing to find it\&. If you are lucky, you may manage to find a file that either can\*(Aqt be sent across your network or that takes much longer to transfer than other similar length files\&. You can then examine this file for repeated patterns that you can test using the
500 \fB\-p\fR
501 option of
502 \fBping\fR\&.
503 .SH "TTL DETAILS"
504 .PP
505 The TTL value of an IP packet represents the maximum number of IP routers that the packet can go through before being thrown away\&. In current practice you can expect each router in the Internet to decrement the TTL field by exactly one\&.
506 .PP
507 The TTL field for TCP packets may take various values\&. The maximum possible value of this field is 255, a recommended initial value is 64\&. For more information, see the TCP/Lower\-Level Interface section of RFC9293\&.
508 .PP
509 In normal operation
510 \fBping\fR
511 prints the TTL value from the packet it receives\&. When a remote system receives a ping packet, it can do one of three things with the TTL field in its response:
512 .PP
513 .RS 4
514 \(bu Not change it; this is what Berkeley Unix systems did before the 4\&.3BSD Tahoe release\&. In this case the TTL value in the received packet will be 255 minus the number of routers in the round\-trip path\&.
515 .RE
516 .PP
517 .RS 4
518 \(bu Set it to 255; this is what current Berkeley Unix systems do\&. In this case the TTL value in the received packet will be 255 minus the number of routers in the path
519 \fBfrom\fR
520 the remote system
521 \fBto\fR
522 the
523 \fBping\fRing host\&.
524 .RE
525 .PP
526 .RS 4
527 \(bu Set it to some other value\&. Some machines use the same value for ICMP packets that they use for TCP packets, for example either 30 or 60\&. Others may use completely wild values\&.
528 .RE
529 .SH "BUGS"
530 .PP
531 .RS 4
532 \(bu Many Hosts and Gateways ignore the RECORD_ROUTE option\&.
533 .RE
534 .PP
535 .RS 4
536 \(bu The maximum IP header length is too small for options like RECORD_ROUTE to be completely useful\&. There\*(Aqs not much that can be done about this, however\&.
537 .RE
538 .PP
539 .RS 4
540 \(bu Flood pinging is not recommended in general, and flood pinging the broadcast address should only be done under very controlled conditions\&.
541 .RE
542 .SH "SEE ALSO"
543 .PP
544 \fBip\fR(8),
545 \fBss\fR(8)\&.
546 .SH "HISTORY"
547 .PP
548 The
549 \fBping\fR
550 command appeared in 4\&.3BSD\&.
551 .PP
552 The version described here is its descendant specific to Linux\&.
553 .PP
554 As of version s20150815, the
555 \fBping6\fR
556 binary doesn\*(Aqt exist anymore\&. It has been merged into
557 \fBping\fR\&. Creating a symlink named
558 \fBping6\fR
559 pointing to
560 \fBping\fR
561 will result in the same functionality as before\&.
562 .SH "SECURITY"
563 .PP
564 \fBping\fR
565 requires CAP_NET_RAW capability to be executed 1) if the program is used for non\-echo queries (see
566 \fB\-N\fR
567 option) or when the identification field set to 0 for ECHO_REQUEST (see
568 \fB\-e\fR), or 2) if kernel does not support ICMP datagram sockets, or 3) if the user is not allowed to create an ICMP echo socket\&. The program may be used as set\-uid root\&.
569 .SH "AVAILABILITY"
570 .PP
571 \fBping\fR
572 is part of
573 \fIiputils\fR
574 package\&.