source: patches/iputils-s20121221-fixes-2.patch@ dd5aa46

systemd
Last change on this file since dd5aa46 was 205fbc0, checked in by William Harrington <kb0iic@…>, 11 years ago

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