| ping.8 (22990) | ping.8 (23247) |
|---|---|
| 1.\" Copyright (c) 1985, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 16 unchanged lines hidden (view full) --- 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" @(#)ping.8 8.2 (Berkeley) 12/11/93 | 1.\" Copyright (c) 1985, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 16 unchanged lines hidden (view full) --- 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" @(#)ping.8 8.2 (Berkeley) 12/11/93 |
| 33.\" $Id$ | 33.\" $Id: ping.8,v 1.7 1997/02/22 14:33:06 peter Exp $ |
| 34.\" | 34.\" |
| 35.Dd December 11, 1993 | 35.Dd March 1, 1997 |
| 36.Dt PING 8 37.Os BSD 4.3 38.Sh NAME 39.Nm ping 40.Nd send 41.Tn ICMP ECHO_REQUEST 42packets to network hosts 43.Sh SYNOPSIS --- 105 unchanged lines hidden (view full) --- 149.It Fl R 150Record route. 151Includes the 152.Tn RECORD_ROUTE 153option in the 154.Tn ECHO_REQUEST 155packet and displays 156the route buffer on returned packets. | 36.Dt PING 8 37.Os BSD 4.3 38.Sh NAME 39.Nm ping 40.Nd send 41.Tn ICMP ECHO_REQUEST 42packets to network hosts 43.Sh SYNOPSIS --- 105 unchanged lines hidden (view full) --- 149.It Fl R 150Record route. 151Includes the 152.Tn RECORD_ROUTE 153option in the 154.Tn ECHO_REQUEST 155packet and displays 156the route buffer on returned packets. |
| 157Note that the IP header is only large enough for nine such routes. 158Many hosts ignore or discard this option. | 157Note that the IP header is only large enough for nine such routes; 158the 159.Xr traceroute 8 160command is usually better at determining the route packets take to a 161particular destination. 162Many hosts ignore or discard the 163.Tn RECORD_ROUTE 164option. |
| 159.It Fl r 160Bypass the normal routing tables and send directly to a host on an attached 161network. 162If the host is not on a directly-attached network, an error is returned. 163This option can be used to ping a local host through an interface 164that has no route through it (e.g., after the interface was dropped by 165.Xr routed 8 ) . 166.It Fl s Ar packetsize --- 165 unchanged lines hidden (view full) --- 332Set it to some other value. 333Some machines use the same value for 334.Tn ICMP 335packets that they use for 336.Tn TCP 337packets, for example either 30 or 60. 338Others may use completely wild values. 339.El | 165.It Fl r 166Bypass the normal routing tables and send directly to a host on an attached 167network. 168If the host is not on a directly-attached network, an error is returned. 169This option can be used to ping a local host through an interface 170that has no route through it (e.g., after the interface was dropped by 171.Xr routed 8 ) . 172.It Fl s Ar packetsize --- 165 unchanged lines hidden (view full) --- 338Set it to some other value. 339Some machines use the same value for 340.Tn ICMP 341packets that they use for 342.Tn TCP 343packets, for example either 30 or 60. 344Others may use completely wild values. 345.El |
| 346.Sh RETURN VALUES 347The 348.Nm ping 349command returns an exit status of zero if at least one response was 350heard from the specified 351.Ar host ; 352a status of two if the transmission was successful but no responses 353were received; or another value 354.Pq from Aq Pa sysexits.h 355if an error occurred. 356.Sh SEE ALSO 357.Xr netstat 1 , 358.Xr ifconfig 8 , 359.Xr routed 8 , 360.Xr traceroute 8 361.Sh HISTORY 362The 363.Nm 364command appeared in 365.Bx 4.3 . 366.Sh AUTHORS 367The original 368.Nm 369command was written by Mike Muuss while at the US Army Ballistics 370Research Laboratory. |
|
| 340.Sh BUGS 341Many Hosts and Gateways ignore the 342.Tn RECORD_ROUTE 343option. 344.Pp 345The maximum IP header length is too small for options like 346.Tn RECORD_ROUTE 347to 348be completely useful. 349There's not much that can be done about this, however. 350.Pp 351Flood pinging is not recommended in general, and flood pinging the 352broadcast address should only be done under very controlled conditions. 353.Pp 354The 355.Fl v 356option is not worth much on busy hosts. | 371.Sh BUGS 372Many Hosts and Gateways ignore the 373.Tn RECORD_ROUTE 374option. 375.Pp 376The maximum IP header length is too small for options like 377.Tn RECORD_ROUTE 378to 379be completely useful. 380There's not much that can be done about this, however. 381.Pp 382Flood pinging is not recommended in general, and flood pinging the 383broadcast address should only be done under very controlled conditions. 384.Pp 385The 386.Fl v 387option is not worth much on busy hosts. |
| 357.Sh SEE ALSO 358.Xr netstat 1 , 359.Xr ifconfig 8 , 360.Xr routed 8 361.Sh HISTORY 362The 363.Nm 364command appeared in 365.Bx 4.3 . | |