summaryrefslogtreecommitdiffstats
path: root/sbin/ping6/ping6.8
diff options
context:
space:
mode:
authorume <ume@FreeBSD.org>2003-10-24 18:26:30 +0000
committerume <ume@FreeBSD.org>2003-10-24 18:26:30 +0000
commit881c4fa39150df7d0de2dae7ae808f6a73cb199a (patch)
tree6ce05cb7459c9a9be90d670c12bfddbbbcb6946d /sbin/ping6/ping6.8
parent0b2009d038122fd790a91ca95c5d9044ff2715c0 (diff)
downloadFreeBSD-src-881c4fa39150df7d0de2dae7ae808f6a73cb199a.zip
FreeBSD-src-881c4fa39150df7d0de2dae7ae808f6a73cb199a.tar.gz
Switch Advanced Sockets API for IPv6 from RFC2292 to RFC3542
(aka RFC2292bis). Though I believe this commit doesn't break backward compatibility againt existing binaries, it breaks backward compatibility of API. Now, the applications which use Advanced Sockets API such as telnet, ping6, mld6query and traceroute6 use RFC3542 API. Obtained from: KAME
Diffstat (limited to 'sbin/ping6/ping6.8')
-rw-r--r--sbin/ping6/ping6.8132
1 files changed, 61 insertions, 71 deletions
diff --git a/sbin/ping6/ping6.8 b/sbin/ping6/ping6.8
index 554bf2b..84a51ed 100644
--- a/sbin/ping6/ping6.8
+++ b/sbin/ping6/ping6.8
@@ -1,4 +1,4 @@
-.\" $KAME: ping6.8,v 1.43 2001/06/28 06:54:29 suz Exp $
+.\" $KAME: ping6.8,v 1.58 2003/06/20 12:00:22 itojun Exp $
.\"
.\" Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project.
.\" All rights reserved.
@@ -40,9 +40,9 @@ packets to network hosts
.Sh SYNOPSIS
.Nm
.\" without ipsec, or new ipsec
-.Op Fl dfHnNqRtvwW
+.Op Fl dfHmnNqtvwW
.\" old ipsec
-.\" .Op Fl AdEfnNqRtvwW
+.\" .Op Fl AdEfmnNqRtvwW
.Bk -words
.Op Fl a Ar addrtype
.Ek
@@ -53,6 +53,9 @@ packets to network hosts
.Op Fl c Ar count
.Ek
.Bk -words
+.Op Fl g Ar gateway
+.Ek
+.Bk -words
.Op Fl h Ar hoplimit
.Ek
.Bk -words
@@ -78,7 +81,7 @@ packets to network hosts
.Op Fl s Ar packetsize
.Ek
.Bk -words
-.Op Ar hops...\&
+.Op Ar hops ...
.Ek
.Bk -words
.Ar host
@@ -86,7 +89,7 @@ packets to network hosts
.Sh DESCRIPTION
The
.Nm
-utility uses the
+command uses the
.Tn ICMPv6
protocol's mandatory
.Tn ICMP6_ECHO_REQUEST
@@ -103,14 +106,14 @@ The options are as follows:
.\" old ipsec
.\" .It Fl A
.\" Enables transport-mode IPsec authentication header
-.\" (experimental).
+.\" .Pq experimental .
.It Fl a Ar addrtype
Generate ICMPv6 Node Information Node Addresses query, rather than echo-request.
.Ar addrtype
must be a string constructed of the following characters.
.Bl -tag -width Ds -compact
.It Ic a
-requests all the responder's unicast addresses.
+requests unicast addresses from all of the responder's interfaces.
If the character is omitted,
only those addresses which belong to the interface which has the
responder's address are requests.
@@ -134,7 +137,7 @@ This is an experimental option.
Set socket buffer size.
.It Fl c Ar count
Stop after sending
-(and receiving)
+.Pq and receiving
.Ar count
.Tn ECHO_RESPONSE
packets.
@@ -144,7 +147,7 @@ Set the
option on the socket being used.
.\" .It Fl E
.\" Enables transport-mode IPsec encapsulated security payload
-.\" (experimental).
+.\" .Pq experimental .
.It Fl f
Flood ping.
Outputs packets as fast as they come back or one hundred times per second,
@@ -152,7 +155,7 @@ whichever is more.
For every
.Tn ECHO_REQUEST
sent a period
-.Dq .\&
+.Dq \&.
is printed, while for every
.Tn ECHO_REPLY
received a backspace is printed.
@@ -161,11 +164,16 @@ Only the super-user may use this option.
.Bf -emphasis
This can be very hard on a network and should be used with caution.
.Ef
+.It Fl g Ar gateway
+Specifies to use
+.Ar gateway
+as the next hop to the destination.
+The gateway must be a neighbor of the sending node.
.It Fl H
Specifies to try reverse-lookup of IPv6 addresses.
The
.Nm
-utility does not try reverse-lookup unless the option is specified.
+command does not try reverse-lookup unless the option is specified.
.It Fl h Ar hoplimit
Set the IPv6 hoplimit.
.It Fl I Ar interface
@@ -189,6 +197,16 @@ is specified,
sends that many packets as fast as possible before falling into its normal
mode of behavior.
Only the super-user may use this option.
+.It Fl m
+By default,
+.Nm
+asks the kernel to fragment packets to fit into the minimum IPv6 MTU.
+.Fl m
+will suppress the behavior in the following two levels:
+when the option is specified once, the behavior will be disabled for
+unicast packets.
+When the option is more than once, it will be disabled for both
+unicast and multicast packets.
.It Fl n
Numeric output only.
No attempt will be made to lookup symbolic names from addresses in the reply.
@@ -197,12 +215,12 @@ Probe node information multicast group
.Pq Li ff02::2:xxxx:xxxx .
.Ar host
must be string hostname of the target
-(must not be a numeric IPv6 address).
+.Pq must not be a numeric IPv6 address .
Node information multicast group will be computed based on given
.Ar host ,
and will be used as the final destination.
Since node information multicast group is a link-local multicast group,
-destination link needs to be specified by
+outgoing interface needs to be specified by
.Fl I
option.
.It Fl p Ar pattern
@@ -222,26 +240,10 @@ specifies IPsec policy to be used for the probe.
Quiet output.
Nothing is displayed except the summary lines at startup time and
when finished.
-.It Fl R
-Make the kernel believe that the target
-.Ar host
-(or the first
-.Ar hop
-if you specify
-.Ar hops )
-is reachable, by injecting upper-layer reachability confirmation hint.
-The option is meaningful only if the target
-.Ar host
-(or the first hop)
-is a neighbor.
.It Fl S Ar sourceaddr
Specifies the source address of request packets.
-The source address must be one of the unicast addresses of the sending node.
-If the outgoing interface is specified by the
-.Fl I
-option as well,
-.Ar sourceaddr
-needs to be an address assigned to the specified interface.
+The source address must be one of the unicast addresses of the sending node,
+and must be numeric.
.It Fl s Ar packetsize
Specifies the number of data bytes to be sent.
The default is 56, which translates into 64
@@ -299,26 +301,13 @@ 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 round-trip time statistics.
When the specified number of packets have been sent
-(and received)
+.Pq and received
or if the program is terminated with a
.Dv SIGINT ,
a brief summary is displayed, showing the number of packets sent and
-received, and the minimum, mean, maximum, and standard deviation of
+received, and the minimum, maximum, mean, and standard deviation of
the round-trip times.
.Pp
-If
-.Nm
-receives a
-.Dv SIGINFO
-(see the
-.Cm status
-argument for
-.Xr stty 1 )
-signal, the current number of packets sent and received, and the
-minimum, mean, maximum, and standard deviation of the round-trip times
-will be written to the standard output in the same format as the
-standard completion message.
-.Pp
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
@@ -335,14 +324,12 @@ during normal operations or from automated scripts.
.\" When a
.\" .Ar packetsize
.\" is given, this indicated the size of this extra piece of data
-.\" (the default is 56).
+.\" .Pq the default is 56 .
.\" Thus the amount of data received inside of an IP packet of type
.\" .Tn ICMP
.\" .Tn ECHO_REPLY
.\" will always be 8 bytes more than the requested data space
-.\" (the
-.\" .Tn ICMP
-.\" header).
+.\" .Pq the Tn ICMP header .
.\" .Pp
.\" If the data space is at least eight bytes large,
.\" .Nm
@@ -353,12 +340,12 @@ during normal operations or from automated scripts.
.Sh DUPLICATE AND DAMAGED PACKETS
The
.Nm
-utility will report duplicate and damaged packets.
+command will report duplicate and damaged packets.
Duplicate packets should never occur when pinging a unicast address,
and seem to be caused by
inappropriate link-level retransmissions.
Duplicates may occur in many situations and are rarely
-(if ever)
+.Pq if ever
a good sign, although the presence of low levels of duplicates may not
always be cause for alarm.
Duplicates are expected when pinging a broadcast or multicast address,
@@ -369,7 +356,7 @@ Damaged packets are obviously serious cause for alarm and often
indicate broken hardware somewhere in the
.Nm
packet's path
-(in the network or in the hosts).
+.Pq in the network or in the hosts .
.Sh TRYING DIFFERENT DATA PATTERNS
The
(inter)network
@@ -398,11 +385,10 @@ You can then examine this file for repeated patterns that you can test
using the
.Fl p
option of
-.Nm .
+.Nm Ns .
.Sh RETURN VALUES
-The
.Nm
-utility returns 0 on success (the host is alive),
+command returns 0 on success (the host is alive),
and non-zero if the arguments are incorrect or the host is not responding.
.Sh EXAMPLES
Normally,
@@ -451,11 +437,28 @@ ping6 -a agl dst.foo.com
.Rs
.%A Matt Crawford
.%T "IPv6 Node Information Queries"
-.%N draft-ietf-ipngwg-icmp-name-lookups-07.txt
-.%D August 2000
+.%N draft-ietf-ipngwg-icmp-name-lookups-09.txt
+.%D May 2002
.%O work in progress material
.Re
+.Sh HISTORY
+The
+.Xr ping 8
+command appeared in
+.Bx 4.3 .
+The
+.Nm
+command with IPv6 support first appeared in the WIDE Hydrangea IPv6
+protocol stack kit.
+.Pp
+IPv6 and IPsec support based on the KAME Project (http://www.kame.net/) stack
+was initially integrated into
+.Fx 4.0
.Sh BUGS
+.Nm
+is intentionally separate from
+.Xr ping 8 .
+.Pp
There have been many discussions on why we separate
.Nm
and
@@ -484,16 +487,3 @@ or
.Fl 4
option (or something like those) to specify the particular address family.
This essentially means that we have two different commands.
-.Sh HISTORY
-The
-.Xr ping 8
-command appeared in
-.Bx 4.3 .
-The
-.Nm
-utility with IPv6 support first appeared in WIDE Hydrangea IPv6 protocol stack
-kit.
-.Pp
-IPv6 and IPsec support based on the KAME Project (http://www.kame.net/) stack
-was initially integrated into
-.Fx 4.0
OpenPOWER on IntegriCloud