source:
patches/iputils-s20121221-fixes-1.patch@
602f33a
Last change on this file since 602f33a was 602f33a, checked in by , 11 years ago | |
---|---|
|
|
File size: 149.5 KB |
-
iputils-s20121221
Submitted By: William Harrington <kb0iic at cross-lfs dot org> Date: 2013-08-06 Initial Package Version: s20121221 Upstream Status: Unknown Origin: Unknown Description: Contains Fixes for Various Issues and Manpages diff -Naur iputils-s20121221.orig/Makefile iputils-s20121221/Makefile
old new 2 2 # Configuration 3 3 # 4 4 5 # CC6 CC=gcc7 5 # Path to parent kernel include files directory 8 6 LIBC_INCLUDE=/usr/include 9 7 # Libraries … … 36 34 37 35 # GNU TLS library for ping6 [yes|no|static] 38 36 USE_GNUTLS=yes 39 # Crypto library for ping6 [shared|static ]37 # Crypto library for ping6 [shared|static|no] 40 38 USE_CRYPTO=shared 41 39 # Resolv library for ping6 [yes|static] 42 40 USE_RESOLV=yes … … 48 46 49 47 # ------------------------------------- 50 48 # What a pity, all new gccs are buggy and -Werror does not work. Sigh. 51 # CCOPT=-fno-strict-aliasing -Wstrict-prototypes -Wall -Werror -g 52 CCOPT=-fno-strict-aliasing -Wstrict-prototypes -Wall -g 53 CCOPTOPT=-O3 54 GLIBCFIX=-D_GNU_SOURCE 55 DEFINES= 49 # CFLAGS+=-fno-strict-aliasing -Wstrict-prototypes -Wall -Werror -g 50 CFLAGS?=-O3 -g 51 CFLAGS+=-fno-strict-aliasing -Wstrict-prototypes -Wall 52 CPPFLAGS+=-D_GNU_SOURCE 56 53 LDLIB= 57 54 58 55 FUNC_LIB = $(if $(filter static,$(1)),$(LDFLAG_STATIC) $(2) $(LDFLAG_DYNAMIC),$(2)) … … 63 60 LIB_CRYPTO = $(call FUNC_LIB,$(USE_GNUTLS),$(LDFLAG_GNUTLS)) 64 61 DEF_CRYPTO = -DUSE_GNUTLS 65 62 else 63 ifneq ($(USE_CRYPTO),no) 66 64 LIB_CRYPTO = $(call FUNC_LIB,$(USE_CRYPTO),$(LDFLAG_CRYPTO)) 65 DEF_CRYPTO = -DUSE_OPENSSL 66 endif 67 67 endif 68 68 69 69 # USE_RESOLV: LIB_RESOLV … … 110 110 IPV6_TARGETS=tracepath6 traceroute6 ping6 111 111 TARGETS=$(IPV4_TARGETS) $(IPV6_TARGETS) 112 112 113 CFLAGS=$(CCOPTOPT) $(CCOPT) $(GLIBCFIX) $(DEFINES)114 113 LDLIBS=$(LDLIB) $(ADDLIB) 115 114 116 115 UNAME_N:=$(shell uname -n) … … 129 128 $(COMPILE.c) $< $(DEF_$(patsubst %.o,%,$@)) -S -o $@ 130 129 %.o: %.c 131 130 $(COMPILE.c) $< $(DEF_$(patsubst %.o,%,$@)) -o $@ 131 LINK.o += $(CFLAGS) 132 132 $(TARGETS): %: %.o 133 133 $(LINK.o) $^ $(LIB_$@) $(LDLIBS) -o $@ 134 134 … … 149 149 DEF_ping_common = $(DEF_CAP) $(DEF_IDN) 150 150 DEF_ping = $(DEF_CAP) $(DEF_IDN) $(DEF_WITHOUT_IFADDRS) 151 151 LIB_ping = $(LIB_CAP) $(LIB_IDN) 152 DEF_ping6 = $(DEF_CAP) $(DEF_IDN) $(DEF_WITHOUT_IFADDRS) $(DEF_ENABLE_PING6_RTHDR) 152 DEF_ping6 = $(DEF_CAP) $(DEF_IDN) $(DEF_WITHOUT_IFADDRS) $(DEF_ENABLE_PING6_RTHDR) $(DEF_CRYPTO) 153 153 LIB_ping6 = $(LIB_CAP) $(LIB_IDN) $(LIB_RESOLV) $(LIB_CRYPTO) 154 154 155 155 ping: ping_common.o -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/arping.8 iputils-s20121221/doc/arping.8
old new 1 .\" This manpage has been automatically generated by docbook2man 2 .\" from a DocBook document. This tool can be found at: 3 .\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 4 .\" Please send any bug reports, improvements, comments, patches, 5 .\" etc. to Steve Cheng <steve@ggi-project.org>. 6 .TH "ARPING" "8" "04 January 2013" "iputils-121221" "System Manager's Manual: iputils" 7 .SH NAME 8 arping \- send ARP REQUEST to a neighbour host 9 .SH SYNOPSIS 10 11 \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 12 13 .SH "DESCRIPTION" 14 .PP 15 Ping \fIdestination\fR on device \fIinterface\fR by ARP packets, 16 using source address \fIsource\fR. 17 .SH "OPTIONS" 18 .TP 19 \fB-A\fR 20 The same as \fB-U\fR, but ARP REPLY packets used instead 21 of ARP REQUEST. 22 .TP 23 \fB-b\fR 24 Send only MAC level broadcasts. Normally \fBarping\fR starts 25 from sending broadcast, and switch to unicast after reply received. 26 .TP 27 \fB-c \fIcount\fB\fR 28 Stop after sending \fIcount\fR ARP REQUEST 29 packets. With 30 \fIdeadline\fR 31 option, \fBarping\fR waits for 32 \fIcount\fR ARP REPLY packets, until the timeout expires. 33 .TP 34 \fB-D\fR 35 Duplicate address detection mode (DAD). See 36 RFC2131, 4.4.1. 37 Returns 0, if DAD succeeded i.e. no replies are received 38 .TP 39 \fB-f\fR 40 Finish after the first reply confirming that target is alive. 41 .TP 42 \fB-I \fIinterface\fB\fR 43 Name of network device where to send ARP REQUEST packets. 44 .TP 45 \fB-h\fR 46 Print help page and exit. 47 .TP 48 \fB-q\fR 49 Quiet output. Nothing is displayed. 50 .TP 51 \fB-s \fIsource\fB\fR 52 IP source address to use in ARP packets. 53 If this option is absent, source address is: 54 .RS 55 .TP 0.2i 56 \(bu 57 In DAD mode (with option \fB-D\fR) set to 0.0.0.0. 58 .TP 0.2i 59 \(bu 60 In Unsolicited ARP mode (with options \fB-U\fR or \fB-A\fR) 61 set to \fIdestination\fR. 62 .TP 0.2i 63 \(bu 64 Otherwise, it is calculated from routing tables. 65 .RE 66 .TP 67 \fB-U\fR 68 Unsolicited ARP mode to update neighbours' ARP caches. 69 No replies are expected. 70 .TP 71 \fB-V\fR 72 Print version of the program and exit. 73 .TP 74 \fB-w \fIdeadline\fB\fR 75 Specify a timeout, in seconds, before 76 \fBarping\fR 77 exits regardless of how many 78 packets have been sent or received. In this case 79 \fBarping\fR 80 does not stop after 81 \fIcount\fR 82 packet are sent, it waits either for 83 \fIdeadline\fR 84 expire or until 85 \fIcount\fR 86 probes are answered. 87 .SH "SEE ALSO" 88 .PP 89 \fBping\fR(8), 90 \fBclockdiff\fR(8), 91 \fBtracepath\fR(8). 92 .SH "AUTHOR" 93 .PP 94 \fBarping\fR was written by 95 Alexey Kuznetsov 96 <kuznet@ms2.inr.ac.ru>. 97 It is now maintained by 98 YOSHIFUJI Hideaki 99 <yoshfuji@skbuff.net>. 100 .SH "SECURITY" 101 .PP 102 \fBarping\fR requires CAP_NET_RAW capability 103 to be executed. It is not recommended to be used as set-uid root, 104 because it allows user to modify ARP caches of neighbour hosts. 105 .SH "AVAILABILITY" 106 .PP 107 \fBarping\fR is part of \fIiputils\fR package 108 and the latest versions are available in source form at 109 http://www.skbuff.net/iputils/iputils-current.tar.bz2. -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/clockdiff.8 iputils-s20121221/doc/clockdiff.8
old new 1 .\" This manpage has been automatically generated by docbook2man 2 .\" from a DocBook document. This tool can be found at: 3 .\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 4 .\" Please send any bug reports, improvements, comments, patches, 5 .\" etc. to Steve Cheng <steve@ggi-project.org>. 6 .TH "CLOCKDIFF" "8" "04 January 2013" "iputils-121221" "System Manager's Manual: iputils" 7 .SH NAME 8 clockdiff \- measure clock difference between hosts 9 .SH SYNOPSIS 10 11 \fBclockdiff\fR [\fB-o\fR] [\fB-o1\fR] \fB\fIdestination\fB\fR 12 13 .SH "DESCRIPTION" 14 .PP 15 \fBclockdiff\fR Measures clock difference between us and 16 \fIdestination\fR with 1 msec resolution using ICMP TIMESTAMP 17 [2] 18 packets or, optionally, IP TIMESTAMP option 19 [3] 20 option added to ICMP ECHO. 21 [1] 22 .SH "OPTIONS" 23 .TP 24 \fB-o\fR 25 Use IP TIMESTAMP with ICMP ECHO instead of ICMP TIMESTAMP 26 messages. It is useful with some destinations, which do not support 27 ICMP TIMESTAMP (f.e. Solaris <2.4). 28 .TP 29 \fB-o1\fR 30 Slightly different form of \fB-o\fR, namely it uses three-term 31 IP TIMESTAMP with prespecified hop addresses instead of four term one. 32 What flavor works better depends on target host. Particularly, 33 \fB-o\fR is better for Linux. 34 .SH "WARNINGS" 35 .TP 0.2i 36 \(bu 37 Some nodes (Cisco) use non-standard timestamps, which is allowed 38 by RFC, but makes timestamps mostly useless. 39 .TP 0.2i 40 \(bu 41 Some nodes generate messed timestamps (Solaris>2.4), when 42 run \fBxntpd\fR. Seems, its IP stack uses a corrupted clock source, 43 which is synchronized to time-of-day clock periodically and jumps 44 randomly making timestamps mostly useless. Good news is that you can 45 use NTP in this case, which is even better. 46 .TP 0.2i 47 \(bu 48 \fBclockdiff\fR shows difference in time modulo 24 days. 49 .SH "SEE ALSO" 50 .PP 51 \fBping\fR(8), 52 \fBarping\fR(8), 53 \fBtracepath\fR(8). 54 .SH "REFERENCES" 55 .PP 56 [1] ICMP ECHO, 57 RFC0792, page 14. 58 .PP 59 [2] ICMP TIMESTAMP, 60 RFC0792, page 16. 61 .PP 62 [3] IP TIMESTAMP option, 63 RFC0791, 3.1, page 16. 64 .SH "AUTHOR" 65 .PP 66 \fBclockdiff\fR was compiled by 67 Alexey Kuznetsov 68 <kuznet@ms2.inr.ac.ru>. It was based on code borrowed 69 from BSD \fBtimed\fR daemon. 70 It is now maintained by 71 YOSHIFUJI Hideaki 72 <yoshfuji@skbuff.net>. 73 .SH "SECURITY" 74 .PP 75 \fBclockdiff\fR requires CAP_NET_RAW capability 76 to be executed. It is safe to be used as set-uid root. 77 .SH "AVAILABILITY" 78 .PP 79 \fBclockdiff\fR is part of \fIiputils\fR package 80 and the latest versions are available in source form at 81 http://www.skbuff.net/iputils/iputils-current.tar.bz2. -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/index.html iputils-s20121221/doc/index.html
old new 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 2 <HTML 3 ><HEAD 4 ><TITLE 5 >System Manager's Manual: iputils</TITLE 6 ><META 7 NAME="GENERATOR" 8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK 9 REL="NEXT" 10 TITLE="ping" 11 HREF="r3.html"></HEAD 12 ><BODY 13 CLASS="REFERENCE" 14 BGCOLOR="#FFFFFF" 15 TEXT="#000000" 16 LINK="#0000FF" 17 VLINK="#840084" 18 ALINK="#0000FF" 19 ><DIV 20 CLASS="NAVHEADER" 21 ><TABLE 22 SUMMARY="Header navigation table" 23 WIDTH="100%" 24 BORDER="0" 25 CELLPADDING="0" 26 CELLSPACING="0" 27 ><TR 28 ><TD 29 WIDTH="10%" 30 ALIGN="left" 31 VALIGN="bottom" 32 > </TD 33 ><TD 34 WIDTH="80%" 35 ALIGN="center" 36 VALIGN="bottom" 37 ></TD 38 ><TD 39 WIDTH="10%" 40 ALIGN="right" 41 VALIGN="bottom" 42 ><A 43 HREF="r3.html" 44 ACCESSKEY="N" 45 >Next</A 46 ></TD 47 ></TR 48 ></TABLE 49 ><HR 50 ALIGN="LEFT" 51 WIDTH="100%"></DIV 52 ><DIV 53 CLASS="REFERENCE" 54 ><A 55 NAME="INDEX" 56 ></A 57 ><DIV 58 CLASS="TITLEPAGE" 59 ><H1 60 CLASS="TITLE" 61 >I. System Manager's Manual: iputils</H1 62 ><DIV 63 CLASS="TOC" 64 ><DL 65 ><DT 66 ><B 67 >Table of Contents</B 68 ></DT 69 ><DT 70 ><A 71 HREF="r3.html" 72 >ping</A 73 > -- send ICMP ECHO_REQUEST to network hosts</DT 74 ><DT 75 ><A 76 HREF="r466.html" 77 >arping</A 78 > -- send ARP REQUEST to a neighbour host</DT 79 ><DT 80 ><A 81 HREF="r625.html" 82 >clockdiff</A 83 > -- measure clock difference between hosts</DT 84 ><DT 85 ><A 86 HREF="r720.html" 87 >rarpd</A 88 > -- answer RARP REQUESTs</DT 89 ><DT 90 ><A 91 HREF="r819.html" 92 >tracepath</A 93 > -- traces path to a network host discovering MTU along this path</DT 94 ><DT 95 ><A 96 HREF="r918.html" 97 >traceroute6</A 98 > -- traces path to a network host</DT 99 ><DT 100 ><A 101 HREF="r983.html" 102 >tftpd</A 103 > -- Trivial File Transfer Protocol server</DT 104 ><DT 105 ><A 106 HREF="r1056.html" 107 >ninfod</A 108 > -- Respond to IPv6 Node Information Queries</DT 109 ><DT 110 ><A 111 HREF="r1125.html" 112 >rdisc</A 113 > -- network router discovery daemon</DT 114 ><DT 115 ><A 116 HREF="r1269.html" 117 >pg3</A 118 > -- send stream of UDP packets</DT 119 ></DL 120 ></DIV 121 ></DIV 122 ></DIV 123 ><DIV 124 CLASS="NAVFOOTER" 125 ><HR 126 ALIGN="LEFT" 127 WIDTH="100%"><TABLE 128 SUMMARY="Footer navigation table" 129 WIDTH="100%" 130 BORDER="0" 131 CELLPADDING="0" 132 CELLSPACING="0" 133 ><TR 134 ><TD 135 WIDTH="33%" 136 ALIGN="left" 137 VALIGN="top" 138 > </TD 139 ><TD 140 WIDTH="34%" 141 ALIGN="center" 142 VALIGN="top" 143 > </TD 144 ><TD 145 WIDTH="33%" 146 ALIGN="right" 147 VALIGN="top" 148 ><A 149 HREF="r3.html" 150 ACCESSKEY="N" 151 >Next</A 152 ></TD 153 ></TR 154 ><TR 155 ><TD 156 WIDTH="33%" 157 ALIGN="left" 158 VALIGN="top" 159 > </TD 160 ><TD 161 WIDTH="34%" 162 ALIGN="center" 163 VALIGN="top" 164 > </TD 165 ><TD 166 WIDTH="33%" 167 ALIGN="right" 168 VALIGN="top" 169 >ping</TD 170 ></TR 171 ></TABLE 172 ></DIV 173 ></BODY 174 ></HTML 175 > 176 No newline at end of file -
doc/iputils.html
diff -Naur iputils-s20121221.orig/doc/iputils.html iputils-s20121221/doc/iputils.html
old new 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 2 <HTML 3 ><HEAD 4 ><TITLE 5 >iputils: documentation directory</TITLE 6 ><META 7 NAME="GENERATOR" 8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"></HEAD 9 ><BODY 10 CLASS="ARTICLE" 11 BGCOLOR="#FFFFFF" 12 TEXT="#000000" 13 LINK="#0000FF" 14 VLINK="#840084" 15 ALINK="#0000FF" 16 ><DIV 17 CLASS="ARTICLE" 18 ><DIV 19 CLASS="TITLEPAGE" 20 ><H1 21 CLASS="TITLE" 22 ><A 23 NAME="AEN2" 24 >iputils: documentation directory</A 25 ></H1 26 ><HR></DIV 27 ><DIV 28 CLASS="TOC" 29 ><DL 30 ><DT 31 ><B 32 >Table of Contents</B 33 ></DT 34 ><DT 35 >1. <A 36 HREF="#AEN4" 37 >Index</A 38 ></DT 39 ><DT 40 >2. <A 41 HREF="#AEN34" 42 >Historical notes</A 43 ></DT 44 ><DT 45 >3. <A 46 HREF="#AEN89" 47 >Installation notes</A 48 ></DT 49 ><DT 50 >4. <A 51 HREF="#AEN109" 52 >Availability</A 53 ></DT 54 ><DT 55 >5. <A 56 HREF="#AEN114" 57 >Copying</A 58 ></DT 59 ></DL 60 ></DIV 61 ><DIV 62 CLASS="SECT1" 63 ><H2 64 CLASS="SECT1" 65 ><A 66 NAME="AEN4" 67 >1. Index</A 68 ></H2 69 ><P 70 ></P 71 ><UL 72 ><LI 73 ><P 74 > <A 75 HREF="ping.html" 76 TARGET="_top" 77 >ping, ping6</A 78 >. 79 </P 80 ></LI 81 ><LI 82 ><P 83 > <A 84 HREF="arping.html" 85 TARGET="_top" 86 >arping</A 87 >. 88 </P 89 ></LI 90 ><LI 91 ><P 92 > <A 93 HREF="clockdiff.html" 94 TARGET="_top" 95 >clockdiff</A 96 >. 97 </P 98 ></LI 99 ><LI 100 ><P 101 > <A 102 HREF="rarpd.html" 103 TARGET="_top" 104 >rarpd</A 105 >. 106 </P 107 ></LI 108 ><LI 109 ><P 110 > <A 111 HREF="tracepath.html" 112 TARGET="_top" 113 >tracepath, tracepath6</A 114 >. 115 </P 116 ></LI 117 ><LI 118 ><P 119 > <A 120 HREF="traceroute6.html" 121 TARGET="_top" 122 >traceroute6</A 123 >. 124 </P 125 ></LI 126 ><LI 127 ><P 128 > <A 129 HREF="rdisc.html" 130 TARGET="_top" 131 >rdisc</A 132 >. 133 </P 134 ></LI 135 ><LI 136 ><P 137 > <A 138 HREF="tftpd.html" 139 TARGET="_top" 140 >tftpd</A 141 >. 142 </P 143 ></LI 144 ><LI 145 ><P 146 > <A 147 HREF="pg3.html" 148 TARGET="_top" 149 >pg3, ipg, pgset</A 150 >. 151 </P 152 ></LI 153 ></UL 154 ></DIV 155 ><DIV 156 CLASS="SECT1" 157 ><HR><H2 158 CLASS="SECT1" 159 ><A 160 NAME="AEN34" 161 >2. Historical notes</A 162 ></H2 163 ><P 164 >This package appeared as a desperate attempt to bring some life 165 to state of basic networking applets: <B 166 CLASS="COMMAND" 167 >ping</B 168 >, <B 169 CLASS="COMMAND" 170 >traceroute</B 171 > 172 etc. Though it was known that port of BSD <B 173 CLASS="COMMAND" 174 >ping</B 175 > to Linux 176 was basically broken, neither maintainers of well known (and superb) 177 Linux net-tools package nor maintainers of Linux distributions 178 worried about fixing well known bugs, which were reported in linux-kernel 179 and linux-net mail lists for ages, were identified and nevertheless 180 not repaired. So, one day 1001th resuming of the subject happened 181 to be the last straw to break camel's back, I just parsed my hard disks 182 and collected a set of utilities, which shared the following properties:</P 183 ><P 184 ></P 185 ><UL 186 ><LI 187 ><P 188 >Small 189 </P 190 ></LI 191 ><LI 192 ><P 193 >Useful despite of this 194 </P 195 ></LI 196 ><LI 197 ><P 198 >I never seen it was made right 199 </P 200 ></LI 201 ><LI 202 ><P 203 >Not quite trivial 204 </P 205 ></LI 206 ><LI 207 ><P 208 >Demonstrating some important feature of Linux 209 </P 210 ></LI 211 ><LI 212 ><P 213 >The last but not the least, I use it more or less regularly 214 </P 215 ></LI 216 ></UL 217 ><P 218 >This utility set was not supposed to be a reference set or something like 219 that. Most of them were cloned from some originals: 220 <DIV 221 CLASS="INFORMALTABLE" 222 ><P 223 ></P 224 ><A 225 NAME="AEN54" 226 ></A 227 ><TABLE 228 BORDER="1" 229 CLASS="CALSTABLE" 230 ><COL><COL><TBODY 231 ><TR 232 ><TD 233 >ping</TD 234 ><TD 235 >cloned of an ancient NetTools-B-xx</TD 236 ></TR 237 ><TR 238 ><TD 239 >ping6</TD 240 ><TD 241 >cloned of a very old Pedro's utility set</TD 242 ></TR 243 ><TR 244 ><TD 245 >traceroute6</TD 246 ><TD 247 >cloned of NRL Sep 96 distribution</TD 248 ></TR 249 ><TR 250 ><TD 251 >rdisc</TD 252 ><TD 253 >cloned of SUN in.rdisc</TD 254 ></TR 255 ><TR 256 ><TD 257 >clockdiff</TD 258 ><TD 259 >broken out of some BSD timed</TD 260 ></TR 261 ><TR 262 ><TD 263 >tftpd</TD 264 ><TD 265 >it is clone of some ancient NetKit package</TD 266 ></TR 267 ></TBODY 268 ></TABLE 269 ><P 270 ></P 271 ></DIV 272 ></P 273 ><P 274 >Also I added some utilities written from scratch, namely 275 <B 276 CLASS="COMMAND" 277 >tracepath</B 278 >, <B 279 CLASS="COMMAND" 280 >arping</B 281 > and later <B 282 CLASS="COMMAND" 283 >rarpd</B 284 > 285 (the last one does not satisfy all the criteria, I used it two or three 286 times).</P 287 ><P 288 >Hesitated a bit I overcame temptation to add <B 289 CLASS="COMMAND" 290 >traceroute</B 291 >. 292 The variant released by LBNL to that time was mostly sane and bugs 293 in it were mostly not specific to Linux, but main reason was that 294 the latest version of LBNL <B 295 CLASS="COMMAND" 296 >traceroute</B 297 > was not 298 <SPAN 299 CLASS="emphasis" 300 ><I 301 CLASS="EMPHASIS" 302 >small</I 303 ></SPAN 304 >, it consisted of several files, 305 used a wicked (and failing with Linux :-)) autoconfiguration etc. 306 So, instead I assembled to iputils a simplistic <B 307 CLASS="COMMAND" 308 >tracepath</B 309 > utility 310 and IPv6 version of traceroute, and published my 311 <A 312 HREF="ftp://ftp.inr.ac.ru/ip-routing/lbl-tools" 313 TARGET="_top" 314 > patches</A 315 >. 316 to LBNL <B 317 CLASS="COMMAND" 318 >traceroute</B 319 > separately.<A 320 NAME="AEN86" 321 HREF="#FTN.AEN86" 322 ><SPAN 323 CLASS="footnote" 324 >[1]</SPAN 325 ></A 326 ></P 327 ></DIV 328 ><DIV 329 CLASS="SECT1" 330 ><HR><H2 331 CLASS="SECT1" 332 ><A 333 NAME="AEN89" 334 >3. Installation notes</A 335 ></H2 336 ><P 337 ><KBD 338 CLASS="USERINPUT" 339 >make</KBD 340 > to compile utilities. <KBD 341 CLASS="USERINPUT" 342 >make html</KBD 343 > to prepare 344 html documentation, <KBD 345 CLASS="USERINPUT" 346 >make man</KBD 347 > if you prefer man pages. 348 Nothing fancy, provided you have DocBook package installed.</P 349 ><P 350 ><KBD 351 CLASS="USERINPUT" 352 >make install</KBD 353 > installs <SPAN 354 CLASS="emphasis" 355 ><I 356 CLASS="EMPHASIS" 357 >only</I 358 ></SPAN 359 > HTML documentation 360 to <TT 361 CLASS="FILENAME" 362 >/usr/doc/iputils</TT 363 >. It even does not try 364 to install binaries and man pages. If you read historical 365 notes above, the reason should be evident. Most of utilities 366 intersect with utilities distributed in another packages, and 367 making such target rewriting existing installation would be a crime 368 from my side. The decision what variant of <B 369 CLASS="COMMAND" 370 >ping</B 371 > is preferred, 372 how to resolve the conflicts etc. is left to you or to person who 373 assembled an rpm. I vote for variant from <B 374 CLASS="COMMAND" 375 >iputils</B 376 > of course.</P 377 ><P 378 >Anyway, select utilities which you like and install them to the places 379 which you prefer together with their man pages.</P 380 ><P 381 >It is possible that compilation will fail, if you use some 382 funny Linux distribution mangling header files in some unexpected ways 383 (expected ones are the ways of redhat of course :-)). 384 I validate iputils against <A 385 HREF="http://www.asplinux.ru" 386 TARGET="_top" 387 >asplinux</A 388 > 389 distribution, which is inevitably followed by validity with respect 390 to <A 391 HREF="http://www.redhat.com" 392 TARGET="_top" 393 >redhat</A 394 >. 395 If your distribution is one of widely known ones, suse or debian, 396 it also will compile provided snapshot is elder than month or so and 397 someone reported all the problems, if they took place at all.</P 398 ><P 399 ><SPAN 400 CLASS="emphasis" 401 ><I 402 CLASS="EMPHASIS" 403 >Anyway, please, do not abuse me complaining about some compilation problems 404 in any distribution different of asplinux or redhat. 405 If you have a fix, please, send it to 406 <A 407 HREF="mailto:kuznet@ms2.inr.ac.ru" 408 TARGET="_top" 409 >me</A 410 >, 411 I will check that it does not break distributions mentioned above 412 and apply it. But I am not going to undertake any investigations, 413 bare reports are deemed to be routed to <TT 414 CLASS="FILENAME" 415 >/dev/null</TT 416 >.</I 417 ></SPAN 418 ></P 419 ></DIV 420 ><DIV 421 CLASS="SECT1" 422 ><HR><H2 423 CLASS="SECT1" 424 ><A 425 NAME="AEN109" 426 >4. Availability</A 427 ></H2 428 ><P 429 >The collection of documents is part of <TT 430 CLASS="FILENAME" 431 >iputils</TT 432 > package 433 and the latest versions are available in source form at 434 <A 435 HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2" 436 TARGET="_top" 437 >http://www.skbuff.net/iputils/iputils-current.tar.bz2</A 438 >.</P 439 ></DIV 440 ><DIV 441 CLASS="SECT1" 442 ><HR><H2 443 CLASS="SECT1" 444 ><A 445 NAME="AEN114" 446 >5. Copying</A 447 ></H2 448 ><P 449 >Different files are copyrighted by different persons and organizations 450 and distributed under different licenses. For details look into corresponding 451 source files.</P 452 ></DIV 453 ></DIV 454 ><H3 455 CLASS="FOOTNOTES" 456 >Notes</H3 457 ><TABLE 458 BORDER="0" 459 CLASS="FOOTNOTES" 460 WIDTH="100%" 461 ><TR 462 ><TD 463 ALIGN="LEFT" 464 VALIGN="TOP" 465 WIDTH="5%" 466 ><A 467 NAME="FTN.AEN86" 468 HREF="#AEN86" 469 ><SPAN 470 CLASS="footnote" 471 >[1]</SPAN 472 ></A 473 ></TD 474 ><TD 475 ALIGN="LEFT" 476 VALIGN="TOP" 477 WIDTH="95%" 478 ><P 479 >This was mistake. 480 Due to this <B 481 CLASS="COMMAND" 482 >traceroute</B 483 > was in a sad state until recently. 484 Good news, redhat-7.2 seems to add these patches to their traceroute 485 rpm eventually. So, I think I will refrain of suicide for awhile.</P 486 ></TD 487 ></TR 488 ></TABLE 489 ></BODY 490 ></HTML 491 > 492 No newline at end of file -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/ninfod.8 iputils-s20121221/doc/ninfod.8
old new 1 .\" This manpage has been automatically generated by docbook2man 2 .\" from a DocBook document. This tool can be found at: 3 .\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 4 .\" Please send any bug reports, improvements, comments, patches, 5 .\" etc. to Steve Cheng <steve@ggi-project.org>. 6 .TH "NINFOD" "8" "04 January 2013" "iputils-121221" "System Manager's Manual: iputils" 7 .SH NAME 8 ninfod \- Respond to IPv6 Node Information Queries 9 .SH SYNOPSIS 10 11 \fBninfod\fR [\fB-dhv\fR] [\fB-p \fIpidfile\fB\fR] [\fB-u \fIuser\fB\fR] 12 13 .SH "DESCRIPTION" 14 .PP 15 Responds to IPv6 Node Information Queries (RFC4620) from clients. 16 Queries can be sent by various implementations of \fBping6\fR command. 17 .SH "OPTIONS" 18 .TP 19 \fB-a\fR 20 Debug mode. Do not go background. 21 .TP 22 \fB-h\fR 23 Show help. 24 .TP 25 \fB-v\fR 26 Verbose mode. 27 .TP 28 \fB-u \fIuser\fB\fR 29 Run as another user. 30 \fIuser\fR can either be username or user ID. 31 .TP 32 \fB-p \fIpidfile\fB\fR 33 File for process-id storage. 34 \fIuser\fR is required to be able to create the file. 35 .SH "SEE ALSO" 36 .PP 37 \fBping\fR(8). 38 .SH "AUTHOR" 39 .PP 40 \fBninfod\fR was written by USAGI/WIDE Project. 41 .SH "COPYING" 42 .PP 43 44 .nf 45 Copyright (C) 2012 YOSHIFUJI Hideaki. 46 Copyright (C) 2002 USAGI/WIDE Project. 47 All rights reserved. 48 49 Redistribution and use in source and binary forms, with or without 50 modification, are permitted provided that the following conditions 51 are met: 52 1. Redistributions of source code must retain the above copyright 53 notice, this list of conditions and the following disclaimer. 54 2. Redistributions in binary form must reproduce the above copyright 55 notice, this list of conditions and the following disclaimer in the 56 documentation and/or other materials provided with the distribution. 57 3. Neither the name of the project nor the names of its contributors 58 may be used to endorse or promote products derived from this software 59 without specific prior written permission. 60 61 THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND 62 ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 63 IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 64 ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE 65 FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 66 DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 67 OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 68 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 69 LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 70 OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 71 SUCH DAMAGE. 72 .fi -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/pg3.8 iputils-s20121221/doc/pg3.8
old new 1 .\" This manpage has been automatically generated by docbook2man 2 .\" from a DocBook document. This tool can be found at: 3 .\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 4 .\" Please send any bug reports, improvements, comments, patches, 5 .\" etc. to Steve Cheng <steve@ggi-project.org>. 6 .TH "PG3" "8" "04 January 2013" "iputils-121221" "System Manager's Manual: iputils" 7 .SH NAME 8 pg3, ipg, pgset \- send stream of UDP packets 9 .SH SYNOPSIS 10 11 \fBsource ipg\fR 12 13 14 \fBpg\fR 15 16 17 \fBpgset\fR \fB\fICOMMAND\fB\fR 18 19 .SH "DESCRIPTION" 20 .PP 21 \fBipg\fR is not a program, it is script which should be sourced 22 to \fBbash\fR. When sourced it loads module \fIpg3\fR and 23 exports a few of functions accessible from parent shell. These macros 24 are \fBpg\fR to start packet injection and to get the results of run; 25 and \fBpgset\fR to setup packet generator. 26 .PP 27 \fBpgset\fR can send the following commands to module \fIpg3\fR: 28 .SH "COMMAND" 29 .TP 30 \fBodev \fIDEVICE\fB\fR 31 Name of Ethernet device to test. See 32 warning below. 33 .TP 34 \fBpkt_size \fIBYTES\fB\fR 35 Size of packet to generate. The size includes all the headers: UDP, IP, 36 MAC, but does not account for overhead internal to medium, i.e. FCS 37 and various paddings. 38 .TP 39 \fBfrags \fINUMBER\fB\fR 40 Each packet will contain \fINUMBER\fR of fragments. 41 Maximal amount for linux-2.4 is 6. Far not all the devices support 42 fragmented buffers. 43 .TP 44 \fBcount \fINUMBER\fB\fR 45 Send stream of \fINUMBER\fR of packets and stop after this. 46 .TP 47 \fBipg \fITIME\fB\fR 48 Introduce artificial delay between packets of \fITIME\fR 49 microseconds. 50 .TP 51 \fBdst \fIIP_ADDRESS\fB\fR 52 Select IP destination where the stream is sent to. 53 Beware, never set this address at random. \fBpg3\fR is not a toy, 54 it creates really tough stream. Default value is 0.0.0.0. 55 .TP 56 \fBdst \fIMAC_ADDRESS\fB\fR 57 Select MAC destination where the stream is sent to. 58 Default value is 00:00:00:00:00:00 in hope that this will not be received 59 by any node on LAN. 60 .TP 61 \fBstop\fR 62 Abort packet injection. 63 .SH "WARNING" 64 .PP 65 When output device is set to some random device different 66 of hardware Ethernet device, \fBpg3\fR will crash kernel. 67 .PP 68 Do not use it on VLAN, ethertap, VTUN and other devices, 69 which emulate Ethernet not being real Ethernet in fact. 70 .SH "AUTHOR" 71 .PP 72 \fBpg3\fR was written by Robert Olsson <robert.olsson@its.uu.se>. 73 .SH "SECURITY" 74 .PP 75 This can be used only by superuser. 76 .PP 77 This tool creates floods of packets which is unlikely to be handled 78 even by high-end machines. For example, it saturates gigabit link with 79 60 byte packets when used with Intel's e1000. In face of such stream 80 switches, routers and end hosts may deadlock, crash, explode. 81 Use only in test lab environment. 82 .SH "AVAILABILITY" 83 .PP 84 \fBpg3\fR is part of \fIiputils\fR package 85 and the latest versions are available in source form at 86 http://www.skbuff.net/iputils/iputils-current.tar.bz2. -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/ping.8 iputils-s20121221/doc/ping.8
old new 1 .\" This manpage has been automatically generated by docbook2man 2 .\" from a DocBook document. This tool can be found at: 3 .\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 4 .\" Please send any bug reports, improvements, comments, patches, 5 .\" etc. to Steve Cheng <steve@ggi-project.org>. 6 .TH "PING" "8" "04 January 2013" "iputils-121221" "System Manager's Manual: iputils" 7 .SH NAME 8 ping, ping6 \- send ICMP ECHO_REQUEST to network hosts 9 .SH SYNOPSIS 10 11 \fBping\fR [\fB-aAbBdDfhLnOqrRUvV\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 12 13 .SH "DESCRIPTION" 14 .PP 15 \fBping\fR uses the ICMP protocol's mandatory ECHO_REQUEST 16 datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway. 17 ECHO_REQUEST datagrams (``pings'') have an IP and ICMP 18 header, followed by a struct timeval and then an arbitrary 19 number of ``pad'' bytes used to fill out the packet. 20 .PP 21 \fBping6\fR is IPv6 version of \fBping\fR, and can also send Node Information Queries (RFC4620). 22 Intermediate \fIhop\fRs may not be allowed, because IPv6 source routing was deprecated (RFC5095). 23 .SH "OPTIONS" 24 .TP 25 \fB-a\fR 26 Audible ping. 27 .TP 28 \fB-A\fR 29 Adaptive ping. Interpacket interval adapts to round-trip time, so that 30 effectively not more than one (or more, if preload is set) unanswered probe 31 is present in the network. Minimal interval is 200msec for not super-user. 32 On networks with low rtt this mode is essentially equivalent to flood mode. 33 .TP 34 \fB-b\fR 35 Allow pinging a broadcast address. 36 .TP 37 \fB-B\fR 38 Do not allow \fBping\fR to change source address of probes. 39 The address is bound to one selected when \fBping\fR starts. 40 .TP 41 \fB-c \fIcount\fB\fR 42 Stop after sending \fIcount\fR ECHO_REQUEST 43 packets. With 44 \fIdeadline\fR 45 option, \fBping\fR waits for 46 \fIcount\fR ECHO_REPLY packets, until the timeout expires. 47 .TP 48 \fB-d\fR 49 Set the SO_DEBUG option on the socket being used. 50 Essentially, this socket option is not used by Linux kernel. 51 .TP 52 \fB-D\fR 53 Print timestamp (unix time + microseconds as in gettimeofday) before 54 each line. 55 .TP 56 \fB-f\fR 57 Flood ping. For every ECHO_REQUEST sent a period ``.'' is printed, 58 while for ever ECHO_REPLY received a backspace is printed. 59 This provides a rapid display of how many packets are being dropped. 60 If interval is not given, it sets interval to zero and 61 outputs packets as fast as they come back or one hundred times per second, 62 whichever is more. 63 Only the super-user may use this option with zero interval. 64 .TP 65 \fB-F \fIflow label\fB\fR 66 \fBping6\fR only. 67 Allocate and set 20 bit flow label (in hex) on echo request packets. 68 If value is zero, kernel allocates random flow label. 69 .TP 70 \fB-h\fR 71 Show help. 72 .TP 73 \fB-i \fIinterval\fB\fR 74 Wait \fIinterval\fR seconds between sending each packet. 75 The default is to wait for one second between each packet normally, 76 or not to wait in flood mode. Only super-user may set interval 77 to values less 0.2 seconds. 78 .TP 79 \fB-I \fIinterface\fB\fR 80 \fIinterface\fR is either an address, or an interface name. 81 If \fIinterface\fR is an address, it sets source address 82 to specified interface address. 83 If \fIinterface\fR in an interface name, it sets 84 source interface to specified interface. 85 For \fBping6\fR, when doing ping to a link-local scope 86 address, link specification (by the '%'-notation in 87 \fIdestination\fR, or by this option) is required. 88 .TP 89 \fB-l \fIpreload\fB\fR 90 If \fIpreload\fR is specified, 91 \fBping\fR sends that many packets not waiting for reply. 92 Only the super-user may select preload more than 3. 93 .TP 94 \fB-L\fR 95 Suppress loopback of multicast packets. This flag only applies if the ping 96 destination is a multicast address. 97 .TP 98 \fB-m \fImark\fB\fR 99 use \fImark\fR to tag the packets going out. This is useful 100 for variety of reasons within the kernel such as using policy 101 routing to select specific outbound processing. 102 .TP 103 \fB-M \fIpmtudisc_opt\fB\fR 104 Select Path MTU Discovery strategy. 105 \fIpmtudisc_option\fR may be either \fIdo\fR 106 (prohibit fragmentation, even local one), 107 \fIwant\fR (do PMTU discovery, fragment locally when packet size 108 is large), or \fIdont\fR (do not set DF flag). 109 .TP 110 \fB-N \fInodeinfo_option\fB\fR 111 \fBping6\fR only. 112 Send ICMPv6 Node Information Queries (RFC4620), instead of Echo Request. 113 .RS 114 .TP 115 \fBhelp\fR 116 Show help for NI support. 117 .RE 118 .RS 119 .TP 120 \fBname\fR 121 Queries for Node Names. 122 .RE 123 .RS 124 .TP 125 \fBipv6\fR 126 Queries for IPv6 Addresses. There are several IPv6 specific flags. 127 .RS 128 .TP 129 \fBipv6-global\fR 130 Request IPv6 global-scope addresses. 131 .RE 132 .RS 133 .TP 134 \fBipv6-sitelocal\fR 135 Request IPv6 site-local addresses. 136 .RE 137 .RS 138 .TP 139 \fBipv6-linklocal\fR 140 Request IPv6 link-local addresses. 141 .RE 142 .RS 143 .TP 144 \fBipv6-all\fR 145 Request IPv6 addresses on other interfaces. 146 .RE 147 .RE 148 .RS 149 .TP 150 \fBipv4\fR 151 Queries for IPv4 Addresses. There is one IPv4 specific flag. 152 .RS 153 .TP 154 \fBipv4-all\fR 155 Request IPv4 addresses on other interfaces. 156 .RE 157 .RE 158 .RS 159 .TP 160 \fBsubject-ipv6=\fIipv6addr\fB\fR 161 IPv6 subject address. 162 .RE 163 .RS 164 .TP 165 \fBsubject-ipv4=\fIipv4addr\fB\fR 166 IPv4 subject address. 167 .RE 168 .RS 169 .TP 170 \fBsubject-name=\fInodename\fB\fR 171 Subject name. If it contains more than one dot, 172 fully-qualified domain name is assumed. 173 .RE 174 .RS 175 .TP 176 \fBsubject-fqdn=\fInodename\fB\fR 177 Subject name. Fully-qualified domain name is 178 always assumed. 179 .RE 180 .TP 181 \fB-n\fR 182 Numeric output only. 183 No attempt will be made to lookup symbolic names for host addresses. 184 .TP 185 \fB-O\fR 186 Report outstanding ICMP ECHO reply before sending next packet. 187 This is useful together with the timestamp \fB-D\fR to 188 log output to a diagnostic file and search for missing answers. 189 .TP 190 \fB-p \fIpattern\fB\fR 191 You may specify up to 16 ``pad'' bytes to fill out the packet you send. 192 This is useful for diagnosing data-dependent problems in a network. 193 For example, \fB-p ff\fR will cause the sent packet 194 to be filled with all ones. 195 .TP 196 \fB-q\fR 197 Quiet output. 198 Nothing is displayed except the summary lines at startup time and 199 when finished. 200 .TP 201 \fB-Q \fItos\fB\fR 202 Set Quality of Service -related bits in ICMP datagrams. 203 \fItos\fR can be decimal (\fBping\fR only) or hex number. 204 205 In RFC2474, these fields are interpreted as 8-bit Differentiated 206 Services (DS), consisting of: bits 0-1 (2 lowest bits) of separate 207 data, and bits 2-7 (highest 6 bits) of Differentiated Services 208 Codepoint (DSCP). In RFC2481 and RFC3168, bits 0-1 are used for ECN. 209 210 Historically (RFC1349, obsoleted by RFC2474), these were interpreted 211 as: bit 0 (lowest bit) for reserved (currently being redefined as 212 congestion control), 1-4 for Type of Service and bits 5-7 213 (highest bits) for Precedence. 214 .TP 215 \fB-r\fR 216 Bypass the normal routing tables and send directly to a host on an attached 217 interface. 218 If the host is not on a directly-attached network, an error is returned. 219 This option can be used to ping a local host through an interface 220 that has no route through it provided the option \fB-I\fR is also 221 used. 222 .TP 223 \fB-R\fR 224 \fBping\fR only. 225 Record route. 226 Includes the RECORD_ROUTE option in the ECHO_REQUEST 227 packet and displays the route buffer on returned packets. 228 Note that the IP header is only large enough for nine such routes. 229 Many hosts ignore or discard this option. 230 .TP 231 \fB-s \fIpacketsize\fB\fR 232 Specifies the number of data bytes to be sent. 233 The default is 56, which translates into 64 ICMP 234 data bytes when combined with the 8 bytes of ICMP header data. 235 .TP 236 \fB-S \fIsndbuf\fB\fR 237 Set socket sndbuf. If not specified, it is selected to buffer 238 not more than one packet. 239 .TP 240 \fB-t \fIttl\fB\fR 241 \fBping\fR only. 242 Set the IP Time to Live. 243 .TP 244 \fB-T \fItimestamp option\fB\fR 245 Set special IP timestamp options. 246 \fItimestamp option\fR may be either 247 \fItsonly\fR (only timestamps), 248 \fItsandaddr\fR (timestamps and addresses) or 249 \fItsprespec host1 [host2 [host3 [host4]]]\fR 250 (timestamp prespecified hops). 251 .TP 252 \fB-U\fR 253 Print full user-to-user latency (the old behaviour). Normally 254 \fBping\fR 255 prints network round trip time, which can be different 256 f.e. due to DNS failures. 257 .TP 258 \fB-v\fR 259 Verbose output. 260 .TP 261 \fB-V\fR 262 Show version and exit. 263 .TP 264 \fB-w \fIdeadline\fB\fR 265 Specify a timeout, in seconds, before 266 \fBping\fR 267 exits regardless of how many 268 packets have been sent or received. In this case 269 \fBping\fR 270 does not stop after 271 \fIcount\fR 272 packet are sent, it waits either for 273 \fIdeadline\fR 274 expire or until 275 \fIcount\fR 276 probes are answered or for some error notification from network. 277 .TP 278 \fB-W \fItimeout\fB\fR 279 Time to wait for a response, in seconds. The option affects only timeout 280 in absence of any responses, otherwise \fBping\fR waits for two RTTs. 281 .PP 282 When using \fBping\fR for fault isolation, it should first be run 283 on the local host, to verify that the local network interface is up 284 and running. Then, hosts and gateways further and further away should be 285 ``pinged''. Round-trip times and packet loss statistics are computed. 286 If duplicate packets are received, they are not included in the packet 287 loss calculation, although the round trip time of these packets is used 288 in calculating the minimum/average/maximum round-trip time numbers. 289 When the specified number of packets have been sent (and received) or 290 if the program is terminated with a 291 SIGINT, a brief summary is displayed. Shorter current statistics 292 can be obtained without termination of process with signal 293 SIGQUIT. 294 .PP 295 If \fBping\fR does not receive any reply packets at all it will 296 exit with code 1. If a packet 297 \fIcount\fR 298 and 299 \fIdeadline\fR 300 are both specified, and fewer than 301 \fIcount\fR 302 packets are received by the time the 303 \fIdeadline\fR 304 has arrived, it will also exit with code 1. 305 On other error it exits with code 2. Otherwise it exits with code 0. This 306 makes it possible to use the exit code to see if a host is alive or 307 not. 308 .PP 309 This program is intended for use in network testing, measurement and 310 management. 311 Because of the load it can impose on the network, it is unwise to use 312 \fBping\fR during normal operations or from automated scripts. 313 .SH "ICMP PACKET DETAILS" 314 .PP 315 An IP header without options is 20 bytes. 316 An ICMP ECHO_REQUEST packet contains an additional 8 bytes worth 317 of ICMP header followed by an arbitrary amount of data. 318 When a \fIpacketsize\fR is given, this indicated the size of this 319 extra piece of data (the default is 56). Thus the amount of data received 320 inside of an IP packet of type ICMP ECHO_REPLY will always be 8 bytes 321 more than the requested data space (the ICMP header). 322 .PP 323 If the data space is at least of size of struct timeval 324 \fBping\fR uses the beginning bytes of this space to include 325 a timestamp which it uses in the computation of round trip times. 326 If the data space is shorter, no round trip times are given. 327 .SH "DUPLICATE AND DAMAGED PACKETS" 328 .PP 329 \fBping\fR will report duplicate and damaged packets. 330 Duplicate packets should never occur, and seem to be caused by 331 inappropriate link-level retransmissions. 332 Duplicates may occur in many situations and are rarely (if ever) a 333 good sign, although the presence of low levels of duplicates may not 334 always be cause for alarm. 335 .PP 336 Damaged packets are obviously serious cause for alarm and often 337 indicate broken hardware somewhere in the 338 \fBping\fR packet's path (in the network or in the hosts). 339 .SH "TRYING DIFFERENT DATA PATTERNS" 340 .PP 341 The (inter)network layer should never treat packets differently depending 342 on the data contained in the data portion. 343 Unfortunately, data-dependent problems have been known to sneak into 344 networks and remain undetected for long periods of time. 345 In many cases the particular pattern that will have problems is something 346 that doesn't have sufficient ``transitions'', such as all ones or all 347 zeros, or a pattern right at the edge, such as almost all zeros. 348 It isn't necessarily enough to specify a data pattern of all zeros (for 349 example) on the command line because the pattern that is of interest is 350 at the data link level, and the relationship between what you type and 351 what the controllers transmit can be complicated. 352 .PP 353 This means that if you have a data-dependent problem you will probably 354 have to do a lot of testing to find it. 355 If you are lucky, you may manage to find a file that either can't be sent 356 across your network or that takes much longer to transfer than other 357 similar length files. 358 You can then examine this file for repeated patterns that you can test 359 using the \fB-p\fR option of \fBping\fR. 360 .SH "TTL DETAILS" 361 .PP 362 The TTL value of an IP packet represents the maximum number of IP routers 363 that the packet can go through before being thrown away. 364 In current practice you can expect each router in the Internet to decrement 365 the TTL field by exactly one. 366 .PP 367 The TCP/IP specification states that the TTL field for TCP 368 packets should be set to 60, but many systems use smaller values 369 (4.3 BSD uses 30, 4.2 used 15). 370 .PP 371 The maximum possible value of this field is 255, and most Unix systems set 372 the TTL field of ICMP ECHO_REQUEST packets to 255. 373 This is why you will find you can ``ping'' some hosts, but not reach them 374 with 375 \fBtelnet\fR(1) 376 or 377 \fBftp\fR(1). 378 .PP 379 In normal operation ping prints the TTL value from the packet it receives. 380 When a remote system receives a ping packet, it can do one of three things 381 with the TTL field in its response: 382 .TP 0.2i 383 \(bu 384 Not change it; this is what Berkeley Unix systems did before the 385 4.3BSD Tahoe release. In this case the TTL value in the received packet 386 will be 255 minus the number of routers in the round-trip path. 387 .TP 0.2i 388 \(bu 389 Set it to 255; this is what current Berkeley Unix systems do. 390 In this case the TTL value in the received packet will be 255 minus the 391 number of routers in the path \fBfrom\fR 392 the remote system \fBto\fR the \fBping\fRing host. 393 .TP 0.2i 394 \(bu 395 Set it to some other value. Some machines use the same value for 396 ICMP packets that they use for TCP packets, for example either 30 or 60. 397 Others may use completely wild values. 398 .SH "BUGS" 399 .TP 0.2i 400 \(bu 401 Many Hosts and Gateways ignore the RECORD_ROUTE option. 402 .TP 0.2i 403 \(bu 404 The maximum IP header length is too small for options like 405 RECORD_ROUTE to be completely useful. 406 There's not much that that can be done about this, however. 407 .TP 0.2i 408 \(bu 409 Flood pinging is not recommended in general, and flood pinging the 410 broadcast address should only be done under very controlled conditions. 411 .SH "SEE ALSO" 412 .PP 413 \fBnetstat\fR(1), 414 \fBifconfig\fR(8). 415 .SH "HISTORY" 416 .PP 417 The \fBping\fR command appeared in 4.3BSD. 418 .PP 419 The version described here is its descendant specific to Linux. 420 .SH "SECURITY" 421 .PP 422 \fBping\fR requires CAP_NET_RAW capability 423 to be executed. It may be used as set-uid root. 424 .SH "AVAILABILITY" 425 .PP 426 \fBping\fR is part of \fIiputils\fR package 427 and the latest versions are available in source form at 428 http://www.skbuff.net/iputils/iputils-current.tar.bz2. -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/r1056.html iputils-s20121221/doc/r1056.html
old new 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 2 <HTML 3 ><HEAD 4 ><TITLE 5 >ninfod</TITLE 6 ><META 7 NAME="GENERATOR" 8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK 9 REL="HOME" 10 TITLE="System Manager's Manual: iputils" 11 HREF="index.html"><LINK 12 REL="PREVIOUS" 13 TITLE="tftpd" 14 HREF="r983.html"><LINK 15 REL="NEXT" 16 TITLE="rdisc" 17 HREF="r1125.html"></HEAD 18 ><BODY 19 CLASS="REFENTRY" 20 BGCOLOR="#FFFFFF" 21 TEXT="#000000" 22 LINK="#0000FF" 23 VLINK="#840084" 24 ALINK="#0000FF" 25 ><DIV 26 CLASS="NAVHEADER" 27 ><TABLE 28 SUMMARY="Header navigation table" 29 WIDTH="100%" 30 BORDER="0" 31 CELLPADDING="0" 32 CELLSPACING="0" 33 ><TR 34 ><TH 35 COLSPAN="3" 36 ALIGN="center" 37 >System Manager's Manual: iputils</TH 38 ></TR 39 ><TR 40 ><TD 41 WIDTH="10%" 42 ALIGN="left" 43 VALIGN="bottom" 44 ><A 45 HREF="r983.html" 46 ACCESSKEY="P" 47 >Prev</A 48 ></TD 49 ><TD 50 WIDTH="80%" 51 ALIGN="center" 52 VALIGN="bottom" 53 ></TD 54 ><TD 55 WIDTH="10%" 56 ALIGN="right" 57 VALIGN="bottom" 58 ><A 59 HREF="r1125.html" 60 ACCESSKEY="N" 61 >Next</A 62 ></TD 63 ></TR 64 ></TABLE 65 ><HR 66 ALIGN="LEFT" 67 WIDTH="100%"></DIV 68 ><H1 69 ><A 70 NAME="NINFOD" 71 ></A 72 >ninfod</H1 73 ><DIV 74 CLASS="REFNAMEDIV" 75 ><A 76 NAME="AEN1061" 77 ></A 78 ><H2 79 >Name</H2 80 >ninfod -- Respond to IPv6 Node Information Queries</DIV 81 ><DIV 82 CLASS="REFSYNOPSISDIV" 83 ><A 84 NAME="AEN1064" 85 ></A 86 ><H2 87 >Synopsis</H2 88 ><P 89 ><B 90 CLASS="COMMAND" 91 >ninfod</B 92 > [<CODE 93 CLASS="OPTION" 94 >-dhv</CODE 95 >] [-p <TT 96 CLASS="REPLACEABLE" 97 ><I 98 >pidfile</I 99 ></TT 100 >] [-u <TT 101 CLASS="REPLACEABLE" 102 ><I 103 >user</I 104 ></TT 105 >]</P 106 ></DIV 107 ><DIV 108 CLASS="REFSECT1" 109 ><A 110 NAME="AEN1073" 111 ></A 112 ><H2 113 >DESCRIPTION</H2 114 ><P 115 >Responds to <A 116 HREF="http://tools.ietf.org/rfc/rfc4620.txt" 117 TARGET="_top" 118 >IPv6 Node Information Queries (RFC4620)</A 119 > from clients. 120 Queries can be sent by various implementations of <B 121 CLASS="COMMAND" 122 >ping6</B 123 > command.</P 124 ></DIV 125 ><DIV 126 CLASS="REFSECT1" 127 ><A 128 NAME="AEN1078" 129 ></A 130 ><H2 131 >OPTIONS</H2 132 ><P 133 ></P 134 ><DIV 135 CLASS="VARIABLELIST" 136 ><DL 137 ><DT 138 ><CODE 139 CLASS="OPTION" 140 >-a</CODE 141 ></DT 142 ><DD 143 ><P 144 >Debug mode. Do not go background. 145 </P 146 ></DD 147 ><DT 148 ><CODE 149 CLASS="OPTION" 150 >-h</CODE 151 ></DT 152 ><DD 153 ><P 154 >Show help. 155 </P 156 ></DD 157 ><DT 158 ><CODE 159 CLASS="OPTION" 160 >-v</CODE 161 ></DT 162 ><DD 163 ><P 164 >Verbose mode. 165 </P 166 ></DD 167 ><DT 168 ><CODE 169 CLASS="OPTION" 170 >-u <TT 171 CLASS="REPLACEABLE" 172 ><I 173 >user</I 174 ></TT 175 ></CODE 176 ></DT 177 ><DD 178 ><P 179 >Run as another user. 180 <TT 181 CLASS="REPLACEABLE" 182 ><I 183 >user</I 184 ></TT 185 > can either be username or user ID. 186 </P 187 ></DD 188 ><DT 189 ><CODE 190 CLASS="OPTION" 191 >-p <TT 192 CLASS="REPLACEABLE" 193 ><I 194 >pidfile</I 195 ></TT 196 ></CODE 197 ></DT 198 ><DD 199 ><P 200 >File for process-id storage. 201 <TT 202 CLASS="REPLACEABLE" 203 ><I 204 >user</I 205 ></TT 206 > is required to be able to create the file. 207 </P 208 ></DD 209 ></DL 210 ></DIV 211 ></DIV 212 ><DIV 213 CLASS="REFSECT1" 214 ><A 215 NAME="AEN1110" 216 ></A 217 ><H2 218 >SEE ALSO</H2 219 ><P 220 ><A 221 HREF="r3.html" 222 ><SPAN 223 CLASS="CITEREFENTRY" 224 ><SPAN 225 CLASS="REFENTRYTITLE" 226 >ping</SPAN 227 >(8)</SPAN 228 ></A 229 >.</P 230 ></DIV 231 ><DIV 232 CLASS="REFSECT1" 233 ><A 234 NAME="AEN1117" 235 ></A 236 ><H2 237 >AUTHOR</H2 238 ><P 239 ><B 240 CLASS="COMMAND" 241 >ninfod</B 242 > was written by USAGI/WIDE Project.</P 243 ></DIV 244 ><DIV 245 CLASS="REFSECT1" 246 ><A 247 NAME="AEN1121" 248 ></A 249 ><H2 250 >COPYING</H2 251 ><P 252 ><P 253 CLASS="LITERALLAYOUT" 254 >Copyright (C) 2012 YOSHIFUJI Hideaki.<br> 255 Copyright (C) 2002 USAGI/WIDE Project.<br> 256 All rights reserved.<br> 257 <br> 258 Redistribution and use in source and binary forms, with or without<br> 259 modification, are permitted provided that the following conditions<br> 260 are met:<br> 261 1. Redistributions of source code must retain the above copyright<br> 262 notice, this list of conditions and the following disclaimer.<br> 263 2. Redistributions in binary form must reproduce the above copyright<br> 264 notice, this list of conditions and the following disclaimer in the<br> 265 documentation and/or other materials provided with the distribution.<br> 266 3. Neither the name of the project nor the names of its contributors<br> 267 may be used to endorse or promote products derived from this software<br> 268 without specific prior written permission.<br> 269 <br> 270 THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND<br> 271 ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE<br> 272 IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE<br> 273 ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE<br> 274 FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL<br> 275 DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS<br> 276 OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)<br> 277 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT<br> 278 LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY<br> 279 OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF<br> 280 SUCH DAMAGE.</P 281 ></P 282 ></DIV 283 ><DIV 284 CLASS="NAVFOOTER" 285 ><HR 286 ALIGN="LEFT" 287 WIDTH="100%"><TABLE 288 SUMMARY="Footer navigation table" 289 WIDTH="100%" 290 BORDER="0" 291 CELLPADDING="0" 292 CELLSPACING="0" 293 ><TR 294 ><TD 295 WIDTH="33%" 296 ALIGN="left" 297 VALIGN="top" 298 ><A 299 HREF="r983.html" 300 ACCESSKEY="P" 301 >Prev</A 302 ></TD 303 ><TD 304 WIDTH="34%" 305 ALIGN="center" 306 VALIGN="top" 307 ><A 308 HREF="index.html" 309 ACCESSKEY="H" 310 >Home</A 311 ></TD 312 ><TD 313 WIDTH="33%" 314 ALIGN="right" 315 VALIGN="top" 316 ><A 317 HREF="r1125.html" 318 ACCESSKEY="N" 319 >Next</A 320 ></TD 321 ></TR 322 ><TR 323 ><TD 324 WIDTH="33%" 325 ALIGN="left" 326 VALIGN="top" 327 >tftpd</TD 328 ><TD 329 WIDTH="34%" 330 ALIGN="center" 331 VALIGN="top" 332 > </TD 333 ><TD 334 WIDTH="33%" 335 ALIGN="right" 336 VALIGN="top" 337 >rdisc</TD 338 ></TR 339 ></TABLE 340 ></DIV 341 ></BODY 342 ></HTML 343 > 344 No newline at end of file -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/r1125.html iputils-s20121221/doc/r1125.html
old new 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 2 <HTML 3 ><HEAD 4 ><TITLE 5 >rdisc</TITLE 6 ><META 7 NAME="GENERATOR" 8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK 9 REL="HOME" 10 TITLE="System Manager's Manual: iputils" 11 HREF="index.html"><LINK 12 REL="PREVIOUS" 13 TITLE="ninfod" 14 HREF="r1056.html"><LINK 15 REL="NEXT" 16 TITLE="pg3" 17 HREF="r1269.html"></HEAD 18 ><BODY 19 CLASS="REFENTRY" 20 BGCOLOR="#FFFFFF" 21 TEXT="#000000" 22 LINK="#0000FF" 23 VLINK="#840084" 24 ALINK="#0000FF" 25 ><DIV 26 CLASS="NAVHEADER" 27 ><TABLE 28 SUMMARY="Header navigation table" 29 WIDTH="100%" 30 BORDER="0" 31 CELLPADDING="0" 32 CELLSPACING="0" 33 ><TR 34 ><TH 35 COLSPAN="3" 36 ALIGN="center" 37 >System Manager's Manual: iputils</TH 38 ></TR 39 ><TR 40 ><TD 41 WIDTH="10%" 42 ALIGN="left" 43 VALIGN="bottom" 44 ><A 45 HREF="r1056.html" 46 ACCESSKEY="P" 47 >Prev</A 48 ></TD 49 ><TD 50 WIDTH="80%" 51 ALIGN="center" 52 VALIGN="bottom" 53 ></TD 54 ><TD 55 WIDTH="10%" 56 ALIGN="right" 57 VALIGN="bottom" 58 ><A 59 HREF="r1269.html" 60 ACCESSKEY="N" 61 >Next</A 62 ></TD 63 ></TR 64 ></TABLE 65 ><HR 66 ALIGN="LEFT" 67 WIDTH="100%"></DIV 68 ><H1 69 ><A 70 NAME="RDISC" 71 ></A 72 >rdisc</H1 73 ><DIV 74 CLASS="REFNAMEDIV" 75 ><A 76 NAME="AEN1130" 77 ></A 78 ><H2 79 >Name</H2 80 >rdisc -- network router discovery daemon</DIV 81 ><DIV 82 CLASS="REFSYNOPSISDIV" 83 ><A 84 NAME="AEN1133" 85 ></A 86 ><H2 87 >Synopsis</H2 88 ><P 89 ><B 90 CLASS="COMMAND" 91 >rdisc</B 92 > [<CODE 93 CLASS="OPTION" 94 >-abdfrstvV</CODE 95 >] [-p <TT 96 CLASS="REPLACEABLE" 97 ><I 98 >preference</I 99 ></TT 100 >] [-T <TT 101 CLASS="REPLACEABLE" 102 ><I 103 >max_interval</I 104 ></TT 105 >] [<TT 106 CLASS="REPLACEABLE" 107 ><I 108 >send_address</I 109 ></TT 110 >] [<TT 111 CLASS="REPLACEABLE" 112 ><I 113 >receive_address</I 114 ></TT 115 >]</P 116 ></DIV 117 ><DIV 118 CLASS="REFSECT1" 119 ><A 120 NAME="AEN1146" 121 ></A 122 ><H2 123 >DESCRIPTION</H2 124 ><P 125 ><B 126 CLASS="COMMAND" 127 >rdisc</B 128 > implements client side of the ICMP router discover protocol. 129 <B 130 CLASS="COMMAND" 131 >rdisc</B 132 > is invoked at boot time to populate the network 133 routing tables with default routes. </P 134 ><P 135 ><B 136 CLASS="COMMAND" 137 >rdisc</B 138 > listens on the ALL_HOSTS (224.0.0.1) multicast address 139 (or <TT 140 CLASS="REPLACEABLE" 141 ><I 142 >receive_address</I 143 ></TT 144 > provided it is given) 145 for ROUTER_ADVERTISE messages from routers. The received 146 messages are handled by first ignoring those listed router addresses 147 with which the host does not share a network. Among the remaining addresses 148 the ones with the highest preference are selected as default routers 149 and a default route is entered in the kernel routing table 150 for each one of them.</P 151 ><P 152 >Optionally, <B 153 CLASS="COMMAND" 154 >rdisc</B 155 > can avoid waiting for routers to announce 156 themselves by sending out a few ROUTER_SOLICITATION messages 157 to the ALL_ROUTERS (224.0.0.2) multicast address 158 (or <TT 159 CLASS="REPLACEABLE" 160 ><I 161 >send_address</I 162 ></TT 163 > provided it is given) 164 when it is started.</P 165 ><P 166 >A timer is associated with each router address and the address will 167 no longer be considered for inclusion in the the routing tables if the 168 timer expires before a new 169 <SPAN 170 CLASS="emphasis" 171 ><I 172 CLASS="EMPHASIS" 173 >advertise</I 174 ></SPAN 175 > message is received from the router. 176 The address will also be excluded from consideration if the host receives an 177 <SPAN 178 CLASS="emphasis" 179 ><I 180 CLASS="EMPHASIS" 181 >advertise</I 182 ></SPAN 183 > 184 message with the preference being maximally negative.</P 185 ><P 186 >Server side of router discovery protocol is supported by Cisco IOS 187 and by any more or less complete UNIX routing daemon, f.e <B 188 CLASS="COMMAND" 189 >gated</B 190 >. 191 Or, <B 192 CLASS="COMMAND" 193 >rdisc</B 194 > can act as responder, if compiled with -DRDISC_SERVER.</P 195 ></DIV 196 ><DIV 197 CLASS="REFSECT1" 198 ><A 199 NAME="AEN1163" 200 ></A 201 ><H2 202 >OPTIONS</H2 203 ><P 204 ></P 205 ><DIV 206 CLASS="VARIABLELIST" 207 ><DL 208 ><DT 209 ><CODE 210 CLASS="OPTION" 211 >-a</CODE 212 ></DT 213 ><DD 214 ><P 215 >Accept all routers independently of the preference they have in their 216 <SPAN 217 CLASS="emphasis" 218 ><I 219 CLASS="EMPHASIS" 220 >advertise</I 221 ></SPAN 222 > messages. 223 Normally <B 224 CLASS="COMMAND" 225 >rdisc</B 226 > only accepts (and enters in the kernel routing 227 tables) the router or routers with the highest preference. 228 </P 229 ></DD 230 ><DT 231 ><CODE 232 CLASS="OPTION" 233 >-b</CODE 234 ></DT 235 ><DD 236 ><P 237 >Opposite to <CODE 238 CLASS="OPTION" 239 >-a</CODE 240 >, i.e. install only router with the best 241 preference value. It is default behaviour. 242 </P 243 ></DD 244 ><DT 245 ><CODE 246 CLASS="OPTION" 247 >-d</CODE 248 ></DT 249 ><DD 250 ><P 251 >Send debugging messages to syslog. 252 </P 253 ></DD 254 ><DT 255 ><CODE 256 CLASS="OPTION" 257 >-f</CODE 258 ></DT 259 ><DD 260 ><P 261 >Run <B 262 CLASS="COMMAND" 263 >rdisc</B 264 > forever even if no routers are found. 265 Normally <B 266 CLASS="COMMAND" 267 >rdisc</B 268 > gives up if it has not received any 269 <SPAN 270 CLASS="emphasis" 271 ><I 272 CLASS="EMPHASIS" 273 >advertise</I 274 ></SPAN 275 > message after after soliciting three times, 276 in which case it exits with a non-zero exit code. 277 If <CODE 278 CLASS="OPTION" 279 >-f</CODE 280 > is not specified in the first form then 281 <CODE 282 CLASS="OPTION" 283 >-s</CODE 284 > must be specified. 285 </P 286 ></DD 287 ><DT 288 ><CODE 289 CLASS="OPTION" 290 >-r</CODE 291 ></DT 292 ><DD 293 ><P 294 >Responder mode, available only if compiled with -DRDISC_SERVER. 295 </P 296 ></DD 297 ><DT 298 ><CODE 299 CLASS="OPTION" 300 >-s</CODE 301 ></DT 302 ><DD 303 ><P 304 >Send three <SPAN 305 CLASS="emphasis" 306 ><I 307 CLASS="EMPHASIS" 308 >solicitation</I 309 ></SPAN 310 > messages initially to quickly discover 311 the routers when the system is booted. 312 When <CODE 313 CLASS="OPTION" 314 >-s</CODE 315 > is specified <B 316 CLASS="COMMAND" 317 >rdisc</B 318 > 319 exits with a non-zero exit code if it can not find any routers. 320 This can be overridden with the <CODE 321 CLASS="OPTION" 322 >-f</CODE 323 > option. 324 </P 325 ></DD 326 ><DT 327 ><CODE 328 CLASS="OPTION" 329 >-p <TT 330 CLASS="REPLACEABLE" 331 ><I 332 >preference</I 333 ></TT 334 ></CODE 335 ></DT 336 ><DD 337 ><P 338 >Set preference in advertisement. 339 Available only with -r option. 340 </P 341 ></DD 342 ><DT 343 ><CODE 344 CLASS="OPTION" 345 >-T <TT 346 CLASS="REPLACEABLE" 347 ><I 348 >max_interval</I 349 ></TT 350 ></CODE 351 ></DT 352 ><DD 353 ><P 354 >Set maximum advertisement interval in seconds. Default is 600 secs. 355 Available only with -r option. 356 </P 357 ></DD 358 ><DT 359 ><CODE 360 CLASS="OPTION" 361 >-t</CODE 362 ></DT 363 ><DD 364 ><P 365 >Test mode. Do not go to background. 366 </P 367 ></DD 368 ><DT 369 ><CODE 370 CLASS="OPTION" 371 >-v</CODE 372 ></DT 373 ><DD 374 ><P 375 >Be verbose i.e. send lots of debugging messages to syslog. 376 </P 377 ></DD 378 ><DT 379 ><CODE 380 CLASS="OPTION" 381 >-V</CODE 382 ></DT 383 ><DD 384 ><P 385 >Print version and exit. 386 </P 387 ></DD 388 ></DL 389 ></DIV 390 ></DIV 391 ><DIV 392 CLASS="REFSECT1" 393 ><A 394 NAME="AEN1235" 395 ></A 396 ><H2 397 >HISTORY</H2 398 ><P 399 >This program was developed by Sun Microsystems (see copyright 400 notice in source file). It was ported to Linux by 401 <A 402 HREF="mailto:kuznet@ms2.inr.ac.ru" 403 TARGET="_top" 404 >Alexey Kuznetsov 405 <kuznet@ms2.inr.ac.ru></A 406 >. 407 It is now maintained by 408 <A 409 HREF="mailto:yoshfuji@skbuff.net" 410 TARGET="_top" 411 >YOSHIFUJI Hideaki 412 <yoshfuji@skbuff.net></A 413 >.</P 414 ></DIV 415 ><DIV 416 CLASS="REFSECT1" 417 ><A 418 NAME="AEN1240" 419 ></A 420 ><H2 421 >SEE ALSO</H2 422 ><P 423 ><SPAN 424 CLASS="CITEREFENTRY" 425 ><SPAN 426 CLASS="REFENTRYTITLE" 427 >icmp</SPAN 428 >(7)</SPAN 429 >, 430 <SPAN 431 CLASS="CITEREFENTRY" 432 ><SPAN 433 CLASS="REFENTRYTITLE" 434 >inet</SPAN 435 >(7)</SPAN 436 >, 437 <A 438 HREF="r3.html" 439 ><SPAN 440 CLASS="CITEREFENTRY" 441 ><SPAN 442 CLASS="REFENTRYTITLE" 443 >ping</SPAN 444 >(8)</SPAN 445 ></A 446 >.</P 447 ></DIV 448 ><DIV 449 CLASS="REFSECT1" 450 ><A 451 NAME="AEN1253" 452 ></A 453 ><H2 454 >REFERENCES</H2 455 ><P 456 >Deering, S.E.,ed "ICMP Router Discovery Messages", 457 <A 458 HREF="http://tools.ietf.org/rfc/rfc1256.txt" 459 TARGET="_top" 460 >RFC1256</A 461 >, Network Information Center, SRI International, 462 Menlo Park, Calif., September 1991.</P 463 ></DIV 464 ><DIV 465 CLASS="REFSECT1" 466 ><A 467 NAME="AEN1257" 468 ></A 469 ><H2 470 >SECURITY</H2 471 ><P 472 ><B 473 CLASS="COMMAND" 474 >rdisc</B 475 > requires <CODE 476 CLASS="CONSTANT" 477 >CAP_NET_RAW</CODE 478 > to listen 479 and send ICMP messages and capability <CODE 480 CLASS="CONSTANT" 481 >CAP_NET_ADMIN</CODE 482 > 483 to update routing tables. </P 484 ></DIV 485 ><DIV 486 CLASS="REFSECT1" 487 ><A 488 NAME="AEN1263" 489 ></A 490 ><H2 491 >AVAILABILITY</H2 492 ><P 493 ><B 494 CLASS="COMMAND" 495 >rdisc</B 496 > is part of <TT 497 CLASS="FILENAME" 498 >iputils</TT 499 > package 500 and the latest versions are available in source form at 501 <A 502 HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2" 503 TARGET="_top" 504 >http://www.skbuff.net/iputils/iputils-current.tar.bz2</A 505 >.</P 506 ></DIV 507 ><DIV 508 CLASS="NAVFOOTER" 509 ><HR 510 ALIGN="LEFT" 511 WIDTH="100%"><TABLE 512 SUMMARY="Footer navigation table" 513 WIDTH="100%" 514 BORDER="0" 515 CELLPADDING="0" 516 CELLSPACING="0" 517 ><TR 518 ><TD 519 WIDTH="33%" 520 ALIGN="left" 521 VALIGN="top" 522 ><A 523 HREF="r1056.html" 524 ACCESSKEY="P" 525 >Prev</A 526 ></TD 527 ><TD 528 WIDTH="34%" 529 ALIGN="center" 530 VALIGN="top" 531 ><A 532 HREF="index.html" 533 ACCESSKEY="H" 534 >Home</A 535 ></TD 536 ><TD 537 WIDTH="33%" 538 ALIGN="right" 539 VALIGN="top" 540 ><A 541 HREF="r1269.html" 542 ACCESSKEY="N" 543 >Next</A 544 ></TD 545 ></TR 546 ><TR 547 ><TD 548 WIDTH="33%" 549 ALIGN="left" 550 VALIGN="top" 551 >ninfod</TD 552 ><TD 553 WIDTH="34%" 554 ALIGN="center" 555 VALIGN="top" 556 > </TD 557 ><TD 558 WIDTH="33%" 559 ALIGN="right" 560 VALIGN="top" 561 >pg3</TD 562 ></TR 563 ></TABLE 564 ></DIV 565 ></BODY 566 ></HTML 567 > 568 No newline at end of file -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/r1269.html iputils-s20121221/doc/r1269.html
old new 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 2 <HTML 3 ><HEAD 4 ><TITLE 5 >pg3</TITLE 6 ><META 7 NAME="GENERATOR" 8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK 9 REL="HOME" 10 TITLE="System Manager's Manual: iputils" 11 HREF="index.html"><LINK 12 REL="PREVIOUS" 13 TITLE="rdisc" 14 HREF="r1125.html"></HEAD 15 ><BODY 16 CLASS="REFENTRY" 17 BGCOLOR="#FFFFFF" 18 TEXT="#000000" 19 LINK="#0000FF" 20 VLINK="#840084" 21 ALINK="#0000FF" 22 ><DIV 23 CLASS="NAVHEADER" 24 ><TABLE 25 SUMMARY="Header navigation table" 26 WIDTH="100%" 27 BORDER="0" 28 CELLPADDING="0" 29 CELLSPACING="0" 30 ><TR 31 ><TH 32 COLSPAN="3" 33 ALIGN="center" 34 >System Manager's Manual: iputils</TH 35 ></TR 36 ><TR 37 ><TD 38 WIDTH="10%" 39 ALIGN="left" 40 VALIGN="bottom" 41 ><A 42 HREF="r1125.html" 43 ACCESSKEY="P" 44 >Prev</A 45 ></TD 46 ><TD 47 WIDTH="80%" 48 ALIGN="center" 49 VALIGN="bottom" 50 ></TD 51 ><TD 52 WIDTH="10%" 53 ALIGN="right" 54 VALIGN="bottom" 55 > </TD 56 ></TR 57 ></TABLE 58 ><HR 59 ALIGN="LEFT" 60 WIDTH="100%"></DIV 61 ><H1 62 ><A 63 NAME="PG3" 64 ></A 65 >pg3</H1 66 ><DIV 67 CLASS="REFNAMEDIV" 68 ><A 69 NAME="AEN1274" 70 ></A 71 ><H2 72 >Name</H2 73 >pg3, ipg, pgset -- send stream of UDP packets</DIV 74 ><DIV 75 CLASS="REFSYNOPSISDIV" 76 ><A 77 NAME="AEN1277" 78 ></A 79 ><H2 80 >Synopsis</H2 81 ><P 82 ><B 83 CLASS="COMMAND" 84 >source ipg</B 85 > </P 86 ><P 87 ><B 88 CLASS="COMMAND" 89 >pg</B 90 > </P 91 ><P 92 ><B 93 CLASS="COMMAND" 94 >pgset</B 95 > {<TT 96 CLASS="REPLACEABLE" 97 ><I 98 >COMMAND</I 99 ></TT 100 >}</P 101 ></DIV 102 ><DIV 103 CLASS="REFSECT1" 104 ><A 105 NAME="AEN1286" 106 ></A 107 ><H2 108 >DESCRIPTION</H2 109 ><P 110 ><B 111 CLASS="COMMAND" 112 >ipg</B 113 > is not a program, it is script which should be sourced 114 to <B 115 CLASS="COMMAND" 116 >bash</B 117 >. When sourced it loads module <TT 118 CLASS="FILENAME" 119 >pg3</TT 120 > and 121 exports a few of functions accessible from parent shell. These macros 122 are <B 123 CLASS="COMMAND" 124 >pg</B 125 > to start packet injection and to get the results of run; 126 and <B 127 CLASS="COMMAND" 128 >pgset</B 129 > to setup packet generator.</P 130 ><P 131 ><B 132 CLASS="COMMAND" 133 >pgset</B 134 > can send the following commands to module <TT 135 CLASS="FILENAME" 136 >pg3</TT 137 >:</P 138 ></DIV 139 ><DIV 140 CLASS="REFSECT1" 141 ><A 142 NAME="AEN1297" 143 ></A 144 ><H2 145 >COMMAND</H2 146 ><P 147 ></P 148 ><DIV 149 CLASS="VARIABLELIST" 150 ><DL 151 ><DT 152 ><CODE 153 CLASS="OPTION" 154 >odev <TT 155 CLASS="REPLACEABLE" 156 ><I 157 >DEVICE</I 158 ></TT 159 ></CODE 160 ></DT 161 ><DD 162 ><P 163 >Name of Ethernet device to test. See 164 <A 165 HREF="r1269.html#PG3.WARNING" 166 >warning</A 167 > below. 168 </P 169 ></DD 170 ><DT 171 ><CODE 172 CLASS="OPTION" 173 >pkt_size <TT 174 CLASS="REPLACEABLE" 175 ><I 176 >BYTES</I 177 ></TT 178 ></CODE 179 ></DT 180 ><DD 181 ><P 182 >Size of packet to generate. The size includes all the headers: UDP, IP, 183 MAC, but does not account for overhead internal to medium, i.e. FCS 184 and various paddings. 185 </P 186 ></DD 187 ><DT 188 ><CODE 189 CLASS="OPTION" 190 >frags <TT 191 CLASS="REPLACEABLE" 192 ><I 193 >NUMBER</I 194 ></TT 195 ></CODE 196 ></DT 197 ><DD 198 ><P 199 >Each packet will contain <TT 200 CLASS="REPLACEABLE" 201 ><I 202 >NUMBER</I 203 ></TT 204 > of fragments. 205 Maximal amount for linux-2.4 is 6. Far not all the devices support 206 fragmented buffers. 207 </P 208 ></DD 209 ><DT 210 ><CODE 211 CLASS="OPTION" 212 >count <TT 213 CLASS="REPLACEABLE" 214 ><I 215 >NUMBER</I 216 ></TT 217 ></CODE 218 ></DT 219 ><DD 220 ><P 221 >Send stream of <TT 222 CLASS="REPLACEABLE" 223 ><I 224 >NUMBER</I 225 ></TT 226 > of packets and stop after this. 227 </P 228 ></DD 229 ><DT 230 ><CODE 231 CLASS="OPTION" 232 >ipg <TT 233 CLASS="REPLACEABLE" 234 ><I 235 >TIME</I 236 ></TT 237 ></CODE 238 ></DT 239 ><DD 240 ><P 241 >Introduce artificial delay between packets of <TT 242 CLASS="REPLACEABLE" 243 ><I 244 >TIME</I 245 ></TT 246 > 247 microseconds. 248 </P 249 ></DD 250 ><DT 251 ><CODE 252 CLASS="OPTION" 253 >dst <TT 254 CLASS="REPLACEABLE" 255 ><I 256 >IP_ADDRESS</I 257 ></TT 258 ></CODE 259 ></DT 260 ><DD 261 ><P 262 >Select IP destination where the stream is sent to. 263 Beware, never set this address at random. <B 264 CLASS="COMMAND" 265 >pg3</B 266 > is not a toy, 267 it creates really tough stream. Default value is 0.0.0.0. 268 </P 269 ></DD 270 ><DT 271 ><CODE 272 CLASS="OPTION" 273 >dst <TT 274 CLASS="REPLACEABLE" 275 ><I 276 >MAC_ADDRESS</I 277 ></TT 278 ></CODE 279 ></DT 280 ><DD 281 ><P 282 >Select MAC destination where the stream is sent to. 283 Default value is 00:00:00:00:00:00 in hope that this will not be received 284 by any node on LAN. 285 </P 286 ></DD 287 ><DT 288 ><CODE 289 CLASS="OPTION" 290 >stop</CODE 291 ></DT 292 ><DD 293 ><P 294 >Abort packet injection. 295 </P 296 ></DD 297 ></DL 298 ></DIV 299 ></DIV 300 ><DIV 301 CLASS="REFSECT1" 302 ><A 303 NAME="PG3.WARNING" 304 ></A 305 ><H2 306 >WARNING</H2 307 ><P 308 >When output device is set to some random device different 309 of hardware Ethernet device, <B 310 CLASS="COMMAND" 311 >pg3</B 312 > will crash kernel.</P 313 ><P 314 >Do not use it on VLAN, ethertap, VTUN and other devices, 315 which emulate Ethernet not being real Ethernet in fact.</P 316 ></DIV 317 ><DIV 318 CLASS="REFSECT1" 319 ><A 320 NAME="AEN1357" 321 ></A 322 ><H2 323 >AUTHOR</H2 324 ><P 325 ><B 326 CLASS="COMMAND" 327 >pg3</B 328 > was written by <A 329 HREF="mailto:robert.olsson@its.uu.se" 330 TARGET="_top" 331 >Robert Olsson <robert.olsson@its.uu.se></A 332 >.</P 333 ></DIV 334 ><DIV 335 CLASS="REFSECT1" 336 ><A 337 NAME="AEN1362" 338 ></A 339 ><H2 340 >SECURITY</H2 341 ><P 342 >This can be used only by superuser.</P 343 ><P 344 >This tool creates floods of packets which is unlikely to be handled 345 even by high-end machines. For example, it saturates gigabit link with 346 60 byte packets when used with Intel's e1000. In face of such stream 347 switches, routers and end hosts may deadlock, crash, explode. 348 Use only in test lab environment.</P 349 ></DIV 350 ><DIV 351 CLASS="REFSECT1" 352 ><A 353 NAME="AEN1366" 354 ></A 355 ><H2 356 >AVAILABILITY</H2 357 ><P 358 ><B 359 CLASS="COMMAND" 360 >pg3</B 361 > is part of <TT 362 CLASS="FILENAME" 363 >iputils</TT 364 > package 365 and the latest versions are available in source form at 366 <A 367 HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2" 368 TARGET="_top" 369 >http://www.skbuff.net/iputils/iputils-current.tar.bz2</A 370 >.</P 371 ></DIV 372 ><DIV 373 CLASS="NAVFOOTER" 374 ><HR 375 ALIGN="LEFT" 376 WIDTH="100%"><TABLE 377 SUMMARY="Footer navigation table" 378 WIDTH="100%" 379 BORDER="0" 380 CELLPADDING="0" 381 CELLSPACING="0" 382 ><TR 383 ><TD 384 WIDTH="33%" 385 ALIGN="left" 386 VALIGN="top" 387 ><A 388 HREF="r1125.html" 389 ACCESSKEY="P" 390 >Prev</A 391 ></TD 392 ><TD 393 WIDTH="34%" 394 ALIGN="center" 395 VALIGN="top" 396 ><A 397 HREF="index.html" 398 ACCESSKEY="H" 399 >Home</A 400 ></TD 401 ><TD 402 WIDTH="33%" 403 ALIGN="right" 404 VALIGN="top" 405 > </TD 406 ></TR 407 ><TR 408 ><TD 409 WIDTH="33%" 410 ALIGN="left" 411 VALIGN="top" 412 >rdisc</TD 413 ><TD 414 WIDTH="34%" 415 ALIGN="center" 416 VALIGN="top" 417 > </TD 418 ><TD 419 WIDTH="33%" 420 ALIGN="right" 421 VALIGN="top" 422 > </TD 423 ></TR 424 ></TABLE 425 ></DIV 426 ></BODY 427 ></HTML 428 > 429 No newline at end of file -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/r3.html iputils-s20121221/doc/r3.html
old new 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 2 <HTML 3 ><HEAD 4 ><TITLE 5 >ping</TITLE 6 ><META 7 NAME="GENERATOR" 8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK 9 REL="HOME" 10 TITLE="System Manager's Manual: iputils" 11 HREF="index.html"><LINK 12 REL="PREVIOUS" 13 TITLE="System Manager's Manual: iputils" 14 HREF="index.html"><LINK 15 REL="NEXT" 16 TITLE="arping" 17 HREF="r466.html"></HEAD 18 ><BODY 19 CLASS="REFENTRY" 20 BGCOLOR="#FFFFFF" 21 TEXT="#000000" 22 LINK="#0000FF" 23 VLINK="#840084" 24 ALINK="#0000FF" 25 ><DIV 26 CLASS="NAVHEADER" 27 ><TABLE 28 SUMMARY="Header navigation table" 29 WIDTH="100%" 30 BORDER="0" 31 CELLPADDING="0" 32 CELLSPACING="0" 33 ><TR 34 ><TH 35 COLSPAN="3" 36 ALIGN="center" 37 >System Manager's Manual: iputils</TH 38 ></TR 39 ><TR 40 ><TD 41 WIDTH="10%" 42 ALIGN="left" 43 VALIGN="bottom" 44 ><A 45 HREF="index.html" 46 ACCESSKEY="P" 47 >Prev</A 48 ></TD 49 ><TD 50 WIDTH="80%" 51 ALIGN="center" 52 VALIGN="bottom" 53 ></TD 54 ><TD 55 WIDTH="10%" 56 ALIGN="right" 57 VALIGN="bottom" 58 ><A 59 HREF="r466.html" 60 ACCESSKEY="N" 61 >Next</A 62 ></TD 63 ></TR 64 ></TABLE 65 ><HR 66 ALIGN="LEFT" 67 WIDTH="100%"></DIV 68 ><H1 69 ><A 70 NAME="PING" 71 ></A 72 >ping</H1 73 ><DIV 74 CLASS="REFNAMEDIV" 75 ><A 76 NAME="AEN8" 77 ></A 78 ><H2 79 >Name</H2 80 >ping, ping6 -- send ICMP ECHO_REQUEST to network hosts</DIV 81 ><DIV 82 CLASS="REFSYNOPSISDIV" 83 ><A 84 NAME="AEN11" 85 ></A 86 ><H2 87 >Synopsis</H2 88 ><P 89 ><B 90 CLASS="COMMAND" 91 >ping</B 92 > [<CODE 93 CLASS="OPTION" 94 >-aAbBdDfhLnOqrRUvV</CODE 95 >] [-c <TT 96 CLASS="REPLACEABLE" 97 ><I 98 >count</I 99 ></TT 100 >] [-F <TT 101 CLASS="REPLACEABLE" 102 ><I 103 >flowlabel</I 104 ></TT 105 >] [-i <TT 106 CLASS="REPLACEABLE" 107 ><I 108 >interval</I 109 ></TT 110 >] [-I <TT 111 CLASS="REPLACEABLE" 112 ><I 113 >interface</I 114 ></TT 115 >] [-l <TT 116 CLASS="REPLACEABLE" 117 ><I 118 >preload</I 119 ></TT 120 >] [-m <TT 121 CLASS="REPLACEABLE" 122 ><I 123 >mark</I 124 ></TT 125 >] [-M <TT 126 CLASS="REPLACEABLE" 127 ><I 128 >pmtudisc_option</I 129 ></TT 130 >] [-N <TT 131 CLASS="REPLACEABLE" 132 ><I 133 >nodeinfo_option</I 134 ></TT 135 >] [-w <TT 136 CLASS="REPLACEABLE" 137 ><I 138 >deadline</I 139 ></TT 140 >] [-W <TT 141 CLASS="REPLACEABLE" 142 ><I 143 >timeout</I 144 ></TT 145 >] [-p <TT 146 CLASS="REPLACEABLE" 147 ><I 148 >pattern</I 149 ></TT 150 >] [-Q <TT 151 CLASS="REPLACEABLE" 152 ><I 153 >tos</I 154 ></TT 155 >] [-s <TT 156 CLASS="REPLACEABLE" 157 ><I 158 >packetsize</I 159 ></TT 160 >] [-S <TT 161 CLASS="REPLACEABLE" 162 ><I 163 >sndbuf</I 164 ></TT 165 >] [-t <TT 166 CLASS="REPLACEABLE" 167 ><I 168 >ttl</I 169 ></TT 170 >] [-T <TT 171 CLASS="REPLACEABLE" 172 ><I 173 >timestamp option</I 174 ></TT 175 >] [<TT 176 CLASS="REPLACEABLE" 177 ><I 178 >hop</I 179 ></TT 180 >...] {<TT 181 CLASS="REPLACEABLE" 182 ><I 183 >destination</I 184 ></TT 185 >}</P 186 ></DIV 187 ><DIV 188 CLASS="REFSECT1" 189 ><A 190 NAME="AEN52" 191 ></A 192 ><H2 193 >DESCRIPTION</H2 194 ><P 195 ><B 196 CLASS="COMMAND" 197 >ping</B 198 > uses the ICMP protocol's mandatory ECHO_REQUEST 199 datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway. 200 ECHO_REQUEST datagrams (``pings'') have an IP and ICMP 201 header, followed by a <CODE 202 CLASS="STRUCTNAME" 203 >struct timeval</CODE 204 > and then an arbitrary 205 number of ``pad'' bytes used to fill out the packet.</P 206 ><P 207 ><B 208 CLASS="COMMAND" 209 >ping6</B 210 > is IPv6 version of <B 211 CLASS="COMMAND" 212 >ping</B 213 >, and can also send Node Information Queries (RFC4620). 214 Intermediate <TT 215 CLASS="REPLACEABLE" 216 ><I 217 >hop</I 218 ></TT 219 >s may not be allowed, because IPv6 source routing was deprecated (RFC5095).</P 220 ></DIV 221 ><DIV 222 CLASS="REFSECT1" 223 ><A 224 NAME="AEN61" 225 ></A 226 ><H2 227 >OPTIONS</H2 228 ><P 229 ></P 230 ><DIV 231 CLASS="VARIABLELIST" 232 ><DL 233 ><DT 234 ><CODE 235 CLASS="OPTION" 236 >-a</CODE 237 ></DT 238 ><DD 239 ><P 240 >Audible ping. 241 </P 242 ></DD 243 ><DT 244 ><CODE 245 CLASS="OPTION" 246 >-A</CODE 247 ></DT 248 ><DD 249 ><P 250 >Adaptive ping. Interpacket interval adapts to round-trip time, so that 251 effectively not more than one (or more, if preload is set) unanswered probe 252 is present in the network. Minimal interval is 200msec for not super-user. 253 On networks with low rtt this mode is essentially equivalent to flood mode. 254 </P 255 ></DD 256 ><DT 257 ><CODE 258 CLASS="OPTION" 259 >-b</CODE 260 ></DT 261 ><DD 262 ><P 263 >Allow pinging a broadcast address. 264 </P 265 ></DD 266 ><DT 267 ><CODE 268 CLASS="OPTION" 269 >-B</CODE 270 ></DT 271 ><DD 272 ><P 273 >Do not allow <B 274 CLASS="COMMAND" 275 >ping</B 276 > to change source address of probes. 277 The address is bound to one selected when <B 278 CLASS="COMMAND" 279 >ping</B 280 > starts. 281 </P 282 ></DD 283 ><DT 284 ><CODE 285 CLASS="OPTION" 286 ><A 287 NAME="PING.COUNT" 288 ></A 289 >-c <TT 290 CLASS="REPLACEABLE" 291 ><I 292 >count</I 293 ></TT 294 ></CODE 295 ></DT 296 ><DD 297 ><P 298 >Stop after sending <TT 299 CLASS="REPLACEABLE" 300 ><I 301 >count</I 302 ></TT 303 > ECHO_REQUEST 304 packets. With 305 <A 306 HREF="r3.html#PING.DEADLINE" 307 ><TT 308 CLASS="REPLACEABLE" 309 ><I 310 >deadline</I 311 ></TT 312 ></A 313 > 314 option, <B 315 CLASS="COMMAND" 316 >ping</B 317 > waits for 318 <TT 319 CLASS="REPLACEABLE" 320 ><I 321 >count</I 322 ></TT 323 > ECHO_REPLY packets, until the timeout expires. 324 </P 325 ></DD 326 ><DT 327 ><CODE 328 CLASS="OPTION" 329 >-d</CODE 330 ></DT 331 ><DD 332 ><P 333 >Set the <CODE 334 CLASS="CONSTANT" 335 >SO_DEBUG</CODE 336 > option on the socket being used. 337 Essentially, this socket option is not used by Linux kernel. 338 </P 339 ></DD 340 ><DT 341 ><CODE 342 CLASS="OPTION" 343 >-D</CODE 344 ></DT 345 ><DD 346 ><P 347 >Print timestamp (unix time + microseconds as in gettimeofday) before 348 each line. 349 </P 350 ></DD 351 ><DT 352 ><CODE 353 CLASS="OPTION" 354 >-f</CODE 355 ></DT 356 ><DD 357 ><P 358 >Flood ping. For every ECHO_REQUEST sent a period ``.'' is printed, 359 while for ever ECHO_REPLY received a backspace is printed. 360 This provides a rapid display of how many packets are being dropped. 361 If interval is not given, it sets interval to zero and 362 outputs packets as fast as they come back or one hundred times per second, 363 whichever is more. 364 Only the super-user may use this option with zero interval. 365 </P 366 ></DD 367 ><DT 368 ><CODE 369 CLASS="OPTION" 370 >-F <TT 371 CLASS="REPLACEABLE" 372 ><I 373 >flow label</I 374 ></TT 375 ></CODE 376 ></DT 377 ><DD 378 ><P 379 ><B 380 CLASS="COMMAND" 381 >ping6</B 382 > only. 383 Allocate and set 20 bit flow label (in hex) on echo request packets. 384 If value is zero, kernel allocates random flow label. 385 </P 386 ></DD 387 ><DT 388 ><CODE 389 CLASS="OPTION" 390 >-h</CODE 391 ></DT 392 ><DD 393 ><P 394 >Show help. 395 </P 396 ></DD 397 ><DT 398 ><CODE 399 CLASS="OPTION" 400 >-i <TT 401 CLASS="REPLACEABLE" 402 ><I 403 >interval</I 404 ></TT 405 ></CODE 406 ></DT 407 ><DD 408 ><P 409 >Wait <TT 410 CLASS="REPLACEABLE" 411 ><I 412 >interval</I 413 ></TT 414 > seconds between sending each packet. 415 The default is to wait for one second between each packet normally, 416 or not to wait in flood mode. Only super-user may set interval 417 to values less 0.2 seconds. 418 </P 419 ></DD 420 ><DT 421 ><CODE 422 CLASS="OPTION" 423 >-I <TT 424 CLASS="REPLACEABLE" 425 ><I 426 >interface</I 427 ></TT 428 ></CODE 429 ></DT 430 ><DD 431 ><P 432 ><TT 433 CLASS="REPLACEABLE" 434 ><I 435 >interface</I 436 ></TT 437 > is either an address, or an interface name. 438 If <TT 439 CLASS="REPLACEABLE" 440 ><I 441 >interface</I 442 ></TT 443 > is an address, it sets source address 444 to specified interface address. 445 If <TT 446 CLASS="REPLACEABLE" 447 ><I 448 >interface</I 449 ></TT 450 > in an interface name, it sets 451 source interface to specified interface. 452 For <B 453 CLASS="COMMAND" 454 >ping6</B 455 >, when doing ping to a link-local scope 456 address, link specification (by the '%'-notation in 457 <TT 458 CLASS="REPLACEABLE" 459 ><I 460 >destination</I 461 ></TT 462 >, or by this option) is required. 463 </P 464 ></DD 465 ><DT 466 ><CODE 467 CLASS="OPTION" 468 >-l <TT 469 CLASS="REPLACEABLE" 470 ><I 471 >preload</I 472 ></TT 473 ></CODE 474 ></DT 475 ><DD 476 ><P 477 >If <TT 478 CLASS="REPLACEABLE" 479 ><I 480 >preload</I 481 ></TT 482 > is specified, 483 <B 484 CLASS="COMMAND" 485 >ping</B 486 > sends that many packets not waiting for reply. 487 Only the super-user may select preload more than 3. 488 </P 489 ></DD 490 ><DT 491 ><CODE 492 CLASS="OPTION" 493 >-L</CODE 494 ></DT 495 ><DD 496 ><P 497 >Suppress loopback of multicast packets. This flag only applies if the ping 498 destination is a multicast address. 499 </P 500 ></DD 501 ><DT 502 ><CODE 503 CLASS="OPTION" 504 >-m <TT 505 CLASS="REPLACEABLE" 506 ><I 507 >mark</I 508 ></TT 509 ></CODE 510 ></DT 511 ><DD 512 ><P 513 >use <TT 514 CLASS="REPLACEABLE" 515 ><I 516 >mark</I 517 ></TT 518 > to tag the packets going out. This is useful 519 for variety of reasons within the kernel such as using policy 520 routing to select specific outbound processing. 521 </P 522 ></DD 523 ><DT 524 ><CODE 525 CLASS="OPTION" 526 >-M <TT 527 CLASS="REPLACEABLE" 528 ><I 529 >pmtudisc_opt</I 530 ></TT 531 ></CODE 532 ></DT 533 ><DD 534 ><P 535 >Select Path MTU Discovery strategy. 536 <TT 537 CLASS="REPLACEABLE" 538 ><I 539 >pmtudisc_option</I 540 ></TT 541 > may be either <TT 542 CLASS="REPLACEABLE" 543 ><I 544 >do</I 545 ></TT 546 > 547 (prohibit fragmentation, even local one), 548 <TT 549 CLASS="REPLACEABLE" 550 ><I 551 >want</I 552 ></TT 553 > (do PMTU discovery, fragment locally when packet size 554 is large), or <TT 555 CLASS="REPLACEABLE" 556 ><I 557 >dont</I 558 ></TT 559 > (do not set DF flag). 560 </P 561 ></DD 562 ><DT 563 ><CODE 564 CLASS="OPTION" 565 >-N <TT 566 CLASS="REPLACEABLE" 567 ><I 568 >nodeinfo_option</I 569 ></TT 570 ></CODE 571 ></DT 572 ><DD 573 ><P 574 ><B 575 CLASS="COMMAND" 576 >ping6</B 577 > only. 578 Send ICMPv6 Node Information Queries (RFC4620), instead of Echo Request. 579 <P 580 ></P 581 ><DIV 582 CLASS="VARIABLELIST" 583 ><DL 584 ><DT 585 ><CODE 586 CLASS="OPTION" 587 >help</CODE 588 ></DT 589 ><DD 590 ><P 591 >Show help for NI support.</P 592 ></DD 593 ></DL 594 ></DIV 595 > 596 <P 597 ></P 598 ><DIV 599 CLASS="VARIABLELIST" 600 ><DL 601 ><DT 602 ><CODE 603 CLASS="OPTION" 604 >name</CODE 605 ></DT 606 ><DD 607 ><P 608 >Queries for Node Names.</P 609 ></DD 610 ></DL 611 ></DIV 612 > 613 <P 614 ></P 615 ><DIV 616 CLASS="VARIABLELIST" 617 ><DL 618 ><DT 619 ><CODE 620 CLASS="OPTION" 621 >ipv6</CODE 622 ></DT 623 ><DD 624 ><P 625 >Queries for IPv6 Addresses. There are several IPv6 specific flags. 626 <P 627 ></P 628 ><DIV 629 CLASS="VARIABLELIST" 630 ><DL 631 ><DT 632 ><CODE 633 CLASS="OPTION" 634 >ipv6-global</CODE 635 ></DT 636 ><DD 637 ><P 638 >Request IPv6 global-scope addresses.</P 639 ></DD 640 ></DL 641 ></DIV 642 > 643 <P 644 ></P 645 ><DIV 646 CLASS="VARIABLELIST" 647 ><DL 648 ><DT 649 ><CODE 650 CLASS="OPTION" 651 >ipv6-sitelocal</CODE 652 ></DT 653 ><DD 654 ><P 655 >Request IPv6 site-local addresses.</P 656 ></DD 657 ></DL 658 ></DIV 659 > 660 <P 661 ></P 662 ><DIV 663 CLASS="VARIABLELIST" 664 ><DL 665 ><DT 666 ><CODE 667 CLASS="OPTION" 668 >ipv6-linklocal</CODE 669 ></DT 670 ><DD 671 ><P 672 >Request IPv6 link-local addresses.</P 673 ></DD 674 ></DL 675 ></DIV 676 > 677 <P 678 ></P 679 ><DIV 680 CLASS="VARIABLELIST" 681 ><DL 682 ><DT 683 ><CODE 684 CLASS="OPTION" 685 >ipv6-all</CODE 686 ></DT 687 ><DD 688 ><P 689 >Request IPv6 addresses on other interfaces.</P 690 ></DD 691 ></DL 692 ></DIV 693 > 694 </P 695 ></DD 696 ></DL 697 ></DIV 698 > 699 <P 700 ></P 701 ><DIV 702 CLASS="VARIABLELIST" 703 ><DL 704 ><DT 705 ><CODE 706 CLASS="OPTION" 707 >ipv4</CODE 708 ></DT 709 ><DD 710 ><P 711 >Queries for IPv4 Addresses. There is one IPv4 specific flag. 712 <P 713 ></P 714 ><DIV 715 CLASS="VARIABLELIST" 716 ><DL 717 ><DT 718 ><CODE 719 CLASS="OPTION" 720 >ipv4-all</CODE 721 ></DT 722 ><DD 723 ><P 724 >Request IPv4 addresses on other interfaces.</P 725 ></DD 726 ></DL 727 ></DIV 728 > 729 </P 730 ></DD 731 ></DL 732 ></DIV 733 > 734 <P 735 ></P 736 ><DIV 737 CLASS="VARIABLELIST" 738 ><DL 739 ><DT 740 ><CODE 741 CLASS="OPTION" 742 >subject-ipv6=<TT 743 CLASS="REPLACEABLE" 744 ><I 745 >ipv6addr</I 746 ></TT 747 ></CODE 748 ></DT 749 ><DD 750 ><P 751 >IPv6 subject address.</P 752 ></DD 753 ></DL 754 ></DIV 755 > 756 <P 757 ></P 758 ><DIV 759 CLASS="VARIABLELIST" 760 ><DL 761 ><DT 762 ><CODE 763 CLASS="OPTION" 764 >subject-ipv4=<TT 765 CLASS="REPLACEABLE" 766 ><I 767 >ipv4addr</I 768 ></TT 769 ></CODE 770 ></DT 771 ><DD 772 ><P 773 >IPv4 subject address.</P 774 ></DD 775 ></DL 776 ></DIV 777 > 778 <P 779 ></P 780 ><DIV 781 CLASS="VARIABLELIST" 782 ><DL 783 ><DT 784 ><CODE 785 CLASS="OPTION" 786 >subject-name=<TT 787 CLASS="REPLACEABLE" 788 ><I 789 >nodename</I 790 ></TT 791 ></CODE 792 ></DT 793 ><DD 794 ><P 795 >Subject name. If it contains more than one dot, 796 fully-qualified domain name is assumed.</P 797 ></DD 798 ></DL 799 ></DIV 800 > 801 <P 802 ></P 803 ><DIV 804 CLASS="VARIABLELIST" 805 ><DL 806 ><DT 807 ><CODE 808 CLASS="OPTION" 809 >subject-fqdn=<TT 810 CLASS="REPLACEABLE" 811 ><I 812 >nodename</I 813 ></TT 814 ></CODE 815 ></DT 816 ><DD 817 ><P 818 >Subject name. Fully-qualified domain name is 819 always assumed.</P 820 ></DD 821 ></DL 822 ></DIV 823 > 824 </P 825 ></DD 826 ><DT 827 ><CODE 828 CLASS="OPTION" 829 >-n</CODE 830 ></DT 831 ><DD 832 ><P 833 >Numeric output only. 834 No attempt will be made to lookup symbolic names for host addresses. 835 </P 836 ></DD 837 ><DT 838 ><CODE 839 CLASS="OPTION" 840 >-O</CODE 841 ></DT 842 ><DD 843 ><P 844 >Report outstanding ICMP ECHO reply before sending next packet. 845 This is useful together with the timestamp <CODE 846 CLASS="OPTION" 847 >-D</CODE 848 > to 849 log output to a diagnostic file and search for missing answers. 850 </P 851 ></DD 852 ><DT 853 ><CODE 854 CLASS="OPTION" 855 >-p <TT 856 CLASS="REPLACEABLE" 857 ><I 858 >pattern</I 859 ></TT 860 ></CODE 861 ></DT 862 ><DD 863 ><P 864 >You may specify up to 16 ``pad'' bytes to fill out the packet you send. 865 This is useful for diagnosing data-dependent problems in a network. 866 For example, <CODE 867 CLASS="OPTION" 868 >-p ff</CODE 869 > will cause the sent packet 870 to be filled with all ones. 871 </P 872 ></DD 873 ><DT 874 ><CODE 875 CLASS="OPTION" 876 >-q</CODE 877 ></DT 878 ><DD 879 ><P 880 >Quiet output. 881 Nothing is displayed except the summary lines at startup time and 882 when finished. 883 </P 884 ></DD 885 ><DT 886 ><CODE 887 CLASS="OPTION" 888 >-Q <TT 889 CLASS="REPLACEABLE" 890 ><I 891 >tos</I 892 ></TT 893 ></CODE 894 ></DT 895 ><DD 896 ><P 897 > Set Quality of Service -related bits in ICMP datagrams. 898 <TT 899 CLASS="REPLACEABLE" 900 ><I 901 >tos</I 902 ></TT 903 > can be decimal (<B 904 CLASS="COMMAND" 905 >ping</B 906 > only) or hex number. 907 </P 908 ><P 909 > In RFC2474, these fields are interpreted as 8-bit Differentiated 910 Services (DS), consisting of: bits 0-1 (2 lowest bits) of separate 911 data, and bits 2-7 (highest 6 bits) of Differentiated Services 912 Codepoint (DSCP). In RFC2481 and RFC3168, bits 0-1 are used for ECN. 913 </P 914 ><P 915 > Historically (RFC1349, obsoleted by RFC2474), these were interpreted 916 as: bit 0 (lowest bit) for reserved (currently being redefined as 917 congestion control), 1-4 for Type of Service and bits 5-7 918 (highest bits) for Precedence. 919 </P 920 ></DD 921 ><DT 922 ><CODE 923 CLASS="OPTION" 924 >-r</CODE 925 ></DT 926 ><DD 927 ><P 928 >Bypass the normal routing tables and send directly to a host on an attached 929 interface. 930 If the host is not on a directly-attached network, an error is returned. 931 This option can be used to ping a local host through an interface 932 that has no route through it provided the option <CODE 933 CLASS="OPTION" 934 >-I</CODE 935 > is also 936 used. 937 </P 938 ></DD 939 ><DT 940 ><CODE 941 CLASS="OPTION" 942 >-R</CODE 943 ></DT 944 ><DD 945 ><P 946 ><B 947 CLASS="COMMAND" 948 >ping</B 949 > only. 950 Record route. 951 Includes the RECORD_ROUTE option in the ECHO_REQUEST 952 packet and displays the route buffer on returned packets. 953 Note that the IP header is only large enough for nine such routes. 954 Many hosts ignore or discard this option. 955 </P 956 ></DD 957 ><DT 958 ><CODE 959 CLASS="OPTION" 960 >-s <TT 961 CLASS="REPLACEABLE" 962 ><I 963 >packetsize</I 964 ></TT 965 ></CODE 966 ></DT 967 ><DD 968 ><P 969 >Specifies the number of data bytes to be sent. 970 The default is 56, which translates into 64 ICMP 971 data bytes when combined with the 8 bytes of ICMP header data. 972 </P 973 ></DD 974 ><DT 975 ><CODE 976 CLASS="OPTION" 977 >-S <TT 978 CLASS="REPLACEABLE" 979 ><I 980 >sndbuf</I 981 ></TT 982 ></CODE 983 ></DT 984 ><DD 985 ><P 986 >Set socket sndbuf. If not specified, it is selected to buffer 987 not more than one packet. 988 </P 989 ></DD 990 ><DT 991 ><CODE 992 CLASS="OPTION" 993 >-t <TT 994 CLASS="REPLACEABLE" 995 ><I 996 >ttl</I 997 ></TT 998 ></CODE 999 ></DT 1000 ><DD 1001 ><P 1002 ><B 1003 CLASS="COMMAND" 1004 >ping</B 1005 > only. 1006 Set the IP Time to Live. 1007 </P 1008 ></DD 1009 ><DT 1010 ><CODE 1011 CLASS="OPTION" 1012 >-T <TT 1013 CLASS="REPLACEABLE" 1014 ><I 1015 >timestamp option</I 1016 ></TT 1017 ></CODE 1018 ></DT 1019 ><DD 1020 ><P 1021 >Set special IP timestamp options. 1022 <TT 1023 CLASS="REPLACEABLE" 1024 ><I 1025 >timestamp option</I 1026 ></TT 1027 > may be either 1028 <TT 1029 CLASS="REPLACEABLE" 1030 ><I 1031 >tsonly</I 1032 ></TT 1033 > (only timestamps), 1034 <TT 1035 CLASS="REPLACEABLE" 1036 ><I 1037 >tsandaddr</I 1038 ></TT 1039 > (timestamps and addresses) or 1040 <TT 1041 CLASS="REPLACEABLE" 1042 ><I 1043 >tsprespec host1 [host2 [host3 [host4]]]</I 1044 ></TT 1045 > 1046 (timestamp prespecified hops). 1047 </P 1048 ></DD 1049 ><DT 1050 ><CODE 1051 CLASS="OPTION" 1052 >-U</CODE 1053 ></DT 1054 ><DD 1055 ><P 1056 >Print full user-to-user latency (the old behaviour). Normally 1057 <B 1058 CLASS="COMMAND" 1059 >ping</B 1060 > 1061 prints network round trip time, which can be different 1062 f.e. due to DNS failures. 1063 </P 1064 ></DD 1065 ><DT 1066 ><CODE 1067 CLASS="OPTION" 1068 >-v</CODE 1069 ></DT 1070 ><DD 1071 ><P 1072 >Verbose output. 1073 </P 1074 ></DD 1075 ><DT 1076 ><CODE 1077 CLASS="OPTION" 1078 >-V</CODE 1079 ></DT 1080 ><DD 1081 ><P 1082 >Show version and exit. 1083 </P 1084 ></DD 1085 ><DT 1086 ><CODE 1087 CLASS="OPTION" 1088 ><A 1089 NAME="PING.DEADLINE" 1090 ></A 1091 >-w <TT 1092 CLASS="REPLACEABLE" 1093 ><I 1094 >deadline</I 1095 ></TT 1096 ></CODE 1097 ></DT 1098 ><DD 1099 ><P 1100 >Specify a timeout, in seconds, before 1101 <B 1102 CLASS="COMMAND" 1103 >ping</B 1104 > 1105 exits regardless of how many 1106 packets have been sent or received. In this case 1107 <B 1108 CLASS="COMMAND" 1109 >ping</B 1110 > 1111 does not stop after 1112 <A 1113 HREF="r3.html#PING.COUNT" 1114 ><TT 1115 CLASS="REPLACEABLE" 1116 ><I 1117 >count</I 1118 ></TT 1119 ></A 1120 > 1121 packet are sent, it waits either for 1122 <A 1123 HREF="r3.html#PING.DEADLINE" 1124 ><TT 1125 CLASS="REPLACEABLE" 1126 ><I 1127 >deadline</I 1128 ></TT 1129 ></A 1130 > 1131 expire or until 1132 <A 1133 HREF="r3.html#PING.COUNT" 1134 ><TT 1135 CLASS="REPLACEABLE" 1136 ><I 1137 >count</I 1138 ></TT 1139 ></A 1140 > 1141 probes are answered or for some error notification from network. 1142 </P 1143 ></DD 1144 ><DT 1145 ><CODE 1146 CLASS="OPTION" 1147 >-W <TT 1148 CLASS="REPLACEABLE" 1149 ><I 1150 >timeout</I 1151 ></TT 1152 ></CODE 1153 ></DT 1154 ><DD 1155 ><P 1156 >Time to wait for a response, in seconds. The option affects only timeout 1157 in absence of any responses, otherwise <B 1158 CLASS="COMMAND" 1159 >ping</B 1160 > waits for two RTTs. 1161 </P 1162 ></DD 1163 ></DL 1164 ></DIV 1165 ><P 1166 >When using <B 1167 CLASS="COMMAND" 1168 >ping</B 1169 > for fault isolation, it should first be run 1170 on the local host, to verify that the local network interface is up 1171 and running. Then, hosts and gateways further and further away should be 1172 ``pinged''. Round-trip times and packet loss statistics are computed. 1173 If duplicate packets are received, they are not included in the packet 1174 loss calculation, although the round trip time of these packets is used 1175 in calculating the minimum/average/maximum round-trip time numbers. 1176 When the specified number of packets have been sent (and received) or 1177 if the program is terminated with a 1178 <CODE 1179 CLASS="CONSTANT" 1180 >SIGINT</CODE 1181 >, a brief summary is displayed. Shorter current statistics 1182 can be obtained without termination of process with signal 1183 <CODE 1184 CLASS="CONSTANT" 1185 >SIGQUIT</CODE 1186 >.</P 1187 ><P 1188 >If <B 1189 CLASS="COMMAND" 1190 >ping</B 1191 > does not receive any reply packets at all it will 1192 exit with code 1. If a packet 1193 <A 1194 HREF="r3.html#PING.COUNT" 1195 ><TT 1196 CLASS="REPLACEABLE" 1197 ><I 1198 >count</I 1199 ></TT 1200 ></A 1201 > 1202 and 1203 <A 1204 HREF="r3.html#PING.DEADLINE" 1205 ><TT 1206 CLASS="REPLACEABLE" 1207 ><I 1208 >deadline</I 1209 ></TT 1210 ></A 1211 > 1212 are both specified, and fewer than 1213 <A 1214 HREF="r3.html#PING.COUNT" 1215 ><TT 1216 CLASS="REPLACEABLE" 1217 ><I 1218 >count</I 1219 ></TT 1220 ></A 1221 > 1222 packets are received by the time the 1223 <A 1224 HREF="r3.html#PING.DEADLINE" 1225 ><TT 1226 CLASS="REPLACEABLE" 1227 ><I 1228 >deadline</I 1229 ></TT 1230 ></A 1231 > 1232 has arrived, it will also exit with code 1. 1233 On other error it exits with code 2. Otherwise it exits with code 0. This 1234 makes it possible to use the exit code to see if a host is alive or 1235 not.</P 1236 ><P 1237 >This program is intended for use in network testing, measurement and 1238 management. 1239 Because of the load it can impose on the network, it is unwise to use 1240 <B 1241 CLASS="COMMAND" 1242 >ping</B 1243 > during normal operations or from automated scripts.</P 1244 ></DIV 1245 ><DIV 1246 CLASS="REFSECT1" 1247 ><A 1248 NAME="AEN391" 1249 ></A 1250 ><H2 1251 >ICMP PACKET DETAILS</H2 1252 ><P 1253 >An IP header without options is 20 bytes. 1254 An ICMP ECHO_REQUEST packet contains an additional 8 bytes worth 1255 of ICMP header followed by an arbitrary amount of data. 1256 When a <TT 1257 CLASS="REPLACEABLE" 1258 ><I 1259 >packetsize</I 1260 ></TT 1261 > is given, this indicated the size of this 1262 extra piece of data (the default is 56). Thus the amount of data received 1263 inside of an IP packet of type ICMP ECHO_REPLY will always be 8 bytes 1264 more than the requested data space (the ICMP header).</P 1265 ><P 1266 >If the data space is at least of size of <CODE 1267 CLASS="STRUCTNAME" 1268 >struct timeval</CODE 1269 > 1270 <B 1271 CLASS="COMMAND" 1272 >ping</B 1273 > uses the beginning bytes of this space to include 1274 a timestamp which it uses in the computation of round trip times. 1275 If the data space is shorter, no round trip times are given.</P 1276 ></DIV 1277 ><DIV 1278 CLASS="REFSECT1" 1279 ><A 1280 NAME="AEN398" 1281 ></A 1282 ><H2 1283 >DUPLICATE AND DAMAGED PACKETS</H2 1284 ><P 1285 ><B 1286 CLASS="COMMAND" 1287 >ping</B 1288 > will report duplicate and damaged packets. 1289 Duplicate packets should never occur, and seem to be caused by 1290 inappropriate link-level retransmissions. 1291 Duplicates may occur in many situations and are rarely (if ever) a 1292 good sign, although the presence of low levels of duplicates may not 1293 always be cause for alarm.</P 1294 ><P 1295 >Damaged packets are obviously serious cause for alarm and often 1296 indicate broken hardware somewhere in the 1297 <B 1298 CLASS="COMMAND" 1299 >ping</B 1300 > packet's path (in the network or in the hosts).</P 1301 ></DIV 1302 ><DIV 1303 CLASS="REFSECT1" 1304 ><A 1305 NAME="AEN404" 1306 ></A 1307 ><H2 1308 >TRYING DIFFERENT DATA PATTERNS</H2 1309 ><P 1310 >The (inter)network layer should never treat packets differently depending 1311 on the data contained in the data portion. 1312 Unfortunately, data-dependent problems have been known to sneak into 1313 networks and remain undetected for long periods of time. 1314 In many cases the particular pattern that will have problems is something 1315 that doesn't have sufficient ``transitions'', such as all ones or all 1316 zeros, or a pattern right at the edge, such as almost all zeros. 1317 It isn't necessarily enough to specify a data pattern of all zeros (for 1318 example) on the command line because the pattern that is of interest is 1319 at the data link level, and the relationship between what you type and 1320 what the controllers transmit can be complicated.</P 1321 ><P 1322 >This means that if you have a data-dependent problem you will probably 1323 have to do a lot of testing to find it. 1324 If you are lucky, you may manage to find a file that either can't be sent 1325 across your network or that takes much longer to transfer than other 1326 similar length files. 1327 You can then examine this file for repeated patterns that you can test 1328 using the <CODE 1329 CLASS="OPTION" 1330 >-p</CODE 1331 > option of <B 1332 CLASS="COMMAND" 1333 >ping</B 1334 >.</P 1335 ></DIV 1336 ><DIV 1337 CLASS="REFSECT1" 1338 ><A 1339 NAME="AEN410" 1340 ></A 1341 ><H2 1342 >TTL DETAILS</H2 1343 ><P 1344 >The TTL value of an IP packet represents the maximum number of IP routers 1345 that the packet can go through before being thrown away. 1346 In current practice you can expect each router in the Internet to decrement 1347 the TTL field by exactly one.</P 1348 ><P 1349 >The TCP/IP specification states that the TTL field for TCP 1350 packets should be set to 60, but many systems use smaller values 1351 (4.3 BSD uses 30, 4.2 used 15).</P 1352 ><P 1353 >The maximum possible value of this field is 255, and most Unix systems set 1354 the TTL field of ICMP ECHO_REQUEST packets to 255. 1355 This is why you will find you can ``ping'' some hosts, but not reach them 1356 with 1357 <SPAN 1358 CLASS="CITEREFENTRY" 1359 ><SPAN 1360 CLASS="REFENTRYTITLE" 1361 >telnet</SPAN 1362 >(1)</SPAN 1363 > 1364 or 1365 <SPAN 1366 CLASS="CITEREFENTRY" 1367 ><SPAN 1368 CLASS="REFENTRYTITLE" 1369 >ftp</SPAN 1370 >(1)</SPAN 1371 >.</P 1372 ><P 1373 >In normal operation ping prints the TTL value from the packet it receives. 1374 When a remote system receives a ping packet, it can do one of three things 1375 with the TTL field in its response:</P 1376 ><P 1377 ></P 1378 ><UL 1379 ><LI 1380 ><P 1381 >Not change it; this is what Berkeley Unix systems did before the 1382 4.3BSD Tahoe release. In this case the TTL value in the received packet 1383 will be 255 minus the number of routers in the round-trip path. 1384 </P 1385 ></LI 1386 ><LI 1387 ><P 1388 >Set it to 255; this is what current Berkeley Unix systems do. 1389 In this case the TTL value in the received packet will be 255 minus the 1390 number of routers in the path <SPAN 1391 CLASS="emphasis" 1392 ><I 1393 CLASS="EMPHASIS" 1394 >from</I 1395 ></SPAN 1396 > 1397 the remote system <SPAN 1398 CLASS="emphasis" 1399 ><I 1400 CLASS="EMPHASIS" 1401 >to</I 1402 ></SPAN 1403 > the <B 1404 CLASS="COMMAND" 1405 >ping</B 1406 >ing host. 1407 </P 1408 ></LI 1409 ><LI 1410 ><P 1411 >Set it to some other value. Some machines use the same value for 1412 ICMP packets that they use for TCP packets, for example either 30 or 60. 1413 Others may use completely wild values. 1414 </P 1415 ></LI 1416 ></UL 1417 ></DIV 1418 ><DIV 1419 CLASS="REFSECT1" 1420 ><A 1421 NAME="AEN432" 1422 ></A 1423 ><H2 1424 >BUGS</H2 1425 ><P 1426 ></P 1427 ><UL 1428 ><LI 1429 ><P 1430 >Many Hosts and Gateways ignore the RECORD_ROUTE option. 1431 </P 1432 ></LI 1433 ><LI 1434 ><P 1435 >The maximum IP header length is too small for options like 1436 RECORD_ROUTE to be completely useful. 1437 There's not much that that can be done about this, however. 1438 </P 1439 ></LI 1440 ><LI 1441 ><P 1442 >Flood pinging is not recommended in general, and flood pinging the 1443 broadcast address should only be done under very controlled conditions. 1444 </P 1445 ></LI 1446 ></UL 1447 ></DIV 1448 ><DIV 1449 CLASS="REFSECT1" 1450 ><A 1451 NAME="AEN441" 1452 ></A 1453 ><H2 1454 >SEE ALSO</H2 1455 ><P 1456 ><SPAN 1457 CLASS="CITEREFENTRY" 1458 ><SPAN 1459 CLASS="REFENTRYTITLE" 1460 >netstat</SPAN 1461 >(1)</SPAN 1462 >, 1463 <SPAN 1464 CLASS="CITEREFENTRY" 1465 ><SPAN 1466 CLASS="REFENTRYTITLE" 1467 >ifconfig</SPAN 1468 >(8)</SPAN 1469 >.</P 1470 ></DIV 1471 ><DIV 1472 CLASS="REFSECT1" 1473 ><A 1474 NAME="AEN450" 1475 ></A 1476 ><H2 1477 >HISTORY</H2 1478 ><P 1479 >The <B 1480 CLASS="COMMAND" 1481 >ping</B 1482 > command appeared in 4.3BSD.</P 1483 ><P 1484 >The version described here is its descendant specific to Linux.</P 1485 ></DIV 1486 ><DIV 1487 CLASS="REFSECT1" 1488 ><A 1489 NAME="AEN455" 1490 ></A 1491 ><H2 1492 >SECURITY</H2 1493 ><P 1494 ><B 1495 CLASS="COMMAND" 1496 >ping</B 1497 > requires <CODE 1498 CLASS="CONSTANT" 1499 >CAP_NET_RAW</CODE 1500 > capability 1501 to be executed. It may be used as set-uid root.</P 1502 ></DIV 1503 ><DIV 1504 CLASS="REFSECT1" 1505 ><A 1506 NAME="AEN460" 1507 ></A 1508 ><H2 1509 >AVAILABILITY</H2 1510 ><P 1511 ><B 1512 CLASS="COMMAND" 1513 >ping</B 1514 > is part of <TT 1515 CLASS="FILENAME" 1516 >iputils</TT 1517 > package 1518 and the latest versions are available in source form at 1519 <A 1520 HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2" 1521 TARGET="_top" 1522 >http://www.skbuff.net/iputils/iputils-current.tar.bz2</A 1523 >.</P 1524 ></DIV 1525 ><DIV 1526 CLASS="NAVFOOTER" 1527 ><HR 1528 ALIGN="LEFT" 1529 WIDTH="100%"><TABLE 1530 SUMMARY="Footer navigation table" 1531 WIDTH="100%" 1532 BORDER="0" 1533 CELLPADDING="0" 1534 CELLSPACING="0" 1535 ><TR 1536 ><TD 1537 WIDTH="33%" 1538 ALIGN="left" 1539 VALIGN="top" 1540 ><A 1541 HREF="index.html" 1542 ACCESSKEY="P" 1543 >Prev</A 1544 ></TD 1545 ><TD 1546 WIDTH="34%" 1547 ALIGN="center" 1548 VALIGN="top" 1549 ><A 1550 HREF="index.html" 1551 ACCESSKEY="H" 1552 >Home</A 1553 ></TD 1554 ><TD 1555 WIDTH="33%" 1556 ALIGN="right" 1557 VALIGN="top" 1558 ><A 1559 HREF="r466.html" 1560 ACCESSKEY="N" 1561 >Next</A 1562 ></TD 1563 ></TR 1564 ><TR 1565 ><TD 1566 WIDTH="33%" 1567 ALIGN="left" 1568 VALIGN="top" 1569 >System Manager's Manual: iputils</TD 1570 ><TD 1571 WIDTH="34%" 1572 ALIGN="center" 1573 VALIGN="top" 1574 > </TD 1575 ><TD 1576 WIDTH="33%" 1577 ALIGN="right" 1578 VALIGN="top" 1579 >arping</TD 1580 ></TR 1581 ></TABLE 1582 ></DIV 1583 ></BODY 1584 ></HTML 1585 > 1586 No newline at end of file -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/r466.html iputils-s20121221/doc/r466.html
old new 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 2 <HTML 3 ><HEAD 4 ><TITLE 5 >arping</TITLE 6 ><META 7 NAME="GENERATOR" 8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK 9 REL="HOME" 10 TITLE="System Manager's Manual: iputils" 11 HREF="index.html"><LINK 12 REL="PREVIOUS" 13 TITLE="ping" 14 HREF="r3.html"><LINK 15 REL="NEXT" 16 TITLE="clockdiff" 17 HREF="r625.html"></HEAD 18 ><BODY 19 CLASS="REFENTRY" 20 BGCOLOR="#FFFFFF" 21 TEXT="#000000" 22 LINK="#0000FF" 23 VLINK="#840084" 24 ALINK="#0000FF" 25 ><DIV 26 CLASS="NAVHEADER" 27 ><TABLE 28 SUMMARY="Header navigation table" 29 WIDTH="100%" 30 BORDER="0" 31 CELLPADDING="0" 32 CELLSPACING="0" 33 ><TR 34 ><TH 35 COLSPAN="3" 36 ALIGN="center" 37 >System Manager's Manual: iputils</TH 38 ></TR 39 ><TR 40 ><TD 41 WIDTH="10%" 42 ALIGN="left" 43 VALIGN="bottom" 44 ><A 45 HREF="r3.html" 46 ACCESSKEY="P" 47 >Prev</A 48 ></TD 49 ><TD 50 WIDTH="80%" 51 ALIGN="center" 52 VALIGN="bottom" 53 ></TD 54 ><TD 55 WIDTH="10%" 56 ALIGN="right" 57 VALIGN="bottom" 58 ><A 59 HREF="r625.html" 60 ACCESSKEY="N" 61 >Next</A 62 ></TD 63 ></TR 64 ></TABLE 65 ><HR 66 ALIGN="LEFT" 67 WIDTH="100%"></DIV 68 ><H1 69 ><A 70 NAME="ARPING" 71 ></A 72 >arping</H1 73 ><DIV 74 CLASS="REFNAMEDIV" 75 ><A 76 NAME="AEN471" 77 ></A 78 ><H2 79 >Name</H2 80 >arping -- send ARP REQUEST to a neighbour host</DIV 81 ><DIV 82 CLASS="REFSYNOPSISDIV" 83 ><A 84 NAME="AEN474" 85 ></A 86 ><H2 87 >Synopsis</H2 88 ><P 89 ><B 90 CLASS="COMMAND" 91 >arping</B 92 > [<CODE 93 CLASS="OPTION" 94 >-AbDfhqUV</CODE 95 >] [-c <TT 96 CLASS="REPLACEABLE" 97 ><I 98 >count</I 99 ></TT 100 >] [-w <TT 101 CLASS="REPLACEABLE" 102 ><I 103 >deadline</I 104 ></TT 105 >] [-s <TT 106 CLASS="REPLACEABLE" 107 ><I 108 >source</I 109 ></TT 110 >] {-I <TT 111 CLASS="REPLACEABLE" 112 ><I 113 >interface</I 114 ></TT 115 >} {<TT 116 CLASS="REPLACEABLE" 117 ><I 118 >destination</I 119 ></TT 120 >}</P 121 ></DIV 122 ><DIV 123 CLASS="REFSECT1" 124 ><A 125 NAME="AEN489" 126 ></A 127 ><H2 128 >DESCRIPTION</H2 129 ><P 130 >Ping <TT 131 CLASS="REPLACEABLE" 132 ><I 133 >destination</I 134 ></TT 135 > on device <TT 136 CLASS="REPLACEABLE" 137 ><I 138 >interface</I 139 ></TT 140 > by ARP packets, 141 using source address <TT 142 CLASS="REPLACEABLE" 143 ><I 144 >source</I 145 ></TT 146 >.</P 147 ></DIV 148 ><DIV 149 CLASS="REFSECT1" 150 ><A 151 NAME="AEN495" 152 ></A 153 ><H2 154 >OPTIONS</H2 155 ><P 156 ></P 157 ><DIV 158 CLASS="VARIABLELIST" 159 ><DL 160 ><DT 161 ><CODE 162 CLASS="OPTION" 163 >-A</CODE 164 ></DT 165 ><DD 166 ><P 167 >The same as <CODE 168 CLASS="OPTION" 169 >-U</CODE 170 >, but ARP REPLY packets used instead 171 of ARP REQUEST. 172 </P 173 ></DD 174 ><DT 175 ><CODE 176 CLASS="OPTION" 177 >-b</CODE 178 ></DT 179 ><DD 180 ><P 181 >Send only MAC level broadcasts. Normally <B 182 CLASS="COMMAND" 183 >arping</B 184 > starts 185 from sending broadcast, and switch to unicast after reply received. 186 </P 187 ></DD 188 ><DT 189 ><CODE 190 CLASS="OPTION" 191 ><A 192 NAME="ARPING.COUNT" 193 ></A 194 >-c <TT 195 CLASS="REPLACEABLE" 196 ><I 197 >count</I 198 ></TT 199 ></CODE 200 ></DT 201 ><DD 202 ><P 203 >Stop after sending <TT 204 CLASS="REPLACEABLE" 205 ><I 206 >count</I 207 ></TT 208 > ARP REQUEST 209 packets. With 210 <A 211 HREF="r466.html#ARPING.DEADLINE" 212 ><TT 213 CLASS="REPLACEABLE" 214 ><I 215 >deadline</I 216 ></TT 217 ></A 218 > 219 option, <B 220 CLASS="COMMAND" 221 >arping</B 222 > waits for 223 <TT 224 CLASS="REPLACEABLE" 225 ><I 226 >count</I 227 ></TT 228 > ARP REPLY packets, until the timeout expires. 229 </P 230 ></DD 231 ><DT 232 ><CODE 233 CLASS="OPTION" 234 >-D</CODE 235 ></DT 236 ><DD 237 ><P 238 >Duplicate address detection mode (DAD). See 239 <A 240 HREF="http://tools.ietf.org/rfc/rfc2131.txt" 241 TARGET="_top" 242 >RFC2131, 4.4.1</A 243 >. 244 Returns 0, if DAD succeeded i.e. no replies are received 245 </P 246 ></DD 247 ><DT 248 ><CODE 249 CLASS="OPTION" 250 >-f</CODE 251 ></DT 252 ><DD 253 ><P 254 >Finish after the first reply confirming that target is alive. 255 </P 256 ></DD 257 ><DT 258 ><CODE 259 CLASS="OPTION" 260 ><A 261 NAME="OPT.INTERFACE" 262 ></A 263 >-I <TT 264 CLASS="REPLACEABLE" 265 ><I 266 >interface</I 267 ></TT 268 ></CODE 269 ></DT 270 ><DD 271 ><P 272 >Name of network device where to send ARP REQUEST packets. 273 </P 274 ></DD 275 ><DT 276 ><CODE 277 CLASS="OPTION" 278 >-h</CODE 279 ></DT 280 ><DD 281 ><P 282 >Print help page and exit. 283 </P 284 ></DD 285 ><DT 286 ><CODE 287 CLASS="OPTION" 288 >-q</CODE 289 ></DT 290 ><DD 291 ><P 292 >Quiet output. Nothing is displayed. 293 </P 294 ></DD 295 ><DT 296 ><CODE 297 CLASS="OPTION" 298 ><A 299 NAME="OPT.SOURCE" 300 ></A 301 >-s <TT 302 CLASS="REPLACEABLE" 303 ><I 304 >source</I 305 ></TT 306 ></CODE 307 ></DT 308 ><DD 309 ><P 310 >IP source address to use in ARP packets. 311 If this option is absent, source address is: 312 <P 313 ></P 314 ><UL 315 ><LI 316 ><P 317 >In DAD mode (with option <CODE 318 CLASS="OPTION" 319 >-D</CODE 320 >) set to 0.0.0.0. 321 </P 322 ></LI 323 ><LI 324 ><P 325 >In Unsolicited ARP mode (with options <CODE 326 CLASS="OPTION" 327 >-U</CODE 328 > or <CODE 329 CLASS="OPTION" 330 >-A</CODE 331 >) 332 set to <TT 333 CLASS="REPLACEABLE" 334 ><I 335 >destination</I 336 ></TT 337 >. 338 </P 339 ></LI 340 ><LI 341 ><P 342 >Otherwise, it is calculated from routing tables. 343 </P 344 ></LI 345 ></UL 346 > 347 </P 348 ></DD 349 ><DT 350 ><CODE 351 CLASS="OPTION" 352 >-U</CODE 353 ></DT 354 ><DD 355 ><P 356 >Unsolicited ARP mode to update neighbours' ARP caches. 357 No replies are expected. 358 </P 359 ></DD 360 ><DT 361 ><CODE 362 CLASS="OPTION" 363 >-V</CODE 364 ></DT 365 ><DD 366 ><P 367 >Print version of the program and exit. 368 </P 369 ></DD 370 ><DT 371 ><CODE 372 CLASS="OPTION" 373 ><A 374 NAME="ARPING.DEADLINE" 375 ></A 376 >-w <TT 377 CLASS="REPLACEABLE" 378 ><I 379 >deadline</I 380 ></TT 381 ></CODE 382 ></DT 383 ><DD 384 ><P 385 >Specify a timeout, in seconds, before 386 <B 387 CLASS="COMMAND" 388 >arping</B 389 > 390 exits regardless of how many 391 packets have been sent or received. In this case 392 <B 393 CLASS="COMMAND" 394 >arping</B 395 > 396 does not stop after 397 <A 398 HREF="r466.html#ARPING.COUNT" 399 ><TT 400 CLASS="REPLACEABLE" 401 ><I 402 >count</I 403 ></TT 404 ></A 405 > 406 packet are sent, it waits either for 407 <A 408 HREF="r466.html#ARPING.DEADLINE" 409 ><TT 410 CLASS="REPLACEABLE" 411 ><I 412 >deadline</I 413 ></TT 414 ></A 415 > 416 expire or until 417 <A 418 HREF="r466.html#ARPING.COUNT" 419 ><TT 420 CLASS="REPLACEABLE" 421 ><I 422 >count</I 423 ></TT 424 ></A 425 > 426 probes are answered. 427 </P 428 ></DD 429 ></DL 430 ></DIV 431 ></DIV 432 ><DIV 433 CLASS="REFSECT1" 434 ><A 435 NAME="AEN593" 436 ></A 437 ><H2 438 >SEE ALSO</H2 439 ><P 440 ><A 441 HREF="r3.html" 442 ><SPAN 443 CLASS="CITEREFENTRY" 444 ><SPAN 445 CLASS="REFENTRYTITLE" 446 >ping</SPAN 447 >(8)</SPAN 448 ></A 449 >, 450 <A 451 HREF="r625.html" 452 ><SPAN 453 CLASS="CITEREFENTRY" 454 ><SPAN 455 CLASS="REFENTRYTITLE" 456 >clockdiff</SPAN 457 >(8)</SPAN 458 ></A 459 >, 460 <A 461 HREF="r819.html" 462 ><SPAN 463 CLASS="CITEREFENTRY" 464 ><SPAN 465 CLASS="REFENTRYTITLE" 466 >tracepath</SPAN 467 >(8)</SPAN 468 ></A 469 >.</P 470 ></DIV 471 ><DIV 472 CLASS="REFSECT1" 473 ><A 474 NAME="AEN608" 475 ></A 476 ><H2 477 >AUTHOR</H2 478 ><P 479 ><B 480 CLASS="COMMAND" 481 >arping</B 482 > was written by 483 <A 484 HREF="mailto:kuznet@ms2.inr.ac.ru" 485 TARGET="_top" 486 >Alexey Kuznetsov 487 <kuznet@ms2.inr.ac.ru></A 488 >. 489 It is now maintained by 490 <A 491 HREF="mailto:yoshfuji@skbuff.net" 492 TARGET="_top" 493 >YOSHIFUJI Hideaki 494 <yoshfuji@skbuff.net></A 495 >.</P 496 ></DIV 497 ><DIV 498 CLASS="REFSECT1" 499 ><A 500 NAME="AEN614" 501 ></A 502 ><H2 503 >SECURITY</H2 504 ><P 505 ><B 506 CLASS="COMMAND" 507 >arping</B 508 > requires <CODE 509 CLASS="CONSTANT" 510 >CAP_NET_RAW</CODE 511 > capability 512 to be executed. It is not recommended to be used as set-uid root, 513 because it allows user to modify ARP caches of neighbour hosts.</P 514 ></DIV 515 ><DIV 516 CLASS="REFSECT1" 517 ><A 518 NAME="AEN619" 519 ></A 520 ><H2 521 >AVAILABILITY</H2 522 ><P 523 ><B 524 CLASS="COMMAND" 525 >arping</B 526 > is part of <TT 527 CLASS="FILENAME" 528 >iputils</TT 529 > package 530 and the latest versions are available in source form at 531 <A 532 HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2" 533 TARGET="_top" 534 >http://www.skbuff.net/iputils/iputils-current.tar.bz2</A 535 >.</P 536 ></DIV 537 ><DIV 538 CLASS="NAVFOOTER" 539 ><HR 540 ALIGN="LEFT" 541 WIDTH="100%"><TABLE 542 SUMMARY="Footer navigation table" 543 WIDTH="100%" 544 BORDER="0" 545 CELLPADDING="0" 546 CELLSPACING="0" 547 ><TR 548 ><TD 549 WIDTH="33%" 550 ALIGN="left" 551 VALIGN="top" 552 ><A 553 HREF="r3.html" 554 ACCESSKEY="P" 555 >Prev</A 556 ></TD 557 ><TD 558 WIDTH="34%" 559 ALIGN="center" 560 VALIGN="top" 561 ><A 562 HREF="index.html" 563 ACCESSKEY="H" 564 >Home</A 565 ></TD 566 ><TD 567 WIDTH="33%" 568 ALIGN="right" 569 VALIGN="top" 570 ><A 571 HREF="r625.html" 572 ACCESSKEY="N" 573 >Next</A 574 ></TD 575 ></TR 576 ><TR 577 ><TD 578 WIDTH="33%" 579 ALIGN="left" 580 VALIGN="top" 581 >ping</TD 582 ><TD 583 WIDTH="34%" 584 ALIGN="center" 585 VALIGN="top" 586 > </TD 587 ><TD 588 WIDTH="33%" 589 ALIGN="right" 590 VALIGN="top" 591 >clockdiff</TD 592 ></TR 593 ></TABLE 594 ></DIV 595 ></BODY 596 ></HTML 597 > 598 No newline at end of file -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/r625.html iputils-s20121221/doc/r625.html
old new 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 2 <HTML 3 ><HEAD 4 ><TITLE 5 >clockdiff</TITLE 6 ><META 7 NAME="GENERATOR" 8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK 9 REL="HOME" 10 TITLE="System Manager's Manual: iputils" 11 HREF="index.html"><LINK 12 REL="PREVIOUS" 13 TITLE="arping" 14 HREF="r466.html"><LINK 15 REL="NEXT" 16 TITLE="rarpd" 17 HREF="r720.html"></HEAD 18 ><BODY 19 CLASS="REFENTRY" 20 BGCOLOR="#FFFFFF" 21 TEXT="#000000" 22 LINK="#0000FF" 23 VLINK="#840084" 24 ALINK="#0000FF" 25 ><DIV 26 CLASS="NAVHEADER" 27 ><TABLE 28 SUMMARY="Header navigation table" 29 WIDTH="100%" 30 BORDER="0" 31 CELLPADDING="0" 32 CELLSPACING="0" 33 ><TR 34 ><TH 35 COLSPAN="3" 36 ALIGN="center" 37 >System Manager's Manual: iputils</TH 38 ></TR 39 ><TR 40 ><TD 41 WIDTH="10%" 42 ALIGN="left" 43 VALIGN="bottom" 44 ><A 45 HREF="r466.html" 46 ACCESSKEY="P" 47 >Prev</A 48 ></TD 49 ><TD 50 WIDTH="80%" 51 ALIGN="center" 52 VALIGN="bottom" 53 ></TD 54 ><TD 55 WIDTH="10%" 56 ALIGN="right" 57 VALIGN="bottom" 58 ><A 59 HREF="r720.html" 60 ACCESSKEY="N" 61 >Next</A 62 ></TD 63 ></TR 64 ></TABLE 65 ><HR 66 ALIGN="LEFT" 67 WIDTH="100%"></DIV 68 ><H1 69 ><A 70 NAME="CLOCKDIFF" 71 ></A 72 >clockdiff</H1 73 ><DIV 74 CLASS="REFNAMEDIV" 75 ><A 76 NAME="AEN630" 77 ></A 78 ><H2 79 >Name</H2 80 >clockdiff -- measure clock difference between hosts</DIV 81 ><DIV 82 CLASS="REFSYNOPSISDIV" 83 ><A 84 NAME="AEN633" 85 ></A 86 ><H2 87 >Synopsis</H2 88 ><P 89 ><B 90 CLASS="COMMAND" 91 >clockdiff</B 92 > [<CODE 93 CLASS="OPTION" 94 >-o</CODE 95 >] [<CODE 96 CLASS="OPTION" 97 >-o1</CODE 98 >] {<TT 99 CLASS="REPLACEABLE" 100 ><I 101 >destination</I 102 ></TT 103 >}</P 104 ></DIV 105 ><DIV 106 CLASS="REFSECT1" 107 ><A 108 NAME="AEN642" 109 ></A 110 ><H2 111 >DESCRIPTION</H2 112 ><P 113 ><B 114 CLASS="COMMAND" 115 >clockdiff</B 116 > Measures clock difference between us and 117 <TT 118 CLASS="REPLACEABLE" 119 ><I 120 >destination</I 121 ></TT 122 > with 1 msec resolution using ICMP TIMESTAMP 123 <A 124 HREF="r625.html#CLOCKDIFF.ICMP-TIMESTAMP" 125 >[2]</A 126 > 127 packets or, optionally, IP TIMESTAMP option 128 <A 129 HREF="r625.html#CLOCKDIFF.IP-TIMESTAMP" 130 >[3]</A 131 > 132 option added to ICMP ECHO. 133 <A 134 HREF="r625.html#CLOCKDIFF.ICMP-ECHO" 135 >[1]</A 136 ></P 137 ></DIV 138 ><DIV 139 CLASS="REFSECT1" 140 ><A 141 NAME="AEN650" 142 ></A 143 ><H2 144 >OPTIONS</H2 145 ><P 146 ></P 147 ><DIV 148 CLASS="VARIABLELIST" 149 ><DL 150 ><DT 151 ><CODE 152 CLASS="OPTION" 153 >-o</CODE 154 ></DT 155 ><DD 156 ><P 157 >Use IP TIMESTAMP with ICMP ECHO instead of ICMP TIMESTAMP 158 messages. It is useful with some destinations, which do not support 159 ICMP TIMESTAMP (f.e. Solaris <2.4). 160 </P 161 ></DD 162 ><DT 163 ><CODE 164 CLASS="OPTION" 165 >-o1</CODE 166 ></DT 167 ><DD 168 ><P 169 >Slightly different form of <CODE 170 CLASS="OPTION" 171 >-o</CODE 172 >, namely it uses three-term 173 IP TIMESTAMP with prespecified hop addresses instead of four term one. 174 What flavor works better depends on target host. Particularly, 175 <CODE 176 CLASS="OPTION" 177 >-o</CODE 178 > is better for Linux. 179 </P 180 ></DD 181 ></DL 182 ></DIV 183 ></DIV 184 ><DIV 185 CLASS="REFSECT1" 186 ><A 187 NAME="AEN665" 188 ></A 189 ><H2 190 >WARNINGS</H2 191 ><P 192 ></P 193 ><UL 194 ><LI 195 ><P 196 >Some nodes (Cisco) use non-standard timestamps, which is allowed 197 by RFC, but makes timestamps mostly useless. 198 </P 199 ></LI 200 ><LI 201 ><P 202 >Some nodes generate messed timestamps (Solaris>2.4), when 203 run <B 204 CLASS="COMMAND" 205 >xntpd</B 206 >. Seems, its IP stack uses a corrupted clock source, 207 which is synchronized to time-of-day clock periodically and jumps 208 randomly making timestamps mostly useless. Good news is that you can 209 use NTP in this case, which is even better. 210 </P 211 ></LI 212 ><LI 213 ><P 214 ><B 215 CLASS="COMMAND" 216 >clockdiff</B 217 > shows difference in time modulo 24 days. 218 </P 219 ></LI 220 ></UL 221 ></DIV 222 ><DIV 223 CLASS="REFSECT1" 224 ><A 225 NAME="AEN676" 226 ></A 227 ><H2 228 >SEE ALSO</H2 229 ><P 230 ><A 231 HREF="r3.html" 232 ><SPAN 233 CLASS="CITEREFENTRY" 234 ><SPAN 235 CLASS="REFENTRYTITLE" 236 >ping</SPAN 237 >(8)</SPAN 238 ></A 239 >, 240 <A 241 HREF="r466.html" 242 ><SPAN 243 CLASS="CITEREFENTRY" 244 ><SPAN 245 CLASS="REFENTRYTITLE" 246 >arping</SPAN 247 >(8)</SPAN 248 ></A 249 >, 250 <A 251 HREF="r819.html" 252 ><SPAN 253 CLASS="CITEREFENTRY" 254 ><SPAN 255 CLASS="REFENTRYTITLE" 256 >tracepath</SPAN 257 >(8)</SPAN 258 ></A 259 >.</P 260 ></DIV 261 ><DIV 262 CLASS="REFSECT1" 263 ><A 264 NAME="AEN691" 265 ></A 266 ><H2 267 >REFERENCES</H2 268 ><P 269 >[1] <A 270 NAME="CLOCKDIFF.ICMP-ECHO" 271 ></A 272 >ICMP ECHO, 273 <A 274 HREF="http://tools.ietf.org/rfc/rfc792.txt" 275 TARGET="_top" 276 >RFC0792, page 14</A 277 >.</P 278 ><P 279 >[2] <A 280 NAME="CLOCKDIFF.ICMP-TIMESTAMP" 281 ></A 282 >ICMP TIMESTAMP, 283 <A 284 HREF="http://tools.ietf.org/rfc/rfc792.txt" 285 TARGET="_top" 286 >RFC0792, page 16</A 287 >.</P 288 ><P 289 >[3] <A 290 NAME="CLOCKDIFF.IP-TIMESTAMP" 291 ></A 292 >IP TIMESTAMP option, 293 <A 294 HREF="http://tools.ietf.org/rfc/rfc791.txt" 295 TARGET="_top" 296 >RFC0791, 3.1, page 16</A 297 >.</P 298 ></DIV 299 ><DIV 300 CLASS="REFSECT1" 301 ><A 302 NAME="AEN702" 303 ></A 304 ><H2 305 >AUTHOR</H2 306 ><P 307 ><B 308 CLASS="COMMAND" 309 >clockdiff</B 310 > was compiled by 311 <A 312 HREF="mailto:kuznet@ms2.inr.ac.ru" 313 TARGET="_top" 314 >Alexey Kuznetsov 315 <kuznet@ms2.inr.ac.ru></A 316 >. It was based on code borrowed 317 from BSD <B 318 CLASS="COMMAND" 319 >timed</B 320 > daemon. 321 It is now maintained by 322 <A 323 HREF="mailto:yoshfuji@skbuff.net" 324 TARGET="_top" 325 >YOSHIFUJI Hideaki 326 <yoshfuji@skbuff.net></A 327 >.</P 328 ></DIV 329 ><DIV 330 CLASS="REFSECT1" 331 ><A 332 NAME="AEN709" 333 ></A 334 ><H2 335 >SECURITY</H2 336 ><P 337 ><B 338 CLASS="COMMAND" 339 >clockdiff</B 340 > requires <CODE 341 CLASS="CONSTANT" 342 >CAP_NET_RAW</CODE 343 > capability 344 to be executed. It is safe to be used as set-uid root.</P 345 ></DIV 346 ><DIV 347 CLASS="REFSECT1" 348 ><A 349 NAME="AEN714" 350 ></A 351 ><H2 352 >AVAILABILITY</H2 353 ><P 354 ><B 355 CLASS="COMMAND" 356 >clockdiff</B 357 > is part of <TT 358 CLASS="FILENAME" 359 >iputils</TT 360 > package 361 and the latest versions are available in source form at 362 <A 363 HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2" 364 TARGET="_top" 365 >http://www.skbuff.net/iputils/iputils-current.tar.bz2</A 366 >.</P 367 ></DIV 368 ><DIV 369 CLASS="NAVFOOTER" 370 ><HR 371 ALIGN="LEFT" 372 WIDTH="100%"><TABLE 373 SUMMARY="Footer navigation table" 374 WIDTH="100%" 375 BORDER="0" 376 CELLPADDING="0" 377 CELLSPACING="0" 378 ><TR 379 ><TD 380 WIDTH="33%" 381 ALIGN="left" 382 VALIGN="top" 383 ><A 384 HREF="r466.html" 385 ACCESSKEY="P" 386 >Prev</A 387 ></TD 388 ><TD 389 WIDTH="34%" 390 ALIGN="center" 391 VALIGN="top" 392 ><A 393 HREF="index.html" 394 ACCESSKEY="H" 395 >Home</A 396 ></TD 397 ><TD 398 WIDTH="33%" 399 ALIGN="right" 400 VALIGN="top" 401 ><A 402 HREF="r720.html" 403 ACCESSKEY="N" 404 >Next</A 405 ></TD 406 ></TR 407 ><TR 408 ><TD 409 WIDTH="33%" 410 ALIGN="left" 411 VALIGN="top" 412 >arping</TD 413 ><TD 414 WIDTH="34%" 415 ALIGN="center" 416 VALIGN="top" 417 > </TD 418 ><TD 419 WIDTH="33%" 420 ALIGN="right" 421 VALIGN="top" 422 >rarpd</TD 423 ></TR 424 ></TABLE 425 ></DIV 426 ></BODY 427 ></HTML 428 > 429 No newline at end of file -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/r720.html iputils-s20121221/doc/r720.html
old new 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 2 <HTML 3 ><HEAD 4 ><TITLE 5 >rarpd</TITLE 6 ><META 7 NAME="GENERATOR" 8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK 9 REL="HOME" 10 TITLE="System Manager's Manual: iputils" 11 HREF="index.html"><LINK 12 REL="PREVIOUS" 13 TITLE="clockdiff" 14 HREF="r625.html"><LINK 15 REL="NEXT" 16 TITLE="tracepath" 17 HREF="r819.html"></HEAD 18 ><BODY 19 CLASS="REFENTRY" 20 BGCOLOR="#FFFFFF" 21 TEXT="#000000" 22 LINK="#0000FF" 23 VLINK="#840084" 24 ALINK="#0000FF" 25 ><DIV 26 CLASS="NAVHEADER" 27 ><TABLE 28 SUMMARY="Header navigation table" 29 WIDTH="100%" 30 BORDER="0" 31 CELLPADDING="0" 32 CELLSPACING="0" 33 ><TR 34 ><TH 35 COLSPAN="3" 36 ALIGN="center" 37 >System Manager's Manual: iputils</TH 38 ></TR 39 ><TR 40 ><TD 41 WIDTH="10%" 42 ALIGN="left" 43 VALIGN="bottom" 44 ><A 45 HREF="r625.html" 46 ACCESSKEY="P" 47 >Prev</A 48 ></TD 49 ><TD 50 WIDTH="80%" 51 ALIGN="center" 52 VALIGN="bottom" 53 ></TD 54 ><TD 55 WIDTH="10%" 56 ALIGN="right" 57 VALIGN="bottom" 58 ><A 59 HREF="r819.html" 60 ACCESSKEY="N" 61 >Next</A 62 ></TD 63 ></TR 64 ></TABLE 65 ><HR 66 ALIGN="LEFT" 67 WIDTH="100%"></DIV 68 ><H1 69 ><A 70 NAME="RARPD" 71 ></A 72 >rarpd</H1 73 ><DIV 74 CLASS="REFNAMEDIV" 75 ><A 76 NAME="AEN725" 77 ></A 78 ><H2 79 >Name</H2 80 >rarpd -- answer RARP REQUESTs</DIV 81 ><DIV 82 CLASS="REFSYNOPSISDIV" 83 ><A 84 NAME="AEN728" 85 ></A 86 ><H2 87 >Synopsis</H2 88 ><P 89 ><B 90 CLASS="COMMAND" 91 >arping</B 92 > [<CODE 93 CLASS="OPTION" 94 >-aAvde</CODE 95 >] [-b <TT 96 CLASS="REPLACEABLE" 97 ><I 98 >bootdir</I 99 ></TT 100 >] [<TT 101 CLASS="REPLACEABLE" 102 ><I 103 >interface</I 104 ></TT 105 >]</P 106 ></DIV 107 ><DIV 108 CLASS="REFSECT1" 109 ><A 110 NAME="AEN737" 111 ></A 112 ><H2 113 >DESCRIPTION</H2 114 ><P 115 >Listens 116 <A 117 HREF="http://tools.ietf.org/rfc/rfc903.txt" 118 TARGET="_top" 119 >RARP</A 120 > 121 requests from clients. Provided MAC address of client 122 is found in <TT 123 CLASS="FILENAME" 124 >/etc/ethers</TT 125 > database and 126 obtained host name is resolvable to an IP address appropriate 127 for attached network, <B 128 CLASS="COMMAND" 129 >rarpd</B 130 > answers to client with RARPD 131 reply carrying an IP address.</P 132 ><P 133 >To allow multiple boot servers on the network <B 134 CLASS="COMMAND" 135 >rarpd</B 136 > 137 optionally checks for presence Sun-like bootable image in TFTP directory. 138 It should have form <KBD 139 CLASS="USERINPUT" 140 >Hexadecimal_IP.ARCH</KBD 141 >, f.e. to load 142 sparc 193.233.7.98 <TT 143 CLASS="FILENAME" 144 >C1E90762.SUN4M</TT 145 > is linked to 146 an image appropriate for SUM4M in directory <TT 147 CLASS="FILENAME" 148 >/etc/tftpboot</TT 149 >.</P 150 ></DIV 151 ><DIV 152 CLASS="REFSECT1" 153 ><A 154 NAME="AEN748" 155 ></A 156 ><H2 157 >WARNING</H2 158 ><P 159 >This facility is deeply obsoleted by 160 <A 161 HREF="http://tools.ietf.org/rfc/rfc951.txt" 162 TARGET="_top" 163 >BOOTP</A 164 > 165 and later 166 <A 167 HREF="http://tools.ietf.org/rfc/rfc2131.txt" 168 TARGET="_top" 169 >DHCP</A 170 > protocols. 171 However, some clients really still need this to boot.</P 172 ></DIV 173 ><DIV 174 CLASS="REFSECT1" 175 ><A 176 NAME="AEN753" 177 ></A 178 ><H2 179 >OPTIONS</H2 180 ><P 181 ></P 182 ><DIV 183 CLASS="VARIABLELIST" 184 ><DL 185 ><DT 186 ><CODE 187 CLASS="OPTION" 188 >-a</CODE 189 ></DT 190 ><DD 191 ><P 192 >Listen on all the interfaces. Currently it is an internal 193 option, its function is overridden with <TT 194 CLASS="REPLACEABLE" 195 ><I 196 >interface</I 197 ></TT 198 > 199 argument. It should not be used. 200 </P 201 ></DD 202 ><DT 203 ><CODE 204 CLASS="OPTION" 205 >-A</CODE 206 ></DT 207 ><DD 208 ><P 209 >Listen not only RARP but also ARP messages, some rare clients 210 use ARP by some unknown reason. 211 </P 212 ></DD 213 ><DT 214 ><CODE 215 CLASS="OPTION" 216 >-v</CODE 217 ></DT 218 ><DD 219 ><P 220 >Be verbose. 221 </P 222 ></DD 223 ><DT 224 ><CODE 225 CLASS="OPTION" 226 >-d</CODE 227 ></DT 228 ><DD 229 ><P 230 >Debug mode. Do not go to background. 231 </P 232 ></DD 233 ><DT 234 ><CODE 235 CLASS="OPTION" 236 >-e</CODE 237 ></DT 238 ><DD 239 ><P 240 >Do not check for presence of a boot image, reply if MAC address 241 resolves to a valid IP address using <TT 242 CLASS="FILENAME" 243 >/etc/ethers</TT 244 > 245 database and DNS. 246 </P 247 ></DD 248 ><DT 249 ><CODE 250 CLASS="OPTION" 251 >-b <TT 252 CLASS="REPLACEABLE" 253 ><I 254 >bootdir</I 255 ></TT 256 ></CODE 257 ></DT 258 ><DD 259 ><P 260 >TFTP boot directory. Default is <TT 261 CLASS="FILENAME" 262 >/etc/tftpboot</TT 263 > 264 </P 265 ></DD 266 ></DL 267 ></DIV 268 ></DIV 269 ><DIV 270 CLASS="REFSECT1" 271 ><A 272 NAME="AEN790" 273 ></A 274 ><H2 275 >SEE ALSO</H2 276 ><P 277 ><A 278 HREF="r466.html" 279 ><SPAN 280 CLASS="CITEREFENTRY" 281 ><SPAN 282 CLASS="REFENTRYTITLE" 283 >arping</SPAN 284 >(8)</SPAN 285 ></A 286 >, 287 <A 288 HREF="r983.html" 289 ><SPAN 290 CLASS="CITEREFENTRY" 291 ><SPAN 292 CLASS="REFENTRYTITLE" 293 >tftpd</SPAN 294 >(8)</SPAN 295 ></A 296 >.</P 297 ></DIV 298 ><DIV 299 CLASS="REFSECT1" 300 ><A 301 NAME="AEN801" 302 ></A 303 ><H2 304 >AUTHOR</H2 305 ><P 306 ><B 307 CLASS="COMMAND" 308 >rarpd</B 309 > was written by 310 <A 311 HREF="mailto:kuznet@ms2.inr.ac.ru" 312 TARGET="_top" 313 >Alexey Kuznetsov 314 <kuznet@ms2.inr.ac.ru></A 315 >. 316 It is now maintained by 317 <A 318 HREF="mailto:yoshfuji@skbuff.net" 319 TARGET="_top" 320 >YOSHIFUJI Hideaki 321 <yoshfuji@skbuff.net></A 322 >.</P 323 ></DIV 324 ><DIV 325 CLASS="REFSECT1" 326 ><A 327 NAME="AEN807" 328 ></A 329 ><H2 330 >SECURITY</H2 331 ><P 332 ><B 333 CLASS="COMMAND" 334 >rarpd</B 335 > requires <CODE 336 CLASS="CONSTANT" 337 >CAP_NET_RAW</CODE 338 > capability 339 to listen and send RARP and ARP packets. It also needs <CODE 340 CLASS="CONSTANT" 341 >CAP_NET_ADMIN</CODE 342 > 343 to give to kernel hint for ARP resolution; this is not strictly required, 344 but some (most of, to be more exact) clients are so badly broken that 345 are not able to answer ARP before they are finally booted. This is 346 not wonderful taking into account that clients using RARPD in 2002 347 are all unsupported relic creatures of 90's and even earlier.</P 348 ></DIV 349 ><DIV 350 CLASS="REFSECT1" 351 ><A 352 NAME="AEN813" 353 ></A 354 ><H2 355 >AVAILABILITY</H2 356 ><P 357 ><B 358 CLASS="COMMAND" 359 >rarpd</B 360 > is part of <TT 361 CLASS="FILENAME" 362 >iputils</TT 363 > package 364 and the latest versions are available in source form at 365 <A 366 HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2" 367 TARGET="_top" 368 >http://www.skbuff.net/iputils/iputils-current.tar.bz2</A 369 >.</P 370 ></DIV 371 ><DIV 372 CLASS="NAVFOOTER" 373 ><HR 374 ALIGN="LEFT" 375 WIDTH="100%"><TABLE 376 SUMMARY="Footer navigation table" 377 WIDTH="100%" 378 BORDER="0" 379 CELLPADDING="0" 380 CELLSPACING="0" 381 ><TR 382 ><TD 383 WIDTH="33%" 384 ALIGN="left" 385 VALIGN="top" 386 ><A 387 HREF="r625.html" 388 ACCESSKEY="P" 389 >Prev</A 390 ></TD 391 ><TD 392 WIDTH="34%" 393 ALIGN="center" 394 VALIGN="top" 395 ><A 396 HREF="index.html" 397 ACCESSKEY="H" 398 >Home</A 399 ></TD 400 ><TD 401 WIDTH="33%" 402 ALIGN="right" 403 VALIGN="top" 404 ><A 405 HREF="r819.html" 406 ACCESSKEY="N" 407 >Next</A 408 ></TD 409 ></TR 410 ><TR 411 ><TD 412 WIDTH="33%" 413 ALIGN="left" 414 VALIGN="top" 415 >clockdiff</TD 416 ><TD 417 WIDTH="34%" 418 ALIGN="center" 419 VALIGN="top" 420 > </TD 421 ><TD 422 WIDTH="33%" 423 ALIGN="right" 424 VALIGN="top" 425 >tracepath</TD 426 ></TR 427 ></TABLE 428 ></DIV 429 ></BODY 430 ></HTML 431 > 432 No newline at end of file -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/r819.html iputils-s20121221/doc/r819.html
old new 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 2 <HTML 3 ><HEAD 4 ><TITLE 5 >tracepath</TITLE 6 ><META 7 NAME="GENERATOR" 8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK 9 REL="HOME" 10 TITLE="System Manager's Manual: iputils" 11 HREF="index.html"><LINK 12 REL="PREVIOUS" 13 TITLE="rarpd" 14 HREF="r720.html"><LINK 15 REL="NEXT" 16 TITLE="traceroute6" 17 HREF="r918.html"></HEAD 18 ><BODY 19 CLASS="REFENTRY" 20 BGCOLOR="#FFFFFF" 21 TEXT="#000000" 22 LINK="#0000FF" 23 VLINK="#840084" 24 ALINK="#0000FF" 25 ><DIV 26 CLASS="NAVHEADER" 27 ><TABLE 28 SUMMARY="Header navigation table" 29 WIDTH="100%" 30 BORDER="0" 31 CELLPADDING="0" 32 CELLSPACING="0" 33 ><TR 34 ><TH 35 COLSPAN="3" 36 ALIGN="center" 37 >System Manager's Manual: iputils</TH 38 ></TR 39 ><TR 40 ><TD 41 WIDTH="10%" 42 ALIGN="left" 43 VALIGN="bottom" 44 ><A 45 HREF="r720.html" 46 ACCESSKEY="P" 47 >Prev</A 48 ></TD 49 ><TD 50 WIDTH="80%" 51 ALIGN="center" 52 VALIGN="bottom" 53 ></TD 54 ><TD 55 WIDTH="10%" 56 ALIGN="right" 57 VALIGN="bottom" 58 ><A 59 HREF="r918.html" 60 ACCESSKEY="N" 61 >Next</A 62 ></TD 63 ></TR 64 ></TABLE 65 ><HR 66 ALIGN="LEFT" 67 WIDTH="100%"></DIV 68 ><H1 69 ><A 70 NAME="TRACEPATH" 71 ></A 72 >tracepath</H1 73 ><DIV 74 CLASS="REFNAMEDIV" 75 ><A 76 NAME="AEN824" 77 ></A 78 ><H2 79 >Name</H2 80 >tracepath, tracepath6 -- traces path to a network host discovering MTU along this path</DIV 81 ><DIV 82 CLASS="REFSYNOPSISDIV" 83 ><A 84 NAME="AEN827" 85 ></A 86 ><H2 87 >Synopsis</H2 88 ><P 89 ><B 90 CLASS="COMMAND" 91 >tracepath</B 92 > [-n] [-b] [-l <TT 93 CLASS="REPLACEABLE" 94 ><I 95 >pktlen</I 96 ></TT 97 >] [-p <TT 98 CLASS="REPLACEABLE" 99 ><I 100 >port</I 101 ></TT 102 >] {<TT 103 CLASS="REPLACEABLE" 104 ><I 105 >destination</I 106 ></TT 107 >}</P 108 ></DIV 109 ><DIV 110 CLASS="REFSECT1" 111 ><A 112 NAME="AEN838" 113 ></A 114 ><H2 115 >DESCRIPTION</H2 116 ><P 117 >It traces path to <TT 118 CLASS="REPLACEABLE" 119 ><I 120 >destination</I 121 ></TT 122 > discovering MTU along this path. 123 It uses UDP port <TT 124 CLASS="REPLACEABLE" 125 ><I 126 >port</I 127 ></TT 128 > or some random port. 129 It is similar to <B 130 CLASS="COMMAND" 131 >traceroute</B 132 >, only does not require superuser 133 privileges and has no fancy options.</P 134 ><P 135 ><B 136 CLASS="COMMAND" 137 >tracepath6</B 138 > is good replacement for <B 139 CLASS="COMMAND" 140 >traceroute6</B 141 > 142 and classic example of application of Linux error queues. 143 The situation with IPv4 is worse, because commercial 144 IP routers do not return enough information in ICMP error messages. 145 Probably, it will change, when they will be updated. 146 For now it uses Van Jacobson's trick, sweeping a range 147 of UDP ports to maintain trace history.</P 148 ></DIV 149 ><DIV 150 CLASS="REFSECT1" 151 ><A 152 NAME="AEN847" 153 ></A 154 ><H2 155 >OPTIONS</H2 156 ><P 157 ></P 158 ><DIV 159 CLASS="VARIABLELIST" 160 ><DL 161 ><DT 162 ><CODE 163 CLASS="OPTION" 164 >-n</CODE 165 ></DT 166 ><DD 167 ><P 168 >Print primarily IP addresses numerically. 169 </P 170 ></DD 171 ><DT 172 ><CODE 173 CLASS="OPTION" 174 >-b</CODE 175 ></DT 176 ><DD 177 ><P 178 >Print both of host names and IP addresses. 179 </P 180 ></DD 181 ><DT 182 ><CODE 183 CLASS="OPTION" 184 >-l</CODE 185 ></DT 186 ><DD 187 ><P 188 >Sets the initial packet length to <TT 189 CLASS="REPLACEABLE" 190 ><I 191 >pktlen</I 192 ></TT 193 > instead of 194 65535 for <B 195 CLASS="COMMAND" 196 >tracepath</B 197 > or 128000 for <B 198 CLASS="COMMAND" 199 >tracepath6</B 200 >. 201 </P 202 ></DD 203 ><DT 204 ><CODE 205 CLASS="OPTION" 206 >-p</CODE 207 ></DT 208 ><DD 209 ><P 210 >Sets the initial destination port to use. 211 </P 212 ></DD 213 ></DL 214 ></DIV 215 ></DIV 216 ><DIV 217 CLASS="REFSECT1" 218 ><A 219 NAME="AEN873" 220 ></A 221 ><H2 222 >OUTPUT</H2 223 ><P 224 ><P 225 CLASS="LITERALLAYOUT" 226 >root@mops:~ # tracepath6 3ffe:2400:0:109::2<br> 227 1?: [LOCALHOST] pmtu 1500<br> 228 1: dust.inr.ac.ru 0.411ms<br> 229 2: dust.inr.ac.ru asymm 1 0.390ms pmtu 1480<br> 230 2: 3ffe:2400:0:109::2 463.514ms reached<br> 231 Resume: pmtu 1480 hops 2 back 2</P 232 ></P 233 ><P 234 >The first column shows <TT 235 CLASS="LITERAL" 236 >TTL</TT 237 > of the probe, followed by colon. 238 Usually value of <TT 239 CLASS="LITERAL" 240 >TTL</TT 241 > is obtained from reply from network, 242 but sometimes reply does not contain necessary information and 243 we have to guess it. In this case the number is followed by ?.</P 244 ><P 245 >The second column shows the network hop, which replied to the probe. 246 It is either address of router or word <TT 247 CLASS="LITERAL" 248 >[LOCALHOST]</TT 249 >, if 250 the probe was not sent to the network.</P 251 ><P 252 >The rest of line shows miscellaneous information about path to 253 the correspinding network hop. As rule it contains value of RTT. 254 Additionally, it can show Path MTU, when it changes. 255 If the path is asymmetric 256 or the probe finishes before it reach prescribed hop, difference 257 between number of hops in forward and backward direction is shown 258 following keyword <TT 259 CLASS="LITERAL" 260 >async</TT 261 >. This information is not reliable. 262 F.e. the third line shows asymmetry of 1, it is because the first probe 263 with TTL of 2 was rejected at the first hop due to Path MTU Discovery.</P 264 ><P 265 >The last line summarizes information about all the path to the destination, 266 it shows detected Path MTU, amount of hops to the destination and our 267 guess about amount of hops from the destination to us, which can be 268 different when the path is asymmetric.</P 269 ></DIV 270 ><DIV 271 CLASS="REFSECT1" 272 ><A 273 NAME="AEN885" 274 ></A 275 ><H2 276 >SEE ALSO</H2 277 ><P 278 ><SPAN 279 CLASS="CITEREFENTRY" 280 ><SPAN 281 CLASS="REFENTRYTITLE" 282 >traceroute</SPAN 283 >(8)</SPAN 284 >, 285 <A 286 HREF="r918.html" 287 ><SPAN 288 CLASS="CITEREFENTRY" 289 ><SPAN 290 CLASS="REFENTRYTITLE" 291 >traceroute6</SPAN 292 >(8)</SPAN 293 ></A 294 >, 295 <A 296 HREF="r3.html" 297 ><SPAN 298 CLASS="CITEREFENTRY" 299 ><SPAN 300 CLASS="REFENTRYTITLE" 301 >ping</SPAN 302 >(8)</SPAN 303 ></A 304 >.</P 305 ></DIV 306 ><DIV 307 CLASS="REFSECT1" 308 ><A 309 NAME="AEN899" 310 ></A 311 ><H2 312 >AUTHOR</H2 313 ><P 314 ><B 315 CLASS="COMMAND" 316 >tracepath</B 317 > was written by 318 <A 319 HREF="mailto:kuznet@ms2.inr.ac.ru" 320 TARGET="_top" 321 >Alexey Kuznetsov 322 <kuznet@ms2.inr.ac.ru></A 323 >.</P 324 ></DIV 325 ><DIV 326 CLASS="REFSECT1" 327 ><A 328 NAME="AEN904" 329 ></A 330 ><H2 331 >SECURITY</H2 332 ><P 333 >No security issues.</P 334 ><P 335 >This lapidary deserves to be elaborated. 336 <B 337 CLASS="COMMAND" 338 >tracepath</B 339 > is not a privileged program, unlike 340 <B 341 CLASS="COMMAND" 342 >traceroute</B 343 >, <B 344 CLASS="COMMAND" 345 >ping</B 346 > and other beasts of this kind. 347 <B 348 CLASS="COMMAND" 349 >tracepath</B 350 > may be executed by everyone who has some access 351 to network, enough to send UDP datagrams to investigated destination 352 using given port.</P 353 ></DIV 354 ><DIV 355 CLASS="REFSECT1" 356 ><A 357 NAME="AEN912" 358 ></A 359 ><H2 360 >AVAILABILITY</H2 361 ><P 362 ><B 363 CLASS="COMMAND" 364 >tracepath</B 365 > is part of <TT 366 CLASS="FILENAME" 367 >iputils</TT 368 > package 369 and the latest versions are available in source form at 370 <A 371 HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2" 372 TARGET="_top" 373 >http://www.skbuff.net/iputils/iputils-current.tar.bz2</A 374 >.</P 375 ></DIV 376 ><DIV 377 CLASS="NAVFOOTER" 378 ><HR 379 ALIGN="LEFT" 380 WIDTH="100%"><TABLE 381 SUMMARY="Footer navigation table" 382 WIDTH="100%" 383 BORDER="0" 384 CELLPADDING="0" 385 CELLSPACING="0" 386 ><TR 387 ><TD 388 WIDTH="33%" 389 ALIGN="left" 390 VALIGN="top" 391 ><A 392 HREF="r720.html" 393 ACCESSKEY="P" 394 >Prev</A 395 ></TD 396 ><TD 397 WIDTH="34%" 398 ALIGN="center" 399 VALIGN="top" 400 ><A 401 HREF="index.html" 402 ACCESSKEY="H" 403 >Home</A 404 ></TD 405 ><TD 406 WIDTH="33%" 407 ALIGN="right" 408 VALIGN="top" 409 ><A 410 HREF="r918.html" 411 ACCESSKEY="N" 412 >Next</A 413 ></TD 414 ></TR 415 ><TR 416 ><TD 417 WIDTH="33%" 418 ALIGN="left" 419 VALIGN="top" 420 >rarpd</TD 421 ><TD 422 WIDTH="34%" 423 ALIGN="center" 424 VALIGN="top" 425 > </TD 426 ><TD 427 WIDTH="33%" 428 ALIGN="right" 429 VALIGN="top" 430 >traceroute6</TD 431 ></TR 432 ></TABLE 433 ></DIV 434 ></BODY 435 ></HTML 436 > 437 No newline at end of file -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/r918.html iputils-s20121221/doc/r918.html
old new 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 2 <HTML 3 ><HEAD 4 ><TITLE 5 >traceroute6</TITLE 6 ><META 7 NAME="GENERATOR" 8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK 9 REL="HOME" 10 TITLE="System Manager's Manual: iputils" 11 HREF="index.html"><LINK 12 REL="PREVIOUS" 13 TITLE="tracepath" 14 HREF="r819.html"><LINK 15 REL="NEXT" 16 TITLE="tftpd" 17 HREF="r983.html"></HEAD 18 ><BODY 19 CLASS="REFENTRY" 20 BGCOLOR="#FFFFFF" 21 TEXT="#000000" 22 LINK="#0000FF" 23 VLINK="#840084" 24 ALINK="#0000FF" 25 ><DIV 26 CLASS="NAVHEADER" 27 ><TABLE 28 SUMMARY="Header navigation table" 29 WIDTH="100%" 30 BORDER="0" 31 CELLPADDING="0" 32 CELLSPACING="0" 33 ><TR 34 ><TH 35 COLSPAN="3" 36 ALIGN="center" 37 >System Manager's Manual: iputils</TH 38 ></TR 39 ><TR 40 ><TD 41 WIDTH="10%" 42 ALIGN="left" 43 VALIGN="bottom" 44 ><A 45 HREF="r819.html" 46 ACCESSKEY="P" 47 >Prev</A 48 ></TD 49 ><TD 50 WIDTH="80%" 51 ALIGN="center" 52 VALIGN="bottom" 53 ></TD 54 ><TD 55 WIDTH="10%" 56 ALIGN="right" 57 VALIGN="bottom" 58 ><A 59 HREF="r983.html" 60 ACCESSKEY="N" 61 >Next</A 62 ></TD 63 ></TR 64 ></TABLE 65 ><HR 66 ALIGN="LEFT" 67 WIDTH="100%"></DIV 68 ><H1 69 ><A 70 NAME="TRACEROUTE6" 71 ></A 72 >traceroute6</H1 73 ><DIV 74 CLASS="REFNAMEDIV" 75 ><A 76 NAME="AEN923" 77 ></A 78 ><H2 79 >Name</H2 80 >traceroute6 -- traces path to a network host</DIV 81 ><DIV 82 CLASS="REFSYNOPSISDIV" 83 ><A 84 NAME="AEN926" 85 ></A 86 ><H2 87 >Synopsis</H2 88 ><P 89 ><B 90 CLASS="COMMAND" 91 >traceroute6</B 92 > [<CODE 93 CLASS="OPTION" 94 >-dnrvV</CODE 95 >] [-i <TT 96 CLASS="REPLACEABLE" 97 ><I 98 >interface</I 99 ></TT 100 >] [-m <TT 101 CLASS="REPLACEABLE" 102 ><I 103 >max_ttl</I 104 ></TT 105 >] [-p <TT 106 CLASS="REPLACEABLE" 107 ><I 108 >port</I 109 ></TT 110 >] [-q <TT 111 CLASS="REPLACEABLE" 112 ><I 113 >max_probes</I 114 ></TT 115 >] [-s <TT 116 CLASS="REPLACEABLE" 117 ><I 118 >source</I 119 ></TT 120 >] [-w <TT 121 CLASS="REPLACEABLE" 122 ><I 123 >wait time</I 124 ></TT 125 >] {<TT 126 CLASS="REPLACEABLE" 127 ><I 128 >destination</I 129 ></TT 130 >} [<TT 131 CLASS="REPLACEABLE" 132 ><I 133 >size</I 134 ></TT 135 >]</P 136 ></DIV 137 ><DIV 138 CLASS="REFSECT1" 139 ><A 140 NAME="AEN947" 141 ></A 142 ><H2 143 >DESCRIPTION</H2 144 ><P 145 >Description can be found in 146 <SPAN 147 CLASS="CITEREFENTRY" 148 ><SPAN 149 CLASS="REFENTRYTITLE" 150 >traceroute</SPAN 151 >(8)</SPAN 152 >, 153 all the references to IP replaced to IPv6. It is needless to copy 154 the description from there.</P 155 ></DIV 156 ><DIV 157 CLASS="REFSECT1" 158 ><A 159 NAME="AEN953" 160 ></A 161 ><H2 162 >SEE ALSO</H2 163 ><P 164 ><SPAN 165 CLASS="CITEREFENTRY" 166 ><SPAN 167 CLASS="REFENTRYTITLE" 168 >traceroute</SPAN 169 >(8)</SPAN 170 >, 171 <SPAN 172 CLASS="CITEREFENTRY" 173 ><SPAN 174 CLASS="REFENTRYTITLE" 175 >tracepath</SPAN 176 >(8)</SPAN 177 >, 178 <SPAN 179 CLASS="CITEREFENTRY" 180 ><SPAN 181 CLASS="REFENTRYTITLE" 182 >ping</SPAN 183 >(8)</SPAN 184 >.</P 185 ></DIV 186 ><DIV 187 CLASS="REFSECT1" 188 ><A 189 NAME="AEN965" 190 ></A 191 ><H2 192 >HISTORY</H2 193 ><P 194 >This program has long history. Author of <B 195 CLASS="COMMAND" 196 >traceroute</B 197 > 198 is Van Jacobson and it first appeared in 1988. This clone is 199 based on a port of <B 200 CLASS="COMMAND" 201 >traceroute</B 202 > to IPv6 published 203 in NRL IPv6 distribution in 1996. In turn, it was ported 204 to Linux by Pedro Roque. After this it was kept in sync by 205 <A 206 HREF="mailto:kuznet@ms2.inr.ac.ru" 207 TARGET="_top" 208 >Alexey Kuznetsov 209 <kuznet@ms2.inr.ac.ru></A 210 >. And eventually entered 211 <B 212 CLASS="COMMAND" 213 >iputils</B 214 > package.</P 215 ></DIV 216 ><DIV 217 CLASS="REFSECT1" 218 ><A 219 NAME="AEN972" 220 ></A 221 ><H2 222 >SECURITY</H2 223 ><P 224 ><B 225 CLASS="COMMAND" 226 >tracepath6</B 227 > requires <CODE 228 CLASS="CONSTANT" 229 >CAP_NET_RAW</CODE 230 > capability 231 to be executed. It is safe to be used as set-uid root.</P 232 ></DIV 233 ><DIV 234 CLASS="REFSECT1" 235 ><A 236 NAME="AEN977" 237 ></A 238 ><H2 239 >AVAILABILITY</H2 240 ><P 241 ><B 242 CLASS="COMMAND" 243 >traceroute6</B 244 > is part of <TT 245 CLASS="FILENAME" 246 >iputils</TT 247 > package 248 and the latest versions are available in source form at 249 <A 250 HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2" 251 TARGET="_top" 252 >http://www.skbuff.net/iputils/iputils-current.tar.bz2</A 253 >.</P 254 ></DIV 255 ><DIV 256 CLASS="NAVFOOTER" 257 ><HR 258 ALIGN="LEFT" 259 WIDTH="100%"><TABLE 260 SUMMARY="Footer navigation table" 261 WIDTH="100%" 262 BORDER="0" 263 CELLPADDING="0" 264 CELLSPACING="0" 265 ><TR 266 ><TD 267 WIDTH="33%" 268 ALIGN="left" 269 VALIGN="top" 270 ><A 271 HREF="r819.html" 272 ACCESSKEY="P" 273 >Prev</A 274 ></TD 275 ><TD 276 WIDTH="34%" 277 ALIGN="center" 278 VALIGN="top" 279 ><A 280 HREF="index.html" 281 ACCESSKEY="H" 282 >Home</A 283 ></TD 284 ><TD 285 WIDTH="33%" 286 ALIGN="right" 287 VALIGN="top" 288 ><A 289 HREF="r983.html" 290 ACCESSKEY="N" 291 >Next</A 292 ></TD 293 ></TR 294 ><TR 295 ><TD 296 WIDTH="33%" 297 ALIGN="left" 298 VALIGN="top" 299 >tracepath</TD 300 ><TD 301 WIDTH="34%" 302 ALIGN="center" 303 VALIGN="top" 304 > </TD 305 ><TD 306 WIDTH="33%" 307 ALIGN="right" 308 VALIGN="top" 309 >tftpd</TD 310 ></TR 311 ></TABLE 312 ></DIV 313 ></BODY 314 ></HTML 315 > 316 No newline at end of file -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/r983.html iputils-s20121221/doc/r983.html
old new 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 2 <HTML 3 ><HEAD 4 ><TITLE 5 >tftpd</TITLE 6 ><META 7 NAME="GENERATOR" 8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK 9 REL="HOME" 10 TITLE="System Manager's Manual: iputils" 11 HREF="index.html"><LINK 12 REL="PREVIOUS" 13 TITLE="traceroute6" 14 HREF="r918.html"><LINK 15 REL="NEXT" 16 TITLE="ninfod" 17 HREF="r1056.html"></HEAD 18 ><BODY 19 CLASS="REFENTRY" 20 BGCOLOR="#FFFFFF" 21 TEXT="#000000" 22 LINK="#0000FF" 23 VLINK="#840084" 24 ALINK="#0000FF" 25 ><DIV 26 CLASS="NAVHEADER" 27 ><TABLE 28 SUMMARY="Header navigation table" 29 WIDTH="100%" 30 BORDER="0" 31 CELLPADDING="0" 32 CELLSPACING="0" 33 ><TR 34 ><TH 35 COLSPAN="3" 36 ALIGN="center" 37 >System Manager's Manual: iputils</TH 38 ></TR 39 ><TR 40 ><TD 41 WIDTH="10%" 42 ALIGN="left" 43 VALIGN="bottom" 44 ><A 45 HREF="r918.html" 46 ACCESSKEY="P" 47 >Prev</A 48 ></TD 49 ><TD 50 WIDTH="80%" 51 ALIGN="center" 52 VALIGN="bottom" 53 ></TD 54 ><TD 55 WIDTH="10%" 56 ALIGN="right" 57 VALIGN="bottom" 58 ><A 59 HREF="r1056.html" 60 ACCESSKEY="N" 61 >Next</A 62 ></TD 63 ></TR 64 ></TABLE 65 ><HR 66 ALIGN="LEFT" 67 WIDTH="100%"></DIV 68 ><H1 69 ><A 70 NAME="TFTPD" 71 ></A 72 >tftpd</H1 73 ><DIV 74 CLASS="REFNAMEDIV" 75 ><A 76 NAME="AEN988" 77 ></A 78 ><H2 79 >Name</H2 80 >tftpd -- Trivial File Transfer Protocol server</DIV 81 ><DIV 82 CLASS="REFSYNOPSISDIV" 83 ><A 84 NAME="AEN991" 85 ></A 86 ><H2 87 >Synopsis</H2 88 ><P 89 ><B 90 CLASS="COMMAND" 91 >tftpd</B 92 > {<TT 93 CLASS="REPLACEABLE" 94 ><I 95 >directory</I 96 ></TT 97 >}</P 98 ></DIV 99 ><DIV 100 CLASS="REFSECT1" 101 ><A 102 NAME="AEN996" 103 ></A 104 ><H2 105 >DESCRIPTION</H2 106 ><P 107 ><B 108 CLASS="COMMAND" 109 >tftpd</B 110 > is a server which supports the DARPA 111 Trivial File Transfer Protocol 112 (<A 113 HREF="http://tools.ietf.org/rfc/rfc1350.txt" 114 TARGET="_top" 115 >RFC1350</A 116 >). 117 The TFTP server is started 118 by <SPAN 119 CLASS="CITEREFENTRY" 120 ><SPAN 121 CLASS="REFENTRYTITLE" 122 >inetd</SPAN 123 >(8)</SPAN 124 >.</P 125 ><P 126 ><TT 127 CLASS="REPLACEABLE" 128 ><I 129 >directory</I 130 ></TT 131 > is required argument; if it is not given 132 <B 133 CLASS="COMMAND" 134 >tftpd</B 135 > aborts. This path is prepended to any file name requested 136 via TFTP protocol, effectively chrooting <B 137 CLASS="COMMAND" 138 >tftpd</B 139 > to this directory. 140 File names are validated not to escape out of this directory, however 141 administrator may configure such escape using symbolic links.</P 142 ><P 143 >It is in difference of variants of <B 144 CLASS="COMMAND" 145 >tftpd</B 146 > usually distributed 147 with unix-like systems, which take a list of directories and match 148 file names to start from one of given prefixes or to some random 149 default, when no arguments were given. There are two reasons not to 150 behave in this way: first, it is inconvenient, clients are not expected 151 to know something about layout of filesystem on server host. 152 And second, TFTP protocol is not a tool for browsing of server's filesystem, 153 it is just an agent allowing to boot dumb clients. </P 154 ><P 155 >In the case when <B 156 CLASS="COMMAND" 157 >tftpd</B 158 > is used together with 159 <A 160 HREF="r720.html" 161 ><SPAN 162 CLASS="CITEREFENTRY" 163 ><SPAN 164 CLASS="REFENTRYTITLE" 165 >rarpd</SPAN 166 >(8)</SPAN 167 ></A 168 >, 169 tftp directories in these services should coincide and it is expected 170 that each client booted via TFTP has boot image corresponding 171 its IP address with an architecture suffix following Sun Microsystems 172 conventions. See 173 <A 174 HREF="r720.html" 175 ><SPAN 176 CLASS="CITEREFENTRY" 177 ><SPAN 178 CLASS="REFENTRYTITLE" 179 >rarpd</SPAN 180 >(8)</SPAN 181 ></A 182 > 183 for more details.</P 184 ></DIV 185 ><DIV 186 CLASS="REFSECT1" 187 ><A 188 NAME="AEN1020" 189 ></A 190 ><H2 191 >SECURITY</H2 192 ><P 193 >TFTP protocol does not provide any authentication. 194 Due to this capital flaw <B 195 CLASS="COMMAND" 196 >tftpd</B 197 > is not able to restrict 198 access to files and will allow only publically readable 199 files to be accessed. Files may be written only if they already 200 exist and are publically writable.</P 201 ><P 202 >Impact is evident, directory exported via TFTP <SPAN 203 CLASS="emphasis" 204 ><I 205 CLASS="EMPHASIS" 206 >must not</I 207 ></SPAN 208 > 209 contain sensitive information of any kind, everyone is allowed 210 to read it as soon as a client is allowed. Boot images do not contain 211 such information as rule, however you should think twice before 212 publishing f.e. Cisco IOS config files via TFTP, they contain 213 <SPAN 214 CLASS="emphasis" 215 ><I 216 CLASS="EMPHASIS" 217 >unencrypted</I 218 ></SPAN 219 > passwords and may contain some information 220 about the network, which you were not going to make public.</P 221 ><P 222 >The <B 223 CLASS="COMMAND" 224 >tftpd</B 225 > server should be executed by <B 226 CLASS="COMMAND" 227 >inetd</B 228 > 229 with dropped root privileges, namely with a user ID giving minimal 230 access to files published in tftp directory. If it is executed 231 as superuser occasionally, <B 232 CLASS="COMMAND" 233 >tftpd</B 234 > drops its UID and GID 235 to 65534, which is most likely not the thing which you expect. 236 However, this is not very essential; remember, only files accessible 237 for everyone can be read or written via TFTP.</P 238 ></DIV 239 ><DIV 240 CLASS="REFSECT1" 241 ><A 242 NAME="AEN1031" 243 ></A 244 ><H2 245 >SEE ALSO</H2 246 ><P 247 ><A 248 HREF="r720.html" 249 ><SPAN 250 CLASS="CITEREFENTRY" 251 ><SPAN 252 CLASS="REFENTRYTITLE" 253 >rarpd</SPAN 254 >(8)</SPAN 255 ></A 256 >, 257 <SPAN 258 CLASS="CITEREFENTRY" 259 ><SPAN 260 CLASS="REFENTRYTITLE" 261 >tftp</SPAN 262 >(1)</SPAN 263 >, 264 <SPAN 265 CLASS="CITEREFENTRY" 266 ><SPAN 267 CLASS="REFENTRYTITLE" 268 >inetd</SPAN 269 >(8)</SPAN 270 >.</P 271 ></DIV 272 ><DIV 273 CLASS="REFSECT1" 274 ><A 275 NAME="AEN1044" 276 ></A 277 ><H2 278 >HISTORY</H2 279 ><P 280 >The <B 281 CLASS="COMMAND" 282 >tftpd</B 283 > command appeared in 4.2BSD. The source in iputils 284 is cleaned up both syntactically (ANSIized) and semantically (UDP socket IO).</P 285 ><P 286 >It is distributed with iputils mostly as good demo of an interesting feature 287 (<CODE 288 CLASS="CONSTANT" 289 >MSG_CONFIRM</CODE 290 >) allowing to boot long images by dumb clients 291 not answering ARP requests until they are finally booted. 292 However, this is full functional and can be used in production.</P 293 ></DIV 294 ><DIV 295 CLASS="REFSECT1" 296 ><A 297 NAME="AEN1050" 298 ></A 299 ><H2 300 >AVAILABILITY</H2 301 ><P 302 ><B 303 CLASS="COMMAND" 304 >tftpd</B 305 > is part of <TT 306 CLASS="FILENAME" 307 >iputils</TT 308 > package 309 and the latest versions are available in source form at 310 <A 311 HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2" 312 TARGET="_top" 313 >http://www.skbuff.net/iputils/iputils-current.tar.bz2</A 314 >.</P 315 ></DIV 316 ><DIV 317 CLASS="NAVFOOTER" 318 ><HR 319 ALIGN="LEFT" 320 WIDTH="100%"><TABLE 321 SUMMARY="Footer navigation table" 322 WIDTH="100%" 323 BORDER="0" 324 CELLPADDING="0" 325 CELLSPACING="0" 326 ><TR 327 ><TD 328 WIDTH="33%" 329 ALIGN="left" 330 VALIGN="top" 331 ><A 332 HREF="r918.html" 333 ACCESSKEY="P" 334 >Prev</A 335 ></TD 336 ><TD 337 WIDTH="34%" 338 ALIGN="center" 339 VALIGN="top" 340 ><A 341 HREF="index.html" 342 ACCESSKEY="H" 343 >Home</A 344 ></TD 345 ><TD 346 WIDTH="33%" 347 ALIGN="right" 348 VALIGN="top" 349 ><A 350 HREF="r1056.html" 351 ACCESSKEY="N" 352 >Next</A 353 ></TD 354 ></TR 355 ><TR 356 ><TD 357 WIDTH="33%" 358 ALIGN="left" 359 VALIGN="top" 360 >traceroute6</TD 361 ><TD 362 WIDTH="34%" 363 ALIGN="center" 364 VALIGN="top" 365 > </TD 366 ><TD 367 WIDTH="33%" 368 ALIGN="right" 369 VALIGN="top" 370 >ninfod</TD 371 ></TR 372 ></TABLE 373 ></DIV 374 ></BODY 375 ></HTML 376 > 377 No newline at end of file -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/rarpd.8 iputils-s20121221/doc/rarpd.8
old new 1 .\" This manpage has been automatically generated by docbook2man 2 .\" from a DocBook document. This tool can be found at: 3 .\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 4 .\" Please send any bug reports, improvements, comments, patches, 5 .\" etc. to Steve Cheng <steve@ggi-project.org>. 6 .TH "RARPD" "8" "04 January 2013" "iputils-121221" "System Manager's Manual: iputils" 7 .SH NAME 8 rarpd \- answer RARP REQUESTs 9 .SH SYNOPSIS 10 11 \fBarping\fR [\fB-aAvde\fR] [\fB-b \fIbootdir\fB\fR] [\fB\fIinterface\fB\fR] 12 13 .SH "DESCRIPTION" 14 .PP 15 Listens 16 RARP 17 requests from clients. Provided MAC address of client 18 is found in \fI/etc/ethers\fR database and 19 obtained host name is resolvable to an IP address appropriate 20 for attached network, \fBrarpd\fR answers to client with RARPD 21 reply carrying an IP address. 22 .PP 23 To allow multiple boot servers on the network \fBrarpd\fR 24 optionally checks for presence Sun-like bootable image in TFTP directory. 25 It should have form \fBHexadecimal_IP.ARCH\fR, f.e. to load 26 sparc 193.233.7.98 \fIC1E90762.SUN4M\fR is linked to 27 an image appropriate for SUM4M in directory \fI/etc/tftpboot\fR. 28 .SH "WARNING" 29 .PP 30 This facility is deeply obsoleted by 31 BOOTP 32 and later 33 DHCP protocols. 34 However, some clients really still need this to boot. 35 .SH "OPTIONS" 36 .TP 37 \fB-a\fR 38 Listen on all the interfaces. Currently it is an internal 39 option, its function is overridden with \fIinterface\fR 40 argument. It should not be used. 41 .TP 42 \fB-A\fR 43 Listen not only RARP but also ARP messages, some rare clients 44 use ARP by some unknown reason. 45 .TP 46 \fB-v\fR 47 Be verbose. 48 .TP 49 \fB-d\fR 50 Debug mode. Do not go to background. 51 .TP 52 \fB-e\fR 53 Do not check for presence of a boot image, reply if MAC address 54 resolves to a valid IP address using \fI/etc/ethers\fR 55 database and DNS. 56 .TP 57 \fB-b \fIbootdir\fB\fR 58 TFTP boot directory. Default is \fI/etc/tftpboot\fR 59 .SH "SEE ALSO" 60 .PP 61 \fBarping\fR(8), 62 \fBtftpd\fR(8). 63 .SH "AUTHOR" 64 .PP 65 \fBrarpd\fR was written by 66 Alexey Kuznetsov 67 <kuznet@ms2.inr.ac.ru>. 68 It is now maintained by 69 YOSHIFUJI Hideaki 70 <yoshfuji@skbuff.net>. 71 .SH "SECURITY" 72 .PP 73 \fBrarpd\fR requires CAP_NET_RAW capability 74 to listen and send RARP and ARP packets. It also needs CAP_NET_ADMIN 75 to give to kernel hint for ARP resolution; this is not strictly required, 76 but some (most of, to be more exact) clients are so badly broken that 77 are not able to answer ARP before they are finally booted. This is 78 not wonderful taking into account that clients using RARPD in 2002 79 are all unsupported relic creatures of 90's and even earlier. 80 .SH "AVAILABILITY" 81 .PP 82 \fBrarpd\fR is part of \fIiputils\fR package 83 and the latest versions are available in source form at 84 http://www.skbuff.net/iputils/iputils-current.tar.bz2. -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/rdisc.8 iputils-s20121221/doc/rdisc.8
old new 1 .\" This manpage has been automatically generated by docbook2man 2 .\" from a DocBook document. This tool can be found at: 3 .\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 4 .\" Please send any bug reports, improvements, comments, patches, 5 .\" etc. to Steve Cheng <steve@ggi-project.org>. 6 .TH "RDISC" "8" "04 January 2013" "iputils-121221" "System Manager's Manual: iputils" 7 .SH NAME 8 rdisc \- network router discovery daemon 9 .SH SYNOPSIS 10 11 \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] 12 13 .SH "DESCRIPTION" 14 .PP 15 \fBrdisc\fR implements client side of the ICMP router discover protocol. 16 \fBrdisc\fR is invoked at boot time to populate the network 17 routing tables with default routes. 18 .PP 19 \fBrdisc\fR listens on the ALL_HOSTS (224.0.0.1) multicast address 20 (or \fIreceive_address\fR provided it is given) 21 for ROUTER_ADVERTISE messages from routers. The received 22 messages are handled by first ignoring those listed router addresses 23 with which the host does not share a network. Among the remaining addresses 24 the ones with the highest preference are selected as default routers 25 and a default route is entered in the kernel routing table 26 for each one of them. 27 .PP 28 Optionally, \fBrdisc\fR can avoid waiting for routers to announce 29 themselves by sending out a few ROUTER_SOLICITATION messages 30 to the ALL_ROUTERS (224.0.0.2) multicast address 31 (or \fIsend_address\fR provided it is given) 32 when it is started. 33 .PP 34 A timer is associated with each router address and the address will 35 no longer be considered for inclusion in the the routing tables if the 36 timer expires before a new 37 \fBadvertise\fR message is received from the router. 38 The address will also be excluded from consideration if the host receives an 39 \fBadvertise\fR 40 message with the preference being maximally negative. 41 .PP 42 Server side of router discovery protocol is supported by Cisco IOS 43 and by any more or less complete UNIX routing daemon, f.e \fBgated\fR. 44 Or, \fBrdisc\fR can act as responder, if compiled with -DRDISC_SERVER. 45 .SH "OPTIONS" 46 .TP 47 \fB-a\fR 48 Accept all routers independently of the preference they have in their 49 \fBadvertise\fR messages. 50 Normally \fBrdisc\fR only accepts (and enters in the kernel routing 51 tables) the router or routers with the highest preference. 52 .TP 53 \fB-b\fR 54 Opposite to \fB-a\fR, i.e. install only router with the best 55 preference value. It is default behaviour. 56 .TP 57 \fB-d\fR 58 Send debugging messages to syslog. 59 .TP 60 \fB-f\fR 61 Run \fBrdisc\fR forever even if no routers are found. 62 Normally \fBrdisc\fR gives up if it has not received any 63 \fBadvertise\fR message after after soliciting three times, 64 in which case it exits with a non-zero exit code. 65 If \fB-f\fR is not specified in the first form then 66 \fB-s\fR must be specified. 67 .TP 68 \fB-r\fR 69 Responder mode, available only if compiled with -DRDISC_SERVER. 70 .TP 71 \fB-s\fR 72 Send three \fBsolicitation\fR messages initially to quickly discover 73 the routers when the system is booted. 74 When \fB-s\fR is specified \fBrdisc\fR 75 exits with a non-zero exit code if it can not find any routers. 76 This can be overridden with the \fB-f\fR option. 77 .TP 78 \fB-p \fIpreference\fB\fR 79 Set preference in advertisement. 80 Available only with -r option. 81 .TP 82 \fB-T \fImax_interval\fB\fR 83 Set maximum advertisement interval in seconds. Default is 600 secs. 84 Available only with -r option. 85 .TP 86 \fB-t\fR 87 Test mode. Do not go to background. 88 .TP 89 \fB-v\fR 90 Be verbose i.e. send lots of debugging messages to syslog. 91 .TP 92 \fB-V\fR 93 Print version and exit. 94 .SH "HISTORY" 95 .PP 96 This program was developed by Sun Microsystems (see copyright 97 notice in source file). It was ported to Linux by 98 Alexey Kuznetsov 99 <kuznet@ms2.inr.ac.ru>. 100 It is now maintained by 101 YOSHIFUJI Hideaki 102 <yoshfuji@skbuff.net>. 103 .SH "SEE ALSO" 104 .PP 105 \fBicmp\fR(7), 106 \fBinet\fR(7), 107 \fBping\fR(8). 108 .SH "REFERENCES" 109 .PP 110 Deering, S.E.,ed "ICMP Router Discovery Messages", 111 RFC1256, Network Information Center, SRI International, 112 Menlo Park, Calif., September 1991. 113 .SH "SECURITY" 114 .PP 115 \fBrdisc\fR requires CAP_NET_RAW to listen 116 and send ICMP messages and capability CAP_NET_ADMIN 117 to update routing tables. 118 .SH "AVAILABILITY" 119 .PP 120 \fBrdisc\fR is part of \fIiputils\fR package 121 and the latest versions are available in source form at 122 http://www.skbuff.net/iputils/iputils-current.tar.bz2. -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/tftpd.8 iputils-s20121221/doc/tftpd.8
old new 1 .\" This manpage has been automatically generated by docbook2man 2 .\" from a DocBook document. This tool can be found at: 3 .\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 4 .\" Please send any bug reports, improvements, comments, patches, 5 .\" etc. to Steve Cheng <steve@ggi-project.org>. 6 .TH "TFTPD" "8" "04 January 2013" "iputils-121221" "System Manager's Manual: iputils" 7 .SH NAME 8 tftpd \- Trivial File Transfer Protocol server 9 .SH SYNOPSIS 10 11 \fBtftpd\fR \fB\fIdirectory\fB\fR 12 13 .SH "DESCRIPTION" 14 .PP 15 \fBtftpd\fR is a server which supports the DARPA 16 Trivial File Transfer Protocol 17 (RFC1350). 18 The TFTP server is started 19 by \fBinetd\fR(8). 20 .PP 21 \fIdirectory\fR is required argument; if it is not given 22 \fBtftpd\fR aborts. This path is prepended to any file name requested 23 via TFTP protocol, effectively chrooting \fBtftpd\fR to this directory. 24 File names are validated not to escape out of this directory, however 25 administrator may configure such escape using symbolic links. 26 .PP 27 It is in difference of variants of \fBtftpd\fR usually distributed 28 with unix-like systems, which take a list of directories and match 29 file names to start from one of given prefixes or to some random 30 default, when no arguments were given. There are two reasons not to 31 behave in this way: first, it is inconvenient, clients are not expected 32 to know something about layout of filesystem on server host. 33 And second, TFTP protocol is not a tool for browsing of server's filesystem, 34 it is just an agent allowing to boot dumb clients. 35 .PP 36 In the case when \fBtftpd\fR is used together with 37 \fBrarpd\fR(8), 38 tftp directories in these services should coincide and it is expected 39 that each client booted via TFTP has boot image corresponding 40 its IP address with an architecture suffix following Sun Microsystems 41 conventions. See 42 \fBrarpd\fR(8) 43 for more details. 44 .SH "SECURITY" 45 .PP 46 TFTP protocol does not provide any authentication. 47 Due to this capital flaw \fBtftpd\fR is not able to restrict 48 access to files and will allow only publically readable 49 files to be accessed. Files may be written only if they already 50 exist and are publically writable. 51 .PP 52 Impact is evident, directory exported via TFTP \fBmust not\fR 53 contain sensitive information of any kind, everyone is allowed 54 to read it as soon as a client is allowed. Boot images do not contain 55 such information as rule, however you should think twice before 56 publishing f.e. Cisco IOS config files via TFTP, they contain 57 \fBunencrypted\fR passwords and may contain some information 58 about the network, which you were not going to make public. 59 .PP 60 The \fBtftpd\fR server should be executed by \fBinetd\fR 61 with dropped root privileges, namely with a user ID giving minimal 62 access to files published in tftp directory. If it is executed 63 as superuser occasionally, \fBtftpd\fR drops its UID and GID 64 to 65534, which is most likely not the thing which you expect. 65 However, this is not very essential; remember, only files accessible 66 for everyone can be read or written via TFTP. 67 .SH "SEE ALSO" 68 .PP 69 \fBrarpd\fR(8), 70 \fBtftp\fR(1), 71 \fBinetd\fR(8). 72 .SH "HISTORY" 73 .PP 74 The \fBtftpd\fR command appeared in 4.2BSD. The source in iputils 75 is cleaned up both syntactically (ANSIized) and semantically (UDP socket IO). 76 .PP 77 It is distributed with iputils mostly as good demo of an interesting feature 78 (MSG_CONFIRM) allowing to boot long images by dumb clients 79 not answering ARP requests until they are finally booted. 80 However, this is full functional and can be used in production. 81 .SH "AVAILABILITY" 82 .PP 83 \fBtftpd\fR is part of \fIiputils\fR package 84 and the latest versions are available in source form at 85 http://www.skbuff.net/iputils/iputils-current.tar.bz2. -
iputils-s20121221
diff -Naur iputils-s20121221.orig/doc/tracepath.8 iputils-s20121221/doc/tracepath.8
old new 1 .\" This manpage has been automatically generated by docbook2man 2 .\" from a DocBook document. This tool can be found at: 3 .\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 4 .\" Please send any bug reports, improvements, comments, patches, 5 .\" etc. to Steve Cheng <steve@ggi-project.org>. 6 .TH "TRACEPATH" "8" "04 January 2013" "iputils-121221" "System Manager's Manual: iputils" 7 .SH NAME 8 tracepath, tracepath6 \- traces path to a network host discovering MTU along this path 9 .SH SYNOPSIS 10 11 \fBtracepath\fR [\fB-n\fR] [\fB-b\fR] [\fB-l \fIpktlen\fB\fR] [\fB-p \fIport\fB\fR] \fB\fIdestination\fB\fR 12 13 .SH "DESCRIPTION" 14 .PP 15 It traces path to \fIdestination\fR discovering MTU along this path. 16 It uses UDP port \fIport\fR or some random port. 17 It is similar to \fBtraceroute\fR, only does not require superuser 18 privileges and has no fancy options. 19 .PP 20 \fBtracepath6\fR is good replacement for \fBtraceroute6\fR 21 and classic example of application of Linux error queues. 22 The situation with IPv4 is worse, because commercial 23 IP routers do not return enough information in ICMP error messages. 24 Probably, it will change, when they will be updated. 25 For now it uses Van Jacobson's trick, sweeping a range 26 of UDP ports to maintain trace history. 27 .SH "OPTIONS" 28 .TP 29 \fB-n\fR 30 Print primarily IP addresses numerically. 31 .TP 32 \fB-b\fR 33 Print both of host names and IP addresses. 34 .TP 35 \fB-l\fR 36 Sets the initial packet length to \fIpktlen\fR instead of 37 65535 for \fBtracepath\fR or 128000 for \fBtracepath6\fR. 38 .TP 39 \fB-p\fR 40 Sets the initial destination port to use. 41 .SH "OUTPUT" 42 .PP 43 44 .nf 45 root@mops:~ # tracepath6 3ffe:2400:0:109::2 46 1?: [LOCALHOST] pmtu 1500 47 1: dust.inr.ac.ru 0.411ms 48 2: dust.inr.ac.ru asymm 1 0.390ms pmtu 1480 49 2: 3ffe:2400:0:109::2 463.514ms reached 50 Resume: pmtu 1480 hops 2 back 2 51 .fi 52 .PP 53 The first column shows TTL of the probe, followed by colon. 54 Usually value of TTL is obtained from reply from network, 55 but sometimes reply does not contain necessary information and 56 we have to guess it. In this case the number is followed by ?. 57 .PP 58 The second column shows the network hop, which replied to the probe. 59 It is either address of router or word [LOCALHOST], if 60 the probe was not sent to the network. 61 .PP 62 The rest of line shows miscellaneous information about path to 63 the correspinding network hop. As rule it contains value of RTT. 64 Additionally, it can show Path MTU, when it changes. 65 If the path is asymmetric 66 or the probe finishes before it reach prescribed hop, difference 67 between number of hops in forward and backward direction is shown 68 following keyword async. This information is not reliable. 69 F.e. the third line shows asymmetry of 1, it is because the first probe 70 with TTL of 2 was rejected at the first hop due to Path MTU Discovery. 71 .PP 72 The last line summarizes information about all the path to the destination, 73 it shows detected Path MTU, amount of hops to the destination and our 74 guess about amount of hops from the destination to us, which can be 75 different when the path is asymmetric. 76 .SH "SEE ALSO" 77 .PP 78 \fBtraceroute\fR(8), 79 \fBtraceroute6\fR(8), 80 \fBping\fR(8). 81 .SH "AUTHOR" 82 .PP 83 \fBtracepath\fR was written by 84 Alexey Kuznetsov 85 <kuznet@ms2.inr.ac.ru>. 86 .SH "SECURITY" 87 .PP 88 No security issues. 89 .PP 90 This lapidary deserves to be elaborated. 91 \fBtracepath\fR is not a privileged program, unlike 92 \fBtraceroute\fR, \fBping\fR and other beasts of this kind. 93 \fBtracepath\fR may be executed by everyone who has some access 94 to network, enough to send UDP datagrams to investigated destination 95 using given port. 96 .SH "AVAILABILITY" 97 .PP 98 \fBtracepath\fR is part of \fIiputils\fR package 99 and the latest versions are available in source form at 100 http://www.skbuff.net/iputils/iputils-current.tar.bz2. -
doc/traceroute6.8
diff -Naur iputils-s20121221.orig/doc/traceroute6.8 iputils-s20121221/doc/traceroute6.8
old new 1 .\" This manpage has been automatically generated by docbook2man 2 .\" from a DocBook document. This tool can be found at: 3 .\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 4 .\" Please send any bug reports, improvements, comments, patches, 5 .\" etc. to Steve Cheng <steve@ggi-project.org>. 6 .TH "TRACEROUTE6" "8" "04 January 2013" "iputils-121221" "System Manager's Manual: iputils" 7 .SH NAME 8 traceroute6 \- traces path to a network host 9 .SH SYNOPSIS 10 11 \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] 12 13 .SH "DESCRIPTION" 14 .PP 15 Description can be found in 16 \fBtraceroute\fR(8), 17 all the references to IP replaced to IPv6. It is needless to copy 18 the description from there. 19 .SH "SEE ALSO" 20 .PP 21 \fBtraceroute\fR(8), 22 \fBtracepath\fR(8), 23 \fBping\fR(8). 24 .SH "HISTORY" 25 .PP 26 This program has long history. Author of \fBtraceroute\fR 27 is Van Jacobson and it first appeared in 1988. This clone is 28 based on a port of \fBtraceroute\fR to IPv6 published 29 in NRL IPv6 distribution in 1996. In turn, it was ported 30 to Linux by Pedro Roque. After this it was kept in sync by 31 Alexey Kuznetsov 32 <kuznet@ms2.inr.ac.ru>. And eventually entered 33 \fBiputils\fR package. 34 .SH "SECURITY" 35 .PP 36 \fBtracepath6\fR requires CAP_NET_RAW capability 37 to be executed. It is safe to be used as set-uid root. 38 .SH "AVAILABILITY" 39 .PP 40 \fBtraceroute6\fR is part of \fIiputils\fR package 41 and the latest versions are available in source form at 42 http://www.skbuff.net/iputils/iputils-current.tar.bz2. -
iputils-s20121221
diff -Naur iputils-s20121221.orig/ping6.c iputils-s20121221/ping6.c
old new 168 168 169 169 #ifdef USE_GNUTLS 170 170 # include <gnutls/openssl.h> 171 #else 171 # define USE_CRYPTO 172 #elif defined USE_OPENSSL 172 173 # include <openssl/md5.h> 174 # define USE_CRYPTO 173 175 #endif 174 176 175 177 /* Node Information query */ … … 326 328 #if !PING6_NONCE_MEMORY 327 329 static int niquery_nonce(__u8 *nonce, int fill) 328 330 { 331 # ifdef USE_CRYPTO 329 332 static __u8 digest[MD5_DIGEST_LENGTH]; 330 333 static int seq = -1; 331 334 … … 348 351 return -1; 349 352 return ntohsp((__u16 *)nonce); 350 353 } 354 # else 355 fprintf(stderr, "ping6: function not available; crypto disabled\n"); 356 exit(3); 357 # endif 351 358 } 352 359 #endif 353 360 … … 502 509 503 510 static int niquery_option_subject_name_handler(int index, const char *arg) 504 511 { 512 #ifdef USE_CRYPTO 505 513 static char nigroup_buf[INET6_ADDRSTRLEN + 1 + IFNAMSIZ]; 506 514 unsigned char *dnptrs[2], **dpp, **lastdnptr; 507 515 int n; … … 627 635 free(idn); 628 636 free(name); 629 637 exit(1); 638 #else 639 fprintf(stderr, "ping6: function not available; crypto disabled\n"); 640 exit(3); 641 #endif 630 642 } 631 643 632 644 int niquery_option_help_handler(int index, const char *arg) -
iputils-s20121221
diff -Naur iputils-s20121221.orig/tracepath.c iputils-s20121221/tracepath.c
old new 73 73 74 74 void print_host(const char *a, const char *b, int both) 75 75 { 76 int plen = 0; 77 printf("%s", a); 78 plen = strlen(a); 79 if (both) { 80 printf(" (%s)", b); 81 plen += strlen(b) + 3; 82 } 76 int plen; 77 plen = printf("%s", a); 78 if (both) 79 plen += printf(" (%s)", b); 83 80 if (plen >= HOST_COLUMN_SIZE) 84 81 plen = HOST_COLUMN_SIZE - 1; 85 82 printf("%*s", HOST_COLUMN_SIZE - plen, ""); -
iputils-s20121221
diff -Naur iputils-s20121221.orig/tracepath6.c iputils-s20121221/tracepath6.c
old new 86 86 87 87 void print_host(const char *a, const char *b, int both) 88 88 { 89 int plen = 0; 90 printf("%s", a); 91 plen = strlen(a); 92 if (both) { 93 printf(" (%s)", b); 94 plen += strlen(b) + 3; 95 } 89 int plen; 90 plen = printf("%s", a); 91 if (both) 92 plen += printf(" (%s)", b); 96 93 if (plen >= HOST_COLUMN_SIZE) 97 94 plen = HOST_COLUMN_SIZE - 1; 98 95 printf("%*s", HOST_COLUMN_SIZE - plen, "");
Note:
See TracBrowser
for help on using the repository browser.