| ping6.8 (72914) | ping6.8 (78064) |
|---|---|
| 1.\" $KAME: ping6.8,v 1.22 2000/05/31 17:00:07 itojun Exp $ | 1.\" $KAME: ping6.8,v 1.39 2001/04/04 00:08:34 itojun Exp $ |
| 2.\" 3.\" Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project. 4.\" All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright --- 12 unchanged lines hidden (view full) --- 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 28.\" SUCH DAMAGE. 29.\" | 2.\" 3.\" Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project. 4.\" All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright --- 12 unchanged lines hidden (view full) --- 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 28.\" SUCH DAMAGE. 29.\" |
| 30.\" $FreeBSD: head/sbin/ping6/ping6.8 72914 2001-02-22 19:00:51Z ume $ | 30.\" $FreeBSD: head/sbin/ping6/ping6.8 78064 2001-06-11 12:39:29Z ume $ |
| 31.\" 32.Dd May 17, 1998 33.Dt PING6 8 34.Os 35.Sh NAME 36.Nm ping6 37.Nd send 38.Tn ICMPv6 ECHO_REQUEST 39packets to network hosts 40.Sh SYNOPSIS 41.Nm 42.\" without ipsec, or new ipsec | 31.\" 32.Dd May 17, 1998 33.Dt PING6 8 34.Os 35.Sh NAME 36.Nm ping6 37.Nd send 38.Tn ICMPv6 ECHO_REQUEST 39packets to network hosts 40.Sh SYNOPSIS 41.Nm 42.\" without ipsec, or new ipsec |
| 43.Op Fl dfHnNqRvw | 43.Op Fl dfHnNqRtvw |
| 44.\" old ipsec | 44.\" old ipsec |
| 45.\" .Op Fl AdEfnNqRvw | 45.\" .Op Fl AdEfnNqRtvw |
| 46.Bk -words 47.Op Fl a Ar addrtype 48.Ek 49.Bk -words 50.Op Fl b Ar bufsiz 51.Ek 52.Bk -words 53.Op Fl c Ar count --- 125 unchanged lines hidden (view full) --- 179The default is to wait for one second between each packet. 180This option is incompatible with the 181.Fl f 182option. 183.It Fl l Ar preload 184If 185.Ar preload 186is specified, | 46.Bk -words 47.Op Fl a Ar addrtype 48.Ek 49.Bk -words 50.Op Fl b Ar bufsiz 51.Ek 52.Bk -words 53.Op Fl c Ar count --- 125 unchanged lines hidden (view full) --- 179The default is to wait for one second between each packet. 180This option is incompatible with the 181.Fl f 182option. 183.It Fl l Ar preload 184If 185.Ar preload 186is specified, |
| 187.Nm ping | 187.Nm |
| 188sends that many packets as fast as possible before falling into its normal 189mode of behavior. 190Only the super-user may use this option. 191.It Fl n 192Numeric output only. | 188sends that many packets as fast as possible before falling into its normal 189mode of behavior. 190Only the super-user may use this option. 191.It Fl n 192Numeric output only. |
| 193No attempt will be made to lookup symbolic names for host addresses. | 193No attempt will be made to lookup symbolic names from addresses in the reply. |
| 194.It Fl N 195Probe node information multicast group 196.Pq Li ff02::2:xxxx:xxxx . 197.Ar host 198must be string hostname of the target 199.Pq must not be a numeric IPv6 address . 200Node information multicast group will be computed based on given 201.Ar host , --- 6 unchanged lines hidden (view full) --- 208You may specify up to 16 209.Dq pad 210bytes to fill out the packet you send. 211This is useful for diagnosing data-dependent problems in a network. 212For example, 213.Dq Li \-p ff 214will cause the sent packet to be filled with all 215ones. | 194.It Fl N 195Probe node information multicast group 196.Pq Li ff02::2:xxxx:xxxx . 197.Ar host 198must be string hostname of the target 199.Pq must not be a numeric IPv6 address . 200Node information multicast group will be computed based on given 201.Ar host , --- 6 unchanged lines hidden (view full) --- 208You may specify up to 16 209.Dq pad 210bytes to fill out the packet you send. 211This is useful for diagnosing data-dependent problems in a network. 212For example, 213.Dq Li \-p ff 214will cause the sent packet to be filled with all 215ones. |
| 216.Fl Q 217flag, 218.Nm 219prints out any ICMP error messages caused by its own ECHO_REQUEST 220messages. | |
| 221.\" new ipsec 222.It Fl P Ar policy 223.Ar policy 224specifies IPsec policy to be used for the probe. 225.It Fl q 226Quiet output. 227Nothing is displayed except the summary lines at startup time and 228when finished. --- 25 unchanged lines hidden (view full) --- 254.Tn ICMP 255data bytes when combined 256with the 8 bytes of 257.Tn ICMP 258header data. 259You may need to specify 260.Fl b 261as well to extend socket buffer size. | 216.\" new ipsec 217.It Fl P Ar policy 218.Ar policy 219specifies IPsec policy to be used for the probe. 220.It Fl q 221Quiet output. 222Nothing is displayed except the summary lines at startup time and 223when finished. --- 25 unchanged lines hidden (view full) --- 249.Tn ICMP 250data bytes when combined 251with the 8 bytes of 252.Tn ICMP 253header data. 254You may need to specify 255.Fl b 256as well to extend socket buffer size. |
| 257.It Fl t 258Generate ICMPv6 Node Information supported query types query, 259rather than echo-request. 260.Fl s 261has no effect if 262.Fl t 263is specified. |
|
| 262.It Fl v 263Verbose output. 264.Tn ICMP 265packets other than 266.Tn ECHO_RESPONSE 267that are received are listed. 268.It Fl w | 264.It Fl v 265Verbose output. 266.Tn ICMP 267packets other than 268.Tn ECHO_RESPONSE 269that are received are listed. 270.It Fl w |
| 269Generate ICMPv6 Node Information FQDN query, rather than echo-request. | 271Generate ICMPv6 Node Information DNS Name query, rather than echo-request. |
| 270.Fl s 271has no effect if 272.Fl w 273is specified. 274.It Fl W 275Same as 276.Fl w , 277but with old packet format based on 03 draft. --- 52 unchanged lines hidden (view full) --- 330.\" .Pp 331.\" If the data space is at least eight bytes large, 332.\" .Nm 333.\" uses the first eight bytes of this space to include a timestamp which 334.\" it uses in the computation of round trip times. 335.\" If less than eight bytes of pad are specified, no round trip times are 336.\" given. 337.Sh DUPLICATE AND DAMAGED PACKETS | 272.Fl s 273has no effect if 274.Fl w 275is specified. 276.It Fl W 277Same as 278.Fl w , 279but with old packet format based on 03 draft. --- 52 unchanged lines hidden (view full) --- 332.\" .Pp 333.\" If the data space is at least eight bytes large, 334.\" .Nm 335.\" uses the first eight bytes of this space to include a timestamp which 336.\" it uses in the computation of round trip times. 337.\" If less than eight bytes of pad are specified, no round trip times are 338.\" given. 339.Sh DUPLICATE AND DAMAGED PACKETS |
| 338.Nm Ping6 | 340.Nm |
| 339will report duplicate and damaged packets. 340Duplicate packets should never occur when pinging a unicast address, 341and seem to be caused by 342inappropriate link-level retransmissions. 343Duplicates may occur in many situations and are rarely 344.Pq if ever 345a good sign, although the presence of low levels of duplicates may not 346always be cause for alarm. 347Duplicates are expected when pinging a broadcast or multicast address, 348since they are not really duplicates but replies from different hosts 349to the same request. 350.Pp 351Damaged packets are obviously serious cause for alarm and often 352indicate broken hardware somewhere in the | 341will report duplicate and damaged packets. 342Duplicate packets should never occur when pinging a unicast address, 343and seem to be caused by 344inappropriate link-level retransmissions. 345Duplicates may occur in many situations and are rarely 346.Pq if ever 347a good sign, although the presence of low levels of duplicates may not 348always be cause for alarm. 349Duplicates are expected when pinging a broadcast or multicast address, 350since they are not really duplicates but replies from different hosts 351to the same request. 352.Pp 353Damaged packets are obviously serious cause for alarm and often 354indicate broken hardware somewhere in the |
| 353.Nm ping | 355.Nm |
| 354packet's path 355.Pq in the network or in the hosts . 356.Sh TRYING DIFFERENT DATA PATTERNS 357The 358(inter)network 359layer should never treat packets differently depending on the data 360contained in the data portion. 361Unfortunately, data-dependent problems have been known to sneak into --- 19 unchanged lines hidden (view full) --- 381using the 382.Fl p 383option of 384.Nm . 385.Sh RETURN VALUES 386.Nm 387returns 0 on success (the host is alive), 388and non-zero if the arguments are incorrect or the host is not responding. | 356packet's path 357.Pq in the network or in the hosts . 358.Sh TRYING DIFFERENT DATA PATTERNS 359The 360(inter)network 361layer should never treat packets differently depending on the data 362contained in the data portion. 363Unfortunately, data-dependent problems have been known to sneak into --- 19 unchanged lines hidden (view full) --- 383using the 384.Fl p 385option of 386.Nm . 387.Sh RETURN VALUES 388.Nm 389returns 0 on success (the host is alive), 390and non-zero if the arguments are incorrect or the host is not responding. |
| 391.Sh EXAMPLES 392Normally, 393.Xr ping6 8 394works just like 395.Xr ping 8 396would work; the following will send ICMPv6 echo request to 397.Li dst.foo.com . 398.Bd -literal -offset indent 399ping6 -n dst.foo.com 400.Ed 401.Pp 402The following will probe hostnames for all nodes on the network link attached to 403.Li wi0 404interface. 405The address 406.Li ff02::1 407is named the link-local all-node multicast address, and the packet would 408reach every node on the network link. 409.Bd -literal -offset indent 410ping6 -w ff02::1%wi0 411.Ed 412.Pp 413The following will probe addresses assigned to the destination node, 414.Li dst.foo.com . 415.Bd -literal -offset indent 416ping6 -a agl dst.foo.com 417.Ed 418.Pp |
|
| 389.Sh SEE ALSO 390.Xr netstat 1 , | 419.Sh SEE ALSO 420.Xr netstat 1 , |
| 421.Xr icmp6 4 , 422.Xr inet6 4 , 423.Xr ip6 4 , |
|
| 391.Xr ifconfig 8 , 392.Xr ping 8 , 393.Xr routed 8 , 394.Xr traceroute 8 , 395.Xr traceroute6 8 396.Rs 397.%A A. Conta 398.%A S. Deering 399.%T "Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification" 400.%N RFC2463 401.%D December 1998 402.Re 403.Rs 404.%A Matt Crawford 405.%T "IPv6 Node Information Queries" | 424.Xr ifconfig 8 , 425.Xr ping 8 , 426.Xr routed 8 , 427.Xr traceroute 8 , 428.Xr traceroute6 8 429.Rs 430.%A A. Conta 431.%A S. Deering 432.%T "Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification" 433.%N RFC2463 434.%D December 1998 435.Re 436.Rs 437.%A Matt Crawford 438.%T "IPv6 Node Information Queries" |
| 406.%N draft-ietf-ipngwg-icmp-name-lookups-05.txt 407.%D October 22, 1999 | 439.%N draft-ietf-ipngwg-icmp-name-lookups-07.txt 440.%D August 2000 |
| 408.%O work in progress material 409.Re 410.Sh BUGS 411There have been many discussions on why we separate 412.Xr ping6 8 413and 414.Xr ping 8 . 415Some people argued that it would be more convenient to uniform the --- 17 unchanged lines hidden (view full) --- 433command for both IPv4 and IPv6, we would usually type a 434.Fl 6 435or 436.Fl 4 437option (or something like those) to specify the particular address family. 438This essentially means that we have two different commands. 439.Sh HISTORY 440The | 441.%O work in progress material 442.Re 443.Sh BUGS 444There have been many discussions on why we separate 445.Xr ping6 8 446and 447.Xr ping 8 . 448Some people argued that it would be more convenient to uniform the --- 17 unchanged lines hidden (view full) --- 466command for both IPv4 and IPv6, we would usually type a 467.Fl 6 468or 469.Fl 4 470option (or something like those) to specify the particular address family. 471This essentially means that we have two different commands. 472.Sh HISTORY 473The |
| 441.Nm ping | 474.Xr ping 8 |
| 442command appeared in 443.Bx 4.3 . 444The 445.Nm 446command with IPv6 support first appeared in WIDE Hydrangea IPv6 protocol stack 447kit. 448.Pp 449IPv6 and IPsec support based on the KAME Project (http://www.kame.net/) stack 450was initially integrated into 451.Fx 4.0 | 475command appeared in 476.Bx 4.3 . 477The 478.Nm 479command with IPv6 support first appeared in WIDE Hydrangea IPv6 protocol stack 480kit. 481.Pp 482IPv6 and IPsec support based on the KAME Project (http://www.kame.net/) stack 483was initially integrated into 484.Fx 4.0 |