source: patches/iputils-s20101006-doc-1.patch@ 2029c0d9

clfs-2.1 clfs-3.0.0-systemd clfs-3.0.0-sysvinit systemd sysvinit
Last change on this file since 2029c0d9 was ecc1136, checked in by Joe Ciccone <jciccone@…>, 15 years ago

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