1 .\" $KAME: ping6.8,v 1.58 2003/06/20 12:00:22 itojun 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.24 2007/11/20 01:58:34 dd Exp $
38 .Tn ICMPv6 ECHO_REQUEST
39 packets to network hosts
42 .\" without ipsec, or new ipsec
45 .\" .Op Fl AdEfmnNqRtvwW
78 .Op Fl S Ar sourceaddr
81 .Op Fl s Ar packetsize
98 .Tn ICMP6_ECHO_REQUEST
101 from a host or gateway.
102 .Tn ICMP6_ECHO_REQUEST
103 datagrams (``pings'') have an IPv6 header,
106 header formatted as documented in RFC2463.
107 The options are as follows:
111 .\" Enables transport-mode IPsec authentication header
114 Generate ICMPv6 Node Information Node Addresses query, rather than echo-request.
116 must be a string constructed of the following characters.
117 .Bl -tag -width Ds -compact
119 requests unicast addresses from all of the responder's interfaces.
120 If the character is omitted,
121 only those addresses which belong to the interface which has the
122 responder's address are requests.
124 requests responder's IPv4-compatible and IPv4-mapped addresses.
126 requests responder's global-scope addresses.
128 requests responder's site-local addresses.
130 requests responder's link-local addresses.
132 requests responder's anycast addresses.
133 Without this character, the responder will return unicast addresses only.
134 With this character, the responder will return anycast addresses only.
135 Note that the specification does not specify how to get responder's
137 This is an experimental option.
140 Set socket buffer size.
150 option on the socket being used.
152 .\" Enables transport-mode IPsec encapsulated security payload
156 Outputs packets as fast as they come back or one hundred times per second,
162 is printed, while for every
164 received a backspace is printed.
165 This provides a rapid display of how many packets are being dropped.
166 Only the super-user may use this option.
168 This can be very hard on a network and should be used with caution.
173 as the next hop to the destination.
174 The gateway must be a neighbor of the sending node.
176 Specifies to try reverse-lookup of IPv6 addresses.
179 utility does not try reverse-lookup unless the option is specified.
181 Set the IPv6 hoplimit.
182 .It Fl I Ar interface
183 Source packets with the given interface address.
184 This flag applies if the ping destination is a multicast address,
185 or link-local/site-local unicast address.
190 .Em between sending each packet .
191 The default is to wait for one second between each packet.
192 This option is incompatible with the
200 sends that many packets as fast as possible before falling into its normal
202 Only the super-user may use this option.
206 asks the kernel to fragment packets to fit into the minimum IPv6 MTU.
210 will suppress the behavior in the following two levels:
211 when the option is specified once, the behavior will be disabled for
213 When the option is more than once, it will be disabled for both
214 unicast and multicast packets.
217 No attempt will be made to lookup symbolic names from addresses in the reply.
219 Probe node information multicast group
220 .Pq Li ff02::2:xxxx:xxxx .
222 must be string hostname of the target
223 (must not be a numeric IPv6 address).
224 Node information multicast group will be computed based on given
226 and will be used as the final destination.
227 Since node information multicast group is a link-local multicast group,
228 outgoing interface needs to be specified by
232 Exit successfully after receiving one reply packet.
234 You may specify up to 16
236 bytes to fill out the packet you send.
237 This is useful for diagnosing data-dependent problems in a network.
240 will cause the sent packet to be filled with all
245 specifies IPsec policy to be used for the probe.
248 Nothing is displayed except the summary lines at startup time and
250 .It Fl S Ar sourceaddr
251 Specifies the source address of request packets.
252 The source address must be one of the unicast addresses of the sending node,
254 .It Fl s Ar packetsize
255 Specifies the number of data bytes to be sent.
256 The default is 56, which translates into 64
258 data bytes when combined
262 You may need to specify
264 as well to extend socket buffer size.
266 Generate ICMPv6 Node Information supported query types query,
267 rather than echo-request.
277 that are received are listed.
279 Generate ICMPv6 Node Information DNS Name query, rather than echo-request.
287 but with old packet format based on 03 draft.
288 This option is present for backward compatibility.
294 Use the specified traffic class.
296 IPv6 addresses for intermediate nodes,
297 which will be put into type 0 routing header.
299 IPv6 address of the final destination node.
304 for fault isolation, it should first be run on the local host, to verify
305 that the local network interface is up and running.
306 Then, hosts and gateways further and further away should be
308 Round-trip times and packet loss statistics are computed.
309 If duplicate packets are received, they are not included in the packet
310 loss calculation, although the round trip time of these packets is used
311 in calculating the round-trip time statistics.
312 When the specified number of packets have been sent
314 or if the program is terminated with a
316 a brief summary is displayed, showing the number of packets sent and
317 received, and the minimum, mean, maximum, and standard deviation of
318 the round-trip times.
328 signal, the current number of packets sent and received, and the
329 minimum, mean, maximum, and standard deviation of the round-trip times
330 will be written to the standard output in the same format as the
331 standard completion message.
333 This program is intended for use in network testing, measurement and
335 Because of the load it can impose on the network, it is unwise to use
337 during normal operations or from automated scripts.
338 .\" .Sh ICMP PACKET DETAILS
339 .\" An IP header without options is 20 bytes.
343 .\" packet contains an additional 8 bytes worth of
345 .\" header followed by an arbitrary amount of data.
348 .\" is given, this indicated the size of this extra piece of data
349 .\" (the default is 56).
350 .\" Thus the amount of data received inside of an IP packet of type
353 .\" will always be 8 bytes more than the requested data space
358 .\" If the data space is at least eight bytes large,
360 .\" uses the first eight bytes of this space to include a timestamp which
361 .\" it uses in the computation of round trip times.
362 .\" If less than eight bytes of pad are specified, no round trip times are
364 .Sh DUPLICATE AND DAMAGED PACKETS
367 utility will report duplicate and damaged packets.
368 Duplicate packets should never occur when pinging a unicast address,
369 and seem to be caused by
370 inappropriate link-level retransmissions.
371 Duplicates may occur in many situations and are rarely
373 a good sign, although the presence of low levels of duplicates may not
374 always be cause for alarm.
375 Duplicates are expected when pinging a broadcast or multicast address,
376 since they are not really duplicates but replies from different hosts
379 Damaged packets are obviously serious cause for alarm and often
380 indicate broken hardware somewhere in the
383 (in the network or in the hosts).
384 .Sh TRYING DIFFERENT DATA PATTERNS
387 layer should never treat packets differently depending on the data
388 contained in the data portion.
389 Unfortunately, data-dependent problems have been known to sneak into
390 networks and remain undetected for long periods of time.
391 In many cases the particular pattern that will have problems is something
392 that does not have sufficient
394 such as all ones or all zeros, or a pattern right at the edge, such as
397 necessarily enough to specify a data pattern of all zeros (for example)
398 on the command line because the pattern that is of interest is
399 at the data link level, and the relationship between what you type and
400 what the controllers transmit can be complicated.
402 This means that if you have a data-dependent problem you will probably
403 have to do a lot of testing to find it.
404 If you are lucky, you may manage to find a file that either
406 be sent across your network or that takes much longer to transfer than
407 other similar length files.
408 You can then examine this file for repeated patterns that you can test
416 utility returns 0 on success (the host is alive),
417 and non-zero if the arguments are incorrect or the host is not responding.
423 would work; the following will send ICMPv6 echo request to
425 .Bd -literal -offset indent
429 The following will probe hostnames for all nodes on the network link attached to
434 is named the link-local all-node multicast address, and the packet would
435 reach every node on the network link.
436 .Bd -literal -offset indent
440 The following will probe addresses assigned to the destination node,
442 .Bd -literal -offset indent
443 ping6 -a agl dst.foo.com
458 .%T "Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification"
464 .%T "IPv6 Node Information Queries"
465 .%N draft-ietf-ipngwg-icmp-name-lookups-09.txt
467 .%O work in progress material
476 utility with IPv6 support first appeared in the WIDE Hydrangea IPv6
479 IPv6 and IPsec support based on the KAME Project
480 .Pq Pa http://www.kame.net/
481 stack was initially integrated into
487 is intentionally separate from
490 There have been many discussions on why we separate
494 Some people argued that it would be more convenient to uniform the
495 ping command for both IPv4 and IPv6.
496 The followings are an answer to the request.
498 From a developer's point of view:
499 since the underling raw sockets API is totally different between IPv4
500 and IPv6, we would end up having two types of code base.
501 There would actually be less benefit to uniform the two commands
502 into a single command from the developer's standpoint.
504 From an operator's point of view: unlike ordinary network applications
505 like remote login tools, we are usually aware of address family when using
506 network management tools.
507 We do not just want to know the reachability to the host, but want to know the
508 reachability to the host via a particular network protocol such as
510 Thus, even if we had a unified
512 command for both IPv4 and IPv6, we would usually type a
516 option (or something like those) to specify the particular address family.
517 This essentially means that we have two different commands.
projects / apple / network_cmds.git / blob