Clarify and correct the description of the -R (Record Route) flag.
Reviewed by jnemeth, whith help from him.
This commit is contained in:
parent
2716ac0eba
commit
d8e5c31820
|
@ -1,4 +1,4 @@
|
|||
.\" $NetBSD: ping.8,v 1.46 2006/03/21 09:54:12 pavel Exp $
|
||||
.\" $NetBSD: ping.8,v 1.47 2006/03/21 22:54:46 pavel Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1985, 1991, 1993
|
||||
.\" The Regents of the University of California. All rights reserved.
|
||||
|
@ -210,8 +210,10 @@ Includes the
|
|||
option in the
|
||||
.Tn ECHO_REQUEST
|
||||
packet and displays the route buffer on returned packets.
|
||||
Note that the IP header is only large enough for eight such routes,
|
||||
and only six when using the
|
||||
This should show the path to the target host and back, which is
|
||||
especially useful in the case of asymmetric routing.
|
||||
Note that the IP header is only large enough for nine such addresses,
|
||||
and only seven when using the
|
||||
.Fl g
|
||||
option.
|
||||
This is why it was necessary to invent
|
||||
|
|
Loading…
Reference in New Issue