[9163b06] | 1 | Submitted By: William Harrington <kb0iic at cross-lfs dot org>
|
---|
| 2 | Date: 2015-08-30
|
---|
| 3 | Initial Package Version: s20150815
|
---|
| 4 | Upstream Status: Applied
|
---|
| 5 | Origin: git://git.linux-ipv6.org/gitroot/iputils.git
|
---|
| 6 | Description: Edits Makefile USE_ Variables and includes man pages.
|
---|
| 7 |
|
---|
| 8 | diff -Naur iputils-s20150815.orig/Makefile iputils-s20150815/Makefile
|
---|
| 9 | --- iputils-s20150815.orig/Makefile 2015-08-15 14:07:28.000000000 +0000
|
---|
| 10 | +++ iputils-s20150815/Makefile 2015-08-24 00:28:16.063196187 +0000
|
---|
| 11 | @@ -27,7 +27,7 @@
|
---|
| 12 | # sysfs support (with libsysfs - deprecated) [no|yes|static]
|
---|
| 13 | USE_SYSFS=no
|
---|
| 14 | # IDN support [yes|no|static]
|
---|
| 15 | -USE_IDN=yes
|
---|
| 16 | +USE_IDN=no
|
---|
| 17 |
|
---|
| 18 | # Do not use getifaddrs [no|yes|static]
|
---|
| 19 | WITHOUT_IFADDRS=no
|
---|
| 20 | @@ -35,7 +35,7 @@
|
---|
| 21 | ARPING_DEFAULT_DEVICE=
|
---|
| 22 |
|
---|
| 23 | # nettle library for ipv6 ping [yes|no|static]
|
---|
| 24 | -USE_NETTLE=yes
|
---|
| 25 | +USE_NETTLE=no
|
---|
| 26 | # libgcrypt library for ipv6 ping [no|yes|static]
|
---|
| 27 | USE_GCRYPT=no
|
---|
| 28 | # Crypto library for ping6 [shared|static|no]
|
---|
| 29 | diff -Naur iputils-s20150815.orig/doc/arping.8 iputils-s20150815/doc/arping.8
|
---|
| 30 | --- iputils-s20150815.orig/doc/arping.8 1970-01-01 00:00:00.000000000 +0000
|
---|
| 31 | +++ iputils-s20150815/doc/arping.8 2015-08-24 00:27:12.254377152 +0000
|
---|
| 32 | @@ -0,0 +1,109 @@
|
---|
| 33 | +.\" This manpage has been automatically generated by docbook2man
|
---|
| 34 | +.\" from a DocBook document. This tool can be found at:
|
---|
| 35 | +.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
---|
| 36 | +.\" Please send any bug reports, improvements, comments, patches,
|
---|
| 37 | +.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
---|
| 38 | +.TH "ARPING" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
|
---|
| 39 | +.SH NAME
|
---|
| 40 | +arping \- send ARP REQUEST to a neighbour host
|
---|
| 41 | +.SH SYNOPSIS
|
---|
| 42 | +
|
---|
| 43 | +\fBarping\fR [\fB-AbDfhqUV\fR] [\fB-c \fIcount\fB\fR] [\fB-w \fIdeadline\fB\fR] [\fB-s \fIsource\fB\fR] \fB-I \fIinterface\fB\fR \fB\fIdestination\fB\fR
|
---|
| 44 | +
|
---|
| 45 | +.SH "DESCRIPTION"
|
---|
| 46 | +.PP
|
---|
| 47 | +Ping \fIdestination\fR on device \fIinterface\fR by ARP packets,
|
---|
| 48 | +using source address \fIsource\fR.
|
---|
| 49 | +.SH "OPTIONS"
|
---|
| 50 | +.TP
|
---|
| 51 | +\fB-A\fR
|
---|
| 52 | +The same as \fB-U\fR, but ARP REPLY packets used instead
|
---|
| 53 | +of ARP REQUEST.
|
---|
| 54 | +.TP
|
---|
| 55 | +\fB-b\fR
|
---|
| 56 | +Send only MAC level broadcasts. Normally \fBarping\fR starts
|
---|
| 57 | +from sending broadcast, and switch to unicast after reply received.
|
---|
| 58 | +.TP
|
---|
| 59 | +\fB-c \fIcount\fB\fR
|
---|
| 60 | +Stop after sending \fIcount\fR ARP REQUEST
|
---|
| 61 | +packets. With
|
---|
| 62 | +\fIdeadline\fR
|
---|
| 63 | +option, instead wait for
|
---|
| 64 | +\fIcount\fR ARP REPLY packets, or until the timeout expires.
|
---|
| 65 | +.TP
|
---|
| 66 | +\fB-D\fR
|
---|
| 67 | +Duplicate address detection mode (DAD). See
|
---|
| 68 | +RFC2131, 4.4.1.
|
---|
| 69 | +Returns 0, if DAD succeeded i.e. no replies are received
|
---|
| 70 | +.TP
|
---|
| 71 | +\fB-f\fR
|
---|
| 72 | +Finish after the first reply confirming that target is alive.
|
---|
| 73 | +.TP
|
---|
| 74 | +\fB-I \fIinterface\fB\fR
|
---|
| 75 | +Name of network device where to send ARP REQUEST packets.
|
---|
| 76 | +.TP
|
---|
| 77 | +\fB-h\fR
|
---|
| 78 | +Print help page and exit.
|
---|
| 79 | +.TP
|
---|
| 80 | +\fB-q\fR
|
---|
| 81 | +Quiet output. Nothing is displayed.
|
---|
| 82 | +.TP
|
---|
| 83 | +\fB-s \fIsource\fB\fR
|
---|
| 84 | +IP source address to use in ARP packets.
|
---|
| 85 | +If this option is absent, source address is:
|
---|
| 86 | +.RS
|
---|
| 87 | +.TP 0.2i
|
---|
| 88 | +\(bu
|
---|
| 89 | +In DAD mode (with option \fB-D\fR) set to 0.0.0.0.
|
---|
| 90 | +.TP 0.2i
|
---|
| 91 | +\(bu
|
---|
| 92 | +In Unsolicited ARP mode (with options \fB-U\fR or \fB-A\fR)
|
---|
| 93 | +set to \fIdestination\fR.
|
---|
| 94 | +.TP 0.2i
|
---|
| 95 | +\(bu
|
---|
| 96 | +Otherwise, it is calculated from routing tables.
|
---|
| 97 | +.RE
|
---|
| 98 | +.TP
|
---|
| 99 | +\fB-U\fR
|
---|
| 100 | +Unsolicited ARP mode to update neighbours' ARP caches.
|
---|
| 101 | +No replies are expected.
|
---|
| 102 | +.TP
|
---|
| 103 | +\fB-V\fR
|
---|
| 104 | +Print version of the program and exit.
|
---|
| 105 | +.TP
|
---|
| 106 | +\fB-w \fIdeadline\fB\fR
|
---|
| 107 | +Specify a timeout, in seconds, before
|
---|
| 108 | +\fBarping\fR
|
---|
| 109 | +exits regardless of how many
|
---|
| 110 | +packets have been sent or received. In this case
|
---|
| 111 | +\fBarping\fR
|
---|
| 112 | +does not stop after
|
---|
| 113 | +\fIcount\fR
|
---|
| 114 | +packet are sent, it waits either for
|
---|
| 115 | +\fIdeadline\fR
|
---|
| 116 | +expire or until
|
---|
| 117 | +\fIcount\fR
|
---|
| 118 | +probes are answered.
|
---|
| 119 | +.SH "SEE ALSO"
|
---|
| 120 | +.PP
|
---|
| 121 | +\fBping\fR(8),
|
---|
| 122 | +\fBclockdiff\fR(8),
|
---|
| 123 | +\fBtracepath\fR(8).
|
---|
| 124 | +.SH "AUTHOR"
|
---|
| 125 | +.PP
|
---|
| 126 | +\fBarping\fR was written by
|
---|
| 127 | +Alexey Kuznetsov
|
---|
| 128 | +<kuznet@ms2.inr.ac.ru>.
|
---|
| 129 | +It is now maintained by
|
---|
| 130 | +YOSHIFUJI Hideaki
|
---|
| 131 | +<yoshfuji@skbuff.net>.
|
---|
| 132 | +.SH "SECURITY"
|
---|
| 133 | +.PP
|
---|
| 134 | +\fBarping\fR requires CAP_NET_RAW capability
|
---|
| 135 | +to be executed. It is not recommended to be used as set-uid root,
|
---|
| 136 | +because it allows user to modify ARP caches of neighbour hosts.
|
---|
| 137 | +.SH "AVAILABILITY"
|
---|
| 138 | +.PP
|
---|
| 139 | +\fBarping\fR is part of \fIiputils\fR package
|
---|
| 140 | +and the latest versions are available in source form at
|
---|
| 141 | +http://www.skbuff.net/iputils/iputils-current.tar.bz2.
|
---|
| 142 | diff -Naur iputils-s20150815.orig/doc/clockdiff.8 iputils-s20150815/doc/clockdiff.8
|
---|
| 143 | --- iputils-s20150815.orig/doc/clockdiff.8 1970-01-01 00:00:00.000000000 +0000
|
---|
| 144 | +++ iputils-s20150815/doc/clockdiff.8 2015-08-24 00:27:12.387701056 +0000
|
---|
| 145 | @@ -0,0 +1,81 @@
|
---|
| 146 | +.\" This manpage has been automatically generated by docbook2man
|
---|
| 147 | +.\" from a DocBook document. This tool can be found at:
|
---|
| 148 | +.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
---|
| 149 | +.\" Please send any bug reports, improvements, comments, patches,
|
---|
| 150 | +.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
---|
| 151 | +.TH "CLOCKDIFF" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
|
---|
| 152 | +.SH NAME
|
---|
| 153 | +clockdiff \- measure clock difference between hosts
|
---|
| 154 | +.SH SYNOPSIS
|
---|
| 155 | +
|
---|
| 156 | +\fBclockdiff\fR [\fB-o\fR] [\fB-o1\fR] \fB\fIdestination\fB\fR
|
---|
| 157 | +
|
---|
| 158 | +.SH "DESCRIPTION"
|
---|
| 159 | +.PP
|
---|
| 160 | +\fBclockdiff\fR Measures clock difference between us and
|
---|
| 161 | +\fIdestination\fR with 1 msec resolution using ICMP TIMESTAMP
|
---|
| 162 | +[2]
|
---|
| 163 | +packets or, optionally, IP TIMESTAMP option
|
---|
| 164 | +[3]
|
---|
| 165 | +option added to ICMP ECHO.
|
---|
| 166 | +[1]
|
---|
| 167 | +.SH "OPTIONS"
|
---|
| 168 | +.TP
|
---|
| 169 | +\fB-o\fR
|
---|
| 170 | +Use IP TIMESTAMP with ICMP ECHO instead of ICMP TIMESTAMP
|
---|
| 171 | +messages. It is useful with some destinations, which do not support
|
---|
| 172 | +ICMP TIMESTAMP (f.e. Solaris <2.4).
|
---|
| 173 | +.TP
|
---|
| 174 | +\fB-o1\fR
|
---|
| 175 | +Slightly different form of \fB-o\fR, namely it uses three-term
|
---|
| 176 | +IP TIMESTAMP with prespecified hop addresses instead of four term one.
|
---|
| 177 | +What flavor works better depends on target host. Particularly,
|
---|
| 178 | +\fB-o\fR is better for Linux.
|
---|
| 179 | +.SH "WARNINGS"
|
---|
| 180 | +.TP 0.2i
|
---|
| 181 | +\(bu
|
---|
| 182 | +Some nodes (Cisco) use non-standard timestamps, which is allowed
|
---|
| 183 | +by RFC, but makes timestamps mostly useless.
|
---|
| 184 | +.TP 0.2i
|
---|
| 185 | +\(bu
|
---|
| 186 | +Some nodes generate messed timestamps (Solaris>2.4), when
|
---|
| 187 | +run \fBxntpd\fR. Seems, its IP stack uses a corrupted clock source,
|
---|
| 188 | +which is synchronized to time-of-day clock periodically and jumps
|
---|
| 189 | +randomly making timestamps mostly useless. Good news is that you can
|
---|
| 190 | +use NTP in this case, which is even better.
|
---|
| 191 | +.TP 0.2i
|
---|
| 192 | +\(bu
|
---|
| 193 | +\fBclockdiff\fR shows difference in time modulo 24 days.
|
---|
| 194 | +.SH "SEE ALSO"
|
---|
| 195 | +.PP
|
---|
| 196 | +\fBping\fR(8),
|
---|
| 197 | +\fBarping\fR(8),
|
---|
| 198 | +\fBtracepath\fR(8).
|
---|
| 199 | +.SH "REFERENCES"
|
---|
| 200 | +.PP
|
---|
| 201 | +[1] ICMP ECHO,
|
---|
| 202 | +RFC0792, page 14.
|
---|
| 203 | +.PP
|
---|
| 204 | +[2] ICMP TIMESTAMP,
|
---|
| 205 | +RFC0792, page 16.
|
---|
| 206 | +.PP
|
---|
| 207 | +[3] IP TIMESTAMP option,
|
---|
| 208 | +RFC0791, 3.1, page 16.
|
---|
| 209 | +.SH "AUTHOR"
|
---|
| 210 | +.PP
|
---|
| 211 | +\fBclockdiff\fR was compiled by
|
---|
| 212 | +Alexey Kuznetsov
|
---|
| 213 | +<kuznet@ms2.inr.ac.ru>. It was based on code borrowed
|
---|
| 214 | +from BSD \fBtimed\fR daemon.
|
---|
| 215 | +It is now maintained by
|
---|
| 216 | +YOSHIFUJI Hideaki
|
---|
| 217 | +<yoshfuji@skbuff.net>.
|
---|
| 218 | +.SH "SECURITY"
|
---|
| 219 | +.PP
|
---|
| 220 | +\fBclockdiff\fR requires CAP_NET_RAW capability
|
---|
| 221 | +to be executed. It is safe to be used as set-uid root.
|
---|
| 222 | +.SH "AVAILABILITY"
|
---|
| 223 | +.PP
|
---|
| 224 | +\fBclockdiff\fR is part of \fIiputils\fR package
|
---|
| 225 | +and the latest versions are available in source form at
|
---|
| 226 | +http://www.skbuff.net/iputils/iputils-current.tar.bz2.
|
---|
| 227 | diff -Naur iputils-s20150815.orig/doc/ninfod.8 iputils-s20150815/doc/ninfod.8
|
---|
| 228 | --- iputils-s20150815.orig/doc/ninfod.8 1970-01-01 00:00:00.000000000 +0000
|
---|
| 229 | +++ iputils-s20150815/doc/ninfod.8 2015-08-24 00:27:12.524358055 +0000
|
---|
| 230 | @@ -0,0 +1,72 @@
|
---|
| 231 | +.\" This manpage has been automatically generated by docbook2man
|
---|
| 232 | +.\" from a DocBook document. This tool can be found at:
|
---|
| 233 | +.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
---|
| 234 | +.\" Please send any bug reports, improvements, comments, patches,
|
---|
| 235 | +.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
---|
| 236 | +.TH "NINFOD" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
|
---|
| 237 | +.SH NAME
|
---|
| 238 | +ninfod \- Respond to IPv6 Node Information Queries
|
---|
| 239 | +.SH SYNOPSIS
|
---|
| 240 | +
|
---|
| 241 | +\fBninfod\fR [\fB-dhv\fR] [\fB-p \fIpidfile\fB\fR] [\fB-u \fIuser\fB\fR]
|
---|
| 242 | +
|
---|
| 243 | +.SH "DESCRIPTION"
|
---|
| 244 | +.PP
|
---|
| 245 | +Responds to IPv6 Node Information Queries (RFC4620) from clients.
|
---|
| 246 | +Queries can be sent by various implementations of \fBping6\fR command.
|
---|
| 247 | +.SH "OPTIONS"
|
---|
| 248 | +.TP
|
---|
| 249 | +\fB-a\fR
|
---|
| 250 | +Debug mode. Do not go background.
|
---|
| 251 | +.TP
|
---|
| 252 | +\fB-h\fR
|
---|
| 253 | +Show help.
|
---|
| 254 | +.TP
|
---|
| 255 | +\fB-v\fR
|
---|
| 256 | +Verbose mode.
|
---|
| 257 | +.TP
|
---|
| 258 | +\fB-u \fIuser\fB\fR
|
---|
| 259 | +Run as another user.
|
---|
| 260 | +\fIuser\fR can either be username or user ID.
|
---|
| 261 | +.TP
|
---|
| 262 | +\fB-p \fIpidfile\fB\fR
|
---|
| 263 | +File for process-id storage.
|
---|
| 264 | +\fIuser\fR is required to be able to create the file.
|
---|
| 265 | +.SH "SEE ALSO"
|
---|
| 266 | +.PP
|
---|
| 267 | +\fBping\fR(8).
|
---|
| 268 | +.SH "AUTHOR"
|
---|
| 269 | +.PP
|
---|
| 270 | +\fBninfod\fR was written by USAGI/WIDE Project.
|
---|
| 271 | +.SH "COPYING"
|
---|
| 272 | +.PP
|
---|
| 273 | +
|
---|
| 274 | +.nf
|
---|
| 275 | +Copyright (C) 2012 YOSHIFUJI Hideaki.
|
---|
| 276 | +Copyright (C) 2002 USAGI/WIDE Project.
|
---|
| 277 | +All rights reserved.
|
---|
| 278 | +
|
---|
| 279 | +Redistribution and use in source and binary forms, with or without
|
---|
| 280 | +modification, are permitted provided that the following conditions
|
---|
| 281 | +are met:
|
---|
| 282 | +1. Redistributions of source code must retain the above copyright
|
---|
| 283 | + notice, this list of conditions and the following disclaimer.
|
---|
| 284 | +2. Redistributions in binary form must reproduce the above copyright
|
---|
| 285 | + notice, this list of conditions and the following disclaimer in the
|
---|
| 286 | + documentation and/or other materials provided with the distribution.
|
---|
| 287 | +3. Neither the name of the project nor the names of its contributors
|
---|
| 288 | + may be used to endorse or promote products derived from this software
|
---|
| 289 | + without specific prior written permission.
|
---|
| 290 | +
|
---|
| 291 | +THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND
|
---|
| 292 | +ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
---|
| 293 | +IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
---|
| 294 | +ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE
|
---|
| 295 | +FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
---|
| 296 | +DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
---|
| 297 | +OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
---|
| 298 | +HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
---|
| 299 | +LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
---|
| 300 | +OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
---|
| 301 | +SUCH DAMAGE.
|
---|
| 302 | +.fi
|
---|
| 303 | diff -Naur iputils-s20150815.orig/doc/pg3.8 iputils-s20150815/doc/pg3.8
|
---|
| 304 | --- iputils-s20150815.orig/doc/pg3.8 1970-01-01 00:00:00.000000000 +0000
|
---|
| 305 | +++ iputils-s20150815/doc/pg3.8 2015-08-24 00:27:12.657681956 +0000
|
---|
| 306 | @@ -0,0 +1,86 @@
|
---|
| 307 | +.\" This manpage has been automatically generated by docbook2man
|
---|
| 308 | +.\" from a DocBook document. This tool can be found at:
|
---|
| 309 | +.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
---|
| 310 | +.\" Please send any bug reports, improvements, comments, patches,
|
---|
| 311 | +.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
---|
| 312 | +.TH "PG3" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
|
---|
| 313 | +.SH NAME
|
---|
| 314 | +pg3, ipg, pgset \- send stream of UDP packets
|
---|
| 315 | +.SH SYNOPSIS
|
---|
| 316 | +
|
---|
| 317 | +\fBsource ipg\fR
|
---|
| 318 | +
|
---|
| 319 | +
|
---|
| 320 | +\fBpg\fR
|
---|
| 321 | +
|
---|
| 322 | +
|
---|
| 323 | +\fBpgset\fR \fB\fICOMMAND\fB\fR
|
---|
| 324 | +
|
---|
| 325 | +.SH "DESCRIPTION"
|
---|
| 326 | +.PP
|
---|
| 327 | +\fBipg\fR is not a program, it is script which should be sourced
|
---|
| 328 | +to \fBbash\fR. When sourced it loads module \fIpg3\fR and
|
---|
| 329 | +exports a few of functions accessible from parent shell. These macros
|
---|
| 330 | +are \fBpg\fR to start packet injection and to get the results of run;
|
---|
| 331 | +and \fBpgset\fR to setup packet generator.
|
---|
| 332 | +.PP
|
---|
| 333 | +\fBpgset\fR can send the following commands to module \fIpg3\fR:
|
---|
| 334 | +.SH "COMMAND"
|
---|
| 335 | +.TP
|
---|
| 336 | +\fBodev \fIDEVICE\fB\fR
|
---|
| 337 | +Name of Ethernet device to test. See
|
---|
| 338 | +warning below.
|
---|
| 339 | +.TP
|
---|
| 340 | +\fBpkt_size \fIBYTES\fB\fR
|
---|
| 341 | +Size of packet to generate. The size includes all the headers: UDP, IP,
|
---|
| 342 | +MAC, but does not account for overhead internal to medium, i.e. FCS
|
---|
| 343 | +and various paddings.
|
---|
| 344 | +.TP
|
---|
| 345 | +\fBfrags \fINUMBER\fB\fR
|
---|
| 346 | +Each packet will contain \fINUMBER\fR of fragments.
|
---|
| 347 | +Maximal amount for linux-2.4 is 6. Far not all the devices support
|
---|
| 348 | +fragmented buffers.
|
---|
| 349 | +.TP
|
---|
| 350 | +\fBcount \fINUMBER\fB\fR
|
---|
| 351 | +Send stream of \fINUMBER\fR of packets and stop after this.
|
---|
| 352 | +.TP
|
---|
| 353 | +\fBipg \fITIME\fB\fR
|
---|
| 354 | +Introduce artificial delay between packets of \fITIME\fR
|
---|
| 355 | +microseconds.
|
---|
| 356 | +.TP
|
---|
| 357 | +\fBdst \fIIP_ADDRESS\fB\fR
|
---|
| 358 | +Select IP destination where the stream is sent to.
|
---|
| 359 | +Beware, never set this address at random. \fBpg3\fR is not a toy,
|
---|
| 360 | +it creates really tough stream. Default value is 0.0.0.0.
|
---|
| 361 | +.TP
|
---|
| 362 | +\fBdst \fIMAC_ADDRESS\fB\fR
|
---|
| 363 | +Select MAC destination where the stream is sent to.
|
---|
| 364 | +Default value is 00:00:00:00:00:00 in hope that this will not be received
|
---|
| 365 | +by any node on LAN.
|
---|
| 366 | +.TP
|
---|
| 367 | +\fBstop\fR
|
---|
| 368 | +Abort packet injection.
|
---|
| 369 | +.SH "WARNING"
|
---|
| 370 | +.PP
|
---|
| 371 | +When output device is set to some random device different
|
---|
| 372 | +of hardware Ethernet device, \fBpg3\fR will crash kernel.
|
---|
| 373 | +.PP
|
---|
| 374 | +Do not use it on VLAN, ethertap, VTUN and other devices,
|
---|
| 375 | +which emulate Ethernet not being real Ethernet in fact.
|
---|
| 376 | +.SH "AUTHOR"
|
---|
| 377 | +.PP
|
---|
| 378 | +\fBpg3\fR was written by Robert Olsson <robert.olsson@its.uu.se>.
|
---|
| 379 | +.SH "SECURITY"
|
---|
| 380 | +.PP
|
---|
| 381 | +This can be used only by superuser.
|
---|
| 382 | +.PP
|
---|
| 383 | +This tool creates floods of packets which is unlikely to be handled
|
---|
| 384 | +even by high-end machines. For example, it saturates gigabit link with
|
---|
| 385 | +60 byte packets when used with Intel's e1000. In face of such stream
|
---|
| 386 | +switches, routers and end hosts may deadlock, crash, explode.
|
---|
| 387 | +Use only in test lab environment.
|
---|
| 388 | +.SH "AVAILABILITY"
|
---|
| 389 | +.PP
|
---|
| 390 | +\fBpg3\fR is part of \fIiputils\fR package
|
---|
| 391 | +and the latest versions are available in source form at
|
---|
| 392 | +http://www.skbuff.net/iputils/iputils-current.tar.bz2.
|
---|
| 393 | diff -Naur iputils-s20150815.orig/doc/ping.8 iputils-s20150815/doc/ping.8
|
---|
| 394 | --- iputils-s20150815.orig/doc/ping.8 1970-01-01 00:00:00.000000000 +0000
|
---|
| 395 | +++ iputils-s20150815/doc/ping.8 2015-08-24 00:27:12.861000903 +0000
|
---|
| 396 | @@ -0,0 +1,433 @@
|
---|
| 397 | +.\" This manpage has been automatically generated by docbook2man
|
---|
| 398 | +.\" from a DocBook document. This tool can be found at:
|
---|
| 399 | +.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
---|
| 400 | +.\" Please send any bug reports, improvements, comments, patches,
|
---|
| 401 | +.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
---|
| 402 | +.TH "PING" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
|
---|
| 403 | +.SH NAME
|
---|
| 404 | +ping, ping6 \- send ICMP ECHO_REQUEST to network hosts
|
---|
| 405 | +.SH SYNOPSIS
|
---|
| 406 | +
|
---|
| 407 | +\fBping\fR [\fB-aAbBdDfhLnOqrRUvV6\fR] [\fB-c \fIcount\fB\fR] [\fB-F \fIflowlabel\fB\fR] [\fB-i \fIinterval\fB\fR] [\fB-I \fIinterface\fB\fR] [\fB-l \fIpreload\fB\fR] [\fB-m \fImark\fB\fR] [\fB-M \fIpmtudisc_option\fB\fR] [\fB-N \fInodeinfo_option\fB\fR] [\fB-w \fIdeadline\fB\fR] [\fB-W \fItimeout\fB\fR] [\fB-p \fIpattern\fB\fR] [\fB-Q \fItos\fB\fR] [\fB-s \fIpacketsize\fB\fR] [\fB-S \fIsndbuf\fB\fR] [\fB-t \fIttl\fB\fR] [\fB-T \fItimestamp option\fB\fR] [\fB\fIhop\fB\fR\fI ...\fR] \fB\fIdestination\fB\fR
|
---|
| 408 | +
|
---|
| 409 | +.SH "DESCRIPTION"
|
---|
| 410 | +.PP
|
---|
| 411 | +\fBping\fR uses the ICMP protocol's mandatory ECHO_REQUEST
|
---|
| 412 | +datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway.
|
---|
| 413 | +ECHO_REQUEST datagrams (``pings'') have an IP and ICMP
|
---|
| 414 | +header, followed by a struct timeval and then an arbitrary
|
---|
| 415 | +number of ``pad'' bytes used to fill out the packet.
|
---|
| 416 | +.PP
|
---|
| 417 | +\fBping6\fR is IPv6 version of \fBping\fR, and can also send Node Information Queries (RFC4620).
|
---|
| 418 | +Intermediate \fIhop\fRs may not be allowed, because IPv6 source routing was deprecated (RFC5095).
|
---|
| 419 | +.SH "OPTIONS"
|
---|
| 420 | +.TP
|
---|
| 421 | +\fB-a\fR
|
---|
| 422 | +Audible ping.
|
---|
| 423 | +.TP
|
---|
| 424 | +\fB-A\fR
|
---|
| 425 | +Adaptive ping. Interpacket interval adapts to round-trip time, so that
|
---|
| 426 | +effectively not more than one (or more, if preload is set) unanswered probe
|
---|
| 427 | +is present in the network. Minimal interval is 200msec for not super-user.
|
---|
| 428 | +On networks with low rtt this mode is essentially equivalent to flood mode.
|
---|
| 429 | +.TP
|
---|
| 430 | +\fB-b\fR
|
---|
| 431 | +Allow pinging a broadcast address.
|
---|
| 432 | +.TP
|
---|
| 433 | +\fB-B\fR
|
---|
| 434 | +Do not allow \fBping\fR to change source address of probes.
|
---|
| 435 | +The address is bound to one selected when \fBping\fR starts.
|
---|
| 436 | +.TP
|
---|
| 437 | +\fB-c \fIcount\fB\fR
|
---|
| 438 | +Stop after sending \fIcount\fR ECHO_REQUEST
|
---|
| 439 | +packets. With
|
---|
| 440 | +\fIdeadline\fR
|
---|
| 441 | +option, \fBping\fR waits for
|
---|
| 442 | +\fIcount\fR ECHO_REPLY packets, until the timeout expires.
|
---|
| 443 | +.TP
|
---|
| 444 | +\fB-d\fR
|
---|
| 445 | +Set the SO_DEBUG option on the socket being used.
|
---|
| 446 | +Essentially, this socket option is not used by Linux kernel.
|
---|
| 447 | +.TP
|
---|
| 448 | +\fB-D\fR
|
---|
| 449 | +Print timestamp (unix time + microseconds as in gettimeofday) before
|
---|
| 450 | +each line.
|
---|
| 451 | +.TP
|
---|
| 452 | +\fB-f\fR
|
---|
| 453 | +Flood ping. For every ECHO_REQUEST sent a period ``.'' is printed,
|
---|
| 454 | +while for ever ECHO_REPLY received a backspace is printed.
|
---|
| 455 | +This provides a rapid display of how many packets are being dropped.
|
---|
| 456 | +If interval is not given, it sets interval to zero and
|
---|
| 457 | +outputs packets as fast as they come back or one hundred times per second,
|
---|
| 458 | +whichever is more.
|
---|
| 459 | +Only the super-user may use this option with zero interval.
|
---|
| 460 | +.TP
|
---|
| 461 | +\fB-F \fIflow label\fB\fR
|
---|
| 462 | +\fBping6\fR only.
|
---|
| 463 | +Allocate and set 20 bit flow label (in hex) on echo request packets.
|
---|
| 464 | +If value is zero, kernel allocates random flow label.
|
---|
| 465 | +.TP
|
---|
| 466 | +\fB-h\fR
|
---|
| 467 | +Show help.
|
---|
| 468 | +.TP
|
---|
| 469 | +\fB-i \fIinterval\fB\fR
|
---|
| 470 | +Wait \fIinterval\fR seconds between sending each packet.
|
---|
| 471 | +The default is to wait for one second between each packet normally,
|
---|
| 472 | +or not to wait in flood mode. Only super-user may set interval
|
---|
| 473 | +to values less 0.2 seconds.
|
---|
| 474 | +.TP
|
---|
| 475 | +\fB-I \fIinterface\fB\fR
|
---|
| 476 | +\fIinterface\fR is either an address, or an interface name.
|
---|
| 477 | +If \fIinterface\fR is an address, it sets source address
|
---|
| 478 | +to specified interface address.
|
---|
| 479 | +If \fIinterface\fR in an interface name, it sets
|
---|
| 480 | +source interface to specified interface.
|
---|
| 481 | +For \fBping6\fR, when doing ping to a link-local scope
|
---|
| 482 | +address, link specification (by the '%'-notation in
|
---|
| 483 | +\fIdestination\fR, or by this option) is required.
|
---|
| 484 | +.TP
|
---|
| 485 | +\fB-l \fIpreload\fB\fR
|
---|
| 486 | +If \fIpreload\fR is specified,
|
---|
| 487 | +\fBping\fR sends that many packets not waiting for reply.
|
---|
| 488 | +Only the super-user may select preload more than 3.
|
---|
| 489 | +.TP
|
---|
| 490 | +\fB-L\fR
|
---|
| 491 | +Suppress loopback of multicast packets. This flag only applies if the ping
|
---|
| 492 | +destination is a multicast address.
|
---|
| 493 | +.TP
|
---|
| 494 | +\fB-m \fImark\fB\fR
|
---|
| 495 | +use \fImark\fR to tag the packets going out. This is useful
|
---|
| 496 | +for variety of reasons within the kernel such as using policy
|
---|
| 497 | +routing to select specific outbound processing.
|
---|
| 498 | +.TP
|
---|
| 499 | +\fB-M \fIpmtudisc_opt\fB\fR
|
---|
| 500 | +Select Path MTU Discovery strategy.
|
---|
| 501 | +\fIpmtudisc_option\fR may be either \fIdo\fR
|
---|
| 502 | +(prohibit fragmentation, even local one),
|
---|
| 503 | +\fIwant\fR (do PMTU discovery, fragment locally when packet size
|
---|
| 504 | +is large), or \fIdont\fR (do not set DF flag).
|
---|
| 505 | +.TP
|
---|
| 506 | +\fB-N \fInodeinfo_option\fB\fR
|
---|
| 507 | +\fBping6\fR only.
|
---|
| 508 | +Send ICMPv6 Node Information Queries (RFC4620), instead of Echo Request.
|
---|
| 509 | +CAP_NET_RAW capability is required.
|
---|
| 510 | +.RS
|
---|
| 511 | +.TP
|
---|
| 512 | +\fBhelp\fR
|
---|
| 513 | +Show help for NI support.
|
---|
| 514 | +.RE
|
---|
| 515 | +.RS
|
---|
| 516 | +.TP
|
---|
| 517 | +\fBname\fR
|
---|
| 518 | +Queries for Node Names.
|
---|
| 519 | +.RE
|
---|
| 520 | +.RS
|
---|
| 521 | +.TP
|
---|
| 522 | +\fBipv6\fR
|
---|
| 523 | +Queries for IPv6 Addresses. There are several IPv6 specific flags.
|
---|
| 524 | +.RS
|
---|
| 525 | +.TP
|
---|
| 526 | +\fBipv6-global\fR
|
---|
| 527 | +Request IPv6 global-scope addresses.
|
---|
| 528 | +.RE
|
---|
| 529 | +.RS
|
---|
| 530 | +.TP
|
---|
| 531 | +\fBipv6-sitelocal\fR
|
---|
| 532 | +Request IPv6 site-local addresses.
|
---|
| 533 | +.RE
|
---|
| 534 | +.RS
|
---|
| 535 | +.TP
|
---|
| 536 | +\fBipv6-linklocal\fR
|
---|
| 537 | +Request IPv6 link-local addresses.
|
---|
| 538 | +.RE
|
---|
| 539 | +.RS
|
---|
| 540 | +.TP
|
---|
| 541 | +\fBipv6-all\fR
|
---|
| 542 | +Request IPv6 addresses on other interfaces.
|
---|
| 543 | +.RE
|
---|
| 544 | +.RE
|
---|
| 545 | +.RS
|
---|
| 546 | +.TP
|
---|
| 547 | +\fBipv4\fR
|
---|
| 548 | +Queries for IPv4 Addresses. There is one IPv4 specific flag.
|
---|
| 549 | +.RS
|
---|
| 550 | +.TP
|
---|
| 551 | +\fBipv4-all\fR
|
---|
| 552 | +Request IPv4 addresses on other interfaces.
|
---|
| 553 | +.RE
|
---|
| 554 | +.RE
|
---|
| 555 | +.RS
|
---|
| 556 | +.TP
|
---|
| 557 | +\fBsubject-ipv6=\fIipv6addr\fB\fR
|
---|
| 558 | +IPv6 subject address.
|
---|
| 559 | +.RE
|
---|
| 560 | +.RS
|
---|
| 561 | +.TP
|
---|
| 562 | +\fBsubject-ipv4=\fIipv4addr\fB\fR
|
---|
| 563 | +IPv4 subject address.
|
---|
| 564 | +.RE
|
---|
| 565 | +.RS
|
---|
| 566 | +.TP
|
---|
| 567 | +\fBsubject-name=\fInodename\fB\fR
|
---|
| 568 | +Subject name. If it contains more than one dot,
|
---|
| 569 | +fully-qualified domain name is assumed.
|
---|
| 570 | +.RE
|
---|
| 571 | +.RS
|
---|
| 572 | +.TP
|
---|
| 573 | +\fBsubject-fqdn=\fInodename\fB\fR
|
---|
| 574 | +Subject name. Fully-qualified domain name is
|
---|
| 575 | +always assumed.
|
---|
| 576 | +.RE
|
---|
| 577 | +.TP
|
---|
| 578 | +\fB-n\fR
|
---|
| 579 | +Numeric output only.
|
---|
| 580 | +No attempt will be made to lookup symbolic names for host addresses.
|
---|
| 581 | +.TP
|
---|
| 582 | +\fB-O\fR
|
---|
| 583 | +Report outstanding ICMP ECHO reply before sending next packet.
|
---|
| 584 | +This is useful together with the timestamp \fB-D\fR to
|
---|
| 585 | +log output to a diagnostic file and search for missing answers.
|
---|
| 586 | +.TP
|
---|
| 587 | +\fB-p \fIpattern\fB\fR
|
---|
| 588 | +You may specify up to 16 ``pad'' bytes to fill out the packet you send.
|
---|
| 589 | +This is useful for diagnosing data-dependent problems in a network.
|
---|
| 590 | +For example, \fB-p ff\fR will cause the sent packet
|
---|
| 591 | +to be filled with all ones.
|
---|
| 592 | +.TP
|
---|
| 593 | +\fB-q\fR
|
---|
| 594 | +Quiet output.
|
---|
| 595 | +Nothing is displayed except the summary lines at startup time and
|
---|
| 596 | +when finished.
|
---|
| 597 | +.TP
|
---|
| 598 | +\fB-Q \fItos\fB\fR
|
---|
| 599 | +Set Quality of Service -related bits in ICMP datagrams.
|
---|
| 600 | +\fItos\fR can be decimal (\fBping\fR only) or hex number.
|
---|
| 601 | +
|
---|
| 602 | +In RFC2474, these fields are interpreted as 8-bit Differentiated
|
---|
| 603 | +Services (DS), consisting of: bits 0-1 (2 lowest bits) of separate
|
---|
| 604 | +data, and bits 2-7 (highest 6 bits) of Differentiated Services
|
---|
| 605 | +Codepoint (DSCP). In RFC2481 and RFC3168, bits 0-1 are used for ECN.
|
---|
| 606 | +
|
---|
| 607 | +Historically (RFC1349, obsoleted by RFC2474), these were interpreted
|
---|
| 608 | +as: bit 0 (lowest bit) for reserved (currently being redefined as
|
---|
| 609 | +congestion control), 1-4 for Type of Service and bits 5-7
|
---|
| 610 | +(highest bits) for Precedence.
|
---|
| 611 | +.TP
|
---|
| 612 | +\fB-r\fR
|
---|
| 613 | +Bypass the normal routing tables and send directly to a host on an attached
|
---|
| 614 | +interface.
|
---|
| 615 | +If the host is not on a directly-attached network, an error is returned.
|
---|
| 616 | +This option can be used to ping a local host through an interface
|
---|
| 617 | +that has no route through it provided the option \fB-I\fR is also
|
---|
| 618 | +used.
|
---|
| 619 | +.TP
|
---|
| 620 | +\fB-R\fR
|
---|
| 621 | +\fBping\fR only.
|
---|
| 622 | +Record route.
|
---|
| 623 | +Includes the RECORD_ROUTE option in the ECHO_REQUEST
|
---|
| 624 | +packet and displays the route buffer on returned packets.
|
---|
| 625 | +Note that the IP header is only large enough for nine such routes.
|
---|
| 626 | +Many hosts ignore or discard this option.
|
---|
| 627 | +.TP
|
---|
| 628 | +\fB-s \fIpacketsize\fB\fR
|
---|
| 629 | +Specifies the number of data bytes to be sent.
|
---|
| 630 | +The default is 56, which translates into 64 ICMP
|
---|
| 631 | +data bytes when combined with the 8 bytes of ICMP header data.
|
---|
| 632 | +.TP
|
---|
| 633 | +\fB-S \fIsndbuf\fB\fR
|
---|
| 634 | +Set socket sndbuf. If not specified, it is selected to buffer
|
---|
| 635 | +not more than one packet.
|
---|
| 636 | +.TP
|
---|
| 637 | +\fB-t \fIttl\fB\fR
|
---|
| 638 | +\fBping\fR only.
|
---|
| 639 | +Set the IP Time to Live.
|
---|
| 640 | +.TP
|
---|
| 641 | +\fB-T \fItimestamp option\fB\fR
|
---|
| 642 | +Set special IP timestamp options.
|
---|
| 643 | +\fItimestamp option\fR may be either
|
---|
| 644 | +\fItsonly\fR (only timestamps),
|
---|
| 645 | +\fItsandaddr\fR (timestamps and addresses) or
|
---|
| 646 | +\fItsprespec host1 [host2 [host3 [host4]]]\fR
|
---|
| 647 | +(timestamp prespecified hops).
|
---|
| 648 | +.TP
|
---|
| 649 | +\fB-U\fR
|
---|
| 650 | +Print full user-to-user latency (the old behaviour). Normally
|
---|
| 651 | +\fBping\fR
|
---|
| 652 | +prints network round trip time, which can be different
|
---|
| 653 | +f.e. due to DNS failures.
|
---|
| 654 | +.TP
|
---|
| 655 | +\fB-v\fR
|
---|
| 656 | +Verbose output.
|
---|
| 657 | +.TP
|
---|
| 658 | +\fB-V\fR
|
---|
| 659 | +Show version and exit.
|
---|
| 660 | +.TP
|
---|
| 661 | +\fB-w \fIdeadline\fB\fR
|
---|
| 662 | +Specify a timeout, in seconds, before
|
---|
| 663 | +\fBping\fR
|
---|
| 664 | +exits regardless of how many
|
---|
| 665 | +packets have been sent or received. In this case
|
---|
| 666 | +\fBping\fR
|
---|
| 667 | +does not stop after
|
---|
| 668 | +\fIcount\fR
|
---|
| 669 | +packet are sent, it waits either for
|
---|
| 670 | +\fIdeadline\fR
|
---|
| 671 | +expire or until
|
---|
| 672 | +\fIcount\fR
|
---|
| 673 | +probes are answered or for some error notification from network.
|
---|
| 674 | +.TP
|
---|
| 675 | +\fB-W \fItimeout\fB\fR
|
---|
| 676 | +Time to wait for a response, in seconds. The option affects only timeout
|
---|
| 677 | +in absence of any responses, otherwise \fBping\fR waits for two RTTs.
|
---|
| 678 | +.PP
|
---|
| 679 | +When using \fBping\fR for fault isolation, it should first be run
|
---|
| 680 | +on the local host, to verify that the local network interface is up
|
---|
| 681 | +and running. Then, hosts and gateways further and further away should be
|
---|
| 682 | +``pinged''. Round-trip times and packet loss statistics are computed.
|
---|
| 683 | +If duplicate packets are received, they are not included in the packet
|
---|
| 684 | +loss calculation, although the round trip time of these packets is used
|
---|
| 685 | +in calculating the minimum/average/maximum round-trip time numbers.
|
---|
| 686 | +When the specified number of packets have been sent (and received) or
|
---|
| 687 | +if the program is terminated with a
|
---|
| 688 | +SIGINT, a brief summary is displayed. Shorter current statistics
|
---|
| 689 | +can be obtained without termination of process with signal
|
---|
| 690 | +SIGQUIT.
|
---|
| 691 | +.PP
|
---|
| 692 | +If \fBping\fR does not receive any reply packets at all it will
|
---|
| 693 | +exit with code 1. If a packet
|
---|
| 694 | +\fIcount\fR
|
---|
| 695 | +and
|
---|
| 696 | +\fIdeadline\fR
|
---|
| 697 | +are both specified, and fewer than
|
---|
| 698 | +\fIcount\fR
|
---|
| 699 | +packets are received by the time the
|
---|
| 700 | +\fIdeadline\fR
|
---|
| 701 | +has arrived, it will also exit with code 1.
|
---|
| 702 | +On other error it exits with code 2. Otherwise it exits with code 0. This
|
---|
| 703 | +makes it possible to use the exit code to see if a host is alive or
|
---|
| 704 | +not.
|
---|
| 705 | +.PP
|
---|
| 706 | +This program is intended for use in network testing, measurement and
|
---|
| 707 | +management.
|
---|
| 708 | +Because of the load it can impose on the network, it is unwise to use
|
---|
| 709 | +\fBping\fR during normal operations or from automated scripts.
|
---|
| 710 | +.SH "ICMP PACKET DETAILS"
|
---|
| 711 | +.PP
|
---|
| 712 | +An IP header without options is 20 bytes.
|
---|
| 713 | +An ICMP ECHO_REQUEST packet contains an additional 8 bytes worth
|
---|
| 714 | +of ICMP header followed by an arbitrary amount of data.
|
---|
| 715 | +When a \fIpacketsize\fR is given, this indicated the size of this
|
---|
| 716 | +extra piece of data (the default is 56). Thus the amount of data received
|
---|
| 717 | +inside of an IP packet of type ICMP ECHO_REPLY will always be 8 bytes
|
---|
| 718 | +more than the requested data space (the ICMP header).
|
---|
| 719 | +.PP
|
---|
| 720 | +If the data space is at least of size of struct timeval
|
---|
| 721 | +\fBping\fR uses the beginning bytes of this space to include
|
---|
| 722 | +a timestamp which it uses in the computation of round trip times.
|
---|
| 723 | +If the data space is shorter, no round trip times are given.
|
---|
| 724 | +.SH "DUPLICATE AND DAMAGED PACKETS"
|
---|
| 725 | +.PP
|
---|
| 726 | +\fBping\fR will report duplicate and damaged packets.
|
---|
| 727 | +Duplicate packets should never occur, and seem to be caused by
|
---|
| 728 | +inappropriate link-level retransmissions.
|
---|
| 729 | +Duplicates may occur in many situations and are rarely (if ever) a
|
---|
| 730 | +good sign, although the presence of low levels of duplicates may not
|
---|
| 731 | +always be cause for alarm.
|
---|
| 732 | +.PP
|
---|
| 733 | +Damaged packets are obviously serious cause for alarm and often
|
---|
| 734 | +indicate broken hardware somewhere in the
|
---|
| 735 | +\fBping\fR packet's path (in the network or in the hosts).
|
---|
| 736 | +.SH "TRYING DIFFERENT DATA PATTERNS"
|
---|
| 737 | +.PP
|
---|
| 738 | +The (inter)network layer should never treat packets differently depending
|
---|
| 739 | +on the data contained in the data portion.
|
---|
| 740 | +Unfortunately, data-dependent problems have been known to sneak into
|
---|
| 741 | +networks and remain undetected for long periods of time.
|
---|
| 742 | +In many cases the particular pattern that will have problems is something
|
---|
| 743 | +that doesn't have sufficient ``transitions'', such as all ones or all
|
---|
| 744 | +zeros, or a pattern right at the edge, such as almost all zeros.
|
---|
| 745 | +It isn't necessarily enough to specify a data pattern of all zeros (for
|
---|
| 746 | +example) on the command line because the pattern that is of interest is
|
---|
| 747 | +at the data link level, and the relationship between what you type and
|
---|
| 748 | +what the controllers transmit can be complicated.
|
---|
| 749 | +.PP
|
---|
| 750 | +This means that if you have a data-dependent problem you will probably
|
---|
| 751 | +have to do a lot of testing to find it.
|
---|
| 752 | +If you are lucky, you may manage to find a file that either can't be sent
|
---|
| 753 | +across your network or that takes much longer to transfer than other
|
---|
| 754 | +similar length files.
|
---|
| 755 | +You can then examine this file for repeated patterns that you can test
|
---|
| 756 | +using the \fB-p\fR option of \fBping\fR.
|
---|
| 757 | +.SH "TTL DETAILS"
|
---|
| 758 | +.PP
|
---|
| 759 | +The TTL value of an IP packet represents the maximum number of IP routers
|
---|
| 760 | +that the packet can go through before being thrown away.
|
---|
| 761 | +In current practice you can expect each router in the Internet to decrement
|
---|
| 762 | +the TTL field by exactly one.
|
---|
| 763 | +.PP
|
---|
| 764 | +The TCP/IP specification states that the TTL field for TCP
|
---|
| 765 | +packets should be set to 60, but many systems use smaller values
|
---|
| 766 | +(4.3 BSD uses 30, 4.2 used 15).
|
---|
| 767 | +.PP
|
---|
| 768 | +The maximum possible value of this field is 255, and most Unix systems set
|
---|
| 769 | +the TTL field of ICMP ECHO_REQUEST packets to 255.
|
---|
| 770 | +This is why you will find you can ``ping'' some hosts, but not reach them
|
---|
| 771 | +with
|
---|
| 772 | +\fBtelnet\fR(1)
|
---|
| 773 | +or
|
---|
| 774 | +\fBftp\fR(1).
|
---|
| 775 | +.PP
|
---|
| 776 | +In normal operation ping prints the TTL value from the packet it receives.
|
---|
| 777 | +When a remote system receives a ping packet, it can do one of three things
|
---|
| 778 | +with the TTL field in its response:
|
---|
| 779 | +.TP 0.2i
|
---|
| 780 | +\(bu
|
---|
| 781 | +Not change it; this is what Berkeley Unix systems did before the
|
---|
| 782 | +4.3BSD Tahoe release. In this case the TTL value in the received packet
|
---|
| 783 | +will be 255 minus the number of routers in the round-trip path.
|
---|
| 784 | +.TP 0.2i
|
---|
| 785 | +\(bu
|
---|
| 786 | +Set it to 255; this is what current Berkeley Unix systems do.
|
---|
| 787 | +In this case the TTL value in the received packet will be 255 minus the
|
---|
| 788 | +number of routers in the path \fBfrom\fR
|
---|
| 789 | +the remote system \fBto\fR the \fBping\fRing host.
|
---|
| 790 | +.TP 0.2i
|
---|
| 791 | +\(bu
|
---|
| 792 | +Set it to some other value. Some machines use the same value for
|
---|
| 793 | +ICMP packets that they use for TCP packets, for example either 30 or 60.
|
---|
| 794 | +Others may use completely wild values.
|
---|
| 795 | +.SH "BUGS"
|
---|
| 796 | +.TP 0.2i
|
---|
| 797 | +\(bu
|
---|
| 798 | +Many Hosts and Gateways ignore the RECORD_ROUTE option.
|
---|
| 799 | +.TP 0.2i
|
---|
| 800 | +\(bu
|
---|
| 801 | +The maximum IP header length is too small for options like
|
---|
| 802 | +RECORD_ROUTE to be completely useful.
|
---|
| 803 | +There's not much that can be done about this, however.
|
---|
| 804 | +.TP 0.2i
|
---|
| 805 | +\(bu
|
---|
| 806 | +Flood pinging is not recommended in general, and flood pinging the
|
---|
| 807 | +broadcast address should only be done under very controlled conditions.
|
---|
| 808 | +.SH "SEE ALSO"
|
---|
| 809 | +.PP
|
---|
| 810 | +\fBnetstat\fR(1),
|
---|
| 811 | +\fBifconfig\fR(8).
|
---|
| 812 | +.SH "HISTORY"
|
---|
| 813 | +.PP
|
---|
| 814 | +The \fBping\fR command appeared in 4.3BSD.
|
---|
| 815 | +.PP
|
---|
| 816 | +The version described here is its descendant specific to Linux.
|
---|
| 817 | +.SH "SECURITY"
|
---|
| 818 | +.PP
|
---|
| 819 | +\fBping\fR requires CAP_NET_RAW capability
|
---|
| 820 | +to be executed 1) if the program is used for non-echo queries
|
---|
| 821 | +(See \fB-N\fR option), or 2) if kernel does not
|
---|
| 822 | +support non-raw ICMP sockets, or 3) if the user is not allowed
|
---|
| 823 | +to create an ICMP echo socket. The program may be used as
|
---|
| 824 | +set-uid root.
|
---|
| 825 | +.SH "AVAILABILITY"
|
---|
| 826 | +.PP
|
---|
| 827 | +\fBping\fR is part of \fIiputils\fR package
|
---|
| 828 | +and the latest versions are available in source form at
|
---|
| 829 | +http://www.skbuff.net/iputils/iputils-current.tar.bz2.
|
---|
| 830 | diff -Naur iputils-s20150815.orig/doc/rarpd.8 iputils-s20150815/doc/rarpd.8
|
---|
| 831 | --- iputils-s20150815.orig/doc/rarpd.8 1970-01-01 00:00:00.000000000 +0000
|
---|
| 832 | +++ iputils-s20150815/doc/rarpd.8 2015-08-24 00:27:12.994324803 +0000
|
---|
| 833 | @@ -0,0 +1,84 @@
|
---|
| 834 | +.\" This manpage has been automatically generated by docbook2man
|
---|
| 835 | +.\" from a DocBook document. This tool can be found at:
|
---|
| 836 | +.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
---|
| 837 | +.\" Please send any bug reports, improvements, comments, patches,
|
---|
| 838 | +.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
---|
| 839 | +.TH "RARPD" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
|
---|
| 840 | +.SH NAME
|
---|
| 841 | +rarpd \- answer RARP REQUESTs
|
---|
| 842 | +.SH SYNOPSIS
|
---|
| 843 | +
|
---|
| 844 | +\fBarping\fR [\fB-aAvde\fR] [\fB-b \fIbootdir\fB\fR] [\fB\fIinterface\fB\fR]
|
---|
| 845 | +
|
---|
| 846 | +.SH "DESCRIPTION"
|
---|
| 847 | +.PP
|
---|
| 848 | +Listens
|
---|
| 849 | +RARP
|
---|
| 850 | +requests from clients. Provided MAC address of client
|
---|
| 851 | +is found in \fI/etc/ethers\fR database and
|
---|
| 852 | +obtained host name is resolvable to an IP address appropriate
|
---|
| 853 | +for attached network, \fBrarpd\fR answers to client with RARPD
|
---|
| 854 | +reply carrying an IP address.
|
---|
| 855 | +.PP
|
---|
| 856 | +To allow multiple boot servers on the network \fBrarpd\fR
|
---|
| 857 | +optionally checks for presence Sun-like bootable image in TFTP directory.
|
---|
| 858 | +It should have form \fBHexadecimal_IP.ARCH\fR, f.e. to load
|
---|
| 859 | +sparc 193.233.7.98 \fIC1E90762.SUN4M\fR is linked to
|
---|
| 860 | +an image appropriate for SUM4M in directory \fI/etc/tftpboot\fR.
|
---|
| 861 | +.SH "WARNING"
|
---|
| 862 | +.PP
|
---|
| 863 | +This facility is deeply obsoleted by
|
---|
| 864 | +BOOTP
|
---|
| 865 | +and later
|
---|
| 866 | +DHCP protocols.
|
---|
| 867 | +However, some clients really still need this to boot.
|
---|
| 868 | +.SH "OPTIONS"
|
---|
| 869 | +.TP
|
---|
| 870 | +\fB-a\fR
|
---|
| 871 | +Listen on all the interfaces. Currently it is an internal
|
---|
| 872 | +option, its function is overridden with \fIinterface\fR
|
---|
| 873 | +argument. It should not be used.
|
---|
| 874 | +.TP
|
---|
| 875 | +\fB-A\fR
|
---|
| 876 | +Listen not only RARP but also ARP messages, some rare clients
|
---|
| 877 | +use ARP by some unknown reason.
|
---|
| 878 | +.TP
|
---|
| 879 | +\fB-v\fR
|
---|
| 880 | +Be verbose.
|
---|
| 881 | +.TP
|
---|
| 882 | +\fB-d\fR
|
---|
| 883 | +Debug mode. Do not go to background.
|
---|
| 884 | +.TP
|
---|
| 885 | +\fB-e\fR
|
---|
| 886 | +Do not check for presence of a boot image, reply if MAC address
|
---|
| 887 | +resolves to a valid IP address using \fI/etc/ethers\fR
|
---|
| 888 | +database and DNS.
|
---|
| 889 | +.TP
|
---|
| 890 | +\fB-b \fIbootdir\fB\fR
|
---|
| 891 | +TFTP boot directory. Default is \fI/etc/tftpboot\fR
|
---|
| 892 | +.SH "SEE ALSO"
|
---|
| 893 | +.PP
|
---|
| 894 | +\fBarping\fR(8),
|
---|
| 895 | +\fBtftpd\fR(8).
|
---|
| 896 | +.SH "AUTHOR"
|
---|
| 897 | +.PP
|
---|
| 898 | +\fBrarpd\fR was written by
|
---|
| 899 | +Alexey Kuznetsov
|
---|
| 900 | +<kuznet@ms2.inr.ac.ru>.
|
---|
| 901 | +It is now maintained by
|
---|
| 902 | +YOSHIFUJI Hideaki
|
---|
| 903 | +<yoshfuji@skbuff.net>.
|
---|
| 904 | +.SH "SECURITY"
|
---|
| 905 | +.PP
|
---|
| 906 | +\fBrarpd\fR requires CAP_NET_RAW capability
|
---|
| 907 | +to listen and send RARP and ARP packets. It also needs CAP_NET_ADMIN
|
---|
| 908 | +to give to kernel hint for ARP resolution; this is not strictly required,
|
---|
| 909 | +but some (most of, to be more exact) clients are so badly broken that
|
---|
| 910 | +are not able to answer ARP before they are finally booted. This is
|
---|
| 911 | +not wonderful taking into account that clients using RARPD in 2002
|
---|
| 912 | +are all unsupported relic creatures of 90's and even earlier.
|
---|
| 913 | +.SH "AVAILABILITY"
|
---|
| 914 | +.PP
|
---|
| 915 | +\fBrarpd\fR is part of \fIiputils\fR package
|
---|
| 916 | +and the latest versions are available in source form at
|
---|
| 917 | +http://www.skbuff.net/iputils/iputils-current.tar.bz2.
|
---|
| 918 | diff -Naur iputils-s20150815.orig/doc/rdisc.8 iputils-s20150815/doc/rdisc.8
|
---|
| 919 | --- iputils-s20150815.orig/doc/rdisc.8 1970-01-01 00:00:00.000000000 +0000
|
---|
| 920 | +++ iputils-s20150815/doc/rdisc.8 2015-08-24 00:27:13.124315607 +0000
|
---|
| 921 | @@ -0,0 +1,122 @@
|
---|
| 922 | +.\" This manpage has been automatically generated by docbook2man
|
---|
| 923 | +.\" from a DocBook document. This tool can be found at:
|
---|
| 924 | +.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
---|
| 925 | +.\" Please send any bug reports, improvements, comments, patches,
|
---|
| 926 | +.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
---|
| 927 | +.TH "RDISC" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
|
---|
| 928 | +.SH NAME
|
---|
| 929 | +rdisc \- network router discovery daemon
|
---|
| 930 | +.SH SYNOPSIS
|
---|
| 931 | +
|
---|
| 932 | +\fBrdisc\fR [\fB-abdfrstvV\fR] [\fB-p \fIpreference\fB\fR] [\fB-T \fImax_interval\fB\fR] [\fB\fIsend_address\fB\fR] [\fB\fIreceive_address\fB\fR]
|
---|
| 933 | +
|
---|
| 934 | +.SH "DESCRIPTION"
|
---|
| 935 | +.PP
|
---|
| 936 | +\fBrdisc\fR implements client side of the ICMP router discover protocol.
|
---|
| 937 | +\fBrdisc\fR is invoked at boot time to populate the network
|
---|
| 938 | +routing tables with default routes.
|
---|
| 939 | +.PP
|
---|
| 940 | +\fBrdisc\fR listens on the ALL_HOSTS (224.0.0.1) multicast address
|
---|
| 941 | +(or \fIreceive_address\fR provided it is given)
|
---|
| 942 | +for ROUTER_ADVERTISE messages from routers. The received
|
---|
| 943 | +messages are handled by first ignoring those listed router addresses
|
---|
| 944 | +with which the host does not share a network. Among the remaining addresses
|
---|
| 945 | +the ones with the highest preference are selected as default routers
|
---|
| 946 | +and a default route is entered in the kernel routing table
|
---|
| 947 | +for each one of them.
|
---|
| 948 | +.PP
|
---|
| 949 | +Optionally, \fBrdisc\fR can avoid waiting for routers to announce
|
---|
| 950 | +themselves by sending out a few ROUTER_SOLICITATION messages
|
---|
| 951 | +to the ALL_ROUTERS (224.0.0.2) multicast address
|
---|
| 952 | +(or \fIsend_address\fR provided it is given)
|
---|
| 953 | +when it is started.
|
---|
| 954 | +.PP
|
---|
| 955 | +A timer is associated with each router address and the address will
|
---|
| 956 | +no longer be considered for inclusion in the the routing tables if the
|
---|
| 957 | +timer expires before a new
|
---|
| 958 | +\fBadvertise\fR message is received from the router.
|
---|
| 959 | +The address will also be excluded from consideration if the host receives an
|
---|
| 960 | +\fBadvertise\fR
|
---|
| 961 | +message with the preference being maximally negative.
|
---|
| 962 | +.PP
|
---|
| 963 | +Server side of router discovery protocol is supported by Cisco IOS
|
---|
| 964 | +and by any more or less complete UNIX routing daemon, f.e \fBgated\fR.
|
---|
| 965 | +Or, \fBrdisc\fR can act as responder, if compiled with -DRDISC_SERVER.
|
---|
| 966 | +.SH "OPTIONS"
|
---|
| 967 | +.TP
|
---|
| 968 | +\fB-a\fR
|
---|
| 969 | +Accept all routers independently of the preference they have in their
|
---|
| 970 | +\fBadvertise\fR messages.
|
---|
| 971 | +Normally \fBrdisc\fR only accepts (and enters in the kernel routing
|
---|
| 972 | +tables) the router or routers with the highest preference.
|
---|
| 973 | +.TP
|
---|
| 974 | +\fB-b\fR
|
---|
| 975 | +Opposite to \fB-a\fR, i.e. install only router with the best
|
---|
| 976 | +preference value. It is default behaviour.
|
---|
| 977 | +.TP
|
---|
| 978 | +\fB-d\fR
|
---|
| 979 | +Send debugging messages to syslog.
|
---|
| 980 | +.TP
|
---|
| 981 | +\fB-f\fR
|
---|
| 982 | +Run \fBrdisc\fR forever even if no routers are found.
|
---|
| 983 | +Normally \fBrdisc\fR gives up if it has not received any
|
---|
| 984 | +\fBadvertise\fR message after after soliciting three times,
|
---|
| 985 | +in which case it exits with a non-zero exit code.
|
---|
| 986 | +If \fB-f\fR is not specified in the first form then
|
---|
| 987 | +\fB-s\fR must be specified.
|
---|
| 988 | +.TP
|
---|
| 989 | +\fB-r\fR
|
---|
| 990 | +Responder mode, available only if compiled with -DRDISC_SERVER.
|
---|
| 991 | +.TP
|
---|
| 992 | +\fB-s\fR
|
---|
| 993 | +Send three \fBsolicitation\fR messages initially to quickly discover
|
---|
| 994 | +the routers when the system is booted.
|
---|
| 995 | +When \fB-s\fR is specified \fBrdisc\fR
|
---|
| 996 | +exits with a non-zero exit code if it can not find any routers.
|
---|
| 997 | +This can be overridden with the \fB-f\fR option.
|
---|
| 998 | +.TP
|
---|
| 999 | +\fB-p \fIpreference\fB\fR
|
---|
| 1000 | +Set preference in advertisement.
|
---|
| 1001 | +Available only with -r option.
|
---|
| 1002 | +.TP
|
---|
| 1003 | +\fB-T \fImax_interval\fB\fR
|
---|
| 1004 | +Set maximum advertisement interval in seconds. Default is 600 secs.
|
---|
| 1005 | +Available only with -r option.
|
---|
| 1006 | +.TP
|
---|
| 1007 | +\fB-t\fR
|
---|
| 1008 | +Test mode. Do not go to background.
|
---|
| 1009 | +.TP
|
---|
| 1010 | +\fB-v\fR
|
---|
| 1011 | +Be verbose i.e. send lots of debugging messages to syslog.
|
---|
| 1012 | +.TP
|
---|
| 1013 | +\fB-V\fR
|
---|
| 1014 | +Print version and exit.
|
---|
| 1015 | +.SH "HISTORY"
|
---|
| 1016 | +.PP
|
---|
| 1017 | +This program was developed by Sun Microsystems (see copyright
|
---|
| 1018 | +notice in source file). It was ported to Linux by
|
---|
| 1019 | +Alexey Kuznetsov
|
---|
| 1020 | +<kuznet@ms2.inr.ac.ru>.
|
---|
| 1021 | +It is now maintained by
|
---|
| 1022 | +YOSHIFUJI Hideaki
|
---|
| 1023 | +<yoshfuji@skbuff.net>.
|
---|
| 1024 | +.SH "SEE ALSO"
|
---|
| 1025 | +.PP
|
---|
| 1026 | +\fBicmp\fR(7),
|
---|
| 1027 | +\fBinet\fR(7),
|
---|
| 1028 | +\fBping\fR(8).
|
---|
| 1029 | +.SH "REFERENCES"
|
---|
| 1030 | +.PP
|
---|
| 1031 | +Deering, S.E.,ed "ICMP Router Discovery Messages",
|
---|
| 1032 | +RFC1256, Network Information Center, SRI International,
|
---|
| 1033 | +Menlo Park, Calif., September 1991.
|
---|
| 1034 | +.SH "SECURITY"
|
---|
| 1035 | +.PP
|
---|
| 1036 | +\fBrdisc\fR requires CAP_NET_RAW to listen
|
---|
| 1037 | +and send ICMP messages and capability CAP_NET_ADMIN
|
---|
| 1038 | +to update routing tables.
|
---|
| 1039 | +.SH "AVAILABILITY"
|
---|
| 1040 | +.PP
|
---|
| 1041 | +\fBrdisc\fR is part of \fIiputils\fR package
|
---|
| 1042 | +and the latest versions are available in source form at
|
---|
| 1043 | +http://www.skbuff.net/iputils/iputils-current.tar.bz2.
|
---|
| 1044 | diff -Naur iputils-s20150815.orig/doc/tftpd.8 iputils-s20150815/doc/tftpd.8
|
---|
| 1045 | --- iputils-s20150815.orig/doc/tftpd.8 1970-01-01 00:00:00.000000000 +0000
|
---|
| 1046 | +++ iputils-s20150815/doc/tftpd.8 2015-08-24 00:27:13.260972607 +0000
|
---|
| 1047 | @@ -0,0 +1,85 @@
|
---|
| 1048 | +.\" This manpage has been automatically generated by docbook2man
|
---|
| 1049 | +.\" from a DocBook document. This tool can be found at:
|
---|
| 1050 | +.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
---|
| 1051 | +.\" Please send any bug reports, improvements, comments, patches,
|
---|
| 1052 | +.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
---|
| 1053 | +.TH "TFTPD" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
|
---|
| 1054 | +.SH NAME
|
---|
| 1055 | +tftpd \- Trivial File Transfer Protocol server
|
---|
| 1056 | +.SH SYNOPSIS
|
---|
| 1057 | +
|
---|
| 1058 | +\fBtftpd\fR \fB\fIdirectory\fB\fR
|
---|
| 1059 | +
|
---|
| 1060 | +.SH "DESCRIPTION"
|
---|
| 1061 | +.PP
|
---|
| 1062 | +\fBtftpd\fR is a server which supports the DARPA
|
---|
| 1063 | +Trivial File Transfer Protocol
|
---|
| 1064 | +(RFC1350).
|
---|
| 1065 | +The TFTP server is started
|
---|
| 1066 | +by \fBinetd\fR(8).
|
---|
| 1067 | +.PP
|
---|
| 1068 | +\fIdirectory\fR is required argument; if it is not given
|
---|
| 1069 | +\fBtftpd\fR aborts. This path is prepended to any file name requested
|
---|
| 1070 | +via TFTP protocol, effectively chrooting \fBtftpd\fR to this directory.
|
---|
| 1071 | +File names are validated not to escape out of this directory, however
|
---|
| 1072 | +administrator may configure such escape using symbolic links.
|
---|
| 1073 | +.PP
|
---|
| 1074 | +It is in difference of variants of \fBtftpd\fR usually distributed
|
---|
| 1075 | +with unix-like systems, which take a list of directories and match
|
---|
| 1076 | +file names to start from one of given prefixes or to some random
|
---|
| 1077 | +default, when no arguments were given. There are two reasons not to
|
---|
| 1078 | +behave in this way: first, it is inconvenient, clients are not expected
|
---|
| 1079 | +to know something about layout of filesystem on server host.
|
---|
| 1080 | +And second, TFTP protocol is not a tool for browsing of server's filesystem,
|
---|
| 1081 | +it is just an agent allowing to boot dumb clients.
|
---|
| 1082 | +.PP
|
---|
| 1083 | +In the case when \fBtftpd\fR is used together with
|
---|
| 1084 | +\fBrarpd\fR(8),
|
---|
| 1085 | +tftp directories in these services should coincide and it is expected
|
---|
| 1086 | +that each client booted via TFTP has boot image corresponding
|
---|
| 1087 | +its IP address with an architecture suffix following Sun Microsystems
|
---|
| 1088 | +conventions. See
|
---|
| 1089 | +\fBrarpd\fR(8)
|
---|
| 1090 | +for more details.
|
---|
| 1091 | +.SH "SECURITY"
|
---|
| 1092 | +.PP
|
---|
| 1093 | +TFTP protocol does not provide any authentication.
|
---|
| 1094 | +Due to this capital flaw \fBtftpd\fR is not able to restrict
|
---|
| 1095 | +access to files and will allow only publically readable
|
---|
| 1096 | +files to be accessed. Files may be written only if they already
|
---|
| 1097 | +exist and are publically writable.
|
---|
| 1098 | +.PP
|
---|
| 1099 | +Impact is evident, directory exported via TFTP \fBmust not\fR
|
---|
| 1100 | +contain sensitive information of any kind, everyone is allowed
|
---|
| 1101 | +to read it as soon as a client is allowed. Boot images do not contain
|
---|
| 1102 | +such information as rule, however you should think twice before
|
---|
| 1103 | +publishing f.e. Cisco IOS config files via TFTP, they contain
|
---|
| 1104 | +\fBunencrypted\fR passwords and may contain some information
|
---|
| 1105 | +about the network, which you were not going to make public.
|
---|
| 1106 | +.PP
|
---|
| 1107 | +The \fBtftpd\fR server should be executed by \fBinetd\fR
|
---|
| 1108 | +with dropped root privileges, namely with a user ID giving minimal
|
---|
| 1109 | +access to files published in tftp directory. If it is executed
|
---|
| 1110 | +as superuser occasionally, \fBtftpd\fR drops its UID and GID
|
---|
| 1111 | +to 65534, which is most likely not the thing which you expect.
|
---|
| 1112 | +However, this is not very essential; remember, only files accessible
|
---|
| 1113 | +for everyone can be read or written via TFTP.
|
---|
| 1114 | +.SH "SEE ALSO"
|
---|
| 1115 | +.PP
|
---|
| 1116 | +\fBrarpd\fR(8),
|
---|
| 1117 | +\fBtftp\fR(1),
|
---|
| 1118 | +\fBinetd\fR(8).
|
---|
| 1119 | +.SH "HISTORY"
|
---|
| 1120 | +.PP
|
---|
| 1121 | +The \fBtftpd\fR command appeared in 4.2BSD. The source in iputils
|
---|
| 1122 | +is cleaned up both syntactically (ANSIized) and semantically (UDP socket IO).
|
---|
| 1123 | +.PP
|
---|
| 1124 | +It is distributed with iputils mostly as good demo of an interesting feature
|
---|
| 1125 | +(MSG_CONFIRM) allowing to boot long images by dumb clients
|
---|
| 1126 | +not answering ARP requests until they are finally booted.
|
---|
| 1127 | +However, this is full functional and can be used in production.
|
---|
| 1128 | +.SH "AVAILABILITY"
|
---|
| 1129 | +.PP
|
---|
| 1130 | +\fBtftpd\fR is part of \fIiputils\fR package
|
---|
| 1131 | +and the latest versions are available in source form at
|
---|
| 1132 | +http://www.skbuff.net/iputils/iputils-current.tar.bz2.
|
---|
| 1133 | diff -Naur iputils-s20150815.orig/doc/tracepath.8 iputils-s20150815/doc/tracepath.8
|
---|
| 1134 | --- iputils-s20150815.orig/doc/tracepath.8 1970-01-01 00:00:00.000000000 +0000
|
---|
| 1135 | +++ iputils-s20150815/doc/tracepath.8 2015-08-24 00:27:13.394296509 +0000
|
---|
| 1136 | @@ -0,0 +1,104 @@
|
---|
| 1137 | +.\" This manpage has been automatically generated by docbook2man
|
---|
| 1138 | +.\" from a DocBook document. This tool can be found at:
|
---|
| 1139 | +.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
---|
| 1140 | +.\" Please send any bug reports, improvements, comments, patches,
|
---|
| 1141 | +.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
---|
| 1142 | +.TH "TRACEPATH" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
|
---|
| 1143 | +.SH NAME
|
---|
| 1144 | +tracepath, tracepath6 \- traces path to a network host discovering MTU along this path
|
---|
| 1145 | +.SH SYNOPSIS
|
---|
| 1146 | +
|
---|
| 1147 | +\fBtracepath\fR [\fB-n\fR] [\fB-b\fR] [\fB-l \fIpktlen\fB\fR] [\fB-m \fImax_hops\fB\fR] [\fB-p \fIport\fB\fR] \fB\fIdestination\fB\fR
|
---|
| 1148 | +
|
---|
| 1149 | +.SH "DESCRIPTION"
|
---|
| 1150 | +.PP
|
---|
| 1151 | +It traces path to \fIdestination\fR discovering MTU along this path.
|
---|
| 1152 | +It uses UDP port \fIport\fR or some random port.
|
---|
| 1153 | +It is similar to \fBtraceroute\fR, only does not require superuser
|
---|
| 1154 | +privileges and has no fancy options.
|
---|
| 1155 | +.PP
|
---|
| 1156 | +\fBtracepath6\fR is good replacement for \fBtraceroute6\fR
|
---|
| 1157 | +and classic example of application of Linux error queues.
|
---|
| 1158 | +The situation with IPv4 is worse, because commercial
|
---|
| 1159 | +IP routers do not return enough information in ICMP error messages.
|
---|
| 1160 | +Probably, it will change, when they will be updated.
|
---|
| 1161 | +For now it uses Van Jacobson's trick, sweeping a range
|
---|
| 1162 | +of UDP ports to maintain trace history.
|
---|
| 1163 | +.SH "OPTIONS"
|
---|
| 1164 | +.TP
|
---|
| 1165 | +\fB-n\fR
|
---|
| 1166 | +Print primarily IP addresses numerically.
|
---|
| 1167 | +.TP
|
---|
| 1168 | +\fB-b\fR
|
---|
| 1169 | +Print both of host names and IP addresses.
|
---|
| 1170 | +.TP
|
---|
| 1171 | +\fB-l\fR
|
---|
| 1172 | +Sets the initial packet length to \fIpktlen\fR instead of
|
---|
| 1173 | +65535 for \fBtracepath\fR or 128000 for \fBtracepath6\fR.
|
---|
| 1174 | +.TP
|
---|
| 1175 | +\fB-m\fR
|
---|
| 1176 | +Set maximum hops (or maximum TTLs) to \fImax_hops\fR
|
---|
| 1177 | +instead of 30.
|
---|
| 1178 | +.TP
|
---|
| 1179 | +\fB-p\fR
|
---|
| 1180 | +Sets the initial destination port to use.
|
---|
| 1181 | +.SH "OUTPUT"
|
---|
| 1182 | +.PP
|
---|
| 1183 | +
|
---|
| 1184 | +.nf
|
---|
| 1185 | +root@mops:~ # tracepath6 3ffe:2400:0:109::2
|
---|
| 1186 | + 1?: [LOCALHOST] pmtu 1500
|
---|
| 1187 | + 1: dust.inr.ac.ru 0.411ms
|
---|
| 1188 | + 2: dust.inr.ac.ru asymm 1 0.390ms pmtu 1480
|
---|
| 1189 | + 2: 3ffe:2400:0:109::2 463.514ms reached
|
---|
| 1190 | + Resume: pmtu 1480 hops 2 back 2
|
---|
| 1191 | +.fi
|
---|
| 1192 | +.PP
|
---|
| 1193 | +The first column shows TTL of the probe, followed by colon.
|
---|
| 1194 | +Usually value of TTL is obtained from reply from network,
|
---|
| 1195 | +but sometimes reply does not contain necessary information and
|
---|
| 1196 | +we have to guess it. In this case the number is followed by ?.
|
---|
| 1197 | +.PP
|
---|
| 1198 | +The second column shows the network hop, which replied to the probe.
|
---|
| 1199 | +It is either address of router or word [LOCALHOST], if
|
---|
| 1200 | +the probe was not sent to the network.
|
---|
| 1201 | +.PP
|
---|
| 1202 | +The rest of line shows miscellaneous information about path to
|
---|
| 1203 | +the correspinding network hop. As rule it contains value of RTT.
|
---|
| 1204 | +Additionally, it can show Path MTU, when it changes.
|
---|
| 1205 | +If the path is asymmetric
|
---|
| 1206 | +or the probe finishes before it reach prescribed hop, difference
|
---|
| 1207 | +between number of hops in forward and backward direction is shown
|
---|
| 1208 | +following keyword async. This information is not reliable.
|
---|
| 1209 | +F.e. the third line shows asymmetry of 1, it is because the first probe
|
---|
| 1210 | +with TTL of 2 was rejected at the first hop due to Path MTU Discovery.
|
---|
| 1211 | +.PP
|
---|
| 1212 | +The last line summarizes information about all the path to the destination,
|
---|
| 1213 | +it shows detected Path MTU, amount of hops to the destination and our
|
---|
| 1214 | +guess about amount of hops from the destination to us, which can be
|
---|
| 1215 | +different when the path is asymmetric.
|
---|
| 1216 | +.SH "SEE ALSO"
|
---|
| 1217 | +.PP
|
---|
| 1218 | +\fBtraceroute\fR(8),
|
---|
| 1219 | +\fBtraceroute6\fR(8),
|
---|
| 1220 | +\fBping\fR(8).
|
---|
| 1221 | +.SH "AUTHOR"
|
---|
| 1222 | +.PP
|
---|
| 1223 | +\fBtracepath\fR was written by
|
---|
| 1224 | +Alexey Kuznetsov
|
---|
| 1225 | +<kuznet@ms2.inr.ac.ru>.
|
---|
| 1226 | +.SH "SECURITY"
|
---|
| 1227 | +.PP
|
---|
| 1228 | +No security issues.
|
---|
| 1229 | +.PP
|
---|
| 1230 | +This lapidary deserves to be elaborated.
|
---|
| 1231 | +\fBtracepath\fR is not a privileged program, unlike
|
---|
| 1232 | +\fBtraceroute\fR, \fBping\fR and other beasts of this kind.
|
---|
| 1233 | +\fBtracepath\fR may be executed by everyone who has some access
|
---|
| 1234 | +to network, enough to send UDP datagrams to investigated destination
|
---|
| 1235 | +using given port.
|
---|
| 1236 | +.SH "AVAILABILITY"
|
---|
| 1237 | +.PP
|
---|
| 1238 | +\fBtracepath\fR is part of \fIiputils\fR package
|
---|
| 1239 | +and the latest versions are available in source form at
|
---|
| 1240 | +http://www.skbuff.net/iputils/iputils-current.tar.bz2.
|
---|
| 1241 | diff -Naur iputils-s20150815.orig/doc/traceroute6.8 iputils-s20150815/doc/traceroute6.8
|
---|
| 1242 | --- iputils-s20150815.orig/doc/traceroute6.8 1970-01-01 00:00:00.000000000 +0000
|
---|
| 1243 | +++ iputils-s20150815/doc/traceroute6.8 2015-08-24 00:27:13.527620409 +0000
|
---|
| 1244 | @@ -0,0 +1,42 @@
|
---|
| 1245 | +.\" This manpage has been automatically generated by docbook2man
|
---|
| 1246 | +.\" from a DocBook document. This tool can be found at:
|
---|
| 1247 | +.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
---|
| 1248 | +.\" Please send any bug reports, improvements, comments, patches,
|
---|
| 1249 | +.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
---|
| 1250 | +.TH "TRACEROUTE6" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
|
---|
| 1251 | +.SH NAME
|
---|
| 1252 | +traceroute6 \- traces path to a network host
|
---|
| 1253 | +.SH SYNOPSIS
|
---|
| 1254 | +
|
---|
| 1255 | +\fBtraceroute6\fR [\fB-dnrvV\fR] [\fB-i \fIinterface\fB\fR] [\fB-m \fImax_ttl\fB\fR] [\fB-p \fIport\fB\fR] [\fB-q \fImax_probes\fB\fR] [\fB-s \fIsource\fB\fR] [\fB-w \fIwait time\fB\fR] \fB\fIdestination\fB\fR [\fB\fIsize\fB\fR]
|
---|
| 1256 | +
|
---|
| 1257 | +.SH "DESCRIPTION"
|
---|
| 1258 | +.PP
|
---|
| 1259 | +Description can be found in
|
---|
| 1260 | +\fBtraceroute\fR(8),
|
---|
| 1261 | +all the references to IP replaced to IPv6. It is needless to copy
|
---|
| 1262 | +the description from there.
|
---|
| 1263 | +.SH "SEE ALSO"
|
---|
| 1264 | +.PP
|
---|
| 1265 | +\fBtraceroute\fR(8),
|
---|
| 1266 | +\fBtracepath\fR(8),
|
---|
| 1267 | +\fBping\fR(8).
|
---|
| 1268 | +.SH "HISTORY"
|
---|
| 1269 | +.PP
|
---|
| 1270 | +This program has long history. Author of \fBtraceroute\fR
|
---|
| 1271 | +is Van Jacobson and it first appeared in 1988. This clone is
|
---|
| 1272 | +based on a port of \fBtraceroute\fR to IPv6 published
|
---|
| 1273 | +in NRL IPv6 distribution in 1996. In turn, it was ported
|
---|
| 1274 | +to Linux by Pedro Roque. After this it was kept in sync by
|
---|
| 1275 | +Alexey Kuznetsov
|
---|
| 1276 | +<kuznet@ms2.inr.ac.ru>. And eventually entered
|
---|
| 1277 | +\fBiputils\fR package.
|
---|
| 1278 | +.SH "SECURITY"
|
---|
| 1279 | +.PP
|
---|
| 1280 | +\fBtracepath6\fR requires CAP_NET_RAW capability
|
---|
| 1281 | +to be executed. It is safe to be used as set-uid root.
|
---|
| 1282 | +.SH "AVAILABILITY"
|
---|
| 1283 | +.PP
|
---|
| 1284 | +\fBtraceroute6\fR is part of \fIiputils\fR package
|
---|
| 1285 | +and the latest versions are available in source form at
|
---|
| 1286 | +http://www.skbuff.net/iputils/iputils-current.tar.bz2.
|
---|