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
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
95 .Tn ICMP6_ECHO_REQUEST
98 from a host or gateway.
99 .Tn ICMP6_ECHO_REQUEST
100 datagrams (``pings'') have an IPv6 header,
103 header formatted as documented in RFC2463.
104 The options are as follows:
108 .\" Enables transport-mode IPsec authentication header
111 Generate ICMPv6 Node Information Node Addresses query, rather than echo-request.
113 must be a string constructed of the following characters.
114 .Bl -tag -width Ds -compact
116 requests unicast addresses from all of the responder's interfaces.
117 If the character is omitted,
118 only those addresses which belong to the interface which has the
119 responder's address are requests.
121 requests responder's IPv4-compatible and IPv4-mapped addresses.
123 requests responder's global-scope addresses.
125 requests responder's site-local addresses.
127 requests responder's link-local addresses.
129 requests responder's anycast addresses.
130 Without this character, the responder will return unicast addresses only.
131 With this character, the responder will return anycast addresses only.
132 Note that the specification does not specify how to get responder's
134 This is an experimental option.
137 Set socket buffer size.
147 option on the socket being used.
149 .\" Enables transport-mode IPsec encapsulated security payload
153 Outputs packets as fast as they come back or one hundred times per second,
159 is printed, while for every
161 received a backspace is printed.
162 This provides a rapid display of how many packets are being dropped.
163 Only the super-user may use this option.
165 This can be very hard on a network and should be used with caution.
170 as the next hop to the destination.
171 The gateway must be a neighbor of the sending node.
173 Specifies to try reverse-lookup of IPv6 addresses.
176 utility does not try reverse-lookup unless the option is specified.
178 Set the IPv6 hoplimit.
179 .It Fl I Ar interface
180 Source packets with the given interface address.
181 This flag applies if the ping destination is a multicast address,
182 or link-local/site-local unicast address.
187 .Em between sending each packet .
188 The default is to wait for one second between each packet.
189 This option is incompatible with the
197 sends that many packets as fast as possible before falling into its normal
199 Only the super-user may use this option.
203 asks the kernel to fragment packets to fit into the minimum IPv6 MTU.
207 will suppress the behavior in the following two levels:
208 when the option is specified once, the behavior will be disabled for
210 When the option is more than once, it will be disabled for both
211 unicast and multicast packets.
214 No attempt will be made to lookup symbolic names from addresses in the reply.
216 Probe node information multicast group
217 .Pq Li ff02::2:xxxx:xxxx .
219 must be string hostname of the target
220 (must not be a numeric IPv6 address).
221 Node information multicast group will be computed based on given
223 and will be used as the final destination.
224 Since node information multicast group is a link-local multicast group,
225 outgoing interface needs to be specified by
229 You may specify up to 16
231 bytes to fill out the packet you send.
232 This is useful for diagnosing data-dependent problems in a network.
235 will cause the sent packet to be filled with all
240 specifies IPsec policy to be used for the probe.
243 Nothing is displayed except the summary lines at startup time and
245 .It Fl S Ar sourceaddr
246 Specifies the source address of request packets.
247 The source address must be one of the unicast addresses of the sending node,
249 .It Fl s Ar packetsize
250 Specifies the number of data bytes to be sent.
251 The default is 56, which translates into 64
253 data bytes when combined
257 You may need to specify
259 as well to extend socket buffer size.
261 Generate ICMPv6 Node Information supported query types query,
262 rather than echo-request.
272 that are received are listed.
274 Generate ICMPv6 Node Information DNS Name query, rather than echo-request.
282 but with old packet format based on 03 draft.
283 This option is present for backward compatibility.
289 IPv6 addresses for intermediate nodes,
290 which will be put into type 0 routing header.
292 IPv6 address of the final destination node.
297 for fault isolation, it should first be run on the local host, to verify
298 that the local network interface is up and running.
299 Then, hosts and gateways further and further away should be
301 Round-trip times and packet loss statistics are computed.
302 If duplicate packets are received, they are not included in the packet
303 loss calculation, although the round trip time of these packets is used
304 in calculating the round-trip time statistics.
305 When the specified number of packets have been sent
307 or if the program is terminated with a
309 a brief summary is displayed, showing the number of packets sent and
310 received, and the minimum, mean, maximum, and standard deviation of
311 the round-trip times.
321 signal, the current number of packets sent and received, and the
322 minimum, mean, maximum, and standard deviation of the round-trip times
323 will be written to the standard output in the same format as the
324 standard completion message.
326 This program is intended for use in network testing, measurement and
328 Because of the load it can impose on the network, it is unwise to use
330 during normal operations or from automated scripts.
331 .\" .Sh ICMP PACKET DETAILS
332 .\" An IP header without options is 20 bytes.
336 .\" packet contains an additional 8 bytes worth of
338 .\" header followed by an arbitrary amount of data.
341 .\" is given, this indicated the size of this extra piece of data
342 .\" (the default is 56).
343 .\" Thus the amount of data received inside of an IP packet of type
346 .\" will always be 8 bytes more than the requested data space
351 .\" If the data space is at least eight bytes large,
353 .\" uses the first eight bytes of this space to include a timestamp which
354 .\" it uses in the computation of round trip times.
355 .\" If less than eight bytes of pad are specified, no round trip times are
357 .Sh DUPLICATE AND DAMAGED PACKETS
360 utility will report duplicate and damaged packets.
361 Duplicate packets should never occur when pinging a unicast address,
362 and seem to be caused by
363 inappropriate link-level retransmissions.
364 Duplicates may occur in many situations and are rarely
366 a good sign, although the presence of low levels of duplicates may not
367 always be cause for alarm.
368 Duplicates are expected when pinging a broadcast or multicast address,
369 since they are not really duplicates but replies from different hosts
372 Damaged packets are obviously serious cause for alarm and often
373 indicate broken hardware somewhere in the
376 (in the network or in the hosts).
377 .Sh TRYING DIFFERENT DATA PATTERNS
380 layer should never treat packets differently depending on the data
381 contained in the data portion.
382 Unfortunately, data-dependent problems have been known to sneak into
383 networks and remain undetected for long periods of time.
384 In many cases the particular pattern that will have problems is something
385 that does not have sufficient
387 such as all ones or all zeros, or a pattern right at the edge, such as
390 necessarily enough to specify a data pattern of all zeros (for example)
391 on the command line because the pattern that is of interest is
392 at the data link level, and the relationship between what you type and
393 what the controllers transmit can be complicated.
395 This means that if you have a data-dependent problem you will probably
396 have to do a lot of testing to find it.
397 If you are lucky, you may manage to find a file that either
399 be sent across your network or that takes much longer to transfer than
400 other similar length files.
401 You can then examine this file for repeated patterns that you can test
409 utility returns 0 on success (the host is alive),
410 and non-zero if the arguments are incorrect or the host is not responding.
416 would work; the following will send ICMPv6 echo request to
418 .Bd -literal -offset indent
422 The following will probe hostnames for all nodes on the network link attached to
427 is named the link-local all-node multicast address, and the packet would
428 reach every node on the network link.
429 .Bd -literal -offset indent
433 The following will probe addresses assigned to the destination node,
435 .Bd -literal -offset indent
436 ping6 -a agl dst.foo.com
451 .%T "Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification"
457 .%T "IPv6 Node Information Queries"
458 .%N draft-ietf-ipngwg-icmp-name-lookups-09.txt
460 .%O work in progress material
469 utility with IPv6 support first appeared in the WIDE Hydrangea IPv6
472 IPv6 and IPsec support based on the KAME Project
473 .Pq Pa http://www.kame.net/
474 stack was initially integrated into
480 is intentionally separate from
483 There have been many discussions on why we separate
487 Some people argued that it would be more convenient to uniform the
488 ping command for both IPv4 and IPv6.
489 The followings are an answer to the request.
491 From a developer's point of view:
492 since the underling raw sockets API is totally different between IPv4
493 and IPv6, we would end up having two types of code base.
494 There would actually be less benefit to uniform the two commands
495 into a single command from the developer's standpoint.
497 From an operator's point of view: unlike ordinary network applications
498 like remote login tools, we are usually aware of address family when using
499 network management tools.
500 We do not just want to know the reachability to the host, but want to know the
501 reachability to the host via a particular network protocol such as
503 Thus, even if we had a unified
505 command for both IPv4 and IPv6, we would usually type a
509 option (or something like those) to specify the particular address family.
510 This essentially means that we have two different commands.
projects / FreeBSD / FreeBSD.git / blob