1 .\" $KAME: ping6.8,v 1.43 2001/06/28 06:54:29 suz Exp $
3 .\" Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project.
4 .\" All rights reserved.
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
9 .\" 1. Redistributions of source code must retain the above copyright
10 .\" notice, this list of conditions and the following disclaimer.
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in the
13 .\" documentation and/or other materials provided with the distribution.
14 .\" 3. Neither the name of the project nor the names of its contributors
15 .\" may be used to endorse or promote products derived from this software
16 .\" without specific prior written permission.
18 .\" THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND
19 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE
22 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
23 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
24 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
26 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
27 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30 .\" $FreeBSD: src/sbin/ping6/ping6.8,v 1.3.2.12 2003/02/24 00:56:42 trhodes Exp $
38 .Tn ICMPv6 ECHO_REQUEST
39 packets to network hosts
42 .\" without ipsec, or new ipsec
45 .\" .Op Fl AdEfnNqRtvwW
75 .Op Fl S Ar sourceaddr
78 .Op Fl s Ar packetsize
92 .Tn ICMP6_ECHO_REQUEST
95 from a host or gateway.
96 .Tn ICMP6_ECHO_REQUEST
97 datagrams (``pings'') have an IPv6 header,
100 header formatted as documented in RFC2463.
101 The options are as follows:
105 .\" Enables transport-mode IPsec authentication header
108 Generate ICMPv6 Node Information Node Addresses query, rather than echo-request.
110 must be a string constructed of the following characters.
111 .Bl -tag -width Ds -compact
113 requests all the responder's unicast addresses.
114 If the character is omitted,
115 only those addresses which belong to the interface which has the
116 responder's address are requests.
118 requests responder's IPv4-compatible and IPv4-mapped addresses.
120 requests responder's global-scope addresses.
122 requests responder's site-local addresses.
124 requests responder's link-local addresses.
126 requests responder's anycast addresses.
127 Without this character, the responder will return unicast addresses only.
128 With this character, the responder will return anycast addresses only.
129 Note that the specification does not specify how to get responder's
131 This is an experimental option.
134 Set socket buffer size.
144 option on the socket being used.
146 .\" Enables transport-mode IPsec encapsulated security payload
150 Outputs packets as fast as they come back or one hundred times per second,
156 is printed, while for every
158 received a backspace is printed.
159 This provides a rapid display of how many packets are being dropped.
160 Only the super-user may use this option.
162 This can be very hard on a network and should be used with caution.
165 Specifies to try reverse-lookup of IPv6 addresses.
168 utility does not try reverse-lookup unless the option is specified.
170 Set the IPv6 hoplimit.
171 .It Fl I Ar interface
172 Source packets with the given interface address.
173 This flag applies if the ping destination is a multicast address,
174 or link-local/site-local unicast address.
179 .Em between sending each packet .
180 The default is to wait for one second between each packet.
181 This option is incompatible with the
189 sends that many packets as fast as possible before falling into its normal
191 Only the super-user may use this option.
194 No attempt will be made to lookup symbolic names from addresses in the reply.
196 Probe node information multicast group
197 .Pq Li ff02::2:xxxx:xxxx .
199 must be string hostname of the target
200 (must not be a numeric IPv6 address).
201 Node information multicast group will be computed based on given
203 and will be used as the final destination.
204 Since node information multicast group is a link-local multicast group,
205 destination link needs to be specified by
209 You may specify up to 16
211 bytes to fill out the packet you send.
212 This is useful for diagnosing data-dependent problems in a network.
215 will cause the sent packet to be filled with all
220 specifies IPsec policy to be used for the probe.
223 Nothing is displayed except the summary lines at startup time and
226 Make the kernel believe that the target
232 is reachable, by injecting upper-layer reachability confirmation hint.
233 The option is meaningful only if the target
237 .It Fl S Ar sourceaddr
238 Specifies the source address of request packets.
239 The source address must be one of the unicast addresses of the sending node.
240 If the outgoing interface is specified by the
244 needs to be an address assigned to the specified interface.
245 .It Fl s Ar packetsize
246 Specifies the number of data bytes to be sent.
247 The default is 56, which translates into 64
249 data bytes when combined
253 You may need to specify
255 as well to extend socket buffer size.
257 Generate ICMPv6 Node Information supported query types query,
258 rather than echo-request.
268 that are received are listed.
270 Generate ICMPv6 Node Information DNS Name query, rather than echo-request.
278 but with old packet format based on 03 draft.
279 This option is present for backward compatibility.
285 IPv6 addresses for intermediate nodes,
286 which will be put into type 0 routing header.
288 IPv6 address of the final destination node.
293 for fault isolation, it should first be run on the local host, to verify
294 that the local network interface is up and running.
295 Then, hosts and gateways further and further away should be
297 Round-trip times and packet loss statistics are computed.
298 If duplicate packets are received, they are not included in the packet
299 loss calculation, although the round trip time of these packets is used
300 in calculating the round-trip time statistics.
301 When the specified number of packets have been sent
303 or if the program is terminated with a
305 a brief summary is displayed, showing the number of packets sent and
306 received, and the minimum, mean, maximum, and standard deviation of
307 the round-trip times.
317 signal, the current number of packets sent and received, and the
318 minimum, mean, maximum, and standard deviation of the round-trip times
319 will be written to the standard output in the same format as the
320 standard completion message.
322 This program is intended for use in network testing, measurement and
324 Because of the load it can impose on the network, it is unwise to use
326 during normal operations or from automated scripts.
327 .\" .Sh ICMP PACKET DETAILS
328 .\" An IP header without options is 20 bytes.
332 .\" packet contains an additional 8 bytes worth of
334 .\" header followed by an arbitrary amount of data.
337 .\" is given, this indicated the size of this extra piece of data
338 .\" (the default is 56).
339 .\" Thus the amount of data received inside of an IP packet of type
342 .\" will always be 8 bytes more than the requested data space
347 .\" If the data space is at least eight bytes large,
349 .\" uses the first eight bytes of this space to include a timestamp which
350 .\" it uses in the computation of round trip times.
351 .\" If less than eight bytes of pad are specified, no round trip times are
353 .Sh DUPLICATE AND DAMAGED PACKETS
356 utility will report duplicate and damaged packets.
357 Duplicate packets should never occur when pinging a unicast address,
358 and seem to be caused by
359 inappropriate link-level retransmissions.
360 Duplicates may occur in many situations and are rarely
362 a good sign, although the presence of low levels of duplicates may not
363 always be cause for alarm.
364 Duplicates are expected when pinging a broadcast or multicast address,
365 since they are not really duplicates but replies from different hosts
368 Damaged packets are obviously serious cause for alarm and often
369 indicate broken hardware somewhere in the
372 (in the network or in the hosts).
373 .Sh TRYING DIFFERENT DATA PATTERNS
376 layer should never treat packets differently depending on the data
377 contained in the data portion.
378 Unfortunately, data-dependent problems have been known to sneak into
379 networks and remain undetected for long periods of time.
380 In many cases the particular pattern that will have problems is something
381 that does not have sufficient
383 such as all ones or all zeros, or a pattern right at the edge, such as
386 necessarily enough to specify a data pattern of all zeros (for example)
387 on the command line because the pattern that is of interest is
388 at the data link level, and the relationship between what you type and
389 what the controllers transmit can be complicated.
391 This means that if you have a data-dependent problem you will probably
392 have to do a lot of testing to find it.
393 If you are lucky, you may manage to find a file that either
395 be sent across your network or that takes much longer to transfer than
396 other similar length files.
397 You can then examine this file for repeated patterns that you can test
405 utility returns 0 on success (the host is alive),
406 and non-zero if the arguments are incorrect or the host is not responding.
412 would work; the following will send ICMPv6 echo request to
414 .Bd -literal -offset indent
418 The following will probe hostnames for all nodes on the network link attached to
423 is named the link-local all-node multicast address, and the packet would
424 reach every node on the network link.
425 .Bd -literal -offset indent
429 The following will probe addresses assigned to the destination node,
431 .Bd -literal -offset indent
432 ping6 -a agl dst.foo.com
447 .%T "Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification"
453 .%T "IPv6 Node Information Queries"
454 .%N draft-ietf-ipngwg-icmp-name-lookups-07.txt
456 .%O work in progress material
459 There have been many discussions on why we separate
463 Some people argued that it would be more convenient to uniform the
464 ping command for both IPv4 and IPv6.
465 The followings are an answer to the request.
467 From a developer's point of view:
468 since the underling raw sockets API is totally different between IPv4
469 and IPv6, we would end up having two types of code base.
470 There would actually be less benefit to uniform the two commands
471 into a single command from the developer's standpoint.
473 From an operator's point of view: unlike ordinary network applications
474 like remote login tools, we are usually aware of address family when using
475 network management tools.
476 We do not just want to know the reachability to the host, but want to know the
477 reachability to the host via a particular network protocol such as
479 Thus, even if we had a unified
481 command for both IPv4 and IPv6, we would usually type a
485 option (or something like those) to specify the particular address family.
486 This essentially means that we have two different commands.
494 utility with IPv6 support first appeared in WIDE Hydrangea IPv6 protocol stack
497 IPv6 and IPsec support based on the KAME Project (http://www.kame.net/) stack
498 was initially integrated into
uqs's projects / games.git / blob