source: patches/iputils-s20121221-fixes-1.patch@ 05715f4

clfs-3.0.0-systemd clfs-3.0.0-sysvinit systemd sysvinit
Last change on this file since 05715f4 was 602f33a, checked in by William Harrington <kb0iic@…>, 11 years ago

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