source: patches/iputils-s20100418-doc-1.patch@ 34be04a6

clfs-1.2 clfs-2.1 clfs-3.0.0-systemd clfs-3.0.0-sysvinit systemd sysvinit
Last change on this file since 34be04a6 was 8867e46, checked in by Joe Ciccone <jciccone@…>, 14 years ago

Updated IPUtils to s20100418.

  • Property mode set to 100644
File size: 132.0 KB
RevLine 
[8867e46]1diff -Naur iputils-s20100418.orig/doc/arping.8 iputils-s20100418/doc/arping.8
2--- iputils-s20100418.orig/doc/arping.8 1969-12-31 19:00:00.000000000 -0500
3+++ iputils-s20100418/doc/arping.8 2010-08-04 22:00:24.906075906 -0400
4@@ -0,0 +1,110 @@
5+.\" This manpage has been automatically generated by docbook2man
6+.\" from a DocBook document. This tool can be found at:
7+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
8+.\" Please send any bug reports, improvements, comments, patches,
9+.\" etc. to Steve Cheng <steve@ggi-project.org>.
10+.TH "ARPING" "8" "04 August 2010" "iputils-100418" "System Manager's Manual: iputils"
11+.SH NAME
12+arping \- send ARP REQUEST to a neighbour host
13+.SH SYNOPSIS
14+
15+\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
16+
17+.SH "DESCRIPTION"
18+.PP
19+Ping \fIdestination\fR on device \fIinterface\fR by ARP packets,
20+using source address \fIsource\fR.
21+.SH "OPTIONS"
22+.TP
23+\fB-A\fR
24+The same as \fB-U\fR, but ARP REPLY packets used instead
25+of ARP REQUEST.
26+.TP
27+\fB-b\fR
28+Send only MAC level broadcasts. Normally \fBarping\fR starts
29+from sending broadcast, and switch to unicast after reply received.
30+.TP
31+\fB-c \fIcount\fB\fR
32+Stop after sending \fIcount\fR ARP REQUEST
33+packets. With
34+\fIdeadline\fR
35+option, \fBarping\fR waits for
36+\fIcount\fR ARP REPLY packets, until the timeout expires.
37+.TP
38+\fB-D\fR
39+Duplicate address detection mode (DAD). See
40+RFC2131, 4.4.1.
41+Returns 0, if DAD succeeded i.e. no replies are received
42+.TP
43+\fB-f\fR
44+Finish after the first reply confirming that target is alive.
45+.TP
46+\fB-I \fIinterface\fB\fR
47+Name of network device where to send ARP REQUEST packets. This option
48+is required.
49+.TP
50+\fB-h\fR
51+Print help page and exit.
52+.TP
53+\fB-q\fR
54+Quiet output. Nothing is displayed.
55+.TP
56+\fB-s \fIsource\fB\fR
57+IP source address to use in ARP packets.
58+If this option is absent, source address is:
59+.RS
60+.TP 0.2i
61+\(bu
62+In DAD mode (with option \fB-D\fR) set to 0.0.0.0.
63+.TP 0.2i
64+\(bu
65+In Unsolicited ARP mode (with options \fB-U\fR or \fB-A\fR)
66+set to \fIdestination\fR.
67+.TP 0.2i
68+\(bu
69+Otherwise, it is calculated from routing tables.
70+.RE
71+.TP
72+\fB-U\fR
73+Unsolicited ARP mode to update neighbours' ARP caches.
74+No replies are expected.
75+.TP
76+\fB-V\fR
77+Print version of the program and exit.
78+.TP
79+\fB-w \fIdeadline\fB\fR
80+Specify a timeout, in seconds, before
81+\fBarping\fR
82+exits regardless of how many
83+packets have been sent or received. In this case
84+\fBarping\fR
85+does not stop after
86+\fIcount\fR
87+packet are sent, it waits either for
88+\fIdeadline\fR
89+expire or until
90+\fIcount\fR
91+probes are answered.
92+.SH "SEE ALSO"
93+.PP
94+\fBping\fR(8),
95+\fBclockdiff\fR(8),
96+\fBtracepath\fR(8).
97+.SH "AUTHOR"
98+.PP
99+\fBarping\fR was written by
100+Alexey Kuznetsov
101+<kuznet@ms2.inr.ac.ru>.
102+It is now maintained by
103+YOSHIFUJI Hideaki
104+<yoshfuji@skbuff.net>.
105+.SH "SECURITY"
106+.PP
107+\fBarping\fR requires CAP_NET_RAWIO capability
108+to be executed. It is not recommended to be used as set-uid root,
109+because it allows user to modify ARP caches of neighbour hosts.
110+.SH "AVAILABILITY"
111+.PP
112+\fBarping\fR is part of \fIiputils\fR package
113+and the latest versions are available in source form at
114+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
115diff -Naur iputils-s20100418.orig/doc/clockdiff.8 iputils-s20100418/doc/clockdiff.8
116--- iputils-s20100418.orig/doc/clockdiff.8 1969-12-31 19:00:00.000000000 -0500
117+++ iputils-s20100418/doc/clockdiff.8 2010-08-04 22:00:21.574452489 -0400
118@@ -0,0 +1,81 @@
119+.\" This manpage has been automatically generated by docbook2man
120+.\" from a DocBook document. This tool can be found at:
121+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
122+.\" Please send any bug reports, improvements, comments, patches,
123+.\" etc. to Steve Cheng <steve@ggi-project.org>.
124+.TH "CLOCKDIFF" "8" "04 August 2010" "iputils-100418" "System Manager's Manual: iputils"
125+.SH NAME
126+clockdiff \- measure clock difference between hosts
127+.SH SYNOPSIS
128+
129+\fBclockdiff\fR [\fB-o\fR] [\fB-o1\fR] \fB\fIdestination\fB\fR
130+
131+.SH "DESCRIPTION"
132+.PP
133+\fBclockdiff\fR Measures clock difference between us and
134+\fIdestination\fR with 1 msec resolution using ICMP TIMESTAMP
135+[2]
136+packets or, optionally, IP TIMESTAMP option
137+[3]
138+option added to ICMP ECHO.
139+[1]
140+.SH "OPTIONS"
141+.TP
142+\fB-o\fR
143+Use IP TIMESTAMP with ICMP ECHO instead of ICMP TIMESTAMP
144+messages. It is useful with some destinations, which do not support
145+ICMP TIMESTAMP (f.e. Solaris <2.4).
146+.TP
147+\fB-o1\fR
148+Slightly different form of \fB-o\fR, namely it uses three-term
149+IP TIMESTAMP with prespecified hop addresses instead of four term one.
150+What flavor works better depends on target host. Particularly,
151+\fB-o\fR is better for Linux.
152+.SH "WARNINGS"
153+.TP 0.2i
154+\(bu
155+Some nodes (Cisco) use non-standard timestamps, which is allowed
156+by RFC, but makes timestamps mostly useless.
157+.TP 0.2i
158+\(bu
159+Some nodes generate messed timestamps (Solaris>2.4), when
160+run \fBxntpd\fR. Seems, its IP stack uses a corrupted clock source,
161+which is synchronized to time-of-day clock periodically and jumps
162+randomly making timestamps mostly useless. Good news is that you can
163+use NTP in this case, which is even better.
164+.TP 0.2i
165+\(bu
166+\fBclockdiff\fR shows difference in time modulo 24 days.
167+.SH "SEE ALSO"
168+.PP
169+\fBping\fR(8),
170+\fBarping\fR(8),
171+\fBtracepath\fR(8).
172+.SH "REFERENCES"
173+.PP
174+[1] ICMP ECHO,
175+RFC0792, page 14.
176+.PP
177+[2] ICMP TIMESTAMP,
178+RFC0792, page 16.
179+.PP
180+[3] IP TIMESTAMP option,
181+RFC0791, 3.1, page 16.
182+.SH "AUTHOR"
183+.PP
184+\fBclockdiff\fR was compiled by
185+Alexey Kuznetsov
186+<kuznet@ms2.inr.ac.ru>. It was based on code borrowed
187+from BSD \fBtimed\fR daemon.
188+It is now maintained by
189+YOSHIFUJI Hideaki
190+<yoshfuji@skbuff.net>.
191+.SH "SECURITY"
192+.PP
193+\fBclockdiff\fR requires CAP_NET_RAWIO capability
194+to be executed. It is safe to be used as set-uid root.
195+.SH "AVAILABILITY"
196+.PP
197+\fBclockdiff\fR is part of \fIiputils\fR package
198+and the latest versions are available in source form at
199+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
200diff -Naur iputils-s20100418.orig/doc/index.html iputils-s20100418/doc/index.html
201--- iputils-s20100418.orig/doc/index.html 1969-12-31 19:00:00.000000000 -0500
202+++ iputils-s20100418/doc/index.html 2010-08-04 22:00:32.445575810 -0400
203@@ -0,0 +1,170 @@
204+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
205+<HTML
206+><HEAD
207+><TITLE
208+>System Manager's Manual: iputils</TITLE
209+><META
210+NAME="GENERATOR"
211+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
212+REL="NEXT"
213+TITLE="ping"
214+HREF="r3.html"></HEAD
215+><BODY
216+CLASS="REFERENCE"
217+BGCOLOR="#FFFFFF"
218+TEXT="#000000"
219+LINK="#0000FF"
220+VLINK="#840084"
221+ALINK="#0000FF"
222+><DIV
223+CLASS="NAVHEADER"
224+><TABLE
225+SUMMARY="Header navigation table"
226+WIDTH="100%"
227+BORDER="0"
228+CELLPADDING="0"
229+CELLSPACING="0"
230+><TR
231+><TD
232+WIDTH="10%"
233+ALIGN="left"
234+VALIGN="bottom"
235+>&nbsp;</TD
236+><TD
237+WIDTH="80%"
238+ALIGN="center"
239+VALIGN="bottom"
240+></TD
241+><TD
242+WIDTH="10%"
243+ALIGN="right"
244+VALIGN="bottom"
245+><A
246+HREF="r3.html"
247+ACCESSKEY="N"
248+>Next</A
249+></TD
250+></TR
251+></TABLE
252+><HR
253+ALIGN="LEFT"
254+WIDTH="100%"></DIV
255+><DIV
256+CLASS="REFERENCE"
257+><A
258+NAME="INDEX"
259+></A
260+><DIV
261+CLASS="TITLEPAGE"
262+><H1
263+CLASS="TITLE"
264+>I. System Manager's Manual: iputils</H1
265+><DIV
266+CLASS="TOC"
267+><DL
268+><DT
269+><B
270+>Table of Contents</B
271+></DT
272+><DT
273+><A
274+HREF="r3.html"
275+>ping</A
276+>&nbsp;--&nbsp;send ICMP ECHO_REQUEST to network hosts</DT
277+><DT
278+><A
279+HREF="r437.html"
280+>arping</A
281+>&nbsp;--&nbsp;send ARP REQUEST to a neighbour host</DT
282+><DT
283+><A
284+HREF="r596.html"
285+>clockdiff</A
286+>&nbsp;--&nbsp;measure clock difference between hosts</DT
287+><DT
288+><A
289+HREF="r691.html"
290+>rarpd</A
291+>&nbsp;--&nbsp;answer RARP REQUESTs</DT
292+><DT
293+><A
294+HREF="r790.html"
295+>tracepath</A
296+>&nbsp;--&nbsp;traces path to a network host discovering MTU along this path</DT
297+><DT
298+><A
299+HREF="r884.html"
300+>traceroute6</A
301+>&nbsp;--&nbsp;traces path to a network host</DT
302+><DT
303+><A
304+HREF="r949.html"
305+>tftpd</A
306+>&nbsp;--&nbsp;Trivial File Transfer Protocol server</DT
307+><DT
308+><A
309+HREF="r1022.html"
310+>rdisc</A
311+>&nbsp;--&nbsp;network router discovery daemon</DT
312+><DT
313+><A
314+HREF="r1144.html"
315+>pg3</A
316+>&nbsp;--&nbsp;send stream of UDP packets</DT
317+></DL
318+></DIV
319+></DIV
320+></DIV
321+><DIV
322+CLASS="NAVFOOTER"
323+><HR
324+ALIGN="LEFT"
325+WIDTH="100%"><TABLE
326+SUMMARY="Footer navigation table"
327+WIDTH="100%"
328+BORDER="0"
329+CELLPADDING="0"
330+CELLSPACING="0"
331+><TR
332+><TD
333+WIDTH="33%"
334+ALIGN="left"
335+VALIGN="top"
336+>&nbsp;</TD
337+><TD
338+WIDTH="34%"
339+ALIGN="center"
340+VALIGN="top"
341+>&nbsp;</TD
342+><TD
343+WIDTH="33%"
344+ALIGN="right"
345+VALIGN="top"
346+><A
347+HREF="r3.html"
348+ACCESSKEY="N"
349+>Next</A
350+></TD
351+></TR
352+><TR
353+><TD
354+WIDTH="33%"
355+ALIGN="left"
356+VALIGN="top"
357+>&nbsp;</TD
358+><TD
359+WIDTH="34%"
360+ALIGN="center"
361+VALIGN="top"
362+>&nbsp;</TD
363+><TD
364+WIDTH="33%"
365+ALIGN="right"
366+VALIGN="top"
367+>ping</TD
368+></TR
369+></TABLE
370+></DIV
371+></BODY
372+></HTML
373+>
374\ No newline at end of file
375diff -Naur iputils-s20100418.orig/doc/iputils.html iputils-s20100418/doc/iputils.html
376--- iputils-s20100418.orig/doc/iputils.html 1969-12-31 19:00:00.000000000 -0500
377+++ iputils-s20100418/doc/iputils.html 2010-08-04 22:00:33.086452519 -0400
378@@ -0,0 +1,491 @@
379+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
380+<HTML
381+><HEAD
382+><TITLE
383+>iputils: documentation directory</TITLE
384+><META
385+NAME="GENERATOR"
386+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"></HEAD
387+><BODY
388+CLASS="ARTICLE"
389+BGCOLOR="#FFFFFF"
390+TEXT="#000000"
391+LINK="#0000FF"
392+VLINK="#840084"
393+ALINK="#0000FF"
394+><DIV
395+CLASS="ARTICLE"
396+><DIV
397+CLASS="TITLEPAGE"
398+><H1
399+CLASS="TITLE"
400+><A
401+NAME="AEN2"
402+>iputils: documentation directory</A
403+></H1
404+><HR></DIV
405+><DIV
406+CLASS="TOC"
407+><DL
408+><DT
409+><B
410+>Table of Contents</B
411+></DT
412+><DT
413+>1. <A
414+HREF="#AEN4"
415+>Index</A
416+></DT
417+><DT
418+>2. <A
419+HREF="#AEN34"
420+>Historical notes</A
421+></DT
422+><DT
423+>3. <A
424+HREF="#AEN89"
425+>Installation notes</A
426+></DT
427+><DT
428+>4. <A
429+HREF="#AEN109"
430+>Availability</A
431+></DT
432+><DT
433+>5. <A
434+HREF="#AEN114"
435+>Copying</A
436+></DT
437+></DL
438+></DIV
439+><DIV
440+CLASS="SECT1"
441+><H2
442+CLASS="SECT1"
443+><A
444+NAME="AEN4"
445+>1. Index</A
446+></H2
447+><P
448+></P
449+><UL
450+><LI
451+><P
452+> <A
453+HREF="ping.html"
454+TARGET="_top"
455+>ping, ping6</A
456+>.
457+ </P
458+></LI
459+><LI
460+><P
461+> <A
462+HREF="arping.html"
463+TARGET="_top"
464+>arping</A
465+>.
466+ </P
467+></LI
468+><LI
469+><P
470+> <A
471+HREF="clockdiff.html"
472+TARGET="_top"
473+>clockdiff</A
474+>.
475+ </P
476+></LI
477+><LI
478+><P
479+> <A
480+HREF="rarpd.html"
481+TARGET="_top"
482+>rarpd</A
483+>.
484+ </P
485+></LI
486+><LI
487+><P
488+> <A
489+HREF="tracepath.html"
490+TARGET="_top"
491+>tracepath, tracepath6</A
492+>.
493+ </P
494+></LI
495+><LI
496+><P
497+> <A
498+HREF="traceroute6.html"
499+TARGET="_top"
500+>traceroute6</A
501+>.
502+ </P
503+></LI
504+><LI
505+><P
506+> <A
507+HREF="rdisc.html"
508+TARGET="_top"
509+>rdisc</A
510+>.
511+ </P
512+></LI
513+><LI
514+><P
515+> <A
516+HREF="tftpd.html"
517+TARGET="_top"
518+>tftpd</A
519+>.
520+ </P
521+></LI
522+><LI
523+><P
524+> <A
525+HREF="pg3.html"
526+TARGET="_top"
527+>pg3, ipg, pgset</A
528+>.
529+ </P
530+></LI
531+></UL
532+></DIV
533+><DIV
534+CLASS="SECT1"
535+><HR><H2
536+CLASS="SECT1"
537+><A
538+NAME="AEN34"
539+>2. Historical notes</A
540+></H2
541+><P
542+>This package appeared as a desperate attempt to bring some life
543+to state of basic networking applets: <B
544+CLASS="COMMAND"
545+>ping</B
546+>, <B
547+CLASS="COMMAND"
548+>traceroute</B
549+>
550+etc. Though it was known that port of BSD <B
551+CLASS="COMMAND"
552+>ping</B
553+> to Linux
554+was basically broken, neither maintainers of well known (and superb)
555+Linux net-tools package nor maintainers of Linux distributions
556+worried about fixing well known bugs, which were reported in linux-kernel
557+and linux-net mail lists for ages, were identified and nevertheless
558+not repaired. So, one day 1001th resuming of the subject happened
559+to be the last straw to break camel's back, I just parsed my hard disks
560+and collected a set of utilities, which shared the following properties:</P
561+><P
562+></P
563+><UL
564+><LI
565+><P
566+>Small
567+ </P
568+></LI
569+><LI
570+><P
571+>Useful despite of this
572+ </P
573+></LI
574+><LI
575+><P
576+>I never seen it was made right
577+ </P
578+></LI
579+><LI
580+><P
581+>Not quite trivial
582+ </P
583+></LI
584+><LI
585+><P
586+>Demonstrating some important feature of Linux
587+ </P
588+></LI
589+><LI
590+><P
591+>The last but not the least, I use it more or less regularly
592+ </P
593+></LI
594+></UL
595+><P
596+>This utility set was not supposed to be a reference set or something like
597+that. Most of them were cloned from some originals:
598+<DIV
599+CLASS="INFORMALTABLE"
600+><P
601+></P
602+><A
603+NAME="AEN54"
604+></A
605+><TABLE
606+BORDER="1"
607+CLASS="CALSTABLE"
608+><COL><COL><TBODY
609+><TR
610+><TD
611+>ping</TD
612+><TD
613+>cloned of an ancient NetTools-B-xx</TD
614+></TR
615+><TR
616+><TD
617+>ping6</TD
618+><TD
619+>cloned of a very old Pedro's utility set</TD
620+></TR
621+><TR
622+><TD
623+>traceroute6</TD
624+><TD
625+>cloned of NRL Sep 96 distribution</TD
626+></TR
627+><TR
628+><TD
629+>rdisc</TD
630+><TD
631+>cloned of SUN in.rdisc</TD
632+></TR
633+><TR
634+><TD
635+>clockdiff</TD
636+><TD
637+>broken out of some BSD timed</TD
638+></TR
639+><TR
640+><TD
641+>tftpd</TD
642+><TD
643+>it is clone of some ancient NetKit package</TD
644+></TR
645+></TBODY
646+></TABLE
647+><P
648+></P
649+></DIV
650+></P
651+><P
652+>Also I added some utilities written from scratch, namely
653+<B
654+CLASS="COMMAND"
655+>tracepath</B
656+>, <B
657+CLASS="COMMAND"
658+>arping</B
659+> and later <B
660+CLASS="COMMAND"
661+>rarpd</B
662+>
663+(the last one does not satisfy all the criteria, I used it two or three
664+times).</P
665+><P
666+>Hesitated a bit I overcame temptation to add <B
667+CLASS="COMMAND"
668+>traceroute</B
669+>.
670+The variant released by LBNL to that time was mostly sane and bugs
671+in it were mostly not specific to Linux, but main reason was that
672+the latest version of LBNL <B
673+CLASS="COMMAND"
674+>traceroute</B
675+> was not
676+<SPAN
677+CLASS="emphasis"
678+><I
679+CLASS="EMPHASIS"
680+>small</I
681+></SPAN
682+>, it consisted of several files,
683+used a wicked (and failing with Linux :-)) autoconfiguration etc.
684+So, instead I assembled to iputils a simplistic <B
685+CLASS="COMMAND"
686+>tracepath</B
687+> utility
688+and IPv6 version of traceroute, and published my
689+<A
690+HREF="ftp://ftp.inr.ac.ru/ip-routing/lbl-tools"
691+TARGET="_top"
692+> patches</A
693+>.
694+to LBNL <B
695+CLASS="COMMAND"
696+>traceroute</B
697+> separately.<A
698+NAME="AEN86"
699+HREF="#FTN.AEN86"
700+><SPAN
701+CLASS="footnote"
702+>[1]</SPAN
703+></A
704+></P
705+></DIV
706+><DIV
707+CLASS="SECT1"
708+><HR><H2
709+CLASS="SECT1"
710+><A
711+NAME="AEN89"
712+>3. Installation notes</A
713+></H2
714+><P
715+><KBD
716+CLASS="USERINPUT"
717+>make</KBD
718+> to compile utilities. <KBD
719+CLASS="USERINPUT"
720+>make html</KBD
721+> to prepare
722+html documentation, <KBD
723+CLASS="USERINPUT"
724+>make man</KBD
725+> if you prefer man pages.
726+Nothing fancy, provided you have DocBook package installed.</P
727+><P
728+><KBD
729+CLASS="USERINPUT"
730+>make install</KBD
731+> installs <SPAN
732+CLASS="emphasis"
733+><I
734+CLASS="EMPHASIS"
735+>only</I
736+></SPAN
737+> HTML documentation
738+to <TT
739+CLASS="FILENAME"
740+>/usr/doc/iputils</TT
741+>. It even does not try
742+to install binaries and man pages. If you read historical
743+notes above, the reason should be evident. Most of utilities
744+intersect with utilities distributed in another packages, and
745+making such target rewriting existing installation would be a crime
746+from my side. The decision what variant of <B
747+CLASS="COMMAND"
748+>ping</B
749+> is preferred,
750+how to resolve the conflicts etc. is left to you or to person who
751+assembled an rpm. I vote for variant from <B
752+CLASS="COMMAND"
753+>iputils</B
754+> of course.</P
755+><P
756+>Anyway, select utilities which you like and install them to the places
757+which you prefer together with their man pages.</P
758+><P
759+>It is possible that compilation will fail, if you use some
760+funny Linux distribution mangling header files in some unexpected ways
761+(expected ones are the ways of redhat of course :-)).
762+I validate iputils against <A
763+HREF="http://www.asplinux.ru"
764+TARGET="_top"
765+>asplinux</A
766+>
767+distribution, which is inevitably followed by validity with respect
768+to <A
769+HREF="http://www.redhat.com"
770+TARGET="_top"
771+>redhat</A
772+>.
773+If your distribution is one of widely known ones, suse or debian,
774+it also will compile provided snapshot is elder than month or so and
775+someone reported all the problems, if they took place at all.</P
776+><P
777+><SPAN
778+CLASS="emphasis"
779+><I
780+CLASS="EMPHASIS"
781+>Anyway, please, do not abuse me complaining about some compilation problems
782+in any distribution different of asplinux or redhat.
783+If you have a fix, please, send it to
784+<A
785+HREF="mailto:kuznet@ms2.inr.ac.ru"
786+TARGET="_top"
787+>me</A
788+>,
789+I will check that it does not break distributions mentioned above
790+and apply it. But I am not going to undertake any investigations,
791+bare reports are deemed to be routed to <TT
792+CLASS="FILENAME"
793+>/dev/null</TT
794+>.</I
795+></SPAN
796+></P
797+></DIV
798+><DIV
799+CLASS="SECT1"
800+><HR><H2
801+CLASS="SECT1"
802+><A
803+NAME="AEN109"
804+>4. Availability</A
805+></H2
806+><P
807+>The collection of documents is part of <TT
808+CLASS="FILENAME"
809+>iputils</TT
810+> package
811+and the latest versions are available in source form at
812+<A
813+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
814+TARGET="_top"
815+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
816+>.</P
817+></DIV
818+><DIV
819+CLASS="SECT1"
820+><HR><H2
821+CLASS="SECT1"
822+><A
823+NAME="AEN114"
824+>5. Copying</A
825+></H2
826+><P
827+>Different files are copyrighted by different persons and organizations
828+and distributed under different licenses. For details look into corresponding
829+source files.</P
830+></DIV
831+></DIV
832+><H3
833+CLASS="FOOTNOTES"
834+>Notes</H3
835+><TABLE
836+BORDER="0"
837+CLASS="FOOTNOTES"
838+WIDTH="100%"
839+><TR
840+><TD
841+ALIGN="LEFT"
842+VALIGN="TOP"
843+WIDTH="5%"
844+><A
845+NAME="FTN.AEN86"
846+HREF="#AEN86"
847+><SPAN
848+CLASS="footnote"
849+>[1]</SPAN
850+></A
851+></TD
852+><TD
853+ALIGN="LEFT"
854+VALIGN="TOP"
855+WIDTH="95%"
856+><P
857+>This was mistake.
858+Due to this <B
859+CLASS="COMMAND"
860+>traceroute</B
861+> was in a sad state until recently.
862+Good news, redhat-7.2 seems to add these patches to their traceroute
863+rpm eventually. So, I think I will refrain of suicide for awhile.</P
864+></TD
865+></TR
866+></TABLE
867+></BODY
868+></HTML
869+>
870\ No newline at end of file
871diff -Naur iputils-s20100418.orig/doc/pg3.8 iputils-s20100418/doc/pg3.8
872--- iputils-s20100418.orig/doc/pg3.8 1969-12-31 19:00:00.000000000 -0500
873+++ iputils-s20100418/doc/pg3.8 2010-08-04 22:00:21.690453269 -0400
874@@ -0,0 +1,86 @@
875+.\" This manpage has been automatically generated by docbook2man
876+.\" from a DocBook document. This tool can be found at:
877+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
878+.\" Please send any bug reports, improvements, comments, patches,
879+.\" etc. to Steve Cheng <steve@ggi-project.org>.
880+.TH "PG3" "8" "04 August 2010" "iputils-100418" "System Manager's Manual: iputils"
881+.SH NAME
882+pg3, ipg, pgset \- send stream of UDP packets
883+.SH SYNOPSIS
884+
885+\fBsource ipg\fR
886+
887+
888+\fBpg\fR
889+
890+
891+\fBpgset\fR \fB\fICOMMAND\fB\fR
892+
893+.SH "DESCRIPTION"
894+.PP
895+\fBipg\fR is not a program, it is script which should be sourced
896+to \fBbash\fR. When sourced it loads module \fIpg3\fR and
897+exports a few of functions accessible from parent shell. These macros
898+are \fBpg\fR to start packet injection and to get the results of run;
899+and \fBpgset\fR to setup packet generator.
900+.PP
901+\fBpgset\fR can send the following commands to module \fIpg3\fR:
902+.SH "COMMAND"
903+.TP
904+\fBodev \fIDEVICE\fB\fR
905+Name of Ethernet device to test. See
906+warning below.
907+.TP
908+\fBpkt_size \fIBYTES\fB\fR
909+Size of packet to generate. The size includes all the headers: UDP, IP,
910+MAC, but does not account for overhead internal to medium, i.e. FCS
911+and various paddings.
912+.TP
913+\fBfrags \fINUMBER\fB\fR
914+Each packet will contain \fINUMBER\fR of fragments.
915+Maximal amount for linux-2.4 is 6. Far not all the devices support
916+fragmented buffers.
917+.TP
918+\fBcount \fINUMBER\fB\fR
919+Send stream of \fINUMBER\fR of packets and stop after this.
920+.TP
921+\fBipg \fITIME\fB\fR
922+Introduce artificial delay between packets of \fITIME\fR
923+microseconds.
924+.TP
925+\fBdst \fIIP_ADDRESS\fB\fR
926+Select IP destination where the stream is sent to.
927+Beware, never set this address at random. \fBpg3\fR is not a toy,
928+it creates really tough stream. Default value is 0.0.0.0.
929+.TP
930+\fBdst \fIMAC_ADDRESS\fB\fR
931+Select MAC destination where the stream is sent to.
932+Default value is 00:00:00:00:00:00 in hope that this will not be received
933+by any node on LAN.
934+.TP
935+\fBstop\fR
936+Abort packet injection.
937+.SH "WARNING"
938+.PP
939+When output device is set to some random device different
940+of hardware Ethernet device, \fBpg3\fR will crash kernel.
941+.PP
942+Do not use it on VLAN, ethertap, VTUN and other devices,
943+which emulate Ethernet not being real Ethernet in fact.
944+.SH "AUTHOR"
945+.PP
946+\fBpg3\fR was written by Robert Olsson <robert.olsson@its.uu.se>.
947+.SH "SECURITY"
948+.PP
949+This can be used only by superuser.
950+.PP
951+This tool creates floods of packets which is unlikely to be handled
952+even by high-end machines. For example, it saturates gigabit link with
953+60 byte packets when used with Intel's e1000. In face of such stream
954+switches, routers and end hosts may deadlock, crash, explode.
955+Use only in test lab environment.
956+.SH "AVAILABILITY"
957+.PP
958+\fBpg3\fR is part of \fIiputils\fR package
959+and the latest versions are available in source form at
960+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
961diff -Naur iputils-s20100418.orig/doc/ping.8 iputils-s20100418/doc/ping.8
962--- iputils-s20100418.orig/doc/ping.8 1969-12-31 19:00:00.000000000 -0500
963+++ iputils-s20100418/doc/ping.8 2010-08-04 22:00:25.102076673 -0400
964@@ -0,0 +1,408 @@
965+.\" This manpage has been automatically generated by docbook2man
966+.\" from a DocBook document. This tool can be found at:
967+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
968+.\" Please send any bug reports, improvements, comments, patches,
969+.\" etc. to Steve Cheng <steve@ggi-project.org>.
970+.TH "PING" "8" "04 August 2010" "iputils-100418" "System Manager's Manual: iputils"
971+.SH NAME
972+ping, ping6 \- send ICMP ECHO_REQUEST to network hosts
973+.SH SYNOPSIS
974+
975+\fBping\fR [\fB-LRUbdfnqrvVaAB\fR] [\fB-c \fIcount\fB\fR] [\fB-m \fImark\fB\fR] [\fB-i \fIinterval\fB\fR] [\fB-l \fIpreload\fB\fR] [\fB-p \fIpattern\fB\fR] [\fB-s \fIpacketsize\fB\fR] [\fB-t \fIttl\fB\fR] [\fB-w \fIdeadline\fB\fR] [\fB-F \fIflowlabel\fB\fR] [\fB-I \fIinterface\fB\fR] [\fB-M \fIhint\fB\fR] [\fB-N \fInioption\fB\fR] [\fB-Q \fItos\fB\fR] [\fB-S \fIsndbuf\fB\fR] [\fB-T \fItimestamp option\fB\fR] [\fB-W \fItimeout\fB\fR] [\fB\fIhop\fB\fR\fI ...\fR] \fB\fIdestination\fB\fR
976+
977+.SH "DESCRIPTION"
978+.PP
979+\fBping\fR uses the ICMP protocol's mandatory ECHO_REQUEST
980+datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway.
981+ECHO_REQUEST datagrams (``pings'') have an IP and ICMP
982+header, followed by a struct timeval and then an arbitrary
983+number of ``pad'' bytes used to fill out the packet.
984+.PP
985+\fBping6\fR can also send Node Information Queries (RFC4620).
986+.SH "OPTIONS"
987+.TP
988+\fB-a\fR
989+Audible ping.
990+.TP
991+\fB-A\fR
992+Adaptive ping. Interpacket interval adapts to round-trip time, so that
993+effectively not more than one (or more, if preload is set) unanswered probes
994+present in the network. Minimal interval is 200msec for not super-user.
995+On networks with low rtt this mode is essentially equivalent to flood mode.
996+.TP
997+\fB-b\fR
998+Allow pinging a broadcast address.
999+.TP
1000+\fB-B\fR
1001+Do not allow \fBping\fR to change source address of probes.
1002+The address is bound to one selected when \fBping\fR starts.
1003+.TP
1004+\fB-m \fImark\fB\fR
1005+use \fImark\fR to tag the packets going out. This is useful
1006+for variety of reasons within the kernel such as using policy
1007+routing to select specific outbound processing.
1008+.TP
1009+\fB-c \fIcount\fB\fR
1010+Stop after sending \fIcount\fR ECHO_REQUEST
1011+packets. With
1012+\fIdeadline\fR
1013+option, \fBping\fR waits for
1014+\fIcount\fR ECHO_REPLY packets, until the timeout expires.
1015+.TP
1016+\fB-d\fR
1017+Set the SO_DEBUG option on the socket being used.
1018+Essentially, this socket option is not used by Linux kernel.
1019+.TP
1020+\fB-F \fIflow label\fB\fR
1021+Allocate and set 20 bit flow label on echo request packets.
1022+(Only \fBping6\fR). If value is zero, kernel allocates random flow label.
1023+.TP
1024+\fB-f\fR
1025+Flood ping. For every ECHO_REQUEST sent a period ``.'' is printed,
1026+while for ever ECHO_REPLY received a backspace is printed.
1027+This provides a rapid display of how many packets are being dropped.
1028+If interval is not given, it sets interval to zero and
1029+outputs packets as fast as they come back or one hundred times per second,
1030+whichever is more.
1031+Only the super-user may use this option with zero interval.
1032+.TP
1033+\fB-i \fIinterval\fB\fR
1034+Wait \fIinterval\fR seconds between sending each packet.
1035+The default is to wait for one second between each packet normally,
1036+or not to wait in flood mode. Only super-user may set interval
1037+to values less 0.2 seconds.
1038+.TP
1039+\fB-I \fIinterface address\fB\fR
1040+Set source address to specified interface address. Argument
1041+may be numeric IP address or name of device. When pinging IPv6
1042+link-local address this option is required.
1043+.TP
1044+\fB-l \fIpreload\fB\fR
1045+If \fIpreload\fR is specified,
1046+\fBping\fR sends that many packets not waiting for reply.
1047+Only the super-user may select preload more than 3.
1048+.TP
1049+\fB-L\fR
1050+Suppress loopback of multicast packets. This flag only applies if the ping
1051+destination is a multicast address.
1052+.TP
1053+\fB-N \fInioption\fB\fR
1054+Send ICMPv6 Node Information Queries (RFC4620), instead of Echo Request.
1055+.RS
1056+.TP
1057+\fBname\fR
1058+Queries for Node Names.
1059+.RE
1060+.RS
1061+.TP
1062+\fBipv6\fR
1063+Queries for IPv6 Addresses. There are several IPv6 specific flags.
1064+.RS
1065+.TP
1066+\fBipv6-global\fR
1067+Request IPv6 global-scope addresses.
1068+.RE
1069+.RS
1070+.TP
1071+\fBipv6-sitelocal\fR
1072+Request IPv6 site-local addresses.
1073+.RE
1074+.RS
1075+.TP
1076+\fBipv6-linklocal\fR
1077+Request IPv6 link-local addresses.
1078+.RE
1079+.RS
1080+.TP
1081+\fBipv6-all\fR
1082+Request IPv6 addresses on other interfaces.
1083+.RE
1084+.RE
1085+.RS
1086+.TP
1087+\fBipv4\fR
1088+Queries for IPv4 Addresses. There is one IPv4 specific flag.
1089+.RS
1090+.TP
1091+\fBipv4-all\fR
1092+Request IPv4 addresses on other interfaces.
1093+.RE
1094+.RE
1095+.RS
1096+.TP
1097+\fBsubject-ipv6=\fIipv6addr\fB\fR
1098+IPv6 subject address.
1099+.RE
1100+.RS
1101+.TP
1102+\fBsubject-ipv4=\fIipv4addr\fB\fR
1103+IPv4 subject address.
1104+.RE
1105+.RS
1106+.TP
1107+\fBsubject-name=\fInodename\fB\fR
1108+Subject name. If it contains more than one dot,
1109+fully-qualified domain name is assumed.
1110+.RE
1111+.RS
1112+.TP
1113+\fBsubject-fqdn=\fInodename\fB\fR
1114+Subject name. Fully-qualified domain name is
1115+always assumed.
1116+.RE
1117+.TP
1118+\fB-n\fR
1119+Numeric output only.
1120+No attempt will be made to lookup symbolic names for host addresses.
1121+.TP
1122+\fB-p \fIpattern\fB\fR
1123+You may specify up to 16 ``pad'' bytes to fill out the packet you send.
1124+This is useful for diagnosing data-dependent problems in a network.
1125+For example, \fB-p ff\fR will cause the sent packet
1126+to be filled with all ones.
1127+.TP
1128+\fB-D\fR
1129+Print timestamp (unix time + microseconds as in gettimeofday) before
1130+each line.
1131+.TP
1132+\fB-Q \fItos\fB\fR
1133+Set Quality of Service -related bits in ICMP datagrams.
1134+\fItos\fR can be either decimal or hex number.
1135+Traditionally (RFC1349), these have been interpreted as: 0 for reserved
1136+(currently being redefined as congestion control), 1-4 for Type of Service
1137+and 5-7 for Precedence.
1138+Possible settings for Type of Service are: minimal cost: 0x02,
1139+reliability: 0x04, throughput: 0x08, low delay: 0x10. Multiple TOS bits
1140+should not be set simultaneously. Possible settings for
1141+special Precedence range from priority (0x20) to net control (0xe0). You
1142+must be root (CAP_NET_ADMIN capability) to use Critical or
1143+higher precedence value. You cannot set
1144+bit 0x01 (reserved) unless ECN has been enabled in the kernel.
1145+In RFC2474, these fields has been redefined as 8-bit Differentiated
1146+Services (DS), consisting of: bits 0-1 of separate data (ECN will be used,
1147+here), and bits 2-7 of Differentiated Services Codepoint (DSCP).
1148+.TP
1149+\fB-q\fR
1150+Quiet output.
1151+Nothing is displayed except the summary lines at startup time and
1152+when finished.
1153+.TP
1154+\fB-R\fR
1155+Record route.
1156+Includes the RECORD_ROUTE option in the ECHO_REQUEST
1157+packet and displays the route buffer on returned packets.
1158+Note that the IP header is only large enough for nine such routes.
1159+Many hosts ignore or discard this option.
1160+.TP
1161+\fB-r\fR
1162+Bypass the normal routing tables and send directly to a host on an attached
1163+interface.
1164+If the host is not on a directly-attached network, an error is returned.
1165+This option can be used to ping a local host through an interface
1166+that has no route through it provided the option \fB-I\fR is also
1167+used.
1168+.TP
1169+\fB-s \fIpacketsize\fB\fR
1170+Specifies the number of data bytes to be sent.
1171+The default is 56, which translates into 64 ICMP
1172+data bytes when combined with the 8 bytes of ICMP header data.
1173+.TP
1174+\fB-S \fIsndbuf\fB\fR
1175+Set socket sndbuf. If not specified, it is selected to buffer
1176+not more than one packet.
1177+.TP
1178+\fB-t \fIttl\fB\fR
1179+Set the IP Time to Live.
1180+.TP
1181+\fB-T \fItimestamp option\fB\fR
1182+Set special IP timestamp options.
1183+\fItimestamp option\fR may be either
1184+\fItsonly\fR (only timestamps),
1185+\fItsandaddr\fR (timestamps and addresses) or
1186+\fItsprespec host1 [host2 [host3 [host4]]]\fR
1187+(timestamp prespecified hops).
1188+.TP
1189+\fB-M \fIhint\fB\fR
1190+Select Path MTU Discovery strategy.
1191+\fIhint\fR may be either \fIdo\fR
1192+(prohibit fragmentation, even local one),
1193+\fIwant\fR (do PMTU discovery, fragment locally when packet size
1194+is large), or \fIdont\fR (do not set DF flag).
1195+.TP
1196+\fB-U\fR
1197+Print full user-to-user latency (the old behaviour). Normally
1198+\fBping\fR
1199+prints network round trip time, which can be different
1200+f.e. due to DNS failures.
1201+.TP
1202+\fB-v\fR
1203+Verbose output.
1204+.TP
1205+\fB-V\fR
1206+Show version and exit.
1207+.TP
1208+\fB-w \fIdeadline\fB\fR
1209+Specify a timeout, in seconds, before
1210+\fBping\fR
1211+exits regardless of how many
1212+packets have been sent or received. In this case
1213+\fBping\fR
1214+does not stop after
1215+\fIcount\fR
1216+packet are sent, it waits either for
1217+\fIdeadline\fR
1218+expire or until
1219+\fIcount\fR
1220+probes are answered or for some error notification from network.
1221+.TP
1222+\fB-W \fItimeout\fB\fR
1223+Time to wait for a response, in seconds. The option affects only timeout
1224+in absense of any responses, otherwise \fBping\fR waits for two RTTs.
1225+.PP
1226+When using \fBping\fR for fault isolation, it should first be run
1227+on the local host, to verify that the local network interface is up
1228+and running. Then, hosts and gateways further and further away should be
1229+``pinged''. Round-trip times and packet loss statistics are computed.
1230+If duplicate packets are received, they are not included in the packet
1231+loss calculation, although the round trip time of these packets is used
1232+in calculating the minimum/average/maximum round-trip time numbers.
1233+When the specified number of packets have been sent (and received) or
1234+if the program is terminated with a
1235+SIGINT, a brief summary is displayed. Shorter current statistics
1236+can be obtained without termination of process with signal
1237+SIGQUIT.
1238+.PP
1239+If \fBping\fR does not receive any reply packets at all it will
1240+exit with code 1. If a packet
1241+\fIcount\fR
1242+and
1243+\fIdeadline\fR
1244+are both specified, and fewer than
1245+\fIcount\fR
1246+packets are received by the time the
1247+\fIdeadline\fR
1248+has arrived, it will also exit with code 1.
1249+On other error it exits with code 2. Otherwise it exits with code 0. This
1250+makes it possible to use the exit code to see if a host is alive or
1251+not.
1252+.PP
1253+This program is intended for use in network testing, measurement and
1254+management.
1255+Because of the load it can impose on the network, it is unwise to use
1256+\fBping\fR during normal operations or from automated scripts.
1257+.SH "ICMP PACKET DETAILS"
1258+.PP
1259+An IP header without options is 20 bytes.
1260+An ICMP ECHO_REQUEST packet contains an additional 8 bytes worth
1261+of ICMP header followed by an arbitrary amount of data.
1262+When a \fIpacketsize\fR is given, this indicated the size of this
1263+extra piece of data (the default is 56). Thus the amount of data received
1264+inside of an IP packet of type ICMP ECHO_REPLY will always be 8 bytes
1265+more than the requested data space (the ICMP header).
1266+.PP
1267+If the data space is at least of size of struct timeval
1268+\fBping\fR uses the beginning bytes of this space to include
1269+a timestamp which it uses in the computation of round trip times.
1270+If the data space is shorter, no round trip times are given.
1271+.SH "DUPLICATE AND DAMAGED PACKETS"
1272+.PP
1273+\fBping\fR will report duplicate and damaged packets.
1274+Duplicate packets should never occur, and seem to be caused by
1275+inappropriate link-level retransmissions.
1276+Duplicates may occur in many situations and are rarely (if ever) a
1277+good sign, although the presence of low levels of duplicates may not
1278+always be cause for alarm.
1279+.PP
1280+Damaged packets are obviously serious cause for alarm and often
1281+indicate broken hardware somewhere in the
1282+\fBping\fR packet's path (in the network or in the hosts).
1283+.SH "TRYING DIFFERENT DATA PATTERNS"
1284+.PP
1285+The (inter)network layer should never treat packets differently depending
1286+on the data contained in the data portion.
1287+Unfortunately, data-dependent problems have been known to sneak into
1288+networks and remain undetected for long periods of time.
1289+In many cases the particular pattern that will have problems is something
1290+that doesn't have sufficient ``transitions'', such as all ones or all
1291+zeros, or a pattern right at the edge, such as almost all zeros.
1292+It isn't necessarily enough to specify a data pattern of all zeros (for
1293+example) on the command line because the pattern that is of interest is
1294+at the data link level, and the relationship between what you type and
1295+what the controllers transmit can be complicated.
1296+.PP
1297+This means that if you have a data-dependent problem you will probably
1298+have to do a lot of testing to find it.
1299+If you are lucky, you may manage to find a file that either can't be sent
1300+across your network or that takes much longer to transfer than other
1301+similar length files.
1302+You can then examine this file for repeated patterns that you can test
1303+using the \fB-p\fR option of \fBping\fR.
1304+.SH "TTL DETAILS"
1305+.PP
1306+The TTL value of an IP packet represents the maximum number of IP routers
1307+that the packet can go through before being thrown away.
1308+In current practice you can expect each router in the Internet to decrement
1309+the TTL field by exactly one.
1310+.PP
1311+The TCP/IP specification states that the TTL field for TCP
1312+packets should be set to 60, but many systems use smaller values
1313+(4.3 BSD uses 30, 4.2 used 15).
1314+.PP
1315+The maximum possible value of this field is 255, and most Unix systems set
1316+the TTL field of ICMP ECHO_REQUEST packets to 255.
1317+This is why you will find you can ``ping'' some hosts, but not reach them
1318+with
1319+\fBtelnet\fR(1)
1320+or
1321+\fBftp\fR(1).
1322+.PP
1323+In normal operation ping prints the ttl value from the packet it receives.
1324+When a remote system receives a ping packet, it can do one of three things
1325+with the TTL field in its response:
1326+.TP 0.2i
1327+\(bu
1328+Not change it; this is what Berkeley Unix systems did before the
1329+4.3BSD Tahoe release. In this case the TTL value in the received packet
1330+will be 255 minus the number of routers in the round-trip path.
1331+.TP 0.2i
1332+\(bu
1333+Set it to 255; this is what current Berkeley Unix systems do.
1334+In this case the TTL value in the received packet will be 255 minus the
1335+number of routers in the path \fBfrom\fR
1336+the remote system \fBto\fR the \fBping\fRing host.
1337+.TP 0.2i
1338+\(bu
1339+Set it to some other value. Some machines use the same value for
1340+ICMP packets that they use for TCP packets, for example either 30 or 60.
1341+Others may use completely wild values.
1342+.SH "BUGS"
1343+.TP 0.2i
1344+\(bu
1345+Many Hosts and Gateways ignore the RECORD_ROUTE option.
1346+.TP 0.2i
1347+\(bu
1348+The maximum IP header length is too small for options like
1349+RECORD_ROUTE to be completely useful.
1350+There's not much that that can be done about this, however.
1351+.TP 0.2i
1352+\(bu
1353+Flood pinging is not recommended in general, and flood pinging the
1354+broadcast address should only be done under very controlled conditions.
1355+.SH "SEE ALSO"
1356+.PP
1357+\fBnetstat\fR(1),
1358+\fBifconfig\fR(8).
1359+.SH "HISTORY"
1360+.PP
1361+The \fBping\fR command appeared in 4.3BSD.
1362+.PP
1363+The version described here is its descendant specific to Linux.
1364+.SH "SECURITY"
1365+.PP
1366+\fBping\fR requires CAP_NET_RAWIO capability
1367+to be executed. It may be used as set-uid root.
1368+.SH "AVAILABILITY"
1369+.PP
1370+\fBping\fR is part of \fIiputils\fR package
1371+and the latest versions are available in source form at
1372+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
1373diff -Naur iputils-s20100418.orig/doc/r1022.html iputils-s20100418/doc/r1022.html
1374--- iputils-s20100418.orig/doc/r1022.html 1969-12-31 19:00:00.000000000 -0500
1375+++ iputils-s20100418/doc/r1022.html 2010-08-04 22:00:32.441576445 -0400
1376@@ -0,0 +1,511 @@
1377+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
1378+<HTML
1379+><HEAD
1380+><TITLE
1381+>rdisc</TITLE
1382+><META
1383+NAME="GENERATOR"
1384+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
1385+REL="HOME"
1386+TITLE="System Manager's Manual: iputils"
1387+HREF="index.html"><LINK
1388+REL="PREVIOUS"
1389+TITLE="tftpd"
1390+HREF="r949.html"><LINK
1391+REL="NEXT"
1392+TITLE="pg3"
1393+HREF="r1144.html"></HEAD
1394+><BODY
1395+CLASS="REFENTRY"
1396+BGCOLOR="#FFFFFF"
1397+TEXT="#000000"
1398+LINK="#0000FF"
1399+VLINK="#840084"
1400+ALINK="#0000FF"
1401+><DIV
1402+CLASS="NAVHEADER"
1403+><TABLE
1404+SUMMARY="Header navigation table"
1405+WIDTH="100%"
1406+BORDER="0"
1407+CELLPADDING="0"
1408+CELLSPACING="0"
1409+><TR
1410+><TH
1411+COLSPAN="3"
1412+ALIGN="center"
1413+>System Manager's Manual: iputils</TH
1414+></TR
1415+><TR
1416+><TD
1417+WIDTH="10%"
1418+ALIGN="left"
1419+VALIGN="bottom"
1420+><A
1421+HREF="r949.html"
1422+ACCESSKEY="P"
1423+>Prev</A
1424+></TD
1425+><TD
1426+WIDTH="80%"
1427+ALIGN="center"
1428+VALIGN="bottom"
1429+></TD
1430+><TD
1431+WIDTH="10%"
1432+ALIGN="right"
1433+VALIGN="bottom"
1434+><A
1435+HREF="r1144.html"
1436+ACCESSKEY="N"
1437+>Next</A
1438+></TD
1439+></TR
1440+></TABLE
1441+><HR
1442+ALIGN="LEFT"
1443+WIDTH="100%"></DIV
1444+><H1
1445+><A
1446+NAME="RDISC"
1447+></A
1448+>rdisc</H1
1449+><DIV
1450+CLASS="REFNAMEDIV"
1451+><A
1452+NAME="AEN1027"
1453+></A
1454+><H2
1455+>Name</H2
1456+>rdisc&nbsp;--&nbsp;network router discovery daemon</DIV
1457+><DIV
1458+CLASS="REFSYNOPSISDIV"
1459+><A
1460+NAME="AEN1030"
1461+></A
1462+><H2
1463+>Synopsis</H2
1464+><P
1465+><B
1466+CLASS="COMMAND"
1467+>rdisc</B
1468+> [<CODE
1469+CLASS="OPTION"
1470+>-abdfstvV</CODE
1471+>] [<TT
1472+CLASS="REPLACEABLE"
1473+><I
1474+>send_address</I
1475+></TT
1476+>] [<TT
1477+CLASS="REPLACEABLE"
1478+><I
1479+>receive_address</I
1480+></TT
1481+>]</P
1482+></DIV
1483+><DIV
1484+CLASS="REFSECT1"
1485+><A
1486+NAME="AEN1039"
1487+></A
1488+><H2
1489+>DESCRIPTION</H2
1490+><P
1491+><B
1492+CLASS="COMMAND"
1493+>rdisc</B
1494+> implements client side of the ICMP router discover protocol.
1495+<B
1496+CLASS="COMMAND"
1497+>rdisc</B
1498+> is invoked at boot time to populate the network
1499+routing tables with default routes. </P
1500+><P
1501+><B
1502+CLASS="COMMAND"
1503+>rdisc</B
1504+> listens on the ALL_HOSTS (224.0.0.1) multicast address
1505+(or <TT
1506+CLASS="REPLACEABLE"
1507+><I
1508+>receive_address</I
1509+></TT
1510+> provided it is given)
1511+for ROUTER_ADVERTISE messages from routers. The received
1512+messages are handled by first ignoring those listed router addresses
1513+with which the host does not share a network. Among the remaining addresses
1514+the ones with the highest preference are selected as default routers
1515+and a default route is entered in the kernel routing table
1516+for each one of them.</P
1517+><P
1518+>Optionally, <B
1519+CLASS="COMMAND"
1520+>rdisc</B
1521+> can avoid waiting for routers to announce
1522+themselves by sending out a few ROUTER_SOLICITATION messages
1523+to the ALL_ROUTERS (224.0.0.2) multicast address
1524+(or <TT
1525+CLASS="REPLACEABLE"
1526+><I
1527+>send_address</I
1528+></TT
1529+> provided it is given)
1530+when it is started.</P
1531+><P
1532+>A timer is associated with each router address and the address will
1533+no longer be considered for inclusion in the the routing tables if the
1534+timer expires before a new
1535+<SPAN
1536+CLASS="emphasis"
1537+><I
1538+CLASS="EMPHASIS"
1539+>advertise</I
1540+></SPAN
1541+> message is received from the router.
1542+The address will also be excluded from consideration if the host receives an
1543+<SPAN
1544+CLASS="emphasis"
1545+><I
1546+CLASS="EMPHASIS"
1547+>advertise</I
1548+></SPAN
1549+>
1550+message with the preference being maximally negative.</P
1551+><P
1552+>Server side of router discovery protocol is supported by Cisco IOS
1553+and by any more or less complete UNIX routing daemon, f.e <B
1554+CLASS="COMMAND"
1555+>gated</B
1556+>.</P
1557+></DIV
1558+><DIV
1559+CLASS="REFSECT1"
1560+><A
1561+NAME="AEN1055"
1562+></A
1563+><H2
1564+>OPTIONS</H2
1565+><P
1566+></P
1567+><DIV
1568+CLASS="VARIABLELIST"
1569+><DL
1570+><DT
1571+><CODE
1572+CLASS="OPTION"
1573+>-a</CODE
1574+></DT
1575+><DD
1576+><P
1577+>Accept all routers independently of the preference they have in their
1578+<SPAN
1579+CLASS="emphasis"
1580+><I
1581+CLASS="EMPHASIS"
1582+>advertise</I
1583+></SPAN
1584+> messages.
1585+Normally <B
1586+CLASS="COMMAND"
1587+>rdisc</B
1588+> only accepts (and enters in the kernel routing
1589+tables) the router or routers with the highest preference.
1590+ </P
1591+></DD
1592+><DT
1593+><CODE
1594+CLASS="OPTION"
1595+>-b</CODE
1596+></DT
1597+><DD
1598+><P
1599+>Opposite to <CODE
1600+CLASS="OPTION"
1601+>-a</CODE
1602+>, i.e. install only router with the best
1603+preference value. It is default behaviour.
1604+ </P
1605+></DD
1606+><DT
1607+><CODE
1608+CLASS="OPTION"
1609+>-d</CODE
1610+></DT
1611+><DD
1612+><P
1613+>Send debugging messages to syslog.
1614+ </P
1615+></DD
1616+><DT
1617+><CODE
1618+CLASS="OPTION"
1619+>-f</CODE
1620+></DT
1621+><DD
1622+><P
1623+>Run <B
1624+CLASS="COMMAND"
1625+>rdisc</B
1626+> forever even if no routers are found.
1627+Normally <B
1628+CLASS="COMMAND"
1629+>rdisc</B
1630+> gives up if it has not received any
1631+<SPAN
1632+CLASS="emphasis"
1633+><I
1634+CLASS="EMPHASIS"
1635+>advertise</I
1636+></SPAN
1637+> message after after soliciting three times,
1638+in which case it exits with a non-zero exit code.
1639+If <CODE
1640+CLASS="OPTION"
1641+>-f</CODE
1642+> is not specified in the first form then
1643+<CODE
1644+CLASS="OPTION"
1645+>-s</CODE
1646+> must be specified.
1647+ </P
1648+></DD
1649+><DT
1650+><CODE
1651+CLASS="OPTION"
1652+>-s</CODE
1653+></DT
1654+><DD
1655+><P
1656+>Send three <SPAN
1657+CLASS="emphasis"
1658+><I
1659+CLASS="EMPHASIS"
1660+>solicitation</I
1661+></SPAN
1662+> messages initially to quickly discover
1663+the routers when the system is booted.
1664+When <CODE
1665+CLASS="OPTION"
1666+>-s</CODE
1667+> is specified <B
1668+CLASS="COMMAND"
1669+>rdisc</B
1670+>
1671+exits with a non-zero exit code if it can not find any routers.
1672+This can be overridden with the <CODE
1673+CLASS="OPTION"
1674+>-f</CODE
1675+> option.
1676+ </P
1677+></DD
1678+><DT
1679+><CODE
1680+CLASS="OPTION"
1681+>-t</CODE
1682+></DT
1683+><DD
1684+><P
1685+>Test mode. Do not go to background.
1686+ </P
1687+></DD
1688+><DT
1689+><CODE
1690+CLASS="OPTION"
1691+>-v</CODE
1692+></DT
1693+><DD
1694+><P
1695+>Be verbose i.e. send lots of debugging messages to syslog.
1696+ </P
1697+></DD
1698+><DT
1699+><CODE
1700+CLASS="OPTION"
1701+>-V</CODE
1702+></DT
1703+><DD
1704+><P
1705+>Print version and exit.
1706+ </P
1707+></DD
1708+></DL
1709+></DIV
1710+></DIV
1711+><DIV
1712+CLASS="REFSECT1"
1713+><A
1714+NAME="AEN1110"
1715+></A
1716+><H2
1717+>HISTORY</H2
1718+><P
1719+>This program was developed by Sun Microsystems (see copyright
1720+notice in source file). It was ported to Linux by
1721+<A
1722+HREF="mailto:kuznet@ms2.inr.ac.ru"
1723+TARGET="_top"
1724+>Alexey Kuznetsov
1725+&lt;kuznet@ms2.inr.ac.ru&gt;</A
1726+>.
1727+It is now maintained by
1728+<A
1729+HREF="mailto:yoshfuji@skbuff.net"
1730+TARGET="_top"
1731+>YOSHIFUJI Hideaki
1732+&lt;yoshfuji@skbuff.net&gt;</A
1733+>.</P
1734+></DIV
1735+><DIV
1736+CLASS="REFSECT1"
1737+><A
1738+NAME="AEN1115"
1739+></A
1740+><H2
1741+>SEE ALSO</H2
1742+><P
1743+><SPAN
1744+CLASS="CITEREFENTRY"
1745+><SPAN
1746+CLASS="REFENTRYTITLE"
1747+>icmp</SPAN
1748+>(7)</SPAN
1749+>,
1750+<SPAN
1751+CLASS="CITEREFENTRY"
1752+><SPAN
1753+CLASS="REFENTRYTITLE"
1754+>inet</SPAN
1755+>(7)</SPAN
1756+>,
1757+<A
1758+HREF="r3.html"
1759+><SPAN
1760+CLASS="CITEREFENTRY"
1761+><SPAN
1762+CLASS="REFENTRYTITLE"
1763+>ping</SPAN
1764+>(8)</SPAN
1765+></A
1766+>.</P
1767+></DIV
1768+><DIV
1769+CLASS="REFSECT1"
1770+><A
1771+NAME="AEN1128"
1772+></A
1773+><H2
1774+>REFERENCES</H2
1775+><P
1776+>Deering, S.E.,ed "ICMP Router Discovery Messages",
1777+<A
1778+HREF="ftp://ftp.isi.edu/in-notes/rfc1256.txt"
1779+TARGET="_top"
1780+>RFC1256</A
1781+>, Network Information Center, SRI International,
1782+Menlo Park, Calif., September 1991.</P
1783+></DIV
1784+><DIV
1785+CLASS="REFSECT1"
1786+><A
1787+NAME="AEN1132"
1788+></A
1789+><H2
1790+>SECURITY</H2
1791+><P
1792+><B
1793+CLASS="COMMAND"
1794+>rdisc</B
1795+> requires <CODE
1796+CLASS="CONSTANT"
1797+>CAP_NET_RAWIO</CODE
1798+> to listen
1799+and send ICMP messages and capability <CODE
1800+CLASS="CONSTANT"
1801+>CAP_NET_ADMIN</CODE
1802+>
1803+to update routing tables. </P
1804+></DIV
1805+><DIV
1806+CLASS="REFSECT1"
1807+><A
1808+NAME="AEN1138"
1809+></A
1810+><H2
1811+>AVAILABILITY</H2
1812+><P
1813+><B
1814+CLASS="COMMAND"
1815+>rdisc</B
1816+> is part of <TT
1817+CLASS="FILENAME"
1818+>iputils</TT
1819+> package
1820+and the latest versions are available in source form at
1821+<A
1822+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
1823+TARGET="_top"
1824+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
1825+>.</P
1826+></DIV
1827+><DIV
1828+CLASS="NAVFOOTER"
1829+><HR
1830+ALIGN="LEFT"
1831+WIDTH="100%"><TABLE
1832+SUMMARY="Footer navigation table"
1833+WIDTH="100%"
1834+BORDER="0"
1835+CELLPADDING="0"
1836+CELLSPACING="0"
1837+><TR
1838+><TD
1839+WIDTH="33%"
1840+ALIGN="left"
1841+VALIGN="top"
1842+><A
1843+HREF="r949.html"
1844+ACCESSKEY="P"
1845+>Prev</A
1846+></TD
1847+><TD
1848+WIDTH="34%"
1849+ALIGN="center"
1850+VALIGN="top"
1851+><A
1852+HREF="index.html"
1853+ACCESSKEY="H"
1854+>Home</A
1855+></TD
1856+><TD
1857+WIDTH="33%"
1858+ALIGN="right"
1859+VALIGN="top"
1860+><A
1861+HREF="r1144.html"
1862+ACCESSKEY="N"
1863+>Next</A
1864+></TD
1865+></TR
1866+><TR
1867+><TD
1868+WIDTH="33%"
1869+ALIGN="left"
1870+VALIGN="top"
1871+>tftpd</TD
1872+><TD
1873+WIDTH="34%"
1874+ALIGN="center"
1875+VALIGN="top"
1876+>&nbsp;</TD
1877+><TD
1878+WIDTH="33%"
1879+ALIGN="right"
1880+VALIGN="top"
1881+>pg3</TD
1882+></TR
1883+></TABLE
1884+></DIV
1885+></BODY
1886+></HTML
1887+>
1888\ No newline at end of file
1889diff -Naur iputils-s20100418.orig/doc/r1144.html iputils-s20100418/doc/r1144.html
1890--- iputils-s20100418.orig/doc/r1144.html 1969-12-31 19:00:00.000000000 -0500
1891+++ iputils-s20100418/doc/r1144.html 2010-08-04 22:00:32.445575810 -0400
1892@@ -0,0 +1,428 @@
1893+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
1894+<HTML
1895+><HEAD
1896+><TITLE
1897+>pg3</TITLE
1898+><META
1899+NAME="GENERATOR"
1900+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
1901+REL="HOME"
1902+TITLE="System Manager's Manual: iputils"
1903+HREF="index.html"><LINK
1904+REL="PREVIOUS"
1905+TITLE="rdisc"
1906+HREF="r1022.html"></HEAD
1907+><BODY
1908+CLASS="REFENTRY"
1909+BGCOLOR="#FFFFFF"
1910+TEXT="#000000"
1911+LINK="#0000FF"
1912+VLINK="#840084"
1913+ALINK="#0000FF"
1914+><DIV
1915+CLASS="NAVHEADER"
1916+><TABLE
1917+SUMMARY="Header navigation table"
1918+WIDTH="100%"
1919+BORDER="0"
1920+CELLPADDING="0"
1921+CELLSPACING="0"
1922+><TR
1923+><TH
1924+COLSPAN="3"
1925+ALIGN="center"
1926+>System Manager's Manual: iputils</TH
1927+></TR
1928+><TR
1929+><TD
1930+WIDTH="10%"
1931+ALIGN="left"
1932+VALIGN="bottom"
1933+><A
1934+HREF="r1022.html"
1935+ACCESSKEY="P"
1936+>Prev</A
1937+></TD
1938+><TD
1939+WIDTH="80%"
1940+ALIGN="center"
1941+VALIGN="bottom"
1942+></TD
1943+><TD
1944+WIDTH="10%"
1945+ALIGN="right"
1946+VALIGN="bottom"
1947+>&nbsp;</TD
1948+></TR
1949+></TABLE
1950+><HR
1951+ALIGN="LEFT"
1952+WIDTH="100%"></DIV
1953+><H1
1954+><A
1955+NAME="PG3"
1956+></A
1957+>pg3</H1
1958+><DIV
1959+CLASS="REFNAMEDIV"
1960+><A
1961+NAME="AEN1149"
1962+></A
1963+><H2
1964+>Name</H2
1965+>pg3, ipg, pgset&nbsp;--&nbsp;send stream of UDP packets</DIV
1966+><DIV
1967+CLASS="REFSYNOPSISDIV"
1968+><A
1969+NAME="AEN1152"
1970+></A
1971+><H2
1972+>Synopsis</H2
1973+><P
1974+><B
1975+CLASS="COMMAND"
1976+>source ipg</B
1977+> </P
1978+><P
1979+><B
1980+CLASS="COMMAND"
1981+>pg</B
1982+> </P
1983+><P
1984+><B
1985+CLASS="COMMAND"
1986+>pgset</B
1987+> {<TT
1988+CLASS="REPLACEABLE"
1989+><I
1990+>COMMAND</I
1991+></TT
1992+>}</P
1993+></DIV
1994+><DIV
1995+CLASS="REFSECT1"
1996+><A
1997+NAME="AEN1161"
1998+></A
1999+><H2
2000+>DESCRIPTION</H2
2001+><P
2002+><B
2003+CLASS="COMMAND"
2004+>ipg</B
2005+> is not a program, it is script which should be sourced
2006+to <B
2007+CLASS="COMMAND"
2008+>bash</B
2009+>. When sourced it loads module <TT
2010+CLASS="FILENAME"
2011+>pg3</TT
2012+> and
2013+exports a few of functions accessible from parent shell. These macros
2014+are <B
2015+CLASS="COMMAND"
2016+>pg</B
2017+> to start packet injection and to get the results of run;
2018+and <B
2019+CLASS="COMMAND"
2020+>pgset</B
2021+> to setup packet generator.</P
2022+><P
2023+><B
2024+CLASS="COMMAND"
2025+>pgset</B
2026+> can send the following commands to module <TT
2027+CLASS="FILENAME"
2028+>pg3</TT
2029+>:</P
2030+></DIV
2031+><DIV
2032+CLASS="REFSECT1"
2033+><A
2034+NAME="AEN1172"
2035+></A
2036+><H2
2037+>COMMAND</H2
2038+><P
2039+></P
2040+><DIV
2041+CLASS="VARIABLELIST"
2042+><DL
2043+><DT
2044+><CODE
2045+CLASS="OPTION"
2046+>odev <TT
2047+CLASS="REPLACEABLE"
2048+><I
2049+>DEVICE</I
2050+></TT
2051+></CODE
2052+></DT
2053+><DD
2054+><P
2055+>Name of Ethernet device to test. See
2056+<A
2057+HREF="r1144.html#PG3.WARNING"
2058+>warning</A
2059+> below.
2060+ </P
2061+></DD
2062+><DT
2063+><CODE
2064+CLASS="OPTION"
2065+>pkt_size <TT
2066+CLASS="REPLACEABLE"
2067+><I
2068+>BYTES</I
2069+></TT
2070+></CODE
2071+></DT
2072+><DD
2073+><P
2074+>Size of packet to generate. The size includes all the headers: UDP, IP,
2075+MAC, but does not account for overhead internal to medium, i.e. FCS
2076+and various paddings.
2077+ </P
2078+></DD
2079+><DT
2080+><CODE
2081+CLASS="OPTION"
2082+>frags <TT
2083+CLASS="REPLACEABLE"
2084+><I
2085+>NUMBER</I
2086+></TT
2087+></CODE
2088+></DT
2089+><DD
2090+><P
2091+>Each packet will contain <TT
2092+CLASS="REPLACEABLE"
2093+><I
2094+>NUMBER</I
2095+></TT
2096+> of fragments.
2097+Maximal amount for linux-2.4 is 6. Far not all the devices support
2098+fragmented buffers.
2099+ </P
2100+></DD
2101+><DT
2102+><CODE
2103+CLASS="OPTION"
2104+>count <TT
2105+CLASS="REPLACEABLE"
2106+><I
2107+>NUMBER</I
2108+></TT
2109+></CODE
2110+></DT
2111+><DD
2112+><P
2113+>Send stream of <TT
2114+CLASS="REPLACEABLE"
2115+><I
2116+>NUMBER</I
2117+></TT
2118+> of packets and stop after this.
2119+ </P
2120+></DD
2121+><DT
2122+><CODE
2123+CLASS="OPTION"
2124+>ipg <TT
2125+CLASS="REPLACEABLE"
2126+><I
2127+>TIME</I
2128+></TT
2129+></CODE
2130+></DT
2131+><DD
2132+><P
2133+>Introduce artificial delay between packets of <TT
2134+CLASS="REPLACEABLE"
2135+><I
2136+>TIME</I
2137+></TT
2138+>
2139+microseconds.
2140+ </P
2141+></DD
2142+><DT
2143+><CODE
2144+CLASS="OPTION"
2145+>dst <TT
2146+CLASS="REPLACEABLE"
2147+><I
2148+>IP_ADDRESS</I
2149+></TT
2150+></CODE
2151+></DT
2152+><DD
2153+><P
2154+>Select IP destination where the stream is sent to.
2155+Beware, never set this address at random. <B
2156+CLASS="COMMAND"
2157+>pg3</B
2158+> is not a toy,
2159+it creates really tough stream. Default value is 0.0.0.0.
2160+ </P
2161+></DD
2162+><DT
2163+><CODE
2164+CLASS="OPTION"
2165+>dst <TT
2166+CLASS="REPLACEABLE"
2167+><I
2168+>MAC_ADDRESS</I
2169+></TT
2170+></CODE
2171+></DT
2172+><DD
2173+><P
2174+>Select MAC destination where the stream is sent to.
2175+Default value is 00:00:00:00:00:00 in hope that this will not be received
2176+by any node on LAN.
2177+ </P
2178+></DD
2179+><DT
2180+><CODE
2181+CLASS="OPTION"
2182+>stop</CODE
2183+></DT
2184+><DD
2185+><P
2186+>Abort packet injection.
2187+ </P
2188+></DD
2189+></DL
2190+></DIV
2191+></DIV
2192+><DIV
2193+CLASS="REFSECT1"
2194+><A
2195+NAME="PG3.WARNING"
2196+></A
2197+><H2
2198+>WARNING</H2
2199+><P
2200+>When output device is set to some random device different
2201+of hardware Ethernet device, <B
2202+CLASS="COMMAND"
2203+>pg3</B
2204+> will crash kernel.</P
2205+><P
2206+>Do not use it on VLAN, ethertap, VTUN and other devices,
2207+which emulate Ethernet not being real Ethernet in fact.</P
2208+></DIV
2209+><DIV
2210+CLASS="REFSECT1"
2211+><A
2212+NAME="AEN1232"
2213+></A
2214+><H2
2215+>AUTHOR</H2
2216+><P
2217+><B
2218+CLASS="COMMAND"
2219+>pg3</B
2220+> was written by <A
2221+HREF="mailto:robert.olsson@its.uu.se"
2222+TARGET="_top"
2223+>Robert Olsson &lt;robert.olsson@its.uu.se&gt;</A
2224+>.</P
2225+></DIV
2226+><DIV
2227+CLASS="REFSECT1"
2228+><A
2229+NAME="AEN1237"
2230+></A
2231+><H2
2232+>SECURITY</H2
2233+><P
2234+>This can be used only by superuser.</P
2235+><P
2236+>This tool creates floods of packets which is unlikely to be handled
2237+even by high-end machines. For example, it saturates gigabit link with
2238+60 byte packets when used with Intel's e1000. In face of such stream
2239+switches, routers and end hosts may deadlock, crash, explode.
2240+Use only in test lab environment.</P
2241+></DIV
2242+><DIV
2243+CLASS="REFSECT1"
2244+><A
2245+NAME="AEN1241"
2246+></A
2247+><H2
2248+>AVAILABILITY</H2
2249+><P
2250+><B
2251+CLASS="COMMAND"
2252+>pg3</B
2253+> is part of <TT
2254+CLASS="FILENAME"
2255+>iputils</TT
2256+> package
2257+and the latest versions are available in source form at
2258+<A
2259+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
2260+TARGET="_top"
2261+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
2262+>.</P
2263+></DIV
2264+><DIV
2265+CLASS="NAVFOOTER"
2266+><HR
2267+ALIGN="LEFT"
2268+WIDTH="100%"><TABLE
2269+SUMMARY="Footer navigation table"
2270+WIDTH="100%"
2271+BORDER="0"
2272+CELLPADDING="0"
2273+CELLSPACING="0"
2274+><TR
2275+><TD
2276+WIDTH="33%"
2277+ALIGN="left"
2278+VALIGN="top"
2279+><A
2280+HREF="r1022.html"
2281+ACCESSKEY="P"
2282+>Prev</A
2283+></TD
2284+><TD
2285+WIDTH="34%"
2286+ALIGN="center"
2287+VALIGN="top"
2288+><A
2289+HREF="index.html"
2290+ACCESSKEY="H"
2291+>Home</A
2292+></TD
2293+><TD
2294+WIDTH="33%"
2295+ALIGN="right"
2296+VALIGN="top"
2297+>&nbsp;</TD
2298+></TR
2299+><TR
2300+><TD
2301+WIDTH="33%"
2302+ALIGN="left"
2303+VALIGN="top"
2304+>rdisc</TD
2305+><TD
2306+WIDTH="34%"
2307+ALIGN="center"
2308+VALIGN="top"
2309+>&nbsp;</TD
2310+><TD
2311+WIDTH="33%"
2312+ALIGN="right"
2313+VALIGN="top"
2314+>&nbsp;</TD
2315+></TR
2316+></TABLE
2317+></DIV
2318+></BODY
2319+></HTML
2320+>
2321\ No newline at end of file
2322diff -Naur iputils-s20100418.orig/doc/r3.html iputils-s20100418/doc/r3.html
2323--- iputils-s20100418.orig/doc/r3.html 1969-12-31 19:00:00.000000000 -0500
2324+++ iputils-s20100418/doc/r3.html 2010-08-04 22:00:32.373575999 -0400
2325@@ -0,0 +1,1494 @@
2326+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
2327+<HTML
2328+><HEAD
2329+><TITLE
2330+>ping</TITLE
2331+><META
2332+NAME="GENERATOR"
2333+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
2334+REL="HOME"
2335+TITLE="System Manager's Manual: iputils"
2336+HREF="index.html"><LINK
2337+REL="PREVIOUS"
2338+TITLE="System Manager's Manual: iputils"
2339+HREF="index.html"><LINK
2340+REL="NEXT"
2341+TITLE="arping"
2342+HREF="r437.html"></HEAD
2343+><BODY
2344+CLASS="REFENTRY"
2345+BGCOLOR="#FFFFFF"
2346+TEXT="#000000"
2347+LINK="#0000FF"
2348+VLINK="#840084"
2349+ALINK="#0000FF"
2350+><DIV
2351+CLASS="NAVHEADER"
2352+><TABLE
2353+SUMMARY="Header navigation table"
2354+WIDTH="100%"
2355+BORDER="0"
2356+CELLPADDING="0"
2357+CELLSPACING="0"
2358+><TR
2359+><TH
2360+COLSPAN="3"
2361+ALIGN="center"
2362+>System Manager's Manual: iputils</TH
2363+></TR
2364+><TR
2365+><TD
2366+WIDTH="10%"
2367+ALIGN="left"
2368+VALIGN="bottom"
2369+><A
2370+HREF="index.html"
2371+ACCESSKEY="P"
2372+>Prev</A
2373+></TD
2374+><TD
2375+WIDTH="80%"
2376+ALIGN="center"
2377+VALIGN="bottom"
2378+></TD
2379+><TD
2380+WIDTH="10%"
2381+ALIGN="right"
2382+VALIGN="bottom"
2383+><A
2384+HREF="r437.html"
2385+ACCESSKEY="N"
2386+>Next</A
2387+></TD
2388+></TR
2389+></TABLE
2390+><HR
2391+ALIGN="LEFT"
2392+WIDTH="100%"></DIV
2393+><H1
2394+><A
2395+NAME="PING"
2396+></A
2397+>ping</H1
2398+><DIV
2399+CLASS="REFNAMEDIV"
2400+><A
2401+NAME="AEN8"
2402+></A
2403+><H2
2404+>Name</H2
2405+>ping, ping6&nbsp;--&nbsp;send ICMP ECHO_REQUEST to network hosts</DIV
2406+><DIV
2407+CLASS="REFSYNOPSISDIV"
2408+><A
2409+NAME="AEN11"
2410+></A
2411+><H2
2412+>Synopsis</H2
2413+><P
2414+><B
2415+CLASS="COMMAND"
2416+>ping</B
2417+> [<CODE
2418+CLASS="OPTION"
2419+>-LRUbdfnqrvVaAB</CODE
2420+>] [-c <TT
2421+CLASS="REPLACEABLE"
2422+><I
2423+>count</I
2424+></TT
2425+>] [-m <TT
2426+CLASS="REPLACEABLE"
2427+><I
2428+>mark</I
2429+></TT
2430+>] [-i <TT
2431+CLASS="REPLACEABLE"
2432+><I
2433+>interval</I
2434+></TT
2435+>] [-l <TT
2436+CLASS="REPLACEABLE"
2437+><I
2438+>preload</I
2439+></TT
2440+>] [-p <TT
2441+CLASS="REPLACEABLE"
2442+><I
2443+>pattern</I
2444+></TT
2445+>] [-s <TT
2446+CLASS="REPLACEABLE"
2447+><I
2448+>packetsize</I
2449+></TT
2450+>] [-t <TT
2451+CLASS="REPLACEABLE"
2452+><I
2453+>ttl</I
2454+></TT
2455+>] [-w <TT
2456+CLASS="REPLACEABLE"
2457+><I
2458+>deadline</I
2459+></TT
2460+>] [-F <TT
2461+CLASS="REPLACEABLE"
2462+><I
2463+>flowlabel</I
2464+></TT
2465+>] [-I <TT
2466+CLASS="REPLACEABLE"
2467+><I
2468+>interface</I
2469+></TT
2470+>] [-M <TT
2471+CLASS="REPLACEABLE"
2472+><I
2473+>hint</I
2474+></TT
2475+>] [-N <TT
2476+CLASS="REPLACEABLE"
2477+><I
2478+>nioption</I
2479+></TT
2480+>] [-Q <TT
2481+CLASS="REPLACEABLE"
2482+><I
2483+>tos</I
2484+></TT
2485+>] [-S <TT
2486+CLASS="REPLACEABLE"
2487+><I
2488+>sndbuf</I
2489+></TT
2490+>] [-T <TT
2491+CLASS="REPLACEABLE"
2492+><I
2493+>timestamp option</I
2494+></TT
2495+>] [-W <TT
2496+CLASS="REPLACEABLE"
2497+><I
2498+>timeout</I
2499+></TT
2500+>] [<TT
2501+CLASS="REPLACEABLE"
2502+><I
2503+>hop</I
2504+></TT
2505+>...] {<TT
2506+CLASS="REPLACEABLE"
2507+><I
2508+>destination</I
2509+></TT
2510+>}</P
2511+></DIV
2512+><DIV
2513+CLASS="REFSECT1"
2514+><A
2515+NAME="AEN52"
2516+></A
2517+><H2
2518+>DESCRIPTION</H2
2519+><P
2520+><B
2521+CLASS="COMMAND"
2522+>ping</B
2523+> uses the ICMP protocol's mandatory ECHO_REQUEST
2524+datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway.
2525+ECHO_REQUEST datagrams (``pings'') have an IP and ICMP
2526+header, followed by a <CODE
2527+CLASS="STRUCTNAME"
2528+>struct timeval</CODE
2529+> and then an arbitrary
2530+number of ``pad'' bytes used to fill out the packet.</P
2531+><P
2532+><B
2533+CLASS="COMMAND"
2534+>ping6</B
2535+> can also send Node Information Queries (RFC4620).</P
2536+></DIV
2537+><DIV
2538+CLASS="REFSECT1"
2539+><A
2540+NAME="AEN59"
2541+></A
2542+><H2
2543+>OPTIONS</H2
2544+><P
2545+></P
2546+><DIV
2547+CLASS="VARIABLELIST"
2548+><DL
2549+><DT
2550+><CODE
2551+CLASS="OPTION"
2552+>-a</CODE
2553+></DT
2554+><DD
2555+><P
2556+>Audible ping.
2557+ </P
2558+></DD
2559+><DT
2560+><CODE
2561+CLASS="OPTION"
2562+>-A</CODE
2563+></DT
2564+><DD
2565+><P
2566+>Adaptive ping. Interpacket interval adapts to round-trip time, so that
2567+effectively not more than one (or more, if preload is set) unanswered probes
2568+present in the network. Minimal interval is 200msec for not super-user.
2569+On networks with low rtt this mode is essentially equivalent to flood mode.
2570+ </P
2571+></DD
2572+><DT
2573+><CODE
2574+CLASS="OPTION"
2575+>-b</CODE
2576+></DT
2577+><DD
2578+><P
2579+>Allow pinging a broadcast address.
2580+ </P
2581+></DD
2582+><DT
2583+><CODE
2584+CLASS="OPTION"
2585+>-B</CODE
2586+></DT
2587+><DD
2588+><P
2589+>Do not allow <B
2590+CLASS="COMMAND"
2591+>ping</B
2592+> to change source address of probes.
2593+The address is bound to one selected when <B
2594+CLASS="COMMAND"
2595+>ping</B
2596+> starts.
2597+ </P
2598+></DD
2599+><DT
2600+><CODE
2601+CLASS="OPTION"
2602+>-m <TT
2603+CLASS="REPLACEABLE"
2604+><I
2605+>mark</I
2606+></TT
2607+></CODE
2608+></DT
2609+><DD
2610+><P
2611+>use <TT
2612+CLASS="REPLACEABLE"
2613+><I
2614+>mark</I
2615+></TT
2616+> to tag the packets going out. This is useful
2617+for variety of reasons within the kernel such as using policy
2618+routing to select specific outbound processing.
2619+ </P
2620+></DD
2621+><DT
2622+><CODE
2623+CLASS="OPTION"
2624+><A
2625+NAME="PING.COUNT"
2626+></A
2627+>-c <TT
2628+CLASS="REPLACEABLE"
2629+><I
2630+>count</I
2631+></TT
2632+></CODE
2633+></DT
2634+><DD
2635+><P
2636+>Stop after sending <TT
2637+CLASS="REPLACEABLE"
2638+><I
2639+>count</I
2640+></TT
2641+> ECHO_REQUEST
2642+packets. With
2643+<A
2644+HREF="r3.html#PING.DEADLINE"
2645+><TT
2646+CLASS="REPLACEABLE"
2647+><I
2648+>deadline</I
2649+></TT
2650+></A
2651+>
2652+option, <B
2653+CLASS="COMMAND"
2654+>ping</B
2655+> waits for
2656+<TT
2657+CLASS="REPLACEABLE"
2658+><I
2659+>count</I
2660+></TT
2661+> ECHO_REPLY packets, until the timeout expires.
2662+ </P
2663+></DD
2664+><DT
2665+><CODE
2666+CLASS="OPTION"
2667+>-d</CODE
2668+></DT
2669+><DD
2670+><P
2671+>Set the <CODE
2672+CLASS="CONSTANT"
2673+>SO_DEBUG</CODE
2674+> option on the socket being used.
2675+Essentially, this socket option is not used by Linux kernel.
2676+ </P
2677+></DD
2678+><DT
2679+><CODE
2680+CLASS="OPTION"
2681+>-F <TT
2682+CLASS="REPLACEABLE"
2683+><I
2684+>flow label</I
2685+></TT
2686+></CODE
2687+></DT
2688+><DD
2689+><P
2690+>Allocate and set 20 bit flow label on echo request packets.
2691+(Only <B
2692+CLASS="COMMAND"
2693+>ping6</B
2694+>). If value is zero, kernel allocates random flow label.
2695+ </P
2696+></DD
2697+><DT
2698+><CODE
2699+CLASS="OPTION"
2700+>-f</CODE
2701+></DT
2702+><DD
2703+><P
2704+>Flood ping. For every ECHO_REQUEST sent a period ``.'' is printed,
2705+while for ever ECHO_REPLY received a backspace is printed.
2706+This provides a rapid display of how many packets are being dropped.
2707+If interval is not given, it sets interval to zero and
2708+outputs packets as fast as they come back or one hundred times per second,
2709+whichever is more.
2710+Only the super-user may use this option with zero interval.
2711+ </P
2712+></DD
2713+><DT
2714+><CODE
2715+CLASS="OPTION"
2716+>-i <TT
2717+CLASS="REPLACEABLE"
2718+><I
2719+>interval</I
2720+></TT
2721+></CODE
2722+></DT
2723+><DD
2724+><P
2725+>Wait <TT
2726+CLASS="REPLACEABLE"
2727+><I
2728+>interval</I
2729+></TT
2730+> seconds between sending each packet.
2731+The default is to wait for one second between each packet normally,
2732+or not to wait in flood mode. Only super-user may set interval
2733+to values less 0.2 seconds.
2734+ </P
2735+></DD
2736+><DT
2737+><CODE
2738+CLASS="OPTION"
2739+>-I <TT
2740+CLASS="REPLACEABLE"
2741+><I
2742+>interface address</I
2743+></TT
2744+></CODE
2745+></DT
2746+><DD
2747+><P
2748+>Set source address to specified interface address. Argument
2749+may be numeric IP address or name of device. When pinging IPv6
2750+link-local address this option is required.
2751+ </P
2752+></DD
2753+><DT
2754+><CODE
2755+CLASS="OPTION"
2756+>-l <TT
2757+CLASS="REPLACEABLE"
2758+><I
2759+>preload</I
2760+></TT
2761+></CODE
2762+></DT
2763+><DD
2764+><P
2765+>If <TT
2766+CLASS="REPLACEABLE"
2767+><I
2768+>preload</I
2769+></TT
2770+> is specified,
2771+<B
2772+CLASS="COMMAND"
2773+>ping</B
2774+> sends that many packets not waiting for reply.
2775+Only the super-user may select preload more than 3.
2776+ </P
2777+></DD
2778+><DT
2779+><CODE
2780+CLASS="OPTION"
2781+>-L</CODE
2782+></DT
2783+><DD
2784+><P
2785+>Suppress loopback of multicast packets. This flag only applies if the ping
2786+destination is a multicast address.
2787+ </P
2788+></DD
2789+><DT
2790+><CODE
2791+CLASS="OPTION"
2792+>-N <TT
2793+CLASS="REPLACEABLE"
2794+><I
2795+>nioption</I
2796+></TT
2797+></CODE
2798+></DT
2799+><DD
2800+><P
2801+>Send ICMPv6 Node Information Queries (RFC4620), instead of Echo Request.
2802+ <P
2803+></P
2804+><DIV
2805+CLASS="VARIABLELIST"
2806+><DL
2807+><DT
2808+><CODE
2809+CLASS="OPTION"
2810+>name</CODE
2811+></DT
2812+><DD
2813+><P
2814+>Queries for Node Names.</P
2815+></DD
2816+></DL
2817+></DIV
2818+>
2819+ <P
2820+></P
2821+><DIV
2822+CLASS="VARIABLELIST"
2823+><DL
2824+><DT
2825+><CODE
2826+CLASS="OPTION"
2827+>ipv6</CODE
2828+></DT
2829+><DD
2830+><P
2831+>Queries for IPv6 Addresses. There are several IPv6 specific flags.
2832+ <P
2833+></P
2834+><DIV
2835+CLASS="VARIABLELIST"
2836+><DL
2837+><DT
2838+><CODE
2839+CLASS="OPTION"
2840+>ipv6-global</CODE
2841+></DT
2842+><DD
2843+><P
2844+>Request IPv6 global-scope addresses.</P
2845+></DD
2846+></DL
2847+></DIV
2848+>
2849+ <P
2850+></P
2851+><DIV
2852+CLASS="VARIABLELIST"
2853+><DL
2854+><DT
2855+><CODE
2856+CLASS="OPTION"
2857+>ipv6-sitelocal</CODE
2858+></DT
2859+><DD
2860+><P
2861+>Request IPv6 site-local addresses.</P
2862+></DD
2863+></DL
2864+></DIV
2865+>
2866+ <P
2867+></P
2868+><DIV
2869+CLASS="VARIABLELIST"
2870+><DL
2871+><DT
2872+><CODE
2873+CLASS="OPTION"
2874+>ipv6-linklocal</CODE
2875+></DT
2876+><DD
2877+><P
2878+>Request IPv6 link-local addresses.</P
2879+></DD
2880+></DL
2881+></DIV
2882+>
2883+ <P
2884+></P
2885+><DIV
2886+CLASS="VARIABLELIST"
2887+><DL
2888+><DT
2889+><CODE
2890+CLASS="OPTION"
2891+>ipv6-all</CODE
2892+></DT
2893+><DD
2894+><P
2895+>Request IPv6 addresses on other interfaces.</P
2896+></DD
2897+></DL
2898+></DIV
2899+>
2900+ </P
2901+></DD
2902+></DL
2903+></DIV
2904+>
2905+ <P
2906+></P
2907+><DIV
2908+CLASS="VARIABLELIST"
2909+><DL
2910+><DT
2911+><CODE
2912+CLASS="OPTION"
2913+>ipv4</CODE
2914+></DT
2915+><DD
2916+><P
2917+>Queries for IPv4 Addresses. There is one IPv4 specific flag.
2918+ <P
2919+></P
2920+><DIV
2921+CLASS="VARIABLELIST"
2922+><DL
2923+><DT
2924+><CODE
2925+CLASS="OPTION"
2926+>ipv4-all</CODE
2927+></DT
2928+><DD
2929+><P
2930+>Request IPv4 addresses on other interfaces.</P
2931+></DD
2932+></DL
2933+></DIV
2934+>
2935+ </P
2936+></DD
2937+></DL
2938+></DIV
2939+>
2940+ <P
2941+></P
2942+><DIV
2943+CLASS="VARIABLELIST"
2944+><DL
2945+><DT
2946+><CODE
2947+CLASS="OPTION"
2948+>subject-ipv6=<TT
2949+CLASS="REPLACEABLE"
2950+><I
2951+>ipv6addr</I
2952+></TT
2953+></CODE
2954+></DT
2955+><DD
2956+><P
2957+>IPv6 subject address.</P
2958+></DD
2959+></DL
2960+></DIV
2961+>
2962+ <P
2963+></P
2964+><DIV
2965+CLASS="VARIABLELIST"
2966+><DL
2967+><DT
2968+><CODE
2969+CLASS="OPTION"
2970+>subject-ipv4=<TT
2971+CLASS="REPLACEABLE"
2972+><I
2973+>ipv4addr</I
2974+></TT
2975+></CODE
2976+></DT
2977+><DD
2978+><P
2979+>IPv4 subject address.</P
2980+></DD
2981+></DL
2982+></DIV
2983+>
2984+ <P
2985+></P
2986+><DIV
2987+CLASS="VARIABLELIST"
2988+><DL
2989+><DT
2990+><CODE
2991+CLASS="OPTION"
2992+>subject-name=<TT
2993+CLASS="REPLACEABLE"
2994+><I
2995+>nodename</I
2996+></TT
2997+></CODE
2998+></DT
2999+><DD
3000+><P
3001+>Subject name. If it contains more than one dot,
3002+ fully-qualified domain name is assumed.</P
3003+></DD
3004+></DL
3005+></DIV
3006+>
3007+ <P
3008+></P
3009+><DIV
3010+CLASS="VARIABLELIST"
3011+><DL
3012+><DT
3013+><CODE
3014+CLASS="OPTION"
3015+>subject-fqdn=<TT
3016+CLASS="REPLACEABLE"
3017+><I
3018+>nodename</I
3019+></TT
3020+></CODE
3021+></DT
3022+><DD
3023+><P
3024+>Subject name. Fully-qualified domain name is
3025+ always assumed.</P
3026+></DD
3027+></DL
3028+></DIV
3029+>
3030+ </P
3031+></DD
3032+><DT
3033+><CODE
3034+CLASS="OPTION"
3035+>-n</CODE
3036+></DT
3037+><DD
3038+><P
3039+>Numeric output only.
3040+No attempt will be made to lookup symbolic names for host addresses.
3041+ </P
3042+></DD
3043+><DT
3044+><CODE
3045+CLASS="OPTION"
3046+>-p <TT
3047+CLASS="REPLACEABLE"
3048+><I
3049+>pattern</I
3050+></TT
3051+></CODE
3052+></DT
3053+><DD
3054+><P
3055+>You may specify up to 16 ``pad'' bytes to fill out the packet you send.
3056+This is useful for diagnosing data-dependent problems in a network.
3057+For example, <CODE
3058+CLASS="OPTION"
3059+>-p ff</CODE
3060+> will cause the sent packet
3061+to be filled with all ones.
3062+ </P
3063+></DD
3064+><DT
3065+><CODE
3066+CLASS="OPTION"
3067+>-D</CODE
3068+></DT
3069+><DD
3070+><P
3071+>Print timestamp (unix time + microseconds as in gettimeofday) before
3072+each line.
3073+ </P
3074+></DD
3075+><DT
3076+><CODE
3077+CLASS="OPTION"
3078+>-Q <TT
3079+CLASS="REPLACEABLE"
3080+><I
3081+>tos</I
3082+></TT
3083+></CODE
3084+></DT
3085+><DD
3086+><P
3087+>Set Quality of Service -related bits in ICMP datagrams.
3088+<TT
3089+CLASS="REPLACEABLE"
3090+><I
3091+>tos</I
3092+></TT
3093+> can be either decimal or hex number.
3094+Traditionally (RFC1349), these have been interpreted as: 0 for reserved
3095+(currently being redefined as congestion control), 1-4 for Type of Service
3096+and 5-7 for Precedence.
3097+Possible settings for Type of Service are: minimal cost: 0x02,
3098+reliability: 0x04, throughput: 0x08, low delay: 0x10. Multiple TOS bits
3099+should not be set simultaneously. Possible settings for
3100+special Precedence range from priority (0x20) to net control (0xe0). You
3101+must be root (<CODE
3102+CLASS="CONSTANT"
3103+>CAP_NET_ADMIN</CODE
3104+> capability) to use Critical or
3105+higher precedence value. You cannot set
3106+bit 0x01 (reserved) unless ECN has been enabled in the kernel.
3107+In RFC2474, these fields has been redefined as 8-bit Differentiated
3108+Services (DS), consisting of: bits 0-1 of separate data (ECN will be used,
3109+here), and bits 2-7 of Differentiated Services Codepoint (DSCP).
3110+ </P
3111+></DD
3112+><DT
3113+><CODE
3114+CLASS="OPTION"
3115+>-q</CODE
3116+></DT
3117+><DD
3118+><P
3119+>Quiet output.
3120+Nothing is displayed except the summary lines at startup time and
3121+when finished.
3122+ </P
3123+></DD
3124+><DT
3125+><CODE
3126+CLASS="OPTION"
3127+>-R</CODE
3128+></DT
3129+><DD
3130+><P
3131+>Record route.
3132+Includes the RECORD_ROUTE option in the ECHO_REQUEST
3133+packet and displays the route buffer on returned packets.
3134+Note that the IP header is only large enough for nine such routes.
3135+Many hosts ignore or discard this option.
3136+ </P
3137+></DD
3138+><DT
3139+><CODE
3140+CLASS="OPTION"
3141+>-r</CODE
3142+></DT
3143+><DD
3144+><P
3145+>Bypass the normal routing tables and send directly to a host on an attached
3146+interface.
3147+If the host is not on a directly-attached network, an error is returned.
3148+This option can be used to ping a local host through an interface
3149+that has no route through it provided the option <CODE
3150+CLASS="OPTION"
3151+>-I</CODE
3152+> is also
3153+used.
3154+ </P
3155+></DD
3156+><DT
3157+><CODE
3158+CLASS="OPTION"
3159+>-s <TT
3160+CLASS="REPLACEABLE"
3161+><I
3162+>packetsize</I
3163+></TT
3164+></CODE
3165+></DT
3166+><DD
3167+><P
3168+>Specifies the number of data bytes to be sent.
3169+The default is 56, which translates into 64 ICMP
3170+data bytes when combined with the 8 bytes of ICMP header data.
3171+ </P
3172+></DD
3173+><DT
3174+><CODE
3175+CLASS="OPTION"
3176+>-S <TT
3177+CLASS="REPLACEABLE"
3178+><I
3179+>sndbuf</I
3180+></TT
3181+></CODE
3182+></DT
3183+><DD
3184+><P
3185+>Set socket sndbuf. If not specified, it is selected to buffer
3186+not more than one packet.
3187+ </P
3188+></DD
3189+><DT
3190+><CODE
3191+CLASS="OPTION"
3192+>-t <TT
3193+CLASS="REPLACEABLE"
3194+><I
3195+>ttl</I
3196+></TT
3197+></CODE
3198+></DT
3199+><DD
3200+><P
3201+>Set the IP Time to Live.
3202+ </P
3203+></DD
3204+><DT
3205+><CODE
3206+CLASS="OPTION"
3207+>-T <TT
3208+CLASS="REPLACEABLE"
3209+><I
3210+>timestamp option</I
3211+></TT
3212+></CODE
3213+></DT
3214+><DD
3215+><P
3216+>Set special IP timestamp options.
3217+<TT
3218+CLASS="REPLACEABLE"
3219+><I
3220+>timestamp option</I
3221+></TT
3222+> may be either
3223+<TT
3224+CLASS="REPLACEABLE"
3225+><I
3226+>tsonly</I
3227+></TT
3228+> (only timestamps),
3229+<TT
3230+CLASS="REPLACEABLE"
3231+><I
3232+>tsandaddr</I
3233+></TT
3234+> (timestamps and addresses) or
3235+<TT
3236+CLASS="REPLACEABLE"
3237+><I
3238+>tsprespec host1 [host2 [host3 [host4]]]</I
3239+></TT
3240+>
3241+(timestamp prespecified hops).
3242+ </P
3243+></DD
3244+><DT
3245+><CODE
3246+CLASS="OPTION"
3247+>-M <TT
3248+CLASS="REPLACEABLE"
3249+><I
3250+>hint</I
3251+></TT
3252+></CODE
3253+></DT
3254+><DD
3255+><P
3256+>Select Path MTU Discovery strategy.
3257+<TT
3258+CLASS="REPLACEABLE"
3259+><I
3260+>hint</I
3261+></TT
3262+> may be either <TT
3263+CLASS="REPLACEABLE"
3264+><I
3265+>do</I
3266+></TT
3267+>
3268+(prohibit fragmentation, even local one),
3269+<TT
3270+CLASS="REPLACEABLE"
3271+><I
3272+>want</I
3273+></TT
3274+> (do PMTU discovery, fragment locally when packet size
3275+is large), or <TT
3276+CLASS="REPLACEABLE"
3277+><I
3278+>dont</I
3279+></TT
3280+> (do not set DF flag).
3281+ </P
3282+></DD
3283+><DT
3284+><CODE
3285+CLASS="OPTION"
3286+>-U</CODE
3287+></DT
3288+><DD
3289+><P
3290+>Print full user-to-user latency (the old behaviour). Normally
3291+<B
3292+CLASS="COMMAND"
3293+>ping</B
3294+>
3295+prints network round trip time, which can be different
3296+f.e. due to DNS failures.
3297+ </P
3298+></DD
3299+><DT
3300+><CODE
3301+CLASS="OPTION"
3302+>-v</CODE
3303+></DT
3304+><DD
3305+><P
3306+>Verbose output.
3307+ </P
3308+></DD
3309+><DT
3310+><CODE
3311+CLASS="OPTION"
3312+>-V</CODE
3313+></DT
3314+><DD
3315+><P
3316+>Show version and exit.
3317+ </P
3318+></DD
3319+><DT
3320+><CODE
3321+CLASS="OPTION"
3322+><A
3323+NAME="PING.DEADLINE"
3324+></A
3325+>-w <TT
3326+CLASS="REPLACEABLE"
3327+><I
3328+>deadline</I
3329+></TT
3330+></CODE
3331+></DT
3332+><DD
3333+><P
3334+>Specify a timeout, in seconds, before
3335+<B
3336+CLASS="COMMAND"
3337+>ping</B
3338+>
3339+exits regardless of how many
3340+packets have been sent or received. In this case
3341+<B
3342+CLASS="COMMAND"
3343+>ping</B
3344+>
3345+does not stop after
3346+<A
3347+HREF="r3.html#PING.COUNT"
3348+><TT
3349+CLASS="REPLACEABLE"
3350+><I
3351+>count</I
3352+></TT
3353+></A
3354+>
3355+packet are sent, it waits either for
3356+<A
3357+HREF="r3.html#PING.DEADLINE"
3358+><TT
3359+CLASS="REPLACEABLE"
3360+><I
3361+>deadline</I
3362+></TT
3363+></A
3364+>
3365+expire or until
3366+<A
3367+HREF="r3.html#PING.COUNT"
3368+><TT
3369+CLASS="REPLACEABLE"
3370+><I
3371+>count</I
3372+></TT
3373+></A
3374+>
3375+probes are answered or for some error notification from network.
3376+ </P
3377+></DD
3378+><DT
3379+><CODE
3380+CLASS="OPTION"
3381+>-W <TT
3382+CLASS="REPLACEABLE"
3383+><I
3384+>timeout</I
3385+></TT
3386+></CODE
3387+></DT
3388+><DD
3389+><P
3390+>Time to wait for a response, in seconds. The option affects only timeout
3391+in absense of any responses, otherwise <B
3392+CLASS="COMMAND"
3393+>ping</B
3394+> waits for two RTTs.
3395+ </P
3396+></DD
3397+></DL
3398+></DIV
3399+><P
3400+>When using <B
3401+CLASS="COMMAND"
3402+>ping</B
3403+> for fault isolation, it should first be run
3404+on the local host, to verify that the local network interface is up
3405+and running. Then, hosts and gateways further and further away should be
3406+``pinged''. Round-trip times and packet loss statistics are computed.
3407+If duplicate packets are received, they are not included in the packet
3408+loss calculation, although the round trip time of these packets is used
3409+in calculating the minimum/average/maximum round-trip time numbers.
3410+When the specified number of packets have been sent (and received) or
3411+if the program is terminated with a
3412+<CODE
3413+CLASS="CONSTANT"
3414+>SIGINT</CODE
3415+>, a brief summary is displayed. Shorter current statistics
3416+can be obtained without termination of process with signal
3417+<CODE
3418+CLASS="CONSTANT"
3419+>SIGQUIT</CODE
3420+>.</P
3421+><P
3422+>If <B
3423+CLASS="COMMAND"
3424+>ping</B
3425+> does not receive any reply packets at all it will
3426+exit with code 1. If a packet
3427+<A
3428+HREF="r3.html#PING.COUNT"
3429+><TT
3430+CLASS="REPLACEABLE"
3431+><I
3432+>count</I
3433+></TT
3434+></A
3435+>
3436+and
3437+<A
3438+HREF="r3.html#PING.DEADLINE"
3439+><TT
3440+CLASS="REPLACEABLE"
3441+><I
3442+>deadline</I
3443+></TT
3444+></A
3445+>
3446+are both specified, and fewer than
3447+<A
3448+HREF="r3.html#PING.COUNT"
3449+><TT
3450+CLASS="REPLACEABLE"
3451+><I
3452+>count</I
3453+></TT
3454+></A
3455+>
3456+packets are received by the time the
3457+<A
3458+HREF="r3.html#PING.DEADLINE"
3459+><TT
3460+CLASS="REPLACEABLE"
3461+><I
3462+>deadline</I
3463+></TT
3464+></A
3465+>
3466+has arrived, it will also exit with code 1.
3467+On other error it exits with code 2. Otherwise it exits with code 0. This
3468+makes it possible to use the exit code to see if a host is alive or
3469+not.</P
3470+><P
3471+>This program is intended for use in network testing, measurement and
3472+management.
3473+Because of the load it can impose on the network, it is unwise to use
3474+<B
3475+CLASS="COMMAND"
3476+>ping</B
3477+> during normal operations or from automated scripts.</P
3478+></DIV
3479+><DIV
3480+CLASS="REFSECT1"
3481+><A
3482+NAME="AEN362"
3483+></A
3484+><H2
3485+>ICMP PACKET DETAILS</H2
3486+><P
3487+>An IP header without options is 20 bytes.
3488+An ICMP ECHO_REQUEST packet contains an additional 8 bytes worth
3489+of ICMP header followed by an arbitrary amount of data.
3490+When a <TT
3491+CLASS="REPLACEABLE"
3492+><I
3493+>packetsize</I
3494+></TT
3495+> is given, this indicated the size of this
3496+extra piece of data (the default is 56). Thus the amount of data received
3497+inside of an IP packet of type ICMP ECHO_REPLY will always be 8 bytes
3498+more than the requested data space (the ICMP header).</P
3499+><P
3500+>If the data space is at least of size of <CODE
3501+CLASS="STRUCTNAME"
3502+>struct timeval</CODE
3503+>
3504+<B
3505+CLASS="COMMAND"
3506+>ping</B
3507+> uses the beginning bytes of this space to include
3508+a timestamp which it uses in the computation of round trip times.
3509+If the data space is shorter, no round trip times are given.</P
3510+></DIV
3511+><DIV
3512+CLASS="REFSECT1"
3513+><A
3514+NAME="AEN369"
3515+></A
3516+><H2
3517+>DUPLICATE AND DAMAGED PACKETS</H2
3518+><P
3519+><B
3520+CLASS="COMMAND"
3521+>ping</B
3522+> will report duplicate and damaged packets.
3523+Duplicate packets should never occur, and seem to be caused by
3524+inappropriate link-level retransmissions.
3525+Duplicates may occur in many situations and are rarely (if ever) a
3526+good sign, although the presence of low levels of duplicates may not
3527+always be cause for alarm.</P
3528+><P
3529+>Damaged packets are obviously serious cause for alarm and often
3530+indicate broken hardware somewhere in the
3531+<B
3532+CLASS="COMMAND"
3533+>ping</B
3534+> packet's path (in the network or in the hosts).</P
3535+></DIV
3536+><DIV
3537+CLASS="REFSECT1"
3538+><A
3539+NAME="AEN375"
3540+></A
3541+><H2
3542+>TRYING DIFFERENT DATA PATTERNS</H2
3543+><P
3544+>The (inter)network layer should never treat packets differently depending
3545+on the data contained in the data portion.
3546+Unfortunately, data-dependent problems have been known to sneak into
3547+networks and remain undetected for long periods of time.
3548+In many cases the particular pattern that will have problems is something
3549+that doesn't have sufficient ``transitions'', such as all ones or all
3550+zeros, or a pattern right at the edge, such as almost all zeros.
3551+It isn't necessarily enough to specify a data pattern of all zeros (for
3552+example) on the command line because the pattern that is of interest is
3553+at the data link level, and the relationship between what you type and
3554+what the controllers transmit can be complicated.</P
3555+><P
3556+>This means that if you have a data-dependent problem you will probably
3557+have to do a lot of testing to find it.
3558+If you are lucky, you may manage to find a file that either can't be sent
3559+across your network or that takes much longer to transfer than other
3560+similar length files.
3561+You can then examine this file for repeated patterns that you can test
3562+using the <CODE
3563+CLASS="OPTION"
3564+>-p</CODE
3565+> option of <B
3566+CLASS="COMMAND"
3567+>ping</B
3568+>.</P
3569+></DIV
3570+><DIV
3571+CLASS="REFSECT1"
3572+><A
3573+NAME="AEN381"
3574+></A
3575+><H2
3576+>TTL DETAILS</H2
3577+><P
3578+>The TTL value of an IP packet represents the maximum number of IP routers
3579+that the packet can go through before being thrown away.
3580+In current practice you can expect each router in the Internet to decrement
3581+the TTL field by exactly one.</P
3582+><P
3583+>The TCP/IP specification states that the TTL field for TCP
3584+packets should be set to 60, but many systems use smaller values
3585+(4.3 BSD uses 30, 4.2 used 15).</P
3586+><P
3587+>The maximum possible value of this field is 255, and most Unix systems set
3588+the TTL field of ICMP ECHO_REQUEST packets to 255.
3589+This is why you will find you can ``ping'' some hosts, but not reach them
3590+with
3591+<SPAN
3592+CLASS="CITEREFENTRY"
3593+><SPAN
3594+CLASS="REFENTRYTITLE"
3595+>telnet</SPAN
3596+>(1)</SPAN
3597+>
3598+or
3599+<SPAN
3600+CLASS="CITEREFENTRY"
3601+><SPAN
3602+CLASS="REFENTRYTITLE"
3603+>ftp</SPAN
3604+>(1)</SPAN
3605+>.</P
3606+><P
3607+>In normal operation ping prints the ttl value from the packet it receives.
3608+When a remote system receives a ping packet, it can do one of three things
3609+with the TTL field in its response:</P
3610+><P
3611+></P
3612+><UL
3613+><LI
3614+><P
3615+>Not change it; this is what Berkeley Unix systems did before the
3616+4.3BSD Tahoe release. In this case the TTL value in the received packet
3617+will be 255 minus the number of routers in the round-trip path.
3618+ </P
3619+></LI
3620+><LI
3621+><P
3622+>Set it to 255; this is what current Berkeley Unix systems do.
3623+In this case the TTL value in the received packet will be 255 minus the
3624+number of routers in the path <SPAN
3625+CLASS="emphasis"
3626+><I
3627+CLASS="EMPHASIS"
3628+>from</I
3629+></SPAN
3630+>
3631+the remote system <SPAN
3632+CLASS="emphasis"
3633+><I
3634+CLASS="EMPHASIS"
3635+>to</I
3636+></SPAN
3637+> the <B
3638+CLASS="COMMAND"
3639+>ping</B
3640+>ing host.
3641+ </P
3642+></LI
3643+><LI
3644+><P
3645+>Set it to some other value. Some machines use the same value for
3646+ICMP packets that they use for TCP packets, for example either 30 or 60.
3647+Others may use completely wild values.
3648+ </P
3649+></LI
3650+></UL
3651+></DIV
3652+><DIV
3653+CLASS="REFSECT1"
3654+><A
3655+NAME="AEN403"
3656+></A
3657+><H2
3658+>BUGS</H2
3659+><P
3660+></P
3661+><UL
3662+><LI
3663+><P
3664+>Many Hosts and Gateways ignore the RECORD_ROUTE option.
3665+ </P
3666+></LI
3667+><LI
3668+><P
3669+>The maximum IP header length is too small for options like
3670+RECORD_ROUTE to be completely useful.
3671+There's not much that that can be done about this, however.
3672+ </P
3673+></LI
3674+><LI
3675+><P
3676+>Flood pinging is not recommended in general, and flood pinging the
3677+broadcast address should only be done under very controlled conditions.
3678+ </P
3679+></LI
3680+></UL
3681+></DIV
3682+><DIV
3683+CLASS="REFSECT1"
3684+><A
3685+NAME="AEN412"
3686+></A
3687+><H2
3688+>SEE ALSO</H2
3689+><P
3690+><SPAN
3691+CLASS="CITEREFENTRY"
3692+><SPAN
3693+CLASS="REFENTRYTITLE"
3694+>netstat</SPAN
3695+>(1)</SPAN
3696+>,
3697+<SPAN
3698+CLASS="CITEREFENTRY"
3699+><SPAN
3700+CLASS="REFENTRYTITLE"
3701+>ifconfig</SPAN
3702+>(8)</SPAN
3703+>.</P
3704+></DIV
3705+><DIV
3706+CLASS="REFSECT1"
3707+><A
3708+NAME="AEN421"
3709+></A
3710+><H2
3711+>HISTORY</H2
3712+><P
3713+>The <B
3714+CLASS="COMMAND"
3715+>ping</B
3716+> command appeared in 4.3BSD.</P
3717+><P
3718+>The version described here is its descendant specific to Linux.</P
3719+></DIV
3720+><DIV
3721+CLASS="REFSECT1"
3722+><A
3723+NAME="AEN426"
3724+></A
3725+><H2
3726+>SECURITY</H2
3727+><P
3728+><B
3729+CLASS="COMMAND"
3730+>ping</B
3731+> requires <CODE
3732+CLASS="CONSTANT"
3733+>CAP_NET_RAWIO</CODE
3734+> capability
3735+to be executed. It may be used as set-uid root.</P
3736+></DIV
3737+><DIV
3738+CLASS="REFSECT1"
3739+><A
3740+NAME="AEN431"
3741+></A
3742+><H2
3743+>AVAILABILITY</H2
3744+><P
3745+><B
3746+CLASS="COMMAND"
3747+>ping</B
3748+> is part of <TT
3749+CLASS="FILENAME"
3750+>iputils</TT
3751+> package
3752+and the latest versions are available in source form at
3753+<A
3754+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
3755+TARGET="_top"
3756+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
3757+>.</P
3758+></DIV
3759+><DIV
3760+CLASS="NAVFOOTER"
3761+><HR
3762+ALIGN="LEFT"
3763+WIDTH="100%"><TABLE
3764+SUMMARY="Footer navigation table"
3765+WIDTH="100%"
3766+BORDER="0"
3767+CELLPADDING="0"
3768+CELLSPACING="0"
3769+><TR
3770+><TD
3771+WIDTH="33%"
3772+ALIGN="left"
3773+VALIGN="top"
3774+><A
3775+HREF="index.html"
3776+ACCESSKEY="P"
3777+>Prev</A
3778+></TD
3779+><TD
3780+WIDTH="34%"
3781+ALIGN="center"
3782+VALIGN="top"
3783+><A
3784+HREF="index.html"
3785+ACCESSKEY="H"
3786+>Home</A
3787+></TD
3788+><TD
3789+WIDTH="33%"
3790+ALIGN="right"
3791+VALIGN="top"
3792+><A
3793+HREF="r437.html"
3794+ACCESSKEY="N"
3795+>Next</A
3796+></TD
3797+></TR
3798+><TR
3799+><TD
3800+WIDTH="33%"
3801+ALIGN="left"
3802+VALIGN="top"
3803+>System Manager's Manual: iputils</TD
3804+><TD
3805+WIDTH="34%"
3806+ALIGN="center"
3807+VALIGN="top"
3808+>&nbsp;</TD
3809+><TD
3810+WIDTH="33%"
3811+ALIGN="right"
3812+VALIGN="top"
3813+>arping</TD
3814+></TR
3815+></TABLE
3816+></DIV
3817+></BODY
3818+></HTML
3819+>
3820\ No newline at end of file
3821diff -Naur iputils-s20100418.orig/doc/r437.html iputils-s20100418/doc/r437.html
3822--- iputils-s20100418.orig/doc/r437.html 1969-12-31 19:00:00.000000000 -0500
3823+++ iputils-s20100418/doc/r437.html 2010-08-04 22:00:32.385590132 -0400
3824@@ -0,0 +1,598 @@
3825+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
3826+<HTML
3827+><HEAD
3828+><TITLE
3829+>arping</TITLE
3830+><META
3831+NAME="GENERATOR"
3832+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
3833+REL="HOME"
3834+TITLE="System Manager's Manual: iputils"
3835+HREF="index.html"><LINK
3836+REL="PREVIOUS"
3837+TITLE="ping"
3838+HREF="r3.html"><LINK
3839+REL="NEXT"
3840+TITLE="clockdiff"
3841+HREF="r596.html"></HEAD
3842+><BODY
3843+CLASS="REFENTRY"
3844+BGCOLOR="#FFFFFF"
3845+TEXT="#000000"
3846+LINK="#0000FF"
3847+VLINK="#840084"
3848+ALINK="#0000FF"
3849+><DIV
3850+CLASS="NAVHEADER"
3851+><TABLE
3852+SUMMARY="Header navigation table"
3853+WIDTH="100%"
3854+BORDER="0"
3855+CELLPADDING="0"
3856+CELLSPACING="0"
3857+><TR
3858+><TH
3859+COLSPAN="3"
3860+ALIGN="center"
3861+>System Manager's Manual: iputils</TH
3862+></TR
3863+><TR
3864+><TD
3865+WIDTH="10%"
3866+ALIGN="left"
3867+VALIGN="bottom"
3868+><A
3869+HREF="r3.html"
3870+ACCESSKEY="P"
3871+>Prev</A
3872+></TD
3873+><TD
3874+WIDTH="80%"
3875+ALIGN="center"
3876+VALIGN="bottom"
3877+></TD
3878+><TD
3879+WIDTH="10%"
3880+ALIGN="right"
3881+VALIGN="bottom"
3882+><A
3883+HREF="r596.html"
3884+ACCESSKEY="N"
3885+>Next</A
3886+></TD
3887+></TR
3888+></TABLE
3889+><HR
3890+ALIGN="LEFT"
3891+WIDTH="100%"></DIV
3892+><H1
3893+><A
3894+NAME="ARPING"
3895+></A
3896+>arping</H1
3897+><DIV
3898+CLASS="REFNAMEDIV"
3899+><A
3900+NAME="AEN442"
3901+></A
3902+><H2
3903+>Name</H2
3904+>arping&nbsp;--&nbsp;send ARP REQUEST to a neighbour host</DIV
3905+><DIV
3906+CLASS="REFSYNOPSISDIV"
3907+><A
3908+NAME="AEN445"
3909+></A
3910+><H2
3911+>Synopsis</H2
3912+><P
3913+><B
3914+CLASS="COMMAND"
3915+>arping</B
3916+> [<CODE
3917+CLASS="OPTION"
3918+>-AbDfhqUV</CODE
3919+>] [-c <TT
3920+CLASS="REPLACEABLE"
3921+><I
3922+>count</I
3923+></TT
3924+>] [-w <TT
3925+CLASS="REPLACEABLE"
3926+><I
3927+>deadline</I
3928+></TT
3929+>] [-s <TT
3930+CLASS="REPLACEABLE"
3931+><I
3932+>source</I
3933+></TT
3934+>] {-I <TT
3935+CLASS="REPLACEABLE"
3936+><I
3937+>interface</I
3938+></TT
3939+>} {<TT
3940+CLASS="REPLACEABLE"
3941+><I
3942+>destination</I
3943+></TT
3944+>}</P
3945+></DIV
3946+><DIV
3947+CLASS="REFSECT1"
3948+><A
3949+NAME="AEN460"
3950+></A
3951+><H2
3952+>DESCRIPTION</H2
3953+><P
3954+>Ping <TT
3955+CLASS="REPLACEABLE"
3956+><I
3957+>destination</I
3958+></TT
3959+> on device <TT
3960+CLASS="REPLACEABLE"
3961+><I
3962+>interface</I
3963+></TT
3964+> by ARP packets,
3965+using source address <TT
3966+CLASS="REPLACEABLE"
3967+><I
3968+>source</I
3969+></TT
3970+>.</P
3971+></DIV
3972+><DIV
3973+CLASS="REFSECT1"
3974+><A
3975+NAME="AEN466"
3976+></A
3977+><H2
3978+>OPTIONS</H2
3979+><P
3980+></P
3981+><DIV
3982+CLASS="VARIABLELIST"
3983+><DL
3984+><DT
3985+><CODE
3986+CLASS="OPTION"
3987+>-A</CODE
3988+></DT
3989+><DD
3990+><P
3991+>The same as <CODE
3992+CLASS="OPTION"
3993+>-U</CODE
3994+>, but ARP REPLY packets used instead
3995+of ARP REQUEST.
3996+ </P
3997+></DD
3998+><DT
3999+><CODE
4000+CLASS="OPTION"
4001+>-b</CODE
4002+></DT
4003+><DD
4004+><P
4005+>Send only MAC level broadcasts. Normally <B
4006+CLASS="COMMAND"
4007+>arping</B
4008+> starts
4009+from sending broadcast, and switch to unicast after reply received.
4010+ </P
4011+></DD
4012+><DT
4013+><CODE
4014+CLASS="OPTION"
4015+><A
4016+NAME="ARPING.COUNT"
4017+></A
4018+>-c <TT
4019+CLASS="REPLACEABLE"
4020+><I
4021+>count</I
4022+></TT
4023+></CODE
4024+></DT
4025+><DD
4026+><P
4027+>Stop after sending <TT
4028+CLASS="REPLACEABLE"
4029+><I
4030+>count</I
4031+></TT
4032+> ARP REQUEST
4033+packets. With
4034+<A
4035+HREF="r437.html#ARPING.DEADLINE"
4036+><TT
4037+CLASS="REPLACEABLE"
4038+><I
4039+>deadline</I
4040+></TT
4041+></A
4042+>
4043+option, <B
4044+CLASS="COMMAND"
4045+>arping</B
4046+> waits for
4047+<TT
4048+CLASS="REPLACEABLE"
4049+><I
4050+>count</I
4051+></TT
4052+> ARP REPLY packets, until the timeout expires.
4053+ </P
4054+></DD
4055+><DT
4056+><CODE
4057+CLASS="OPTION"
4058+>-D</CODE
4059+></DT
4060+><DD
4061+><P
4062+>Duplicate address detection mode (DAD). See
4063+<A
4064+HREF="ftp://ftp.isi.edu/in-notes/rfc2131.txt"
4065+TARGET="_top"
4066+>RFC2131, 4.4.1</A
4067+>.
4068+Returns 0, if DAD succeeded i.e. no replies are received
4069+ </P
4070+></DD
4071+><DT
4072+><CODE
4073+CLASS="OPTION"
4074+>-f</CODE
4075+></DT
4076+><DD
4077+><P
4078+>Finish after the first reply confirming that target is alive.
4079+ </P
4080+></DD
4081+><DT
4082+><CODE
4083+CLASS="OPTION"
4084+><A
4085+NAME="OPT.INTERFACE"
4086+></A
4087+>-I <TT
4088+CLASS="REPLACEABLE"
4089+><I
4090+>interface</I
4091+></TT
4092+></CODE
4093+></DT
4094+><DD
4095+><P
4096+>Name of network device where to send ARP REQUEST packets. This option
4097+is required.
4098+ </P
4099+></DD
4100+><DT
4101+><CODE
4102+CLASS="OPTION"
4103+>-h</CODE
4104+></DT
4105+><DD
4106+><P
4107+>Print help page and exit.
4108+ </P
4109+></DD
4110+><DT
4111+><CODE
4112+CLASS="OPTION"
4113+>-q</CODE
4114+></DT
4115+><DD
4116+><P
4117+>Quiet output. Nothing is displayed.
4118+ </P
4119+></DD
4120+><DT
4121+><CODE
4122+CLASS="OPTION"
4123+><A
4124+NAME="OPT.SOURCE"
4125+></A
4126+>-s <TT
4127+CLASS="REPLACEABLE"
4128+><I
4129+>source</I
4130+></TT
4131+></CODE
4132+></DT
4133+><DD
4134+><P
4135+>IP source address to use in ARP packets.
4136+If this option is absent, source address is:
4137+ <P
4138+></P
4139+><UL
4140+><LI
4141+><P
4142+>In DAD mode (with option <CODE
4143+CLASS="OPTION"
4144+>-D</CODE
4145+>) set to 0.0.0.0.
4146+ </P
4147+></LI
4148+><LI
4149+><P
4150+>In Unsolicited ARP mode (with options <CODE
4151+CLASS="OPTION"
4152+>-U</CODE
4153+> or <CODE
4154+CLASS="OPTION"
4155+>-A</CODE
4156+>)
4157+set to <TT
4158+CLASS="REPLACEABLE"
4159+><I
4160+>destination</I
4161+></TT
4162+>.
4163+ </P
4164+></LI
4165+><LI
4166+><P
4167+>Otherwise, it is calculated from routing tables.
4168+ </P
4169+></LI
4170+></UL
4171+>
4172+ </P
4173+></DD
4174+><DT
4175+><CODE
4176+CLASS="OPTION"
4177+>-U</CODE
4178+></DT
4179+><DD
4180+><P
4181+>Unsolicited ARP mode to update neighbours' ARP caches.
4182+No replies are expected.
4183+ </P
4184+></DD
4185+><DT
4186+><CODE
4187+CLASS="OPTION"
4188+>-V</CODE
4189+></DT
4190+><DD
4191+><P
4192+>Print version of the program and exit.
4193+ </P
4194+></DD
4195+><DT
4196+><CODE
4197+CLASS="OPTION"
4198+><A
4199+NAME="ARPING.DEADLINE"
4200+></A
4201+>-w <TT
4202+CLASS="REPLACEABLE"
4203+><I
4204+>deadline</I
4205+></TT
4206+></CODE
4207+></DT
4208+><DD
4209+><P
4210+>Specify a timeout, in seconds, before
4211+<B
4212+CLASS="COMMAND"
4213+>arping</B
4214+>
4215+exits regardless of how many
4216+packets have been sent or received. In this case
4217+<B
4218+CLASS="COMMAND"
4219+>arping</B
4220+>
4221+does not stop after
4222+<A
4223+HREF="r437.html#ARPING.COUNT"
4224+><TT
4225+CLASS="REPLACEABLE"
4226+><I
4227+>count</I
4228+></TT
4229+></A
4230+>
4231+packet are sent, it waits either for
4232+<A
4233+HREF="r437.html#ARPING.DEADLINE"
4234+><TT
4235+CLASS="REPLACEABLE"
4236+><I
4237+>deadline</I
4238+></TT
4239+></A
4240+>
4241+expire or until
4242+<A
4243+HREF="r437.html#ARPING.COUNT"
4244+><TT
4245+CLASS="REPLACEABLE"
4246+><I
4247+>count</I
4248+></TT
4249+></A
4250+>
4251+probes are answered.
4252+ </P
4253+></DD
4254+></DL
4255+></DIV
4256+></DIV
4257+><DIV
4258+CLASS="REFSECT1"
4259+><A
4260+NAME="AEN564"
4261+></A
4262+><H2
4263+>SEE ALSO</H2
4264+><P
4265+><A
4266+HREF="r3.html"
4267+><SPAN
4268+CLASS="CITEREFENTRY"
4269+><SPAN
4270+CLASS="REFENTRYTITLE"
4271+>ping</SPAN
4272+>(8)</SPAN
4273+></A
4274+>,
4275+<A
4276+HREF="r596.html"
4277+><SPAN
4278+CLASS="CITEREFENTRY"
4279+><SPAN
4280+CLASS="REFENTRYTITLE"
4281+>clockdiff</SPAN
4282+>(8)</SPAN
4283+></A
4284+>,
4285+<A
4286+HREF="r790.html"
4287+><SPAN
4288+CLASS="CITEREFENTRY"
4289+><SPAN
4290+CLASS="REFENTRYTITLE"
4291+>tracepath</SPAN
4292+>(8)</SPAN
4293+></A
4294+>.</P
4295+></DIV
4296+><DIV
4297+CLASS="REFSECT1"
4298+><A
4299+NAME="AEN579"
4300+></A
4301+><H2
4302+>AUTHOR</H2
4303+><P
4304+><B
4305+CLASS="COMMAND"
4306+>arping</B
4307+> was written by
4308+<A
4309+HREF="mailto:kuznet@ms2.inr.ac.ru"
4310+TARGET="_top"
4311+>Alexey Kuznetsov
4312+&lt;kuznet@ms2.inr.ac.ru&gt;</A
4313+>.
4314+It is now maintained by
4315+<A
4316+HREF="mailto:yoshfuji@skbuff.net"
4317+TARGET="_top"
4318+>YOSHIFUJI Hideaki
4319+&lt;yoshfuji@skbuff.net&gt;</A
4320+>.</P
4321+></DIV
4322+><DIV
4323+CLASS="REFSECT1"
4324+><A
4325+NAME="AEN585"
4326+></A
4327+><H2
4328+>SECURITY</H2
4329+><P
4330+><B
4331+CLASS="COMMAND"
4332+>arping</B
4333+> requires <CODE
4334+CLASS="CONSTANT"
4335+>CAP_NET_RAWIO</CODE
4336+> capability
4337+to be executed. It is not recommended to be used as set-uid root,
4338+because it allows user to modify ARP caches of neighbour hosts.</P
4339+></DIV
4340+><DIV
4341+CLASS="REFSECT1"
4342+><A
4343+NAME="AEN590"
4344+></A
4345+><H2
4346+>AVAILABILITY</H2
4347+><P
4348+><B
4349+CLASS="COMMAND"
4350+>arping</B
4351+> is part of <TT
4352+CLASS="FILENAME"
4353+>iputils</TT
4354+> package
4355+and the latest versions are available in source form at
4356+<A
4357+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
4358+TARGET="_top"
4359+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
4360+>.</P
4361+></DIV
4362+><DIV
4363+CLASS="NAVFOOTER"
4364+><HR
4365+ALIGN="LEFT"
4366+WIDTH="100%"><TABLE
4367+SUMMARY="Footer navigation table"
4368+WIDTH="100%"
4369+BORDER="0"
4370+CELLPADDING="0"
4371+CELLSPACING="0"
4372+><TR
4373+><TD
4374+WIDTH="33%"
4375+ALIGN="left"
4376+VALIGN="top"
4377+><A
4378+HREF="r3.html"
4379+ACCESSKEY="P"
4380+>Prev</A
4381+></TD
4382+><TD
4383+WIDTH="34%"
4384+ALIGN="center"
4385+VALIGN="top"
4386+><A
4387+HREF="index.html"
4388+ACCESSKEY="H"
4389+>Home</A
4390+></TD
4391+><TD
4392+WIDTH="33%"
4393+ALIGN="right"
4394+VALIGN="top"
4395+><A
4396+HREF="r596.html"
4397+ACCESSKEY="N"
4398+>Next</A
4399+></TD
4400+></TR
4401+><TR
4402+><TD
4403+WIDTH="33%"
4404+ALIGN="left"
4405+VALIGN="top"
4406+>ping</TD
4407+><TD
4408+WIDTH="34%"
4409+ALIGN="center"
4410+VALIGN="top"
4411+>&nbsp;</TD
4412+><TD
4413+WIDTH="33%"
4414+ALIGN="right"
4415+VALIGN="top"
4416+>clockdiff</TD
4417+></TR
4418+></TABLE
4419+></DIV
4420+></BODY
4421+></HTML
4422+>
4423\ No newline at end of file
4424diff -Naur iputils-s20100418.orig/doc/r596.html iputils-s20100418/doc/r596.html
4425--- iputils-s20100418.orig/doc/r596.html 1969-12-31 19:00:00.000000000 -0500
4426+++ iputils-s20100418/doc/r596.html 2010-08-04 22:00:32.397576962 -0400
4427@@ -0,0 +1,428 @@
4428+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
4429+<HTML
4430+><HEAD
4431+><TITLE
4432+>clockdiff</TITLE
4433+><META
4434+NAME="GENERATOR"
4435+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
4436+REL="HOME"
4437+TITLE="System Manager's Manual: iputils"
4438+HREF="index.html"><LINK
4439+REL="PREVIOUS"
4440+TITLE="arping"
4441+HREF="r437.html"><LINK
4442+REL="NEXT"
4443+TITLE="rarpd"
4444+HREF="r691.html"></HEAD
4445+><BODY
4446+CLASS="REFENTRY"
4447+BGCOLOR="#FFFFFF"
4448+TEXT="#000000"
4449+LINK="#0000FF"
4450+VLINK="#840084"
4451+ALINK="#0000FF"
4452+><DIV
4453+CLASS="NAVHEADER"
4454+><TABLE
4455+SUMMARY="Header navigation table"
4456+WIDTH="100%"
4457+BORDER="0"
4458+CELLPADDING="0"
4459+CELLSPACING="0"
4460+><TR
4461+><TH
4462+COLSPAN="3"
4463+ALIGN="center"
4464+>System Manager's Manual: iputils</TH
4465+></TR
4466+><TR
4467+><TD
4468+WIDTH="10%"
4469+ALIGN="left"
4470+VALIGN="bottom"
4471+><A
4472+HREF="r437.html"
4473+ACCESSKEY="P"
4474+>Prev</A
4475+></TD
4476+><TD
4477+WIDTH="80%"
4478+ALIGN="center"
4479+VALIGN="bottom"
4480+></TD
4481+><TD
4482+WIDTH="10%"
4483+ALIGN="right"
4484+VALIGN="bottom"
4485+><A
4486+HREF="r691.html"
4487+ACCESSKEY="N"
4488+>Next</A
4489+></TD
4490+></TR
4491+></TABLE
4492+><HR
4493+ALIGN="LEFT"
4494+WIDTH="100%"></DIV
4495+><H1
4496+><A
4497+NAME="CLOCKDIFF"
4498+></A
4499+>clockdiff</H1
4500+><DIV
4501+CLASS="REFNAMEDIV"
4502+><A
4503+NAME="AEN601"
4504+></A
4505+><H2
4506+>Name</H2
4507+>clockdiff&nbsp;--&nbsp;measure clock difference between hosts</DIV
4508+><DIV
4509+CLASS="REFSYNOPSISDIV"
4510+><A
4511+NAME="AEN604"
4512+></A
4513+><H2
4514+>Synopsis</H2
4515+><P
4516+><B
4517+CLASS="COMMAND"
4518+>clockdiff</B
4519+> [<CODE
4520+CLASS="OPTION"
4521+>-o</CODE
4522+>] [<CODE
4523+CLASS="OPTION"
4524+>-o1</CODE
4525+>] {<TT
4526+CLASS="REPLACEABLE"
4527+><I
4528+>destination</I
4529+></TT
4530+>}</P
4531+></DIV
4532+><DIV
4533+CLASS="REFSECT1"
4534+><A
4535+NAME="AEN613"
4536+></A
4537+><H2
4538+>DESCRIPTION</H2
4539+><P
4540+><B
4541+CLASS="COMMAND"
4542+>clockdiff</B
4543+> Measures clock difference between us and
4544+<TT
4545+CLASS="REPLACEABLE"
4546+><I
4547+>destination</I
4548+></TT
4549+> with 1 msec resolution using ICMP TIMESTAMP
4550+<A
4551+HREF="r596.html#CLOCKDIFF.ICMP-TIMESTAMP"
4552+>[2]</A
4553+>
4554+packets or, optionally, IP TIMESTAMP option
4555+<A
4556+HREF="r596.html#CLOCKDIFF.IP-TIMESTAMP"
4557+>[3]</A
4558+>
4559+option added to ICMP ECHO.
4560+<A
4561+HREF="r596.html#CLOCKDIFF.ICMP-ECHO"
4562+>[1]</A
4563+></P
4564+></DIV
4565+><DIV
4566+CLASS="REFSECT1"
4567+><A
4568+NAME="AEN621"
4569+></A
4570+><H2
4571+>OPTIONS</H2
4572+><P
4573+></P
4574+><DIV
4575+CLASS="VARIABLELIST"
4576+><DL
4577+><DT
4578+><CODE
4579+CLASS="OPTION"
4580+>-o</CODE
4581+></DT
4582+><DD
4583+><P
4584+>Use IP TIMESTAMP with ICMP ECHO instead of ICMP TIMESTAMP
4585+messages. It is useful with some destinations, which do not support
4586+ICMP TIMESTAMP (f.e. Solaris &lt;2.4).
4587+ </P
4588+></DD
4589+><DT
4590+><CODE
4591+CLASS="OPTION"
4592+>-o1</CODE
4593+></DT
4594+><DD
4595+><P
4596+>Slightly different form of <CODE
4597+CLASS="OPTION"
4598+>-o</CODE
4599+>, namely it uses three-term
4600+IP TIMESTAMP with prespecified hop addresses instead of four term one.
4601+What flavor works better depends on target host. Particularly,
4602+<CODE
4603+CLASS="OPTION"
4604+>-o</CODE
4605+> is better for Linux.
4606+ </P
4607+></DD
4608+></DL
4609+></DIV
4610+></DIV
4611+><DIV
4612+CLASS="REFSECT1"
4613+><A
4614+NAME="AEN636"
4615+></A
4616+><H2
4617+>WARNINGS</H2
4618+><P
4619+></P
4620+><UL
4621+><LI
4622+><P
4623+>Some nodes (Cisco) use non-standard timestamps, which is allowed
4624+by RFC, but makes timestamps mostly useless.
4625+ </P
4626+></LI
4627+><LI
4628+><P
4629+>Some nodes generate messed timestamps (Solaris&gt;2.4), when
4630+run <B
4631+CLASS="COMMAND"
4632+>xntpd</B
4633+>. Seems, its IP stack uses a corrupted clock source,
4634+which is synchronized to time-of-day clock periodically and jumps
4635+randomly making timestamps mostly useless. Good news is that you can
4636+use NTP in this case, which is even better.
4637+ </P
4638+></LI
4639+><LI
4640+><P
4641+><B
4642+CLASS="COMMAND"
4643+>clockdiff</B
4644+> shows difference in time modulo 24 days.
4645+ </P
4646+></LI
4647+></UL
4648+></DIV
4649+><DIV
4650+CLASS="REFSECT1"
4651+><A
4652+NAME="AEN647"
4653+></A
4654+><H2
4655+>SEE ALSO</H2
4656+><P
4657+><A
4658+HREF="r3.html"
4659+><SPAN
4660+CLASS="CITEREFENTRY"
4661+><SPAN
4662+CLASS="REFENTRYTITLE"
4663+>ping</SPAN
4664+>(8)</SPAN
4665+></A
4666+>,
4667+<A
4668+HREF="r437.html"
4669+><SPAN
4670+CLASS="CITEREFENTRY"
4671+><SPAN
4672+CLASS="REFENTRYTITLE"
4673+>arping</SPAN
4674+>(8)</SPAN
4675+></A
4676+>,
4677+<A
4678+HREF="r790.html"
4679+><SPAN
4680+CLASS="CITEREFENTRY"
4681+><SPAN
4682+CLASS="REFENTRYTITLE"
4683+>tracepath</SPAN
4684+>(8)</SPAN
4685+></A
4686+>.</P
4687+></DIV
4688+><DIV
4689+CLASS="REFSECT1"
4690+><A
4691+NAME="AEN662"
4692+></A
4693+><H2
4694+>REFERENCES</H2
4695+><P
4696+>[1] <A
4697+NAME="CLOCKDIFF.ICMP-ECHO"
4698+></A
4699+>ICMP ECHO,
4700+<A
4701+HREF="ftp://ftp.isi.edu/in-notes/rfc792.txt"
4702+TARGET="_top"
4703+>RFC0792, page 14</A
4704+>.</P
4705+><P
4706+>[2] <A
4707+NAME="CLOCKDIFF.ICMP-TIMESTAMP"
4708+></A
4709+>ICMP TIMESTAMP,
4710+<A
4711+HREF="ftp://ftp.isi.edu/in-notes/rfc792.txt"
4712+TARGET="_top"
4713+>RFC0792, page 16</A
4714+>.</P
4715+><P
4716+>[3] <A
4717+NAME="CLOCKDIFF.IP-TIMESTAMP"
4718+></A
4719+>IP TIMESTAMP option,
4720+<A
4721+HREF="ftp://ftp.isi.edu/in-notes/rfc791.txt"
4722+TARGET="_top"
4723+>RFC0791, 3.1, page 16</A
4724+>.</P
4725+></DIV
4726+><DIV
4727+CLASS="REFSECT1"
4728+><A
4729+NAME="AEN673"
4730+></A
4731+><H2
4732+>AUTHOR</H2
4733+><P
4734+><B
4735+CLASS="COMMAND"
4736+>clockdiff</B
4737+> was compiled by
4738+<A
4739+HREF="mailto:kuznet@ms2.inr.ac.ru"
4740+TARGET="_top"
4741+>Alexey Kuznetsov
4742+&lt;kuznet@ms2.inr.ac.ru&gt;</A
4743+>. It was based on code borrowed
4744+from BSD <B
4745+CLASS="COMMAND"
4746+>timed</B
4747+> daemon.
4748+It is now maintained by
4749+<A
4750+HREF="mailto:yoshfuji@skbuff.net"
4751+TARGET="_top"
4752+>YOSHIFUJI Hideaki
4753+&lt;yoshfuji@skbuff.net&gt;</A
4754+>.</P
4755+></DIV
4756+><DIV
4757+CLASS="REFSECT1"
4758+><A
4759+NAME="AEN680"
4760+></A
4761+><H2
4762+>SECURITY</H2
4763+><P
4764+><B
4765+CLASS="COMMAND"
4766+>clockdiff</B
4767+> requires <CODE
4768+CLASS="CONSTANT"
4769+>CAP_NET_RAWIO</CODE
4770+> capability
4771+to be executed. It is safe to be used as set-uid root.</P
4772+></DIV
4773+><DIV
4774+CLASS="REFSECT1"
4775+><A
4776+NAME="AEN685"
4777+></A
4778+><H2
4779+>AVAILABILITY</H2
4780+><P
4781+><B
4782+CLASS="COMMAND"
4783+>clockdiff</B
4784+> is part of <TT
4785+CLASS="FILENAME"
4786+>iputils</TT
4787+> package
4788+and the latest versions are available in source form at
4789+<A
4790+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
4791+TARGET="_top"
4792+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
4793+>.</P
4794+></DIV
4795+><DIV
4796+CLASS="NAVFOOTER"
4797+><HR
4798+ALIGN="LEFT"
4799+WIDTH="100%"><TABLE
4800+SUMMARY="Footer navigation table"
4801+WIDTH="100%"
4802+BORDER="0"
4803+CELLPADDING="0"
4804+CELLSPACING="0"
4805+><TR
4806+><TD
4807+WIDTH="33%"
4808+ALIGN="left"
4809+VALIGN="top"
4810+><A
4811+HREF="r437.html"
4812+ACCESSKEY="P"
4813+>Prev</A
4814+></TD
4815+><TD
4816+WIDTH="34%"
4817+ALIGN="center"
4818+VALIGN="top"
4819+><A
4820+HREF="index.html"
4821+ACCESSKEY="H"
4822+>Home</A
4823+></TD
4824+><TD
4825+WIDTH="33%"
4826+ALIGN="right"
4827+VALIGN="top"
4828+><A
4829+HREF="r691.html"
4830+ACCESSKEY="N"
4831+>Next</A
4832+></TD
4833+></TR
4834+><TR
4835+><TD
4836+WIDTH="33%"
4837+ALIGN="left"
4838+VALIGN="top"
4839+>arping</TD
4840+><TD
4841+WIDTH="34%"
4842+ALIGN="center"
4843+VALIGN="top"
4844+>&nbsp;</TD
4845+><TD
4846+WIDTH="33%"
4847+ALIGN="right"
4848+VALIGN="top"
4849+>rarpd</TD
4850+></TR
4851+></TABLE
4852+></DIV
4853+></BODY
4854+></HTML
4855+>
4856\ No newline at end of file
4857diff -Naur iputils-s20100418.orig/doc/r691.html iputils-s20100418/doc/r691.html
4858--- iputils-s20100418.orig/doc/r691.html 1969-12-31 19:00:00.000000000 -0500
4859+++ iputils-s20100418/doc/r691.html 2010-08-04 22:00:32.405576771 -0400
4860@@ -0,0 +1,431 @@
4861+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
4862+<HTML
4863+><HEAD
4864+><TITLE
4865+>rarpd</TITLE
4866+><META
4867+NAME="GENERATOR"
4868+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
4869+REL="HOME"
4870+TITLE="System Manager's Manual: iputils"
4871+HREF="index.html"><LINK
4872+REL="PREVIOUS"
4873+TITLE="clockdiff"
4874+HREF="r596.html"><LINK
4875+REL="NEXT"
4876+TITLE="tracepath"
4877+HREF="r790.html"></HEAD
4878+><BODY
4879+CLASS="REFENTRY"
4880+BGCOLOR="#FFFFFF"
4881+TEXT="#000000"
4882+LINK="#0000FF"
4883+VLINK="#840084"
4884+ALINK="#0000FF"
4885+><DIV
4886+CLASS="NAVHEADER"
4887+><TABLE
4888+SUMMARY="Header navigation table"
4889+WIDTH="100%"
4890+BORDER="0"
4891+CELLPADDING="0"
4892+CELLSPACING="0"
4893+><TR
4894+><TH
4895+COLSPAN="3"
4896+ALIGN="center"
4897+>System Manager's Manual: iputils</TH
4898+></TR
4899+><TR
4900+><TD
4901+WIDTH="10%"
4902+ALIGN="left"
4903+VALIGN="bottom"
4904+><A
4905+HREF="r596.html"
4906+ACCESSKEY="P"
4907+>Prev</A
4908+></TD
4909+><TD
4910+WIDTH="80%"
4911+ALIGN="center"
4912+VALIGN="bottom"
4913+></TD
4914+><TD
4915+WIDTH="10%"
4916+ALIGN="right"
4917+VALIGN="bottom"
4918+><A
4919+HREF="r790.html"
4920+ACCESSKEY="N"
4921+>Next</A
4922+></TD
4923+></TR
4924+></TABLE
4925+><HR
4926+ALIGN="LEFT"
4927+WIDTH="100%"></DIV
4928+><H1
4929+><A
4930+NAME="RARPD"
4931+></A
4932+>rarpd</H1
4933+><DIV
4934+CLASS="REFNAMEDIV"
4935+><A
4936+NAME="AEN696"
4937+></A
4938+><H2
4939+>Name</H2
4940+>rarpd&nbsp;--&nbsp;answer RARP REQUESTs</DIV
4941+><DIV
4942+CLASS="REFSYNOPSISDIV"
4943+><A
4944+NAME="AEN699"
4945+></A
4946+><H2
4947+>Synopsis</H2
4948+><P
4949+><B
4950+CLASS="COMMAND"
4951+>arping</B
4952+> [<CODE
4953+CLASS="OPTION"
4954+>-aAvde</CODE
4955+>] [-b <TT
4956+CLASS="REPLACEABLE"
4957+><I
4958+>bootdir</I
4959+></TT
4960+>] [<TT
4961+CLASS="REPLACEABLE"
4962+><I
4963+>interface</I
4964+></TT
4965+>]</P
4966+></DIV
4967+><DIV
4968+CLASS="REFSECT1"
4969+><A
4970+NAME="AEN708"
4971+></A
4972+><H2
4973+>DESCRIPTION</H2
4974+><P
4975+>Listens
4976+<A
4977+HREF="ftp://ftp.isi.edu/in-notes/rfc903.txt"
4978+TARGET="_top"
4979+>RARP</A
4980+>
4981+requests from clients. Provided MAC address of client
4982+is found in <TT
4983+CLASS="FILENAME"
4984+>/etc/ethers</TT
4985+> database and
4986+obtained host name is resolvable to an IP address appropriate
4987+for attached network, <B
4988+CLASS="COMMAND"
4989+>rarpd</B
4990+> answers to client with RARPD
4991+reply carrying an IP address.</P
4992+><P
4993+>To allow multiple boot servers on the network <B
4994+CLASS="COMMAND"
4995+>rarpd</B
4996+>
4997+optionally checks for presence Sun-like bootable image in TFTP directory.
4998+It should have form <KBD
4999+CLASS="USERINPUT"
5000+>Hexadecimal_IP.ARCH</KBD
5001+>, f.e. to load
5002+sparc 193.233.7.98 <TT
5003+CLASS="FILENAME"
5004+>C1E90762.SUN4M</TT
5005+> is linked to
5006+an image appropriate for SUM4M in directory <TT
5007+CLASS="FILENAME"
5008+>/etc/tftpboot</TT
5009+>.</P
5010+></DIV
5011+><DIV
5012+CLASS="REFSECT1"
5013+><A
5014+NAME="AEN719"
5015+></A
5016+><H2
5017+>WARNING</H2
5018+><P
5019+>This facility is deeply obsoleted by
5020+<A
5021+HREF="ftp://ftp.isi.edu/in-notes/rfc951.txt"
5022+TARGET="_top"
5023+>BOOTP</A
5024+>
5025+and later
5026+<A
5027+HREF="ftp://ftp.isi.edu/in-notes/rfc2131.txt"
5028+TARGET="_top"
5029+>DHCP</A
5030+> protocols.
5031+However, some clients really still need this to boot.</P
5032+></DIV
5033+><DIV
5034+CLASS="REFSECT1"
5035+><A
5036+NAME="AEN724"
5037+></A
5038+><H2
5039+>OPTIONS</H2
5040+><P
5041+></P
5042+><DIV
5043+CLASS="VARIABLELIST"
5044+><DL
5045+><DT
5046+><CODE
5047+CLASS="OPTION"
5048+>-a</CODE
5049+></DT
5050+><DD
5051+><P
5052+>Listen on all the interfaces. Currently it is an internal
5053+option, its function is overridden with <TT
5054+CLASS="REPLACEABLE"
5055+><I
5056+>interface</I
5057+></TT
5058+>
5059+argument. It should not be used.
5060+ </P
5061+></DD
5062+><DT
5063+><CODE
5064+CLASS="OPTION"
5065+>-A</CODE
5066+></DT
5067+><DD
5068+><P
5069+>Listen not only RARP but also ARP messages, some rare clients
5070+use ARP by some unknown reason.
5071+ </P
5072+></DD
5073+><DT
5074+><CODE
5075+CLASS="OPTION"
5076+>-v</CODE
5077+></DT
5078+><DD
5079+><P
5080+>Be verbose.
5081+ </P
5082+></DD
5083+><DT
5084+><CODE
5085+CLASS="OPTION"
5086+>-d</CODE
5087+></DT
5088+><DD
5089+><P
5090+>Debug mode. Do not go to background.
5091+ </P
5092+></DD
5093+><DT
5094+><CODE
5095+CLASS="OPTION"
5096+>-e</CODE
5097+></DT
5098+><DD
5099+><P
5100+>Do not check for presence of a boot image, reply if MAC address
5101+resolves to a valid IP address using <TT
5102+CLASS="FILENAME"
5103+>/etc/ethers</TT
5104+>
5105+database and DNS.
5106+ </P
5107+></DD
5108+><DT
5109+><CODE
5110+CLASS="OPTION"
5111+>-b <TT
5112+CLASS="REPLACEABLE"
5113+><I
5114+>bootdir</I
5115+></TT
5116+></CODE
5117+></DT
5118+><DD
5119+><P
5120+>TFTP boot directory. Default is <TT
5121+CLASS="FILENAME"
5122+>/etc/tftpboot</TT
5123+>
5124+ </P
5125+></DD
5126+></DL
5127+></DIV
5128+></DIV
5129+><DIV
5130+CLASS="REFSECT1"
5131+><A
5132+NAME="AEN761"
5133+></A
5134+><H2
5135+>SEE ALSO</H2
5136+><P
5137+><A
5138+HREF="r437.html"
5139+><SPAN
5140+CLASS="CITEREFENTRY"
5141+><SPAN
5142+CLASS="REFENTRYTITLE"
5143+>arping</SPAN
5144+>(8)</SPAN
5145+></A
5146+>,
5147+<A
5148+HREF="r949.html"
5149+><SPAN
5150+CLASS="CITEREFENTRY"
5151+><SPAN
5152+CLASS="REFENTRYTITLE"
5153+>tftpd</SPAN
5154+>(8)</SPAN
5155+></A
5156+>.</P
5157+></DIV
5158+><DIV
5159+CLASS="REFSECT1"
5160+><A
5161+NAME="AEN772"
5162+></A
5163+><H2
5164+>AUTHOR</H2
5165+><P
5166+><B
5167+CLASS="COMMAND"
5168+>rarpd</B
5169+> was written by
5170+<A
5171+HREF="mailto:kuznet@ms2.inr.ac.ru"
5172+TARGET="_top"
5173+>Alexey Kuznetsov
5174+&lt;kuznet@ms2.inr.ac.ru&gt;</A
5175+>.
5176+It is now maintained by
5177+<A
5178+HREF="mailto:yoshfuji@skbuff.net"
5179+TARGET="_top"
5180+>YOSHIFUJI Hideaki
5181+&lt;yoshfuji@skbuff.net&gt;</A
5182+>.</P
5183+></DIV
5184+><DIV
5185+CLASS="REFSECT1"
5186+><A
5187+NAME="AEN778"
5188+></A
5189+><H2
5190+>SECURITY</H2
5191+><P
5192+><B
5193+CLASS="COMMAND"
5194+>rarpd</B
5195+> requires <CODE
5196+CLASS="CONSTANT"
5197+>CAP_NET_RAWIO</CODE
5198+> capability
5199+to listen and send RARP and ARP packets. It also needs <CODE
5200+CLASS="CONSTANT"
5201+>CAP_NET_ADMIN</CODE
5202+>
5203+to give to kernel hint for ARP resolution; this is not strictly required,
5204+but some (most of, to be more exact) clients are so badly broken that
5205+are not able to answer ARP before they are finally booted. This is
5206+not wonderful taking into account that clients using RARPD in 2002
5207+are all unsupported relic creatures of 90's and even earlier.</P
5208+></DIV
5209+><DIV
5210+CLASS="REFSECT1"
5211+><A
5212+NAME="AEN784"
5213+></A
5214+><H2
5215+>AVAILABILITY</H2
5216+><P
5217+><B
5218+CLASS="COMMAND"
5219+>rarpd</B
5220+> is part of <TT
5221+CLASS="FILENAME"
5222+>iputils</TT
5223+> package
5224+and the latest versions are available in source form at
5225+<A
5226+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
5227+TARGET="_top"
5228+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
5229+>.</P
5230+></DIV
5231+><DIV
5232+CLASS="NAVFOOTER"
5233+><HR
5234+ALIGN="LEFT"
5235+WIDTH="100%"><TABLE
5236+SUMMARY="Footer navigation table"
5237+WIDTH="100%"
5238+BORDER="0"
5239+CELLPADDING="0"
5240+CELLSPACING="0"
5241+><TR
5242+><TD
5243+WIDTH="33%"
5244+ALIGN="left"
5245+VALIGN="top"
5246+><A
5247+HREF="r596.html"
5248+ACCESSKEY="P"
5249+>Prev</A
5250+></TD
5251+><TD
5252+WIDTH="34%"
5253+ALIGN="center"
5254+VALIGN="top"
5255+><A
5256+HREF="index.html"
5257+ACCESSKEY="H"
5258+>Home</A
5259+></TD
5260+><TD
5261+WIDTH="33%"
5262+ALIGN="right"
5263+VALIGN="top"
5264+><A
5265+HREF="r790.html"
5266+ACCESSKEY="N"
5267+>Next</A
5268+></TD
5269+></TR
5270+><TR
5271+><TD
5272+WIDTH="33%"
5273+ALIGN="left"
5274+VALIGN="top"
5275+>clockdiff</TD
5276+><TD
5277+WIDTH="34%"
5278+ALIGN="center"
5279+VALIGN="top"
5280+>&nbsp;</TD
5281+><TD
5282+WIDTH="33%"
5283+ALIGN="right"
5284+VALIGN="top"
5285+>tracepath</TD
5286+></TR
5287+></TABLE
5288+></DIV
5289+></BODY
5290+></HTML
5291+>
5292\ No newline at end of file
5293diff -Naur iputils-s20100418.orig/doc/r790.html iputils-s20100418/doc/r790.html
5294--- iputils-s20100418.orig/doc/r790.html 1969-12-31 19:00:00.000000000 -0500
5295+++ iputils-s20100418/doc/r790.html 2010-08-04 22:00:32.417577090 -0400
5296@@ -0,0 +1,426 @@
5297+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
5298+<HTML
5299+><HEAD
5300+><TITLE
5301+>tracepath</TITLE
5302+><META
5303+NAME="GENERATOR"
5304+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
5305+REL="HOME"
5306+TITLE="System Manager's Manual: iputils"
5307+HREF="index.html"><LINK
5308+REL="PREVIOUS"
5309+TITLE="rarpd"
5310+HREF="r691.html"><LINK
5311+REL="NEXT"
5312+TITLE="traceroute6"
5313+HREF="r884.html"></HEAD
5314+><BODY
5315+CLASS="REFENTRY"
5316+BGCOLOR="#FFFFFF"
5317+TEXT="#000000"
5318+LINK="#0000FF"
5319+VLINK="#840084"
5320+ALINK="#0000FF"
5321+><DIV
5322+CLASS="NAVHEADER"
5323+><TABLE
5324+SUMMARY="Header navigation table"
5325+WIDTH="100%"
5326+BORDER="0"
5327+CELLPADDING="0"
5328+CELLSPACING="0"
5329+><TR
5330+><TH
5331+COLSPAN="3"
5332+ALIGN="center"
5333+>System Manager's Manual: iputils</TH
5334+></TR
5335+><TR
5336+><TD
5337+WIDTH="10%"
5338+ALIGN="left"
5339+VALIGN="bottom"
5340+><A
5341+HREF="r691.html"
5342+ACCESSKEY="P"
5343+>Prev</A
5344+></TD
5345+><TD
5346+WIDTH="80%"
5347+ALIGN="center"
5348+VALIGN="bottom"
5349+></TD
5350+><TD
5351+WIDTH="10%"
5352+ALIGN="right"
5353+VALIGN="bottom"
5354+><A
5355+HREF="r884.html"
5356+ACCESSKEY="N"
5357+>Next</A
5358+></TD
5359+></TR
5360+></TABLE
5361+><HR
5362+ALIGN="LEFT"
5363+WIDTH="100%"></DIV
5364+><H1
5365+><A
5366+NAME="TRACEPATH"
5367+></A
5368+>tracepath</H1
5369+><DIV
5370+CLASS="REFNAMEDIV"
5371+><A
5372+NAME="AEN795"
5373+></A
5374+><H2
5375+>Name</H2
5376+>tracepath, tracepath6&nbsp;--&nbsp;traces path to a network host discovering MTU along this path</DIV
5377+><DIV
5378+CLASS="REFSYNOPSISDIV"
5379+><A
5380+NAME="AEN798"
5381+></A
5382+><H2
5383+>Synopsis</H2
5384+><P
5385+><B
5386+CLASS="COMMAND"
5387+>tracepath</B
5388+> [-n] [-b] [-l <TT
5389+CLASS="REPLACEABLE"
5390+><I
5391+>pktlen</I
5392+></TT
5393+>] {<TT
5394+CLASS="REPLACEABLE"
5395+><I
5396+>destination</I
5397+></TT
5398+>} [<TT
5399+CLASS="REPLACEABLE"
5400+><I
5401+>port</I
5402+></TT
5403+>]</P
5404+></DIV
5405+><DIV
5406+CLASS="REFSECT1"
5407+><A
5408+NAME="AEN809"
5409+></A
5410+><H2
5411+>DESCRIPTION</H2
5412+><P
5413+>It traces path to <TT
5414+CLASS="REPLACEABLE"
5415+><I
5416+>destination</I
5417+></TT
5418+> discovering MTU along this path.
5419+It uses UDP port <TT
5420+CLASS="REPLACEABLE"
5421+><I
5422+>port</I
5423+></TT
5424+> or some random port.
5425+It is similar to <B
5426+CLASS="COMMAND"
5427+>traceroute</B
5428+>, only does not not require superuser
5429+privileges and has no fancy options.</P
5430+><P
5431+><B
5432+CLASS="COMMAND"
5433+>tracepath6</B
5434+> is good replacement for <B
5435+CLASS="COMMAND"
5436+>traceroute6</B
5437+>
5438+and classic example of application of Linux error queues.
5439+The situation with IPv4 is worse, because commercial
5440+IP routers do not return enough information in icmp error messages.
5441+Probably, it will change, when they will be updated.
5442+For now it uses Van Jacobson's trick, sweeping a range
5443+of UDP ports to maintain trace history.</P
5444+></DIV
5445+><DIV
5446+CLASS="REFSECT1"
5447+><A
5448+NAME="AEN818"
5449+></A
5450+><H2
5451+>OPTIONS</H2
5452+><P
5453+></P
5454+><DIV
5455+CLASS="VARIABLELIST"
5456+><DL
5457+><DT
5458+><CODE
5459+CLASS="OPTION"
5460+>-n</CODE
5461+></DT
5462+><DD
5463+><P
5464+>Print primarily IP addresses numerically.
5465+ </P
5466+></DD
5467+><DT
5468+><CODE
5469+CLASS="OPTION"
5470+>-b</CODE
5471+></DT
5472+><DD
5473+><P
5474+>Print both of host names and IP addresses.
5475+ </P
5476+></DD
5477+><DT
5478+><CODE
5479+CLASS="OPTION"
5480+>-l</CODE
5481+></DT
5482+><DD
5483+><P
5484+>Sets the initial packet length to <TT
5485+CLASS="REPLACEABLE"
5486+><I
5487+>pktlen</I
5488+></TT
5489+> instead of
5490+65536 for <B
5491+CLASS="COMMAND"
5492+>tracepath</B
5493+> or 128000 for <B
5494+CLASS="COMMAND"
5495+>tracepath6</B
5496+>.
5497+ </P
5498+></DD
5499+></DL
5500+></DIV
5501+></DIV
5502+><DIV
5503+CLASS="REFSECT1"
5504+><A
5505+NAME="AEN839"
5506+></A
5507+><H2
5508+>OUTPUT</H2
5509+><P
5510+><P
5511+CLASS="LITERALLAYOUT"
5512+>root@mops:~&nbsp;#&nbsp;tracepath6&nbsp;3ffe:2400:0:109::2<br>
5513+&nbsp;1?:&nbsp;[LOCALHOST]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;pmtu&nbsp;1500<br>
5514+&nbsp;1:&nbsp;&nbsp;dust.inr.ac.ru&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;0.411ms<br>
5515+&nbsp;2:&nbsp;&nbsp;dust.inr.ac.ru&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;asymm&nbsp;&nbsp;1&nbsp;&nbsp;&nbsp;0.390ms&nbsp;pmtu&nbsp;1480<br>
5516+&nbsp;2:&nbsp;&nbsp;3ffe:2400:0:109::2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;463.514ms&nbsp;reached<br>
5517+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Resume:&nbsp;pmtu&nbsp;1480&nbsp;hops&nbsp;2&nbsp;back&nbsp;2</P
5518+></P
5519+><P
5520+>The first column shows <TT
5521+CLASS="LITERAL"
5522+>TTL</TT
5523+> of the probe, followed by colon.
5524+Usually value of <TT
5525+CLASS="LITERAL"
5526+>TTL</TT
5527+> is obtained from reply from network,
5528+but sometimes reply does not contain necessary information and
5529+we have to guess it. In this case the number is followed by ?.</P
5530+><P
5531+>The second column shows the network hop, which replied to the probe.
5532+It is either address of router or word <TT
5533+CLASS="LITERAL"
5534+>[LOCALHOST]</TT
5535+>, if
5536+the probe was not sent to the network.</P
5537+><P
5538+>The rest of line shows miscellaneous information about path to
5539+the correspinding hetwork hop. As rule it contains value of RTT.
5540+Additionally, it can show Path MTU, when it changes.
5541+If the path is asymmetric
5542+or the probe finishes before it reach prescribed hop, difference
5543+between number of hops in forward and backward direction is shown
5544+folloing keyword <TT
5545+CLASS="LITERAL"
5546+>async</TT
5547+>. This information is not reliable.
5548+F.e. the third line shows asymmetry of 1, it is because the first probe
5549+with TTL of 2 was rejected at the first hop due to Path MTU Discovery.</P
5550+><P
5551+>The last line summarizes information about all the path to the destination,
5552+it shows detected Path MTU, amount of hops to the destination and our
5553+guess about amount of hops from the destination to us, which can be
5554+different when the path is asymmetric.</P
5555+></DIV
5556+><DIV
5557+CLASS="REFSECT1"
5558+><A
5559+NAME="AEN851"
5560+></A
5561+><H2
5562+>SEE ALSO</H2
5563+><P
5564+><SPAN
5565+CLASS="CITEREFENTRY"
5566+><SPAN
5567+CLASS="REFENTRYTITLE"
5568+>traceroute</SPAN
5569+>(8)</SPAN
5570+>,
5571+<A
5572+HREF="r884.html"
5573+><SPAN
5574+CLASS="CITEREFENTRY"
5575+><SPAN
5576+CLASS="REFENTRYTITLE"
5577+>traceroute6</SPAN
5578+>(8)</SPAN
5579+></A
5580+>,
5581+<A
5582+HREF="r3.html"
5583+><SPAN
5584+CLASS="CITEREFENTRY"
5585+><SPAN
5586+CLASS="REFENTRYTITLE"
5587+>ping</SPAN
5588+>(8)</SPAN
5589+></A
5590+>.</P
5591+></DIV
5592+><DIV
5593+CLASS="REFSECT1"
5594+><A
5595+NAME="AEN865"
5596+></A
5597+><H2
5598+>AUTHOR</H2
5599+><P
5600+><B
5601+CLASS="COMMAND"
5602+>tracepath</B
5603+> was written by
5604+<A
5605+HREF="mailto:kuznet@ms2.inr.ac.ru"
5606+TARGET="_top"
5607+>Alexey Kuznetsov
5608+&lt;kuznet@ms2.inr.ac.ru&gt;</A
5609+>.</P
5610+></DIV
5611+><DIV
5612+CLASS="REFSECT1"
5613+><A
5614+NAME="AEN870"
5615+></A
5616+><H2
5617+>SECURITY</H2
5618+><P
5619+>No security issues.</P
5620+><P
5621+>This lapidary deserves to be elaborated.
5622+<B
5623+CLASS="COMMAND"
5624+>tracepath</B
5625+> is not a privileged program, unlike
5626+<B
5627+CLASS="COMMAND"
5628+>traceroute</B
5629+>, <B
5630+CLASS="COMMAND"
5631+>ping</B
5632+> and other beasts of this kind.
5633+<B
5634+CLASS="COMMAND"
5635+>tracepath</B
5636+> may be executed by everyone who has some access
5637+to network, enough to send UDP datagrams to investigated destination
5638+using given port.</P
5639+></DIV
5640+><DIV
5641+CLASS="REFSECT1"
5642+><A
5643+NAME="AEN878"
5644+></A
5645+><H2
5646+>AVAILABILITY</H2
5647+><P
5648+><B
5649+CLASS="COMMAND"
5650+>tracepath</B
5651+> is part of <TT
5652+CLASS="FILENAME"
5653+>iputils</TT
5654+> package
5655+and the latest versions are available in source form at
5656+<A
5657+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
5658+TARGET="_top"
5659+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
5660+>.</P
5661+></DIV
5662+><DIV
5663+CLASS="NAVFOOTER"
5664+><HR
5665+ALIGN="LEFT"
5666+WIDTH="100%"><TABLE
5667+SUMMARY="Footer navigation table"
5668+WIDTH="100%"
5669+BORDER="0"
5670+CELLPADDING="0"
5671+CELLSPACING="0"
5672+><TR
5673+><TD
5674+WIDTH="33%"
5675+ALIGN="left"
5676+VALIGN="top"
5677+><A
5678+HREF="r691.html"
5679+ACCESSKEY="P"
5680+>Prev</A
5681+></TD
5682+><TD
5683+WIDTH="34%"
5684+ALIGN="center"
5685+VALIGN="top"
5686+><A
5687+HREF="index.html"
5688+ACCESSKEY="H"
5689+>Home</A
5690+></TD
5691+><TD
5692+WIDTH="33%"
5693+ALIGN="right"
5694+VALIGN="top"
5695+><A
5696+HREF="r884.html"
5697+ACCESSKEY="N"
5698+>Next</A
5699+></TD
5700+></TR
5701+><TR
5702+><TD
5703+WIDTH="33%"
5704+ALIGN="left"
5705+VALIGN="top"
5706+>rarpd</TD
5707+><TD
5708+WIDTH="34%"
5709+ALIGN="center"
5710+VALIGN="top"
5711+>&nbsp;</TD
5712+><TD
5713+WIDTH="33%"
5714+ALIGN="right"
5715+VALIGN="top"
5716+>traceroute6</TD
5717+></TR
5718+></TABLE
5719+></DIV
5720+></BODY
5721+></HTML
5722+>
5723\ No newline at end of file
5724diff -Naur iputils-s20100418.orig/doc/r884.html iputils-s20100418/doc/r884.html
5725--- iputils-s20100418.orig/doc/r884.html 1969-12-31 19:00:00.000000000 -0500
5726+++ iputils-s20100418/doc/r884.html 2010-08-04 22:00:32.425576855 -0400
5727@@ -0,0 +1,315 @@
5728+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
5729+<HTML
5730+><HEAD
5731+><TITLE
5732+>traceroute6</TITLE
5733+><META
5734+NAME="GENERATOR"
5735+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
5736+REL="HOME"
5737+TITLE="System Manager's Manual: iputils"
5738+HREF="index.html"><LINK
5739+REL="PREVIOUS"
5740+TITLE="tracepath"
5741+HREF="r790.html"><LINK
5742+REL="NEXT"
5743+TITLE="tftpd"
5744+HREF="r949.html"></HEAD
5745+><BODY
5746+CLASS="REFENTRY"
5747+BGCOLOR="#FFFFFF"
5748+TEXT="#000000"
5749+LINK="#0000FF"
5750+VLINK="#840084"
5751+ALINK="#0000FF"
5752+><DIV
5753+CLASS="NAVHEADER"
5754+><TABLE
5755+SUMMARY="Header navigation table"
5756+WIDTH="100%"
5757+BORDER="0"
5758+CELLPADDING="0"
5759+CELLSPACING="0"
5760+><TR
5761+><TH
5762+COLSPAN="3"
5763+ALIGN="center"
5764+>System Manager's Manual: iputils</TH
5765+></TR
5766+><TR
5767+><TD
5768+WIDTH="10%"
5769+ALIGN="left"
5770+VALIGN="bottom"
5771+><A
5772+HREF="r790.html"
5773+ACCESSKEY="P"
5774+>Prev</A
5775+></TD
5776+><TD
5777+WIDTH="80%"
5778+ALIGN="center"
5779+VALIGN="bottom"
5780+></TD
5781+><TD
5782+WIDTH="10%"
5783+ALIGN="right"
5784+VALIGN="bottom"
5785+><A
5786+HREF="r949.html"
5787+ACCESSKEY="N"
5788+>Next</A
5789+></TD
5790+></TR
5791+></TABLE
5792+><HR
5793+ALIGN="LEFT"
5794+WIDTH="100%"></DIV
5795+><H1
5796+><A
5797+NAME="TRACEROUTE6"
5798+></A
5799+>traceroute6</H1
5800+><DIV
5801+CLASS="REFNAMEDIV"
5802+><A
5803+NAME="AEN889"
5804+></A
5805+><H2
5806+>Name</H2
5807+>traceroute6&nbsp;--&nbsp;traces path to a network host</DIV
5808+><DIV
5809+CLASS="REFSYNOPSISDIV"
5810+><A
5811+NAME="AEN892"
5812+></A
5813+><H2
5814+>Synopsis</H2
5815+><P
5816+><B
5817+CLASS="COMMAND"
5818+>traceroute6</B
5819+> [<CODE
5820+CLASS="OPTION"
5821+>-dnrvV</CODE
5822+>] [-i <TT
5823+CLASS="REPLACEABLE"
5824+><I
5825+>interface</I
5826+></TT
5827+>] [-m <TT
5828+CLASS="REPLACEABLE"
5829+><I
5830+>max_ttl</I
5831+></TT
5832+>] [-p <TT
5833+CLASS="REPLACEABLE"
5834+><I
5835+>port</I
5836+></TT
5837+>] [-q <TT
5838+CLASS="REPLACEABLE"
5839+><I
5840+>max_probes</I
5841+></TT
5842+>] [-s <TT
5843+CLASS="REPLACEABLE"
5844+><I
5845+>source</I
5846+></TT
5847+>] [-w <TT
5848+CLASS="REPLACEABLE"
5849+><I
5850+>wait time</I
5851+></TT
5852+>] {<TT
5853+CLASS="REPLACEABLE"
5854+><I
5855+>destination</I
5856+></TT
5857+>} [<TT
5858+CLASS="REPLACEABLE"
5859+><I
5860+>size</I
5861+></TT
5862+>]</P
5863+></DIV
5864+><DIV
5865+CLASS="REFSECT1"
5866+><A
5867+NAME="AEN913"
5868+></A
5869+><H2
5870+>DESCRIPTION</H2
5871+><P
5872+>Description can be found in
5873+<SPAN
5874+CLASS="CITEREFENTRY"
5875+><SPAN
5876+CLASS="REFENTRYTITLE"
5877+>traceroute</SPAN
5878+>(8)</SPAN
5879+>,
5880+all the references to IP replaced to IPv6. It is needless to copy
5881+the description from there.</P
5882+></DIV
5883+><DIV
5884+CLASS="REFSECT1"
5885+><A
5886+NAME="AEN919"
5887+></A
5888+><H2
5889+>SEE ALSO</H2
5890+><P
5891+><SPAN
5892+CLASS="CITEREFENTRY"
5893+><SPAN
5894+CLASS="REFENTRYTITLE"
5895+>traceroute</SPAN
5896+>(8)</SPAN
5897+>,
5898+<SPAN
5899+CLASS="CITEREFENTRY"
5900+><SPAN
5901+CLASS="REFENTRYTITLE"
5902+>tracepath</SPAN
5903+>(8)</SPAN
5904+>,
5905+<SPAN
5906+CLASS="CITEREFENTRY"
5907+><SPAN
5908+CLASS="REFENTRYTITLE"
5909+>ping</SPAN
5910+>(8)</SPAN
5911+>.</P
5912+></DIV
5913+><DIV
5914+CLASS="REFSECT1"
5915+><A
5916+NAME="AEN931"
5917+></A
5918+><H2
5919+>HISTORY</H2
5920+><P
5921+>This program has long history. Author of <B
5922+CLASS="COMMAND"
5923+>traceroute</B
5924+>
5925+is Van Jacobson and it first appeared in 1988. This clone is
5926+based on a port of <B
5927+CLASS="COMMAND"
5928+>traceroute</B
5929+> to IPv6 published
5930+in NRL IPv6 distribution in 1996. In turn, it was ported
5931+to Linux by Pedro Roque. After this it was kept in sync by
5932+<A
5933+HREF="mailto:kuznet@ms2.inr.ac.ru"
5934+TARGET="_top"
5935+>Alexey Kuznetsov
5936+&lt;kuznet@ms2.inr.ac.ru&gt;</A
5937+>. And eventually entered
5938+<B
5939+CLASS="COMMAND"
5940+>iputils</B
5941+> package.</P
5942+></DIV
5943+><DIV
5944+CLASS="REFSECT1"
5945+><A
5946+NAME="AEN938"
5947+></A
5948+><H2
5949+>SECURITY</H2
5950+><P
5951+><B
5952+CLASS="COMMAND"
5953+>tracepath6</B
5954+> requires <CODE
5955+CLASS="CONSTANT"
5956+>CAP_NET_RAWIO</CODE
5957+> capability
5958+to be executed. It is safe to be used as set-uid root.</P
5959+></DIV
5960+><DIV
5961+CLASS="REFSECT1"
5962+><A
5963+NAME="AEN943"
5964+></A
5965+><H2
5966+>AVAILABILITY</H2
5967+><P
5968+><B
5969+CLASS="COMMAND"
5970+>traceroute6</B
5971+> is part of <TT
5972+CLASS="FILENAME"
5973+>iputils</TT
5974+> package
5975+and the latest versions are available in source form at
5976+<A
5977+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
5978+TARGET="_top"
5979+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
5980+>.</P
5981+></DIV
5982+><DIV
5983+CLASS="NAVFOOTER"
5984+><HR
5985+ALIGN="LEFT"
5986+WIDTH="100%"><TABLE
5987+SUMMARY="Footer navigation table"
5988+WIDTH="100%"
5989+BORDER="0"
5990+CELLPADDING="0"
5991+CELLSPACING="0"
5992+><TR
5993+><TD
5994+WIDTH="33%"
5995+ALIGN="left"
5996+VALIGN="top"
5997+><A
5998+HREF="r790.html"
5999+ACCESSKEY="P"
6000+>Prev</A
6001+></TD
6002+><TD
6003+WIDTH="34%"
6004+ALIGN="center"
6005+VALIGN="top"
6006+><A
6007+HREF="index.html"
6008+ACCESSKEY="H"
6009+>Home</A
6010+></TD
6011+><TD
6012+WIDTH="33%"
6013+ALIGN="right"
6014+VALIGN="top"
6015+><A
6016+HREF="r949.html"
6017+ACCESSKEY="N"
6018+>Next</A
6019+></TD
6020+></TR
6021+><TR
6022+><TD
6023+WIDTH="33%"
6024+ALIGN="left"
6025+VALIGN="top"
6026+>tracepath</TD
6027+><TD
6028+WIDTH="34%"
6029+ALIGN="center"
6030+VALIGN="top"
6031+>&nbsp;</TD
6032+><TD
6033+WIDTH="33%"
6034+ALIGN="right"
6035+VALIGN="top"
6036+>tftpd</TD
6037+></TR
6038+></TABLE
6039+></DIV
6040+></BODY
6041+></HTML
6042+>
6043\ No newline at end of file
6044diff -Naur iputils-s20100418.orig/doc/r949.html iputils-s20100418/doc/r949.html
6045--- iputils-s20100418.orig/doc/r949.html 1969-12-31 19:00:00.000000000 -0500
6046+++ iputils-s20100418/doc/r949.html 2010-08-04 22:00:32.433577358 -0400
6047@@ -0,0 +1,376 @@
6048+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
6049+<HTML
6050+><HEAD
6051+><TITLE
6052+>tftpd</TITLE
6053+><META
6054+NAME="GENERATOR"
6055+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
6056+REL="HOME"
6057+TITLE="System Manager's Manual: iputils"
6058+HREF="index.html"><LINK
6059+REL="PREVIOUS"
6060+TITLE="traceroute6"
6061+HREF="r884.html"><LINK
6062+REL="NEXT"
6063+TITLE="rdisc"
6064+HREF="r1022.html"></HEAD
6065+><BODY
6066+CLASS="REFENTRY"
6067+BGCOLOR="#FFFFFF"
6068+TEXT="#000000"
6069+LINK="#0000FF"
6070+VLINK="#840084"
6071+ALINK="#0000FF"
6072+><DIV
6073+CLASS="NAVHEADER"
6074+><TABLE
6075+SUMMARY="Header navigation table"
6076+WIDTH="100%"
6077+BORDER="0"
6078+CELLPADDING="0"
6079+CELLSPACING="0"
6080+><TR
6081+><TH
6082+COLSPAN="3"
6083+ALIGN="center"
6084+>System Manager's Manual: iputils</TH
6085+></TR
6086+><TR
6087+><TD
6088+WIDTH="10%"
6089+ALIGN="left"
6090+VALIGN="bottom"
6091+><A
6092+HREF="r884.html"
6093+ACCESSKEY="P"
6094+>Prev</A
6095+></TD
6096+><TD
6097+WIDTH="80%"
6098+ALIGN="center"
6099+VALIGN="bottom"
6100+></TD
6101+><TD
6102+WIDTH="10%"
6103+ALIGN="right"
6104+VALIGN="bottom"
6105+><A
6106+HREF="r1022.html"
6107+ACCESSKEY="N"
6108+>Next</A
6109+></TD
6110+></TR
6111+></TABLE
6112+><HR
6113+ALIGN="LEFT"
6114+WIDTH="100%"></DIV
6115+><H1
6116+><A
6117+NAME="TFTPD"
6118+></A
6119+>tftpd</H1
6120+><DIV
6121+CLASS="REFNAMEDIV"
6122+><A
6123+NAME="AEN954"
6124+></A
6125+><H2
6126+>Name</H2
6127+>tftpd&nbsp;--&nbsp;Trivial File Transfer Protocol server</DIV
6128+><DIV
6129+CLASS="REFSYNOPSISDIV"
6130+><A
6131+NAME="AEN957"
6132+></A
6133+><H2
6134+>Synopsis</H2
6135+><P
6136+><B
6137+CLASS="COMMAND"
6138+>tftpd</B
6139+> {<TT
6140+CLASS="REPLACEABLE"
6141+><I
6142+>directory</I
6143+></TT
6144+>}</P
6145+></DIV
6146+><DIV
6147+CLASS="REFSECT1"
6148+><A
6149+NAME="AEN962"
6150+></A
6151+><H2
6152+>DESCRIPTION</H2
6153+><P
6154+><B
6155+CLASS="COMMAND"
6156+>tftpd</B
6157+> is a server which supports the DARPA
6158+Trivial File Transfer Protocol
6159+(<A
6160+HREF="ftp://ftp.isi.edu/in-notes/rfc1350.txt"
6161+TARGET="_top"
6162+>RFC1350</A
6163+>).
6164+The TFTP server is started
6165+by <SPAN
6166+CLASS="CITEREFENTRY"
6167+><SPAN
6168+CLASS="REFENTRYTITLE"
6169+>inetd</SPAN
6170+>(8)</SPAN
6171+>.</P
6172+><P
6173+><TT
6174+CLASS="REPLACEABLE"
6175+><I
6176+>directory</I
6177+></TT
6178+> is required argument; if it is not given
6179+<B
6180+CLASS="COMMAND"
6181+>tftpd</B
6182+> aborts. This path is prepended to any file name requested
6183+via TFTP protocol, effectively chrooting <B
6184+CLASS="COMMAND"
6185+>tftpd</B
6186+> to this directory.
6187+File names are validated not to escape out of this directory, however
6188+administrator may configure such escape using symbolic links.</P
6189+><P
6190+>It is in difference of variants of <B
6191+CLASS="COMMAND"
6192+>tftpd</B
6193+> usually distributed
6194+with unix-like systems, which take a list of directories and match
6195+file names to start from one of given prefixes or to some random
6196+default, when no arguments were given. There are two reasons not to
6197+behave in this way: first, it is inconvenient, clients are not expected
6198+to know something about layout of filesystem on server host.
6199+And second, TFTP protocol is not a tool for browsing of server's filesystem,
6200+it is just an agent allowing to boot dumb clients. </P
6201+><P
6202+>In the case when <B
6203+CLASS="COMMAND"
6204+>tftpd</B
6205+> is used together with
6206+<A
6207+HREF="r691.html"
6208+><SPAN
6209+CLASS="CITEREFENTRY"
6210+><SPAN
6211+CLASS="REFENTRYTITLE"
6212+>rarpd</SPAN
6213+>(8)</SPAN
6214+></A
6215+>,
6216+tftp directories in these services should coincide and it is expected
6217+that each client booted via TFTP has boot image corresponding
6218+its IP address with an architecture suffix following Sun Microsystems
6219+conventions. See
6220+<A
6221+HREF="r691.html"
6222+><SPAN
6223+CLASS="CITEREFENTRY"
6224+><SPAN
6225+CLASS="REFENTRYTITLE"
6226+>rarpd</SPAN
6227+>(8)</SPAN
6228+></A
6229+>
6230+for more details.</P
6231+></DIV
6232+><DIV
6233+CLASS="REFSECT1"
6234+><A
6235+NAME="AEN986"
6236+></A
6237+><H2
6238+>SECURITY</H2
6239+><P
6240+>TFTP protocol does not provide any authentication.
6241+Due to this capital flaw <B
6242+CLASS="COMMAND"
6243+>tftpd</B
6244+> is not able to restrict
6245+access to files and will allow only publically readable
6246+files to be accessed. Files may be written only if they already
6247+exist and are publically writable.</P
6248+><P
6249+>Impact is evident, directory exported via TFTP <SPAN
6250+CLASS="emphasis"
6251+><I
6252+CLASS="EMPHASIS"
6253+>must not</I
6254+></SPAN
6255+>
6256+contain sensitive information of any kind, everyone is allowed
6257+to read it as soon as a client is allowed. Boot images do not contain
6258+such information as rule, however you should think twice before
6259+publishing f.e. Cisco IOS config files via TFTP, they contain
6260+<SPAN
6261+CLASS="emphasis"
6262+><I
6263+CLASS="EMPHASIS"
6264+>unencrypted</I
6265+></SPAN
6266+> passwords and may contain some information
6267+about the network, which you were not going to make public.</P
6268+><P
6269+>The <B
6270+CLASS="COMMAND"
6271+>tftpd</B
6272+> server should be executed by <B
6273+CLASS="COMMAND"
6274+>inetd</B
6275+>
6276+with dropped root privileges, namely with a user ID giving minimal
6277+access to files published in tftp directory. If it is executed
6278+as superuser occasionally, <B
6279+CLASS="COMMAND"
6280+>tftpd</B
6281+> drops its UID and GID
6282+to 65534, which is most likely not the thing which you expect.
6283+However, this is not very essential; remember, only files accessible
6284+for everyone can be read or written via TFTP.</P
6285+></DIV
6286+><DIV
6287+CLASS="REFSECT1"
6288+><A
6289+NAME="AEN997"
6290+></A
6291+><H2
6292+>SEE ALSO</H2
6293+><P
6294+><A
6295+HREF="r691.html"
6296+><SPAN
6297+CLASS="CITEREFENTRY"
6298+><SPAN
6299+CLASS="REFENTRYTITLE"
6300+>rarpd</SPAN
6301+>(8)</SPAN
6302+></A
6303+>,
6304+<SPAN
6305+CLASS="CITEREFENTRY"
6306+><SPAN
6307+CLASS="REFENTRYTITLE"
6308+>tftp</SPAN
6309+>(1)</SPAN
6310+>,
6311+<SPAN
6312+CLASS="CITEREFENTRY"
6313+><SPAN
6314+CLASS="REFENTRYTITLE"
6315+>inetd</SPAN
6316+>(8)</SPAN
6317+>.</P
6318+></DIV
6319+><DIV
6320+CLASS="REFSECT1"
6321+><A
6322+NAME="AEN1010"
6323+></A
6324+><H2
6325+>HISTORY</H2
6326+><P
6327+>The <B
6328+CLASS="COMMAND"
6329+>tftpd</B
6330+> command appeared in 4.2BSD. The source in iputils
6331+is cleaned up both syntactically (ANSIized) and semantically (UDP socket IO).</P
6332+><P
6333+>It is distributed with iputils mostly as good demo of an interesting feature
6334+(<CODE
6335+CLASS="CONSTANT"
6336+>MSG_CONFIRM</CODE
6337+>) allowing to boot long images by dumb clients
6338+not answering ARP requests until they are finally booted.
6339+However, this is full functional and can be used in production.</P
6340+></DIV
6341+><DIV
6342+CLASS="REFSECT1"
6343+><A
6344+NAME="AEN1016"
6345+></A
6346+><H2
6347+>AVAILABILITY</H2
6348+><P
6349+><B
6350+CLASS="COMMAND"
6351+>tftpd</B
6352+> is part of <TT
6353+CLASS="FILENAME"
6354+>iputils</TT
6355+> package
6356+and the latest versions are available in source form at
6357+<A
6358+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
6359+TARGET="_top"
6360+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
6361+>.</P
6362+></DIV
6363+><DIV
6364+CLASS="NAVFOOTER"
6365+><HR
6366+ALIGN="LEFT"
6367+WIDTH="100%"><TABLE
6368+SUMMARY="Footer navigation table"
6369+WIDTH="100%"
6370+BORDER="0"
6371+CELLPADDING="0"
6372+CELLSPACING="0"
6373+><TR
6374+><TD
6375+WIDTH="33%"
6376+ALIGN="left"
6377+VALIGN="top"
6378+><A
6379+HREF="r884.html"
6380+ACCESSKEY="P"
6381+>Prev</A
6382+></TD
6383+><TD
6384+WIDTH="34%"
6385+ALIGN="center"
6386+VALIGN="top"
6387+><A
6388+HREF="index.html"
6389+ACCESSKEY="H"
6390+>Home</A
6391+></TD
6392+><TD
6393+WIDTH="33%"
6394+ALIGN="right"
6395+VALIGN="top"
6396+><A
6397+HREF="r1022.html"
6398+ACCESSKEY="N"
6399+>Next</A
6400+></TD
6401+></TR
6402+><TR
6403+><TD
6404+WIDTH="33%"
6405+ALIGN="left"
6406+VALIGN="top"
6407+>traceroute6</TD
6408+><TD
6409+WIDTH="34%"
6410+ALIGN="center"
6411+VALIGN="top"
6412+>&nbsp;</TD
6413+><TD
6414+WIDTH="33%"
6415+ALIGN="right"
6416+VALIGN="top"
6417+>rdisc</TD
6418+></TR
6419+></TABLE
6420+></DIV
6421+></BODY
6422+></HTML
6423+>
6424\ No newline at end of file
6425diff -Naur iputils-s20100418.orig/doc/rarpd.8 iputils-s20100418/doc/rarpd.8
6426--- iputils-s20100418.orig/doc/rarpd.8 1969-12-31 19:00:00.000000000 -0500
6427+++ iputils-s20100418/doc/rarpd.8 2010-08-04 22:00:25.334076349 -0400
6428@@ -0,0 +1,84 @@
6429+.\" This manpage has been automatically generated by docbook2man
6430+.\" from a DocBook document. This tool can be found at:
6431+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
6432+.\" Please send any bug reports, improvements, comments, patches,
6433+.\" etc. to Steve Cheng <steve@ggi-project.org>.
6434+.TH "RARPD" "8" "04 August 2010" "iputils-100418" "System Manager's Manual: iputils"
6435+.SH NAME
6436+rarpd \- answer RARP REQUESTs
6437+.SH SYNOPSIS
6438+
6439+\fBarping\fR [\fB-aAvde\fR] [\fB-b \fIbootdir\fB\fR] [\fB\fIinterface\fB\fR]
6440+
6441+.SH "DESCRIPTION"
6442+.PP
6443+Listens
6444+RARP
6445+requests from clients. Provided MAC address of client
6446+is found in \fI/etc/ethers\fR database and
6447+obtained host name is resolvable to an IP address appropriate
6448+for attached network, \fBrarpd\fR answers to client with RARPD
6449+reply carrying an IP address.
6450+.PP
6451+To allow multiple boot servers on the network \fBrarpd\fR
6452+optionally checks for presence Sun-like bootable image in TFTP directory.
6453+It should have form \fBHexadecimal_IP.ARCH\fR, f.e. to load
6454+sparc 193.233.7.98 \fIC1E90762.SUN4M\fR is linked to
6455+an image appropriate for SUM4M in directory \fI/etc/tftpboot\fR.
6456+.SH "WARNING"
6457+.PP
6458+This facility is deeply obsoleted by
6459+BOOTP
6460+and later
6461+DHCP protocols.
6462+However, some clients really still need this to boot.
6463+.SH "OPTIONS"
6464+.TP
6465+\fB-a\fR
6466+Listen on all the interfaces. Currently it is an internal
6467+option, its function is overridden with \fIinterface\fR
6468+argument. It should not be used.
6469+.TP
6470+\fB-A\fR
6471+Listen not only RARP but also ARP messages, some rare clients
6472+use ARP by some unknown reason.
6473+.TP
6474+\fB-v\fR
6475+Be verbose.
6476+.TP
6477+\fB-d\fR
6478+Debug mode. Do not go to background.
6479+.TP
6480+\fB-e\fR
6481+Do not check for presence of a boot image, reply if MAC address
6482+resolves to a valid IP address using \fI/etc/ethers\fR
6483+database and DNS.
6484+.TP
6485+\fB-b \fIbootdir\fB\fR
6486+TFTP boot directory. Default is \fI/etc/tftpboot\fR
6487+.SH "SEE ALSO"
6488+.PP
6489+\fBarping\fR(8),
6490+\fBtftpd\fR(8).
6491+.SH "AUTHOR"
6492+.PP
6493+\fBrarpd\fR was written by
6494+Alexey Kuznetsov
6495+<kuznet@ms2.inr.ac.ru>.
6496+It is now maintained by
6497+YOSHIFUJI Hideaki
6498+<yoshfuji@skbuff.net>.
6499+.SH "SECURITY"
6500+.PP
6501+\fBrarpd\fR requires CAP_NET_RAWIO capability
6502+to listen and send RARP and ARP packets. It also needs CAP_NET_ADMIN
6503+to give to kernel hint for ARP resolution; this is not strictly required,
6504+but some (most of, to be more exact) clients are so badly broken that
6505+are not able to answer ARP before they are finally booted. This is
6506+not wonderful taking into account that clients using RARPD in 2002
6507+are all unsupported relic creatures of 90's and even earlier.
6508+.SH "AVAILABILITY"
6509+.PP
6510+\fBrarpd\fR is part of \fIiputils\fR package
6511+and the latest versions are available in source form at
6512+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
6513diff -Naur iputils-s20100418.orig/doc/rdisc.8 iputils-s20100418/doc/rdisc.8
6514--- iputils-s20100418.orig/doc/rdisc.8 1969-12-31 19:00:00.000000000 -0500
6515+++ iputils-s20100418/doc/rdisc.8 2010-08-04 22:00:25.602079120 -0400
6516@@ -0,0 +1,110 @@
6517+.\" This manpage has been automatically generated by docbook2man
6518+.\" from a DocBook document. This tool can be found at:
6519+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
6520+.\" Please send any bug reports, improvements, comments, patches,
6521+.\" etc. to Steve Cheng <steve@ggi-project.org>.
6522+.TH "RDISC" "8" "04 August 2010" "iputils-100418" "System Manager's Manual: iputils"
6523+.SH NAME
6524+rdisc \- network router discovery daemon
6525+.SH SYNOPSIS
6526+
6527+\fBrdisc\fR [\fB-abdfstvV\fR] [\fB\fIsend_address\fB\fR] [\fB\fIreceive_address\fB\fR]
6528+
6529+.SH "DESCRIPTION"
6530+.PP
6531+\fBrdisc\fR implements client side of the ICMP router discover protocol.
6532+\fBrdisc\fR is invoked at boot time to populate the network
6533+routing tables with default routes.
6534+.PP
6535+\fBrdisc\fR listens on the ALL_HOSTS (224.0.0.1) multicast address
6536+(or \fIreceive_address\fR provided it is given)
6537+for ROUTER_ADVERTISE messages from routers. The received
6538+messages are handled by first ignoring those listed router addresses
6539+with which the host does not share a network. Among the remaining addresses
6540+the ones with the highest preference are selected as default routers
6541+and a default route is entered in the kernel routing table
6542+for each one of them.
6543+.PP
6544+Optionally, \fBrdisc\fR can avoid waiting for routers to announce
6545+themselves by sending out a few ROUTER_SOLICITATION messages
6546+to the ALL_ROUTERS (224.0.0.2) multicast address
6547+(or \fIsend_address\fR provided it is given)
6548+when it is started.
6549+.PP
6550+A timer is associated with each router address and the address will
6551+no longer be considered for inclusion in the the routing tables if the
6552+timer expires before a new
6553+\fBadvertise\fR message is received from the router.
6554+The address will also be excluded from consideration if the host receives an
6555+\fBadvertise\fR
6556+message with the preference being maximally negative.
6557+.PP
6558+Server side of router discovery protocol is supported by Cisco IOS
6559+and by any more or less complete UNIX routing daemon, f.e \fBgated\fR.
6560+.SH "OPTIONS"
6561+.TP
6562+\fB-a\fR
6563+Accept all routers independently of the preference they have in their
6564+\fBadvertise\fR messages.
6565+Normally \fBrdisc\fR only accepts (and enters in the kernel routing
6566+tables) the router or routers with the highest preference.
6567+.TP
6568+\fB-b\fR
6569+Opposite to \fB-a\fR, i.e. install only router with the best
6570+preference value. It is default behaviour.
6571+.TP
6572+\fB-d\fR
6573+Send debugging messages to syslog.
6574+.TP
6575+\fB-f\fR
6576+Run \fBrdisc\fR forever even if no routers are found.
6577+Normally \fBrdisc\fR gives up if it has not received any
6578+\fBadvertise\fR message after after soliciting three times,
6579+in which case it exits with a non-zero exit code.
6580+If \fB-f\fR is not specified in the first form then
6581+\fB-s\fR must be specified.
6582+.TP
6583+\fB-s\fR
6584+Send three \fBsolicitation\fR messages initially to quickly discover
6585+the routers when the system is booted.
6586+When \fB-s\fR is specified \fBrdisc\fR
6587+exits with a non-zero exit code if it can not find any routers.
6588+This can be overridden with the \fB-f\fR option.
6589+.TP
6590+\fB-t\fR
6591+Test mode. Do not go to background.
6592+.TP
6593+\fB-v\fR
6594+Be verbose i.e. send lots of debugging messages to syslog.
6595+.TP
6596+\fB-V\fR
6597+Print version and exit.
6598+.SH "HISTORY"
6599+.PP
6600+This program was developed by Sun Microsystems (see copyright
6601+notice in source file). It was ported to Linux by
6602+Alexey Kuznetsov
6603+<kuznet@ms2.inr.ac.ru>.
6604+It is now maintained by
6605+YOSHIFUJI Hideaki
6606+<yoshfuji@skbuff.net>.
6607+.SH "SEE ALSO"
6608+.PP
6609+\fBicmp\fR(7),
6610+\fBinet\fR(7),
6611+\fBping\fR(8).
6612+.SH "REFERENCES"
6613+.PP
6614+Deering, S.E.,ed "ICMP Router Discovery Messages",
6615+RFC1256, Network Information Center, SRI International,
6616+Menlo Park, Calif., September 1991.
6617+.SH "SECURITY"
6618+.PP
6619+\fBrdisc\fR requires CAP_NET_RAWIO to listen
6620+and send ICMP messages and capability CAP_NET_ADMIN
6621+to update routing tables.
6622+.SH "AVAILABILITY"
6623+.PP
6624+\fBrdisc\fR is part of \fIiputils\fR package
6625+and the latest versions are available in source form at
6626+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
6627diff -Naur iputils-s20100418.orig/doc/tftpd.8 iputils-s20100418/doc/tftpd.8
6628--- iputils-s20100418.orig/doc/tftpd.8 1969-12-31 19:00:00.000000000 -0500
6629+++ iputils-s20100418/doc/tftpd.8 2010-08-04 22:00:25.782079442 -0400
6630@@ -0,0 +1,85 @@
6631+.\" This manpage has been automatically generated by docbook2man
6632+.\" from a DocBook document. This tool can be found at:
6633+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
6634+.\" Please send any bug reports, improvements, comments, patches,
6635+.\" etc. to Steve Cheng <steve@ggi-project.org>.
6636+.TH "TFTPD" "8" "04 August 2010" "iputils-100418" "System Manager's Manual: iputils"
6637+.SH NAME
6638+tftpd \- Trivial File Transfer Protocol server
6639+.SH SYNOPSIS
6640+
6641+\fBtftpd\fR \fB\fIdirectory\fB\fR
6642+
6643+.SH "DESCRIPTION"
6644+.PP
6645+\fBtftpd\fR is a server which supports the DARPA
6646+Trivial File Transfer Protocol
6647+(RFC1350).
6648+The TFTP server is started
6649+by \fBinetd\fR(8).
6650+.PP
6651+\fIdirectory\fR is required argument; if it is not given
6652+\fBtftpd\fR aborts. This path is prepended to any file name requested
6653+via TFTP protocol, effectively chrooting \fBtftpd\fR to this directory.
6654+File names are validated not to escape out of this directory, however
6655+administrator may configure such escape using symbolic links.
6656+.PP
6657+It is in difference of variants of \fBtftpd\fR usually distributed
6658+with unix-like systems, which take a list of directories and match
6659+file names to start from one of given prefixes or to some random
6660+default, when no arguments were given. There are two reasons not to
6661+behave in this way: first, it is inconvenient, clients are not expected
6662+to know something about layout of filesystem on server host.
6663+And second, TFTP protocol is not a tool for browsing of server's filesystem,
6664+it is just an agent allowing to boot dumb clients.
6665+.PP
6666+In the case when \fBtftpd\fR is used together with
6667+\fBrarpd\fR(8),
6668+tftp directories in these services should coincide and it is expected
6669+that each client booted via TFTP has boot image corresponding
6670+its IP address with an architecture suffix following Sun Microsystems
6671+conventions. See
6672+\fBrarpd\fR(8)
6673+for more details.
6674+.SH "SECURITY"
6675+.PP
6676+TFTP protocol does not provide any authentication.
6677+Due to this capital flaw \fBtftpd\fR is not able to restrict
6678+access to files and will allow only publically readable
6679+files to be accessed. Files may be written only if they already
6680+exist and are publically writable.
6681+.PP
6682+Impact is evident, directory exported via TFTP \fBmust not\fR
6683+contain sensitive information of any kind, everyone is allowed
6684+to read it as soon as a client is allowed. Boot images do not contain
6685+such information as rule, however you should think twice before
6686+publishing f.e. Cisco IOS config files via TFTP, they contain
6687+\fBunencrypted\fR passwords and may contain some information
6688+about the network, which you were not going to make public.
6689+.PP
6690+The \fBtftpd\fR server should be executed by \fBinetd\fR
6691+with dropped root privileges, namely with a user ID giving minimal
6692+access to files published in tftp directory. If it is executed
6693+as superuser occasionally, \fBtftpd\fR drops its UID and GID
6694+to 65534, which is most likely not the thing which you expect.
6695+However, this is not very essential; remember, only files accessible
6696+for everyone can be read or written via TFTP.
6697+.SH "SEE ALSO"
6698+.PP
6699+\fBrarpd\fR(8),
6700+\fBtftp\fR(1),
6701+\fBinetd\fR(8).
6702+.SH "HISTORY"
6703+.PP
6704+The \fBtftpd\fR command appeared in 4.2BSD. The source in iputils
6705+is cleaned up both syntactically (ANSIized) and semantically (UDP socket IO).
6706+.PP
6707+It is distributed with iputils mostly as good demo of an interesting feature
6708+(MSG_CONFIRM) allowing to boot long images by dumb clients
6709+not answering ARP requests until they are finally booted.
6710+However, this is full functional and can be used in production.
6711+.SH "AVAILABILITY"
6712+.PP
6713+\fBtftpd\fR is part of \fIiputils\fR package
6714+and the latest versions are available in source form at
6715+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
6716diff -Naur iputils-s20100418.orig/doc/tracepath.8 iputils-s20100418/doc/tracepath.8
6717--- iputils-s20100418.orig/doc/tracepath.8 1969-12-31 19:00:00.000000000 -0500
6718+++ iputils-s20100418/doc/tracepath.8 2010-08-04 22:00:26.214078440 -0400
6719@@ -0,0 +1,97 @@
6720+.\" This manpage has been automatically generated by docbook2man
6721+.\" from a DocBook document. This tool can be found at:
6722+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
6723+.\" Please send any bug reports, improvements, comments, patches,
6724+.\" etc. to Steve Cheng <steve@ggi-project.org>.
6725+.TH "TRACEPATH" "8" "04 August 2010" "iputils-100418" "System Manager's Manual: iputils"
6726+.SH NAME
6727+tracepath, tracepath6 \- traces path to a network host discovering MTU along this path
6728+.SH SYNOPSIS
6729+
6730+\fBtracepath\fR [\fB-n\fR] [\fB-b\fR] [\fB-l \fIpktlen\fB\fR] \fB\fIdestination\fB\fR [\fB\fIport\fB\fR]
6731+
6732+.SH "DESCRIPTION"
6733+.PP
6734+It traces path to \fIdestination\fR discovering MTU along this path.
6735+It uses UDP port \fIport\fR or some random port.
6736+It is similar to \fBtraceroute\fR, only does not not require superuser
6737+privileges and has no fancy options.
6738+.PP
6739+\fBtracepath6\fR is good replacement for \fBtraceroute6\fR
6740+and classic example of application of Linux error queues.
6741+The situation with IPv4 is worse, because commercial
6742+IP routers do not return enough information in icmp error messages.
6743+Probably, it will change, when they will be updated.
6744+For now it uses Van Jacobson's trick, sweeping a range
6745+of UDP ports to maintain trace history.
6746+.SH "OPTIONS"
6747+.TP
6748+\fB-n\fR
6749+Print primarily IP addresses numerically.
6750+.TP
6751+\fB-b\fR
6752+Print both of host names and IP addresses.
6753+.TP
6754+\fB-l\fR
6755+Sets the initial packet length to \fIpktlen\fR instead of
6756+65536 for \fBtracepath\fR or 128000 for \fBtracepath6\fR.
6757+.SH "OUTPUT"
6758+.PP
6759+
6760+.nf
6761+root@mops:~ # tracepath6 3ffe:2400:0:109::2
6762+ 1?: [LOCALHOST] pmtu 1500
6763+ 1: dust.inr.ac.ru 0.411ms
6764+ 2: dust.inr.ac.ru asymm 1 0.390ms pmtu 1480
6765+ 2: 3ffe:2400:0:109::2 463.514ms reached
6766+ Resume: pmtu 1480 hops 2 back 2
6767+.fi
6768+.PP
6769+The first column shows TTL of the probe, followed by colon.
6770+Usually value of TTL is obtained from reply from network,
6771+but sometimes reply does not contain necessary information and
6772+we have to guess it. In this case the number is followed by ?.
6773+.PP
6774+The second column shows the network hop, which replied to the probe.
6775+It is either address of router or word [LOCALHOST], if
6776+the probe was not sent to the network.
6777+.PP
6778+The rest of line shows miscellaneous information about path to
6779+the correspinding hetwork hop. As rule it contains value of RTT.
6780+Additionally, it can show Path MTU, when it changes.
6781+If the path is asymmetric
6782+or the probe finishes before it reach prescribed hop, difference
6783+between number of hops in forward and backward direction is shown
6784+folloing keyword async. This information is not reliable.
6785+F.e. the third line shows asymmetry of 1, it is because the first probe
6786+with TTL of 2 was rejected at the first hop due to Path MTU Discovery.
6787+.PP
6788+The last line summarizes information about all the path to the destination,
6789+it shows detected Path MTU, amount of hops to the destination and our
6790+guess about amount of hops from the destination to us, which can be
6791+different when the path is asymmetric.
6792+.SH "SEE ALSO"
6793+.PP
6794+\fBtraceroute\fR(8),
6795+\fBtraceroute6\fR(8),
6796+\fBping\fR(8).
6797+.SH "AUTHOR"
6798+.PP
6799+\fBtracepath\fR was written by
6800+Alexey Kuznetsov
6801+<kuznet@ms2.inr.ac.ru>.
6802+.SH "SECURITY"
6803+.PP
6804+No security issues.
6805+.PP
6806+This lapidary deserves to be elaborated.
6807+\fBtracepath\fR is not a privileged program, unlike
6808+\fBtraceroute\fR, \fBping\fR and other beasts of this kind.
6809+\fBtracepath\fR may be executed by everyone who has some access
6810+to network, enough to send UDP datagrams to investigated destination
6811+using given port.
6812+.SH "AVAILABILITY"
6813+.PP
6814+\fBtracepath\fR is part of \fIiputils\fR package
6815+and the latest versions are available in source form at
6816+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
6817diff -Naur iputils-s20100418.orig/doc/traceroute6.8 iputils-s20100418/doc/traceroute6.8
6818--- iputils-s20100418.orig/doc/traceroute6.8 1969-12-31 19:00:00.000000000 -0500
6819+++ iputils-s20100418/doc/traceroute6.8 2010-08-04 22:00:26.173737598 -0400
6820@@ -0,0 +1,42 @@
6821+.\" This manpage has been automatically generated by docbook2man
6822+.\" from a DocBook document. This tool can be found at:
6823+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
6824+.\" Please send any bug reports, improvements, comments, patches,
6825+.\" etc. to Steve Cheng <steve@ggi-project.org>.
6826+.TH "TRACEROUTE6" "8" "04 August 2010" "iputils-100418" "System Manager's Manual: iputils"
6827+.SH NAME
6828+traceroute6 \- traces path to a network host
6829+.SH SYNOPSIS
6830+
6831+\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]
6832+
6833+.SH "DESCRIPTION"
6834+.PP
6835+Description can be found in
6836+\fBtraceroute\fR(8),
6837+all the references to IP replaced to IPv6. It is needless to copy
6838+the description from there.
6839+.SH "SEE ALSO"
6840+.PP
6841+\fBtraceroute\fR(8),
6842+\fBtracepath\fR(8),
6843+\fBping\fR(8).
6844+.SH "HISTORY"
6845+.PP
6846+This program has long history. Author of \fBtraceroute\fR
6847+is Van Jacobson and it first appeared in 1988. This clone is
6848+based on a port of \fBtraceroute\fR to IPv6 published
6849+in NRL IPv6 distribution in 1996. In turn, it was ported
6850+to Linux by Pedro Roque. After this it was kept in sync by
6851+Alexey Kuznetsov
6852+<kuznet@ms2.inr.ac.ru>. And eventually entered
6853+\fBiputils\fR package.
6854+.SH "SECURITY"
6855+.PP
6856+\fBtracepath6\fR requires CAP_NET_RAWIO capability
6857+to be executed. It is safe to be used as set-uid root.
6858+.SH "AVAILABILITY"
6859+.PP
6860+\fBtraceroute6\fR is part of \fIiputils\fR package
6861+and the latest versions are available in source form at
6862+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
Note: See TracBrowser for help on using the repository browser.