Index: BOOK/introduction/common/changelog.xml
===================================================================
--- BOOK/introduction/common/changelog.xml	(revision b575f2084b4e4297105cfca27bda908accc89c8c)
+++ BOOK/introduction/common/changelog.xml	(revision ecc1136c03ab82d05060a4dfccf51599109cc687)
@@ -41,4 +41,7 @@
       <para>January 8, 2011</para>
       <itemizedlist>
+        <listitem>
+          <para>[jciccone] - Updated IPutils to s20101006.</para>
+        </listitem>
         <listitem>
           <para>[jciccone] - Updated Autoconf to 2.68.</para>
Index: BOOK/packages.ent
===================================================================
--- BOOK/packages.ent	(revision b575f2084b4e4297105cfca27bda908accc89c8c)
+++ BOOK/packages.ent	(revision ecc1136c03ab82d05060a4dfccf51599109cc687)
@@ -224,8 +224,8 @@
 <!ENTITY iproute2-home "http://www.linuxfoundation.org/en/Net:Iproute2">
 
-<!ENTITY iputils-version "s20100418">
+<!ENTITY iputils-version "s20101006">
 <!ENTITY iputils-size "96 KB">
 <!ENTITY iputils-url "http://www.skbuff.net/iputils/iputils-&iputils-version;.tar.bz2">
-<!ENTITY iputils-md5 "df6b0062118cdc5c62e3c810f831e976">
+<!ENTITY iputils-md5 "a36c25e9ec17e48be514dc0485e7376c">
 <!ENTITY iputils-home "http://www.linuxfoundation.org/en/Net:Iputils">
 
Index: BOOK/patches.ent
===================================================================
--- BOOK/patches.ent	(revision b575f2084b4e4297105cfca27bda908accc89c8c)
+++ BOOK/patches.ent	(revision ecc1136c03ab82d05060a4dfccf51599109cc687)
@@ -30,9 +30,9 @@
 
 <!ENTITY iputils-fixes-patch "iputils-&iputils-version;-fixes-1.patch">
-<!ENTITY iputils-fixes-patch-md5 "138913183f50dba3ed096bb55a8e5d08">
+<!ENTITY iputils-fixes-patch-md5 "1add4b8cbee814310f95e61997019162">
 <!ENTITY iputils-fixes-patch-size "8 KB">
 
 <!ENTITY iputils-doc-patch "iputils-&iputils-version;-doc-1.patch">
-<!ENTITY iputils-doc-patch-md5 "ca2642c8c92df6f8257f925daaadce6b">
+<!ENTITY iputils-doc-patch-md5 "2eee5e095005bf4be426797a4aefa27b">
 <!ENTITY iputils-doc-patch-size "136 KB">
 
Index: tches/iputils-s20100418-doc-1.patch
===================================================================
--- patches/iputils-s20100418-doc-1.patch	(revision b575f2084b4e4297105cfca27bda908accc89c8c)
+++ 	(revision )
@@ -1,6862 +1,0 @@
-diff -Naur iputils-s20100418.orig/doc/arping.8 iputils-s20100418/doc/arping.8
---- iputils-s20100418.orig/doc/arping.8	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/arping.8	2010-08-04 22:00:24.906075906 -0400
-@@ -0,0 +1,110 @@
-+.\" This manpage has been automatically generated by docbook2man 
-+.\" from a DocBook document.  This tool can be found at:
-+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
-+.\" Please send any bug reports, improvements, comments, patches, 
-+.\" etc. to Steve Cheng <steve@ggi-project.org>.
-+.TH "ARPING" "8" "04 August 2010" "iputils-100418" "System Manager's Manual: iputils"
-+.SH NAME
-+arping \- send ARP REQUEST to a neighbour host
-+.SH SYNOPSIS
-+
-+\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
-+
-+.SH "DESCRIPTION"
-+.PP
-+Ping \fIdestination\fR on device \fIinterface\fR by ARP packets,
-+using source address \fIsource\fR.
-+.SH "OPTIONS"
-+.TP
-+\fB-A\fR
-+The same as \fB-U\fR, but ARP REPLY packets used instead
-+of ARP REQUEST.
-+.TP
-+\fB-b\fR
-+Send only MAC level broadcasts. Normally \fBarping\fR starts
-+from sending broadcast, and switch to unicast after reply received.
-+.TP
-+\fB-c \fIcount\fB\fR
-+Stop after sending \fIcount\fR ARP REQUEST
-+packets. With 
-+\fIdeadline\fR
-+option, \fBarping\fR waits for
-+\fIcount\fR ARP REPLY packets, until the timeout expires.
-+.TP
-+\fB-D\fR
-+Duplicate address detection mode (DAD). See 
-+RFC2131, 4.4.1.
-+Returns 0, if DAD succeeded i.e. no replies are received
-+.TP
-+\fB-f\fR
-+Finish after the first reply confirming that target is alive.
-+.TP
-+\fB-I \fIinterface\fB\fR
-+Name of network device where to send ARP REQUEST packets. This option
-+is required.
-+.TP
-+\fB-h\fR
-+Print help page and exit.
-+.TP
-+\fB-q\fR
-+Quiet output. Nothing is displayed.
-+.TP
-+\fB-s \fIsource\fB\fR
-+IP source address to use in ARP packets.
-+If this option is absent, source address is:
-+.RS
-+.TP 0.2i
-+\(bu
-+In DAD mode (with option \fB-D\fR) set to 0.0.0.0.
-+.TP 0.2i
-+\(bu
-+In Unsolicited ARP mode (with options \fB-U\fR or \fB-A\fR)
-+set to \fIdestination\fR.
-+.TP 0.2i
-+\(bu
-+Otherwise, it is calculated from routing tables.
-+.RE
-+.TP
-+\fB-U\fR
-+Unsolicited ARP mode to update neighbours' ARP caches.
-+No replies are expected.
-+.TP
-+\fB-V\fR
-+Print version of the program and exit.
-+.TP
-+\fB-w \fIdeadline\fB\fR
-+Specify a timeout, in seconds, before
-+\fBarping\fR
-+exits regardless of how many
-+packets have been sent or received. In this case
-+\fBarping\fR
-+does not stop after
-+\fIcount\fR
-+packet are sent, it waits either for
-+\fIdeadline\fR
-+expire or until
-+\fIcount\fR
-+probes are answered.
-+.SH "SEE ALSO"
-+.PP
-+\fBping\fR(8),
-+\fBclockdiff\fR(8),
-+\fBtracepath\fR(8).
-+.SH "AUTHOR"
-+.PP
-+\fBarping\fR was written by
-+Alexey Kuznetsov
-+<kuznet@ms2.inr.ac.ru>.
-+It is now maintained by
-+YOSHIFUJI Hideaki
-+<yoshfuji@skbuff.net>.
-+.SH "SECURITY"
-+.PP
-+\fBarping\fR requires CAP_NET_RAWIO capability
-+to be executed. It is not recommended to be used as set-uid root,
-+because it allows user to modify ARP caches of neighbour hosts.
-+.SH "AVAILABILITY"
-+.PP
-+\fBarping\fR is part of \fIiputils\fR package
-+and the latest versions are  available in source form at
-+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
-diff -Naur iputils-s20100418.orig/doc/clockdiff.8 iputils-s20100418/doc/clockdiff.8
---- iputils-s20100418.orig/doc/clockdiff.8	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/clockdiff.8	2010-08-04 22:00:21.574452489 -0400
-@@ -0,0 +1,81 @@
-+.\" This manpage has been automatically generated by docbook2man 
-+.\" from a DocBook document.  This tool can be found at:
-+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
-+.\" Please send any bug reports, improvements, comments, patches, 
-+.\" etc. to Steve Cheng <steve@ggi-project.org>.
-+.TH "CLOCKDIFF" "8" "04 August 2010" "iputils-100418" "System Manager's Manual: iputils"
-+.SH NAME
-+clockdiff \- measure clock difference between hosts
-+.SH SYNOPSIS
-+
-+\fBclockdiff\fR [\fB-o\fR] [\fB-o1\fR] \fB\fIdestination\fB\fR
-+
-+.SH "DESCRIPTION"
-+.PP
-+\fBclockdiff\fR Measures clock difference between us and
-+\fIdestination\fR with 1 msec resolution using ICMP TIMESTAMP
-+[2]
-+packets or, optionally, IP TIMESTAMP option
-+[3]
-+option added to ICMP ECHO.
-+[1]
-+.SH "OPTIONS"
-+.TP
-+\fB-o\fR
-+Use IP TIMESTAMP with ICMP ECHO instead of ICMP TIMESTAMP
-+messages. It is useful with some destinations, which do not support
-+ICMP TIMESTAMP (f.e. Solaris <2.4).
-+.TP
-+\fB-o1\fR
-+Slightly different form of \fB-o\fR, namely it uses three-term
-+IP TIMESTAMP with prespecified hop addresses instead of four term one.
-+What flavor works better depends on target host. Particularly,
-+\fB-o\fR is better for Linux.
-+.SH "WARNINGS"
-+.TP 0.2i
-+\(bu
-+Some nodes (Cisco) use non-standard timestamps, which is allowed
-+by RFC, but makes timestamps mostly useless.
-+.TP 0.2i
-+\(bu
-+Some nodes generate messed timestamps (Solaris>2.4), when
-+run \fBxntpd\fR. Seems, its IP stack uses a corrupted clock source,
-+which is synchronized to time-of-day clock periodically and jumps
-+randomly making timestamps mostly useless. Good news is that you can
-+use NTP in this case, which is even better.
-+.TP 0.2i
-+\(bu
-+\fBclockdiff\fR shows difference in time modulo 24 days.
-+.SH "SEE ALSO"
-+.PP
-+\fBping\fR(8),
-+\fBarping\fR(8),
-+\fBtracepath\fR(8).
-+.SH "REFERENCES"
-+.PP
-+[1] ICMP ECHO,
-+RFC0792, page 14.
-+.PP
-+[2] ICMP TIMESTAMP,
-+RFC0792, page 16.
-+.PP
-+[3] IP TIMESTAMP option,
-+RFC0791, 3.1, page 16.
-+.SH "AUTHOR"
-+.PP
-+\fBclockdiff\fR was compiled by
-+Alexey Kuznetsov
-+<kuznet@ms2.inr.ac.ru>. It was based on code borrowed
-+from BSD \fBtimed\fR daemon.
-+It is now maintained by
-+YOSHIFUJI Hideaki
-+<yoshfuji@skbuff.net>.
-+.SH "SECURITY"
-+.PP
-+\fBclockdiff\fR requires CAP_NET_RAWIO capability
-+to be executed. It is safe to be used as set-uid root.
-+.SH "AVAILABILITY"
-+.PP
-+\fBclockdiff\fR is part of \fIiputils\fR package
-+and the latest versions are  available in source form at
-+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
-diff -Naur iputils-s20100418.orig/doc/index.html iputils-s20100418/doc/index.html
---- iputils-s20100418.orig/doc/index.html	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/index.html	2010-08-04 22:00:32.445575810 -0400
-@@ -0,0 +1,170 @@
-+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-+<HTML
-+><HEAD
-+><TITLE
-+>System Manager's Manual: iputils</TITLE
-+><META
-+NAME="GENERATOR"
-+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-+REL="NEXT"
-+TITLE="ping"
-+HREF="r3.html"></HEAD
-+><BODY
-+CLASS="REFERENCE"
-+BGCOLOR="#FFFFFF"
-+TEXT="#000000"
-+LINK="#0000FF"
-+VLINK="#840084"
-+ALINK="#0000FF"
-+><DIV
-+CLASS="NAVHEADER"
-+><TABLE
-+SUMMARY="Header navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TD
-+WIDTH="10%"
-+ALIGN="left"
-+VALIGN="bottom"
-+>&nbsp;</TD
-+><TD
-+WIDTH="80%"
-+ALIGN="center"
-+VALIGN="bottom"
-+></TD
-+><TD
-+WIDTH="10%"
-+ALIGN="right"
-+VALIGN="bottom"
-+><A
-+HREF="r3.html"
-+ACCESSKEY="N"
-+>Next</A
-+></TD
-+></TR
-+></TABLE
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"></DIV
-+><DIV
-+CLASS="REFERENCE"
-+><A
-+NAME="INDEX"
-+></A
-+><DIV
-+CLASS="TITLEPAGE"
-+><H1
-+CLASS="TITLE"
-+>I. System Manager's Manual: iputils</H1
-+><DIV
-+CLASS="TOC"
-+><DL
-+><DT
-+><B
-+>Table of Contents</B
-+></DT
-+><DT
-+><A
-+HREF="r3.html"
-+>ping</A
-+>&nbsp;--&nbsp;send ICMP ECHO_REQUEST to network hosts</DT
-+><DT
-+><A
-+HREF="r437.html"
-+>arping</A
-+>&nbsp;--&nbsp;send ARP REQUEST to a neighbour host</DT
-+><DT
-+><A
-+HREF="r596.html"
-+>clockdiff</A
-+>&nbsp;--&nbsp;measure clock difference between hosts</DT
-+><DT
-+><A
-+HREF="r691.html"
-+>rarpd</A
-+>&nbsp;--&nbsp;answer RARP REQUESTs</DT
-+><DT
-+><A
-+HREF="r790.html"
-+>tracepath</A
-+>&nbsp;--&nbsp;traces path to a network host discovering MTU along this path</DT
-+><DT
-+><A
-+HREF="r884.html"
-+>traceroute6</A
-+>&nbsp;--&nbsp;traces path to a network host</DT
-+><DT
-+><A
-+HREF="r949.html"
-+>tftpd</A
-+>&nbsp;--&nbsp;Trivial File Transfer Protocol server</DT
-+><DT
-+><A
-+HREF="r1022.html"
-+>rdisc</A
-+>&nbsp;--&nbsp;network router discovery daemon</DT
-+><DT
-+><A
-+HREF="r1144.html"
-+>pg3</A
-+>&nbsp;--&nbsp;send stream of UDP packets</DT
-+></DL
-+></DIV
-+></DIV
-+></DIV
-+><DIV
-+CLASS="NAVFOOTER"
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"><TABLE
-+SUMMARY="Footer navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+>&nbsp;</TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+>&nbsp;</TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+><A
-+HREF="r3.html"
-+ACCESSKEY="N"
-+>Next</A
-+></TD
-+></TR
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+>&nbsp;</TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+>&nbsp;</TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+>ping</TD
-+></TR
-+></TABLE
-+></DIV
-+></BODY
-+></HTML
-+>
-\ No newline at end of file
-diff -Naur iputils-s20100418.orig/doc/iputils.html iputils-s20100418/doc/iputils.html
---- iputils-s20100418.orig/doc/iputils.html	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/iputils.html	2010-08-04 22:00:33.086452519 -0400
-@@ -0,0 +1,491 @@
-+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-+<HTML
-+><HEAD
-+><TITLE
-+>iputils: documentation directory</TITLE
-+><META
-+NAME="GENERATOR"
-+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"></HEAD
-+><BODY
-+CLASS="ARTICLE"
-+BGCOLOR="#FFFFFF"
-+TEXT="#000000"
-+LINK="#0000FF"
-+VLINK="#840084"
-+ALINK="#0000FF"
-+><DIV
-+CLASS="ARTICLE"
-+><DIV
-+CLASS="TITLEPAGE"
-+><H1
-+CLASS="TITLE"
-+><A
-+NAME="AEN2"
-+>iputils: documentation directory</A
-+></H1
-+><HR></DIV
-+><DIV
-+CLASS="TOC"
-+><DL
-+><DT
-+><B
-+>Table of Contents</B
-+></DT
-+><DT
-+>1. <A
-+HREF="#AEN4"
-+>Index</A
-+></DT
-+><DT
-+>2. <A
-+HREF="#AEN34"
-+>Historical notes</A
-+></DT
-+><DT
-+>3. <A
-+HREF="#AEN89"
-+>Installation notes</A
-+></DT
-+><DT
-+>4. <A
-+HREF="#AEN109"
-+>Availability</A
-+></DT
-+><DT
-+>5. <A
-+HREF="#AEN114"
-+>Copying</A
-+></DT
-+></DL
-+></DIV
-+><DIV
-+CLASS="SECT1"
-+><H2
-+CLASS="SECT1"
-+><A
-+NAME="AEN4"
-+>1. Index</A
-+></H2
-+><P
-+></P
-+><UL
-+><LI
-+><P
-+>  <A
-+HREF="ping.html"
-+TARGET="_top"
-+>ping, ping6</A
-+>.
-+ </P
-+></LI
-+><LI
-+><P
-+>  <A
-+HREF="arping.html"
-+TARGET="_top"
-+>arping</A
-+>.
-+ </P
-+></LI
-+><LI
-+><P
-+>  <A
-+HREF="clockdiff.html"
-+TARGET="_top"
-+>clockdiff</A
-+>.
-+ </P
-+></LI
-+><LI
-+><P
-+>  <A
-+HREF="rarpd.html"
-+TARGET="_top"
-+>rarpd</A
-+>.
-+ </P
-+></LI
-+><LI
-+><P
-+>  <A
-+HREF="tracepath.html"
-+TARGET="_top"
-+>tracepath, tracepath6</A
-+>.
-+ </P
-+></LI
-+><LI
-+><P
-+>  <A
-+HREF="traceroute6.html"
-+TARGET="_top"
-+>traceroute6</A
-+>.
-+ </P
-+></LI
-+><LI
-+><P
-+>  <A
-+HREF="rdisc.html"
-+TARGET="_top"
-+>rdisc</A
-+>.
-+ </P
-+></LI
-+><LI
-+><P
-+>  <A
-+HREF="tftpd.html"
-+TARGET="_top"
-+>tftpd</A
-+>.
-+ </P
-+></LI
-+><LI
-+><P
-+>  <A
-+HREF="pg3.html"
-+TARGET="_top"
-+>pg3, ipg, pgset</A
-+>.
-+ </P
-+></LI
-+></UL
-+></DIV
-+><DIV
-+CLASS="SECT1"
-+><HR><H2
-+CLASS="SECT1"
-+><A
-+NAME="AEN34"
-+>2. Historical notes</A
-+></H2
-+><P
-+>This package appeared as a desperate attempt to bring some life
-+to state of basic networking applets: <B
-+CLASS="COMMAND"
-+>ping</B
-+>, <B
-+CLASS="COMMAND"
-+>traceroute</B
-+>
-+etc. Though it was known that port of BSD <B
-+CLASS="COMMAND"
-+>ping</B
-+> to Linux
-+was basically broken, neither maintainers of well known (and superb)
-+Linux net-tools package nor maintainers of Linux distributions
-+worried about fixing well known bugs, which were reported in linux-kernel
-+and linux-net mail lists for ages, were identified and nevertheless
-+not repaired. So, one day 1001th resuming of the subject happened
-+to be the last straw to break camel's back, I just parsed my hard disks
-+and collected a set of utilities, which shared the following properties:</P
-+><P
-+></P
-+><UL
-+><LI
-+><P
-+>Small
-+ </P
-+></LI
-+><LI
-+><P
-+>Useful despite of this
-+ </P
-+></LI
-+><LI
-+><P
-+>I never seen it was made right
-+ </P
-+></LI
-+><LI
-+><P
-+>Not quite trivial
-+ </P
-+></LI
-+><LI
-+><P
-+>Demonstrating some important feature of Linux 
-+ </P
-+></LI
-+><LI
-+><P
-+>The last but not the least, I use it more or less regularly
-+ </P
-+></LI
-+></UL
-+><P
-+>This utility set was not supposed to be a reference set or something like
-+that. Most of them were cloned from some originals:
-+<DIV
-+CLASS="INFORMALTABLE"
-+><P
-+></P
-+><A
-+NAME="AEN54"
-+></A
-+><TABLE
-+BORDER="1"
-+CLASS="CALSTABLE"
-+><COL><COL><TBODY
-+><TR
-+><TD
-+>ping</TD
-+><TD
-+>cloned of an ancient NetTools-B-xx</TD
-+></TR
-+><TR
-+><TD
-+>ping6</TD
-+><TD
-+>cloned of a very old Pedro's utility set</TD
-+></TR
-+><TR
-+><TD
-+>traceroute6</TD
-+><TD
-+>cloned of NRL Sep 96 distribution</TD
-+></TR
-+><TR
-+><TD
-+>rdisc</TD
-+><TD
-+>cloned of SUN in.rdisc</TD
-+></TR
-+><TR
-+><TD
-+>clockdiff</TD
-+><TD
-+>broken out of some BSD timed</TD
-+></TR
-+><TR
-+><TD
-+>tftpd</TD
-+><TD
-+>it is clone of some ancient NetKit package</TD
-+></TR
-+></TBODY
-+></TABLE
-+><P
-+></P
-+></DIV
-+></P
-+><P
-+>Also I added some utilities written from scratch, namely
-+<B
-+CLASS="COMMAND"
-+>tracepath</B
-+>, <B
-+CLASS="COMMAND"
-+>arping</B
-+> and later <B
-+CLASS="COMMAND"
-+>rarpd</B
-+>
-+(the last one does not satisfy all the criteria, I used it two or three
-+times).</P
-+><P
-+>Hesitated a bit I overcame temptation to add <B
-+CLASS="COMMAND"
-+>traceroute</B
-+>.
-+The variant released by LBNL to that time was mostly sane and bugs
-+in it were mostly not specific to Linux, but main reason was that
-+the latest version of LBNL <B
-+CLASS="COMMAND"
-+>traceroute</B
-+> was not 
-+<SPAN
-+CLASS="emphasis"
-+><I
-+CLASS="EMPHASIS"
-+>small</I
-+></SPAN
-+>, it consisted of several files,
-+used a wicked (and failing with Linux :-)) autoconfiguration etc.
-+So, instead I assembled to iputils a simplistic <B
-+CLASS="COMMAND"
-+>tracepath</B
-+> utility
-+and IPv6 version of traceroute, and published my 
-+<A
-+HREF="ftp://ftp.inr.ac.ru/ip-routing/lbl-tools"
-+TARGET="_top"
-+> patches</A
-+>.
-+to LBNL <B
-+CLASS="COMMAND"
-+>traceroute</B
-+> separately.<A
-+NAME="AEN86"
-+HREF="#FTN.AEN86"
-+><SPAN
-+CLASS="footnote"
-+>[1]</SPAN
-+></A
-+></P
-+></DIV
-+><DIV
-+CLASS="SECT1"
-+><HR><H2
-+CLASS="SECT1"
-+><A
-+NAME="AEN89"
-+>3. Installation notes</A
-+></H2
-+><P
-+><KBD
-+CLASS="USERINPUT"
-+>make</KBD
-+> to compile utilities. <KBD
-+CLASS="USERINPUT"
-+>make html</KBD
-+> to prepare
-+html documentation, <KBD
-+CLASS="USERINPUT"
-+>make man</KBD
-+> if you prefer man pages.
-+Nothing fancy, provided you have DocBook package installed.</P
-+><P
-+><KBD
-+CLASS="USERINPUT"
-+>make install</KBD
-+> installs <SPAN
-+CLASS="emphasis"
-+><I
-+CLASS="EMPHASIS"
-+>only</I
-+></SPAN
-+> HTML documentation
-+to <TT
-+CLASS="FILENAME"
-+>/usr/doc/iputils</TT
-+>. It even does not try
-+to install binaries and man pages. If you read historical
-+notes above, the reason should be evident. Most of utilities
-+intersect with utilities distributed in another packages, and
-+making such target rewriting existing installation would be a crime
-+from my side. The decision what variant of <B
-+CLASS="COMMAND"
-+>ping</B
-+> is preferred,
-+how to resolve the conflicts etc. is left to you or to person who
-+assembled an rpm. I vote for variant from <B
-+CLASS="COMMAND"
-+>iputils</B
-+> of course.</P
-+><P
-+>Anyway, select utilities which you like and install them to the places
-+which you prefer together with their man pages.</P
-+><P
-+>It is possible that compilation will fail, if you use some
-+funny Linux distribution mangling header files in some unexpected ways
-+(expected ones are the ways of redhat of course :-)).
-+I validate iputils against <A
-+HREF="http://www.asplinux.ru"
-+TARGET="_top"
-+>asplinux</A
-+>
-+distribution, which is inevitably followed by validity with respect
-+to <A
-+HREF="http://www.redhat.com"
-+TARGET="_top"
-+>redhat</A
-+>.
-+If your distribution is one of widely known ones, suse or debian,
-+it also will compile provided snapshot is elder than month or so and
-+someone reported all the problems, if they took place at all.</P
-+><P
-+><SPAN
-+CLASS="emphasis"
-+><I
-+CLASS="EMPHASIS"
-+>Anyway, please, do not abuse me complaining about some compilation problems
-+in any distribution different of asplinux or redhat.
-+If you have a fix, please, send it to
-+<A
-+HREF="mailto:kuznet@ms2.inr.ac.ru"
-+TARGET="_top"
-+>me</A
-+>,
-+I will check that it does not break distributions mentioned above
-+and apply it. But I am not going to undertake any investigations,
-+bare reports are deemed to be routed to <TT
-+CLASS="FILENAME"
-+>/dev/null</TT
-+>.</I
-+></SPAN
-+></P
-+></DIV
-+><DIV
-+CLASS="SECT1"
-+><HR><H2
-+CLASS="SECT1"
-+><A
-+NAME="AEN109"
-+>4. Availability</A
-+></H2
-+><P
-+>The collection of documents is part of <TT
-+CLASS="FILENAME"
-+>iputils</TT
-+> package
-+and the latest versions are  available in source form at
-+<A
-+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
-+TARGET="_top"
-+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="SECT1"
-+><HR><H2
-+CLASS="SECT1"
-+><A
-+NAME="AEN114"
-+>5. Copying</A
-+></H2
-+><P
-+>Different files are copyrighted by different persons and organizations
-+and distributed under different licenses. For details look into corresponding
-+source files.</P
-+></DIV
-+></DIV
-+><H3
-+CLASS="FOOTNOTES"
-+>Notes</H3
-+><TABLE
-+BORDER="0"
-+CLASS="FOOTNOTES"
-+WIDTH="100%"
-+><TR
-+><TD
-+ALIGN="LEFT"
-+VALIGN="TOP"
-+WIDTH="5%"
-+><A
-+NAME="FTN.AEN86"
-+HREF="#AEN86"
-+><SPAN
-+CLASS="footnote"
-+>[1]</SPAN
-+></A
-+></TD
-+><TD
-+ALIGN="LEFT"
-+VALIGN="TOP"
-+WIDTH="95%"
-+><P
-+>This was mistake.
-+Due to this <B
-+CLASS="COMMAND"
-+>traceroute</B
-+> was in a sad state until recently.
-+Good news, redhat-7.2 seems to add these patches to their traceroute
-+rpm eventually. So, I think I will refrain of suicide for awhile.</P
-+></TD
-+></TR
-+></TABLE
-+></BODY
-+></HTML
-+>
-\ No newline at end of file
-diff -Naur iputils-s20100418.orig/doc/pg3.8 iputils-s20100418/doc/pg3.8
---- iputils-s20100418.orig/doc/pg3.8	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/pg3.8	2010-08-04 22:00:21.690453269 -0400
-@@ -0,0 +1,86 @@
-+.\" This manpage has been automatically generated by docbook2man 
-+.\" from a DocBook document.  This tool can be found at:
-+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
-+.\" Please send any bug reports, improvements, comments, patches, 
-+.\" etc. to Steve Cheng <steve@ggi-project.org>.
-+.TH "PG3" "8" "04 August 2010" "iputils-100418" "System Manager's Manual: iputils"
-+.SH NAME
-+pg3, ipg, pgset \- send stream of UDP packets
-+.SH SYNOPSIS
-+
-+\fBsource ipg\fR
-+
-+
-+\fBpg\fR
-+
-+
-+\fBpgset\fR \fB\fICOMMAND\fB\fR
-+
-+.SH "DESCRIPTION"
-+.PP
-+\fBipg\fR is not a program, it is script which should be sourced
-+to \fBbash\fR. When sourced it loads module \fIpg3\fR and
-+exports a few of functions accessible from parent shell. These macros
-+are \fBpg\fR to start packet injection and to get the results of run;
-+and \fBpgset\fR to setup packet generator.
-+.PP
-+\fBpgset\fR can send the following commands to module \fIpg3\fR:
-+.SH "COMMAND"
-+.TP
-+\fBodev \fIDEVICE\fB\fR
-+Name of Ethernet device to test. See
-+warning below.
-+.TP
-+\fBpkt_size \fIBYTES\fB\fR
-+Size of packet to generate. The size includes all the headers: UDP, IP,
-+MAC, but does not account for overhead internal to medium, i.e. FCS
-+and various paddings.
-+.TP
-+\fBfrags \fINUMBER\fB\fR
-+Each packet will contain \fINUMBER\fR of fragments.
-+Maximal amount for linux-2.4 is 6. Far not all the devices support
-+fragmented buffers.
-+.TP
-+\fBcount \fINUMBER\fB\fR
-+Send stream of \fINUMBER\fR of packets and stop after this.
-+.TP
-+\fBipg \fITIME\fB\fR
-+Introduce artificial delay between packets of \fITIME\fR
-+microseconds.
-+.TP
-+\fBdst \fIIP_ADDRESS\fB\fR
-+Select IP destination where the stream is sent to.
-+Beware, never set this address at random. \fBpg3\fR is not a toy,
-+it creates really tough stream. Default value is 0.0.0.0.
-+.TP
-+\fBdst \fIMAC_ADDRESS\fB\fR
-+Select MAC destination where the stream is sent to.
-+Default value is 00:00:00:00:00:00 in hope that this will not be received
-+by any node on LAN.
-+.TP
-+\fBstop\fR
-+Abort packet injection.
-+.SH "WARNING"
-+.PP
-+When output device is set to some random device different
-+of hardware Ethernet device, \fBpg3\fR will crash kernel.
-+.PP
-+Do not use it on VLAN, ethertap, VTUN and other devices,
-+which emulate Ethernet not being real Ethernet in fact.
-+.SH "AUTHOR"
-+.PP
-+\fBpg3\fR was written by Robert Olsson <robert.olsson@its.uu.se>.
-+.SH "SECURITY"
-+.PP
-+This can be used only by superuser.
-+.PP
-+This tool creates floods of packets which is unlikely to be handled
-+even by high-end machines. For example, it saturates gigabit link with
-+60 byte packets when used with Intel's e1000. In face of such stream
-+switches, routers and end hosts may deadlock, crash, explode.
-+Use only in test lab environment.
-+.SH "AVAILABILITY"
-+.PP
-+\fBpg3\fR is part of \fIiputils\fR package
-+and the latest versions are  available in source form at
-+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
-diff -Naur iputils-s20100418.orig/doc/ping.8 iputils-s20100418/doc/ping.8
---- iputils-s20100418.orig/doc/ping.8	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/ping.8	2010-08-04 22:00:25.102076673 -0400
-@@ -0,0 +1,408 @@
-+.\" This manpage has been automatically generated by docbook2man 
-+.\" from a DocBook document.  This tool can be found at:
-+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
-+.\" Please send any bug reports, improvements, comments, patches, 
-+.\" etc. to Steve Cheng <steve@ggi-project.org>.
-+.TH "PING" "8" "04 August 2010" "iputils-100418" "System Manager's Manual: iputils"
-+.SH NAME
-+ping, ping6 \- send ICMP ECHO_REQUEST to network hosts
-+.SH SYNOPSIS
-+
-+\fBping\fR [\fB-LRUbdfnqrvVaAB\fR] [\fB-c \fIcount\fB\fR] [\fB-m \fImark\fB\fR] [\fB-i \fIinterval\fB\fR] [\fB-l \fIpreload\fB\fR] [\fB-p \fIpattern\fB\fR] [\fB-s \fIpacketsize\fB\fR] [\fB-t \fIttl\fB\fR] [\fB-w \fIdeadline\fB\fR] [\fB-F \fIflowlabel\fB\fR] [\fB-I \fIinterface\fB\fR] [\fB-M \fIhint\fB\fR] [\fB-N \fInioption\fB\fR] [\fB-Q \fItos\fB\fR] [\fB-S \fIsndbuf\fB\fR] [\fB-T \fItimestamp option\fB\fR] [\fB-W \fItimeout\fB\fR] [\fB\fIhop\fB\fR\fI ...\fR] \fB\fIdestination\fB\fR
-+
-+.SH "DESCRIPTION"
-+.PP
-+\fBping\fR uses the ICMP protocol's mandatory ECHO_REQUEST
-+datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway.
-+ECHO_REQUEST datagrams (``pings'') have an IP and ICMP
-+header, followed by a struct timeval and then an arbitrary
-+number of ``pad'' bytes used to fill out the packet.
-+.PP
-+\fBping6\fR can also send Node Information Queries (RFC4620).
-+.SH "OPTIONS"
-+.TP
-+\fB-a\fR
-+Audible ping.
-+.TP
-+\fB-A\fR
-+Adaptive ping. Interpacket interval adapts to round-trip time, so that
-+effectively not more than one (or more, if preload is set) unanswered probes
-+present in the network. Minimal interval is 200msec for not super-user.
-+On networks with low rtt this mode is essentially equivalent to flood mode.  
-+.TP
-+\fB-b\fR
-+Allow pinging a broadcast address.
-+.TP
-+\fB-B\fR
-+Do not allow \fBping\fR to change source address of probes.
-+The address is bound to one selected when \fBping\fR starts.
-+.TP
-+\fB-m \fImark\fB\fR
-+use \fImark\fR to tag the packets going out. This is useful
-+for variety of reasons within the kernel such as using policy
-+routing to select specific outbound processing.
-+.TP
-+\fB-c \fIcount\fB\fR
-+Stop after sending \fIcount\fR ECHO_REQUEST
-+packets. With 
-+\fIdeadline\fR
-+option, \fBping\fR waits for
-+\fIcount\fR ECHO_REPLY packets, until the timeout expires.
-+.TP
-+\fB-d\fR
-+Set the SO_DEBUG option on the socket being used.
-+Essentially, this socket option is not used by Linux kernel. 
-+.TP
-+\fB-F \fIflow label\fB\fR
-+Allocate and set 20 bit flow label on echo request packets.
-+(Only \fBping6\fR). If value is zero, kernel allocates random flow label.
-+.TP
-+\fB-f\fR
-+Flood ping. For every ECHO_REQUEST sent a period ``.'' is printed,
-+while for ever ECHO_REPLY received a backspace is printed.
-+This provides a rapid display of how many packets are being dropped.
-+If interval is not given, it sets interval to zero and
-+outputs packets as fast as they come back or one hundred times per second,
-+whichever is more.
-+Only the super-user may use this option with zero interval.
-+.TP
-+\fB-i \fIinterval\fB\fR
-+Wait \fIinterval\fR seconds between sending each packet.
-+The default is to wait for one second between each packet normally,
-+or not to wait in flood mode. Only super-user may set interval
-+to values less 0.2 seconds.
-+.TP
-+\fB-I \fIinterface address\fB\fR
-+Set source address to specified interface address. Argument
-+may be numeric IP address or name of device. When pinging IPv6
-+link-local address this option is required.
-+.TP
-+\fB-l \fIpreload\fB\fR
-+If \fIpreload\fR is specified,
-+\fBping\fR sends that many packets not waiting for reply.
-+Only the super-user may select preload more than 3.
-+.TP
-+\fB-L\fR
-+Suppress loopback of multicast packets.  This flag only applies if the ping
-+destination is a multicast address.
-+.TP
-+\fB-N \fInioption\fB\fR
-+Send ICMPv6 Node Information Queries (RFC4620), instead of Echo Request.
-+.RS
-+.TP
-+\fBname\fR
-+Queries for Node Names.
-+.RE
-+.RS
-+.TP
-+\fBipv6\fR
-+Queries for IPv6 Addresses. There are several IPv6 specific flags.
-+.RS
-+.TP
-+\fBipv6-global\fR
-+Request IPv6 global-scope addresses.
-+.RE
-+.RS
-+.TP
-+\fBipv6-sitelocal\fR
-+Request IPv6 site-local addresses.
-+.RE
-+.RS
-+.TP
-+\fBipv6-linklocal\fR
-+Request IPv6 link-local addresses.
-+.RE
-+.RS
-+.TP
-+\fBipv6-all\fR
-+Request IPv6 addresses on other interfaces.
-+.RE
-+.RE
-+.RS
-+.TP
-+\fBipv4\fR
-+Queries for IPv4 Addresses.  There is one IPv4 specific flag.
-+.RS
-+.TP
-+\fBipv4-all\fR
-+Request IPv4 addresses on other interfaces.
-+.RE
-+.RE
-+.RS
-+.TP
-+\fBsubject-ipv6=\fIipv6addr\fB\fR
-+IPv6 subject address.
-+.RE
-+.RS
-+.TP
-+\fBsubject-ipv4=\fIipv4addr\fB\fR
-+IPv4 subject address.
-+.RE
-+.RS
-+.TP
-+\fBsubject-name=\fInodename\fB\fR
-+Subject name.  If it contains more than one dot,
-+fully-qualified domain name is assumed.
-+.RE
-+.RS
-+.TP
-+\fBsubject-fqdn=\fInodename\fB\fR
-+Subject name.  Fully-qualified domain name is
-+always assumed.
-+.RE
-+.TP
-+\fB-n\fR
-+Numeric output only.
-+No attempt will be made to lookup symbolic names for host addresses.
-+.TP
-+\fB-p \fIpattern\fB\fR
-+You may specify up to 16 ``pad'' bytes to fill out the packet you send.
-+This is useful for diagnosing data-dependent problems in a network.
-+For example, \fB-p ff\fR will cause the sent packet
-+to be filled with all ones.
-+.TP
-+\fB-D\fR
-+Print timestamp (unix time + microseconds as in gettimeofday) before
-+each line.
-+.TP
-+\fB-Q \fItos\fB\fR
-+Set Quality of Service -related bits in ICMP datagrams.  
-+\fItos\fR can be either decimal or hex number.
-+Traditionally (RFC1349), these have been interpreted as: 0 for reserved
-+(currently being redefined as congestion control), 1-4 for Type of Service
-+and 5-7 for Precedence.
-+Possible settings for Type of Service are: minimal cost: 0x02, 
-+reliability: 0x04, throughput: 0x08, low delay: 0x10.  Multiple TOS bits
-+should not be set simultaneously.  Possible settings for
-+special Precedence range from priority (0x20) to net control (0xe0).  You
-+must be root (CAP_NET_ADMIN capability) to use Critical or
-+higher precedence value.  You cannot set
-+bit 0x01 (reserved) unless ECN has been enabled in the kernel.
-+In RFC2474, these fields has been redefined as 8-bit Differentiated
-+Services (DS), consisting of: bits 0-1 of separate data (ECN will be used,
-+here), and bits 2-7 of Differentiated Services Codepoint (DSCP).
-+.TP
-+\fB-q\fR
-+Quiet output.
-+Nothing is displayed except the summary lines at startup time and
-+when finished.
-+.TP
-+\fB-R\fR
-+Record route.
-+Includes the RECORD_ROUTE option in the ECHO_REQUEST
-+packet and displays the route buffer on returned packets.
-+Note that the IP header is only large enough for nine such routes.
-+Many hosts ignore or discard this option.
-+.TP
-+\fB-r\fR
-+Bypass the normal routing tables and send directly to a host on an attached
-+interface.
-+If the host is not on a directly-attached network, an error is returned.
-+This option can be used to ping a local host through an interface
-+that has no route through it provided the option \fB-I\fR is also
-+used.
-+.TP
-+\fB-s \fIpacketsize\fB\fR
-+Specifies the number of data bytes to be sent.  
-+The default is 56, which translates into 64 ICMP
-+data bytes when combined with the 8 bytes of ICMP header data.
-+.TP
-+\fB-S \fIsndbuf\fB\fR
-+Set socket sndbuf. If not specified, it is selected to buffer
-+not more than one packet.
-+.TP
-+\fB-t \fIttl\fB\fR
-+Set the IP Time to Live.
-+.TP
-+\fB-T \fItimestamp option\fB\fR
-+Set special IP timestamp options.
-+\fItimestamp option\fR may be either 
-+\fItsonly\fR (only timestamps), 
-+\fItsandaddr\fR (timestamps and addresses) or 
-+\fItsprespec host1 [host2 [host3 [host4]]]\fR
-+(timestamp prespecified hops).
-+.TP
-+\fB-M \fIhint\fB\fR
-+Select Path MTU Discovery strategy.
-+\fIhint\fR may be either \fIdo\fR
-+(prohibit fragmentation, even local one), 
-+\fIwant\fR (do PMTU discovery, fragment locally when packet size
-+is large), or \fIdont\fR (do not set DF flag).
-+.TP
-+\fB-U\fR
-+Print full user-to-user latency (the old behaviour). Normally
-+\fBping\fR
-+prints network round trip time, which can be different
-+f.e. due to DNS failures. 
-+.TP
-+\fB-v\fR
-+Verbose output.
-+.TP
-+\fB-V\fR
-+Show version and exit.
-+.TP
-+\fB-w \fIdeadline\fB\fR
-+Specify a timeout, in seconds, before
-+\fBping\fR
-+exits regardless of how many
-+packets have been sent or received. In this case
-+\fBping\fR
-+does not stop after
-+\fIcount\fR
-+packet are sent, it waits either for
-+\fIdeadline\fR
-+expire or until
-+\fIcount\fR
-+probes are answered or for some error notification from network.   
-+.TP
-+\fB-W \fItimeout\fB\fR
-+Time to wait for a response, in seconds. The option affects only timeout
-+in absense of any responses, otherwise \fBping\fR waits for two RTTs.
-+.PP
-+When using \fBping\fR for fault isolation, it should first be run
-+on the local host, to verify that the local network interface is up
-+and running. Then, hosts and gateways further and further away should be
-+``pinged''. Round-trip times and packet loss statistics are computed.
-+If duplicate packets are received, they are not included in the packet
-+loss calculation, although the round trip time of these packets is used
-+in calculating the minimum/average/maximum round-trip time numbers.
-+When the specified number of packets have been sent (and received) or
-+if the program is terminated with a
-+SIGINT, a brief summary is displayed. Shorter current statistics
-+can be obtained without termination of process with signal
-+SIGQUIT.
-+.PP
-+If \fBping\fR does not receive any reply packets at all it will
-+exit with code 1. If a packet 
-+\fIcount\fR
-+and
-+\fIdeadline\fR
-+are both specified, and fewer than
-+\fIcount\fR
-+packets are received by the time the
-+\fIdeadline\fR
-+has arrived, it will also exit with code 1. 
-+On other error it exits with code 2. Otherwise it exits with code 0. This
-+makes it possible to use the exit code to see if a host is alive or
-+not.
-+.PP
-+This program is intended for use in network testing, measurement and
-+management.
-+Because of the load it can impose on the network, it is unwise to use
-+\fBping\fR during normal operations or from automated scripts.
-+.SH "ICMP PACKET DETAILS"
-+.PP
-+An IP header without options is 20 bytes.
-+An ICMP ECHO_REQUEST packet contains an additional 8 bytes worth
-+of ICMP header followed by an arbitrary amount of data.
-+When a \fIpacketsize\fR is given, this indicated the size of this
-+extra piece of data (the default is 56). Thus the amount of data received
-+inside of an IP packet of type ICMP ECHO_REPLY will always be 8 bytes
-+more than the requested data space (the ICMP header).
-+.PP
-+If the data space is at least of size of struct timeval
-+\fBping\fR uses the beginning bytes of this space to include
-+a timestamp which it uses in the computation of round trip times.
-+If the data space is shorter, no round trip times are given.
-+.SH "DUPLICATE AND DAMAGED PACKETS"
-+.PP
-+\fBping\fR will report duplicate and damaged packets.
-+Duplicate packets should never occur, and seem to be caused by
-+inappropriate link-level retransmissions.
-+Duplicates may occur in many situations and are rarely (if ever) a
-+good sign, although the presence of low levels of duplicates may not
-+always be cause for alarm.
-+.PP
-+Damaged packets are obviously serious cause for alarm and often
-+indicate broken hardware somewhere in the
-+\fBping\fR packet's path (in the network or in the hosts).
-+.SH "TRYING DIFFERENT DATA PATTERNS"
-+.PP
-+The (inter)network layer should never treat packets differently depending
-+on the data contained in the data portion.
-+Unfortunately, data-dependent problems have been known to sneak into
-+networks and remain undetected for long periods of time.
-+In many cases the particular pattern that will have problems is something
-+that doesn't have sufficient ``transitions'', such as all ones or all
-+zeros, or a pattern right at the edge, such as almost all zeros.
-+It isn't necessarily enough to specify a data pattern of all zeros (for
-+example) on the command line because the pattern that is of interest is
-+at the data link level, and the relationship between what you type and
-+what the controllers transmit can be complicated.
-+.PP
-+This means that if you have a data-dependent problem you will probably
-+have to do a lot of testing to find it.
-+If you are lucky, you may manage to find a file that either can't be sent
-+across your network or that takes much longer to transfer than other
-+similar length files.
-+You can then examine this file for repeated patterns that you can test
-+using the \fB-p\fR option of \fBping\fR.
-+.SH "TTL DETAILS"
-+.PP
-+The TTL value of an IP packet represents the maximum number of IP routers
-+that the packet can go through before being thrown away.
-+In current practice you can expect each router in the Internet to decrement
-+the TTL field by exactly one.
-+.PP
-+The TCP/IP specification states that the TTL field for TCP
-+packets should be set to 60, but many systems use smaller values
-+(4.3 BSD uses 30, 4.2 used 15).
-+.PP
-+The maximum possible value of this field is 255, and most Unix systems set
-+the TTL field of ICMP ECHO_REQUEST packets to 255.
-+This is why you will find you can ``ping'' some hosts, but not reach them
-+with
-+\fBtelnet\fR(1)
-+or
-+\fBftp\fR(1).
-+.PP
-+In normal operation ping prints the ttl value from the packet it receives.
-+When a remote system receives a ping packet, it can do one of three things
-+with the TTL field in its response:
-+.TP 0.2i
-+\(bu
-+Not change it; this is what Berkeley Unix systems did before the
-+4.3BSD Tahoe release. In this case the TTL value in the received packet
-+will be 255 minus the number of routers in the round-trip path.
-+.TP 0.2i
-+\(bu
-+Set it to 255; this is what current Berkeley Unix systems do.
-+In this case the TTL value in the received packet will be 255 minus the
-+number of routers in the path \fBfrom\fR
-+the remote system \fBto\fR the \fBping\fRing host.
-+.TP 0.2i
-+\(bu
-+Set it to some other value. Some machines use the same value for
-+ICMP packets that they use for TCP packets, for example either 30 or 60.
-+Others may use completely wild values.
-+.SH "BUGS"
-+.TP 0.2i
-+\(bu
-+Many Hosts and Gateways ignore the RECORD_ROUTE option.
-+.TP 0.2i
-+\(bu
-+The maximum IP header length is too small for options like
-+RECORD_ROUTE to be completely useful.
-+There's not much that that can be done about this, however.
-+.TP 0.2i
-+\(bu
-+Flood pinging is not recommended in general, and flood pinging the
-+broadcast address should only be done under very controlled conditions.
-+.SH "SEE ALSO"
-+.PP
-+\fBnetstat\fR(1),
-+\fBifconfig\fR(8).
-+.SH "HISTORY"
-+.PP
-+The \fBping\fR command appeared in 4.3BSD.
-+.PP
-+The version described here is its descendant specific to Linux.
-+.SH "SECURITY"
-+.PP
-+\fBping\fR requires CAP_NET_RAWIO capability
-+to be executed. It may be used as set-uid root.
-+.SH "AVAILABILITY"
-+.PP
-+\fBping\fR is part of \fIiputils\fR package
-+and the latest versions are  available in source form at
-+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
-diff -Naur iputils-s20100418.orig/doc/r1022.html iputils-s20100418/doc/r1022.html
---- iputils-s20100418.orig/doc/r1022.html	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/r1022.html	2010-08-04 22:00:32.441576445 -0400
-@@ -0,0 +1,511 @@
-+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-+<HTML
-+><HEAD
-+><TITLE
-+>rdisc</TITLE
-+><META
-+NAME="GENERATOR"
-+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-+REL="HOME"
-+TITLE="System Manager's Manual: iputils"
-+HREF="index.html"><LINK
-+REL="PREVIOUS"
-+TITLE="tftpd"
-+HREF="r949.html"><LINK
-+REL="NEXT"
-+TITLE="pg3"
-+HREF="r1144.html"></HEAD
-+><BODY
-+CLASS="REFENTRY"
-+BGCOLOR="#FFFFFF"
-+TEXT="#000000"
-+LINK="#0000FF"
-+VLINK="#840084"
-+ALINK="#0000FF"
-+><DIV
-+CLASS="NAVHEADER"
-+><TABLE
-+SUMMARY="Header navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TH
-+COLSPAN="3"
-+ALIGN="center"
-+>System Manager's Manual: iputils</TH
-+></TR
-+><TR
-+><TD
-+WIDTH="10%"
-+ALIGN="left"
-+VALIGN="bottom"
-+><A
-+HREF="r949.html"
-+ACCESSKEY="P"
-+>Prev</A
-+></TD
-+><TD
-+WIDTH="80%"
-+ALIGN="center"
-+VALIGN="bottom"
-+></TD
-+><TD
-+WIDTH="10%"
-+ALIGN="right"
-+VALIGN="bottom"
-+><A
-+HREF="r1144.html"
-+ACCESSKEY="N"
-+>Next</A
-+></TD
-+></TR
-+></TABLE
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"></DIV
-+><H1
-+><A
-+NAME="RDISC"
-+></A
-+>rdisc</H1
-+><DIV
-+CLASS="REFNAMEDIV"
-+><A
-+NAME="AEN1027"
-+></A
-+><H2
-+>Name</H2
-+>rdisc&nbsp;--&nbsp;network router discovery daemon</DIV
-+><DIV
-+CLASS="REFSYNOPSISDIV"
-+><A
-+NAME="AEN1030"
-+></A
-+><H2
-+>Synopsis</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>rdisc</B
-+>  [<CODE
-+CLASS="OPTION"
-+>-abdfstvV</CODE
-+>] [<TT
-+CLASS="REPLACEABLE"
-+><I
-+>send_address</I
-+></TT
-+>] [<TT
-+CLASS="REPLACEABLE"
-+><I
-+>receive_address</I
-+></TT
-+>]</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN1039"
-+></A
-+><H2
-+>DESCRIPTION</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>rdisc</B
-+> implements client side of the ICMP router discover protocol.
-+<B
-+CLASS="COMMAND"
-+>rdisc</B
-+> is invoked at boot time to populate the network
-+routing tables with default routes. </P
-+><P
-+><B
-+CLASS="COMMAND"
-+>rdisc</B
-+> listens on the ALL_HOSTS (224.0.0.1) multicast address
-+(or <TT
-+CLASS="REPLACEABLE"
-+><I
-+>receive_address</I
-+></TT
-+> provided it is given) 
-+for ROUTER_ADVERTISE messages from routers. The received
-+messages are handled by first ignoring those listed router addresses
-+with which the host does not share a network. Among the remaining addresses
-+the ones with the highest preference are selected as default routers
-+and a default route is entered in the kernel routing table
-+for each one of them.</P
-+><P
-+>Optionally, <B
-+CLASS="COMMAND"
-+>rdisc</B
-+> can avoid waiting for routers to announce 
-+themselves by sending out a few ROUTER_SOLICITATION messages
-+to the ALL_ROUTERS (224.0.0.2) multicast address 
-+(or <TT
-+CLASS="REPLACEABLE"
-+><I
-+>send_address</I
-+></TT
-+> provided it is given) 
-+when it is started.</P
-+><P
-+>A timer is associated with each router address and the address will
-+no longer be considered for inclusion in the the routing tables if the 
-+timer expires before a new 
-+<SPAN
-+CLASS="emphasis"
-+><I
-+CLASS="EMPHASIS"
-+>advertise</I
-+></SPAN
-+> message is received from the router.
-+The address will also be excluded from consideration if the host receives an 
-+<SPAN
-+CLASS="emphasis"
-+><I
-+CLASS="EMPHASIS"
-+>advertise</I
-+></SPAN
-+>
-+message with the preference being maximally negative.</P
-+><P
-+>Server side of router discovery protocol is supported by Cisco IOS
-+and by any more or less complete UNIX routing daemon, f.e <B
-+CLASS="COMMAND"
-+>gated</B
-+>.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN1055"
-+></A
-+><H2
-+>OPTIONS</H2
-+><P
-+></P
-+><DIV
-+CLASS="VARIABLELIST"
-+><DL
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-a</CODE
-+></DT
-+><DD
-+><P
-+>Accept all routers independently of the preference they have in their 
-+<SPAN
-+CLASS="emphasis"
-+><I
-+CLASS="EMPHASIS"
-+>advertise</I
-+></SPAN
-+> messages.
-+Normally <B
-+CLASS="COMMAND"
-+>rdisc</B
-+> only accepts (and enters in the kernel routing
-+tables) the router or routers with the highest preference.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-b</CODE
-+></DT
-+><DD
-+><P
-+>Opposite to <CODE
-+CLASS="OPTION"
-+>-a</CODE
-+>, i.e. install only router with the best
-+preference value. It is default behaviour.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-d</CODE
-+></DT
-+><DD
-+><P
-+>Send debugging messages to syslog.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-f</CODE
-+></DT
-+><DD
-+><P
-+>Run <B
-+CLASS="COMMAND"
-+>rdisc</B
-+> forever even if no routers are found.
-+Normally <B
-+CLASS="COMMAND"
-+>rdisc</B
-+> gives up if it has not received any 
-+<SPAN
-+CLASS="emphasis"
-+><I
-+CLASS="EMPHASIS"
-+>advertise</I
-+></SPAN
-+> message after after soliciting three times,
-+in which case it exits with a non-zero exit code.
-+If <CODE
-+CLASS="OPTION"
-+>-f</CODE
-+> is not specified in the first form then 
-+<CODE
-+CLASS="OPTION"
-+>-s</CODE
-+> must be specified.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-s</CODE
-+></DT
-+><DD
-+><P
-+>Send three <SPAN
-+CLASS="emphasis"
-+><I
-+CLASS="EMPHASIS"
-+>solicitation</I
-+></SPAN
-+> messages initially to quickly discover
-+the routers when the system is booted.
-+When <CODE
-+CLASS="OPTION"
-+>-s</CODE
-+> is specified <B
-+CLASS="COMMAND"
-+>rdisc</B
-+>
-+exits with a non-zero exit code if it can not find any routers.
-+This can be overridden with the <CODE
-+CLASS="OPTION"
-+>-f</CODE
-+> option.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-t</CODE
-+></DT
-+><DD
-+><P
-+>Test mode. Do not go to background.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-v</CODE
-+></DT
-+><DD
-+><P
-+>Be verbose i.e. send lots of debugging messages to syslog.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-V</CODE
-+></DT
-+><DD
-+><P
-+>Print version and exit.
-+  </P
-+></DD
-+></DL
-+></DIV
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN1110"
-+></A
-+><H2
-+>HISTORY</H2
-+><P
-+>This program was developed by Sun Microsystems (see copyright
-+notice in source file). It was ported to Linux by
-+<A
-+HREF="mailto:kuznet@ms2.inr.ac.ru"
-+TARGET="_top"
-+>Alexey Kuznetsov
-+&lt;kuznet@ms2.inr.ac.ru&gt;</A
-+>.
-+It is now maintained by
-+<A
-+HREF="mailto:yoshfuji@skbuff.net"
-+TARGET="_top"
-+>YOSHIFUJI Hideaki
-+&lt;yoshfuji@skbuff.net&gt;</A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN1115"
-+></A
-+><H2
-+>SEE ALSO</H2
-+><P
-+><SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>icmp</SPAN
-+>(7)</SPAN
-+>,
-+<SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>inet</SPAN
-+>(7)</SPAN
-+>,
-+<A
-+HREF="r3.html"
-+><SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>ping</SPAN
-+>(8)</SPAN
-+></A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN1128"
-+></A
-+><H2
-+>REFERENCES</H2
-+><P
-+>Deering, S.E.,ed "ICMP Router Discovery Messages",
-+<A
-+HREF="ftp://ftp.isi.edu/in-notes/rfc1256.txt"
-+TARGET="_top"
-+>RFC1256</A
-+>, Network Information Center, SRI International,
-+Menlo Park, Calif., September 1991.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN1132"
-+></A
-+><H2
-+>SECURITY</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>rdisc</B
-+> requires <CODE
-+CLASS="CONSTANT"
-+>CAP_NET_RAWIO</CODE
-+> to listen
-+and send ICMP messages and capability <CODE
-+CLASS="CONSTANT"
-+>CAP_NET_ADMIN</CODE
-+>
-+to update routing tables. </P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN1138"
-+></A
-+><H2
-+>AVAILABILITY</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>rdisc</B
-+> is part of <TT
-+CLASS="FILENAME"
-+>iputils</TT
-+> package
-+and the latest versions are  available in source form at
-+<A
-+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
-+TARGET="_top"
-+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="NAVFOOTER"
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"><TABLE
-+SUMMARY="Footer navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+><A
-+HREF="r949.html"
-+ACCESSKEY="P"
-+>Prev</A
-+></TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+><A
-+HREF="index.html"
-+ACCESSKEY="H"
-+>Home</A
-+></TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+><A
-+HREF="r1144.html"
-+ACCESSKEY="N"
-+>Next</A
-+></TD
-+></TR
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+>tftpd</TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+>&nbsp;</TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+>pg3</TD
-+></TR
-+></TABLE
-+></DIV
-+></BODY
-+></HTML
-+>
-\ No newline at end of file
-diff -Naur iputils-s20100418.orig/doc/r1144.html iputils-s20100418/doc/r1144.html
---- iputils-s20100418.orig/doc/r1144.html	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/r1144.html	2010-08-04 22:00:32.445575810 -0400
-@@ -0,0 +1,428 @@
-+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-+<HTML
-+><HEAD
-+><TITLE
-+>pg3</TITLE
-+><META
-+NAME="GENERATOR"
-+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-+REL="HOME"
-+TITLE="System Manager's Manual: iputils"
-+HREF="index.html"><LINK
-+REL="PREVIOUS"
-+TITLE="rdisc"
-+HREF="r1022.html"></HEAD
-+><BODY
-+CLASS="REFENTRY"
-+BGCOLOR="#FFFFFF"
-+TEXT="#000000"
-+LINK="#0000FF"
-+VLINK="#840084"
-+ALINK="#0000FF"
-+><DIV
-+CLASS="NAVHEADER"
-+><TABLE
-+SUMMARY="Header navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TH
-+COLSPAN="3"
-+ALIGN="center"
-+>System Manager's Manual: iputils</TH
-+></TR
-+><TR
-+><TD
-+WIDTH="10%"
-+ALIGN="left"
-+VALIGN="bottom"
-+><A
-+HREF="r1022.html"
-+ACCESSKEY="P"
-+>Prev</A
-+></TD
-+><TD
-+WIDTH="80%"
-+ALIGN="center"
-+VALIGN="bottom"
-+></TD
-+><TD
-+WIDTH="10%"
-+ALIGN="right"
-+VALIGN="bottom"
-+>&nbsp;</TD
-+></TR
-+></TABLE
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"></DIV
-+><H1
-+><A
-+NAME="PG3"
-+></A
-+>pg3</H1
-+><DIV
-+CLASS="REFNAMEDIV"
-+><A
-+NAME="AEN1149"
-+></A
-+><H2
-+>Name</H2
-+>pg3, ipg, pgset&nbsp;--&nbsp;send stream of UDP packets</DIV
-+><DIV
-+CLASS="REFSYNOPSISDIV"
-+><A
-+NAME="AEN1152"
-+></A
-+><H2
-+>Synopsis</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>source ipg</B
-+> </P
-+><P
-+><B
-+CLASS="COMMAND"
-+>pg</B
-+> </P
-+><P
-+><B
-+CLASS="COMMAND"
-+>pgset</B
-+>  {<TT
-+CLASS="REPLACEABLE"
-+><I
-+>COMMAND</I
-+></TT
-+>}</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN1161"
-+></A
-+><H2
-+>DESCRIPTION</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>ipg</B
-+> is not a program, it is script which should be sourced
-+to <B
-+CLASS="COMMAND"
-+>bash</B
-+>. When sourced it loads module <TT
-+CLASS="FILENAME"
-+>pg3</TT
-+> and
-+exports a few of functions accessible from parent shell. These macros
-+are <B
-+CLASS="COMMAND"
-+>pg</B
-+> to start packet injection and to get the results of run;
-+and <B
-+CLASS="COMMAND"
-+>pgset</B
-+> to setup packet generator.</P
-+><P
-+><B
-+CLASS="COMMAND"
-+>pgset</B
-+> can send the following commands to module <TT
-+CLASS="FILENAME"
-+>pg3</TT
-+>:</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN1172"
-+></A
-+><H2
-+>COMMAND</H2
-+><P
-+></P
-+><DIV
-+CLASS="VARIABLELIST"
-+><DL
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>odev <TT
-+CLASS="REPLACEABLE"
-+><I
-+>DEVICE</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Name of Ethernet device to test. See
-+<A
-+HREF="r1144.html#PG3.WARNING"
-+>warning</A
-+> below.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>pkt_size <TT
-+CLASS="REPLACEABLE"
-+><I
-+>BYTES</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Size of packet to generate. The size includes all the headers: UDP, IP,
-+MAC, but does not account for overhead internal to medium, i.e. FCS
-+and various paddings.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>frags <TT
-+CLASS="REPLACEABLE"
-+><I
-+>NUMBER</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Each packet will contain <TT
-+CLASS="REPLACEABLE"
-+><I
-+>NUMBER</I
-+></TT
-+> of fragments.
-+Maximal amount for linux-2.4 is 6. Far not all the devices support
-+fragmented buffers.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>count <TT
-+CLASS="REPLACEABLE"
-+><I
-+>NUMBER</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Send stream of <TT
-+CLASS="REPLACEABLE"
-+><I
-+>NUMBER</I
-+></TT
-+> of packets and stop after this.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>ipg <TT
-+CLASS="REPLACEABLE"
-+><I
-+>TIME</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Introduce artificial delay between packets of <TT
-+CLASS="REPLACEABLE"
-+><I
-+>TIME</I
-+></TT
-+>
-+microseconds.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>dst <TT
-+CLASS="REPLACEABLE"
-+><I
-+>IP_ADDRESS</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Select IP destination where the stream is sent to.
-+Beware, never set this address at random. <B
-+CLASS="COMMAND"
-+>pg3</B
-+> is not a toy,
-+it creates really tough stream. Default value is 0.0.0.0.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>dst <TT
-+CLASS="REPLACEABLE"
-+><I
-+>MAC_ADDRESS</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Select MAC destination where the stream is sent to.
-+Default value is 00:00:00:00:00:00 in hope that this will not be received
-+by any node on LAN.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>stop</CODE
-+></DT
-+><DD
-+><P
-+>Abort packet injection.
-+  </P
-+></DD
-+></DL
-+></DIV
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="PG3.WARNING"
-+></A
-+><H2
-+>WARNING</H2
-+><P
-+>When output device is set to some random device different
-+of hardware Ethernet device, <B
-+CLASS="COMMAND"
-+>pg3</B
-+> will crash kernel.</P
-+><P
-+>Do not use it on VLAN, ethertap, VTUN and other devices,
-+which emulate Ethernet not being real Ethernet in fact.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN1232"
-+></A
-+><H2
-+>AUTHOR</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>pg3</B
-+> was written by <A
-+HREF="mailto:robert.olsson@its.uu.se"
-+TARGET="_top"
-+>Robert Olsson &lt;robert.olsson@its.uu.se&gt;</A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN1237"
-+></A
-+><H2
-+>SECURITY</H2
-+><P
-+>This can be used only by superuser.</P
-+><P
-+>This tool creates floods of packets which is unlikely to be handled
-+even by high-end machines. For example, it saturates gigabit link with
-+60 byte packets when used with Intel's e1000. In face of such stream
-+switches, routers and end hosts may deadlock, crash, explode.
-+Use only in test lab environment.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN1241"
-+></A
-+><H2
-+>AVAILABILITY</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>pg3</B
-+> is part of <TT
-+CLASS="FILENAME"
-+>iputils</TT
-+> package
-+and the latest versions are  available in source form at
-+<A
-+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
-+TARGET="_top"
-+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="NAVFOOTER"
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"><TABLE
-+SUMMARY="Footer navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+><A
-+HREF="r1022.html"
-+ACCESSKEY="P"
-+>Prev</A
-+></TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+><A
-+HREF="index.html"
-+ACCESSKEY="H"
-+>Home</A
-+></TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+>&nbsp;</TD
-+></TR
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+>rdisc</TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+>&nbsp;</TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+>&nbsp;</TD
-+></TR
-+></TABLE
-+></DIV
-+></BODY
-+></HTML
-+>
-\ No newline at end of file
-diff -Naur iputils-s20100418.orig/doc/r3.html iputils-s20100418/doc/r3.html
---- iputils-s20100418.orig/doc/r3.html	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/r3.html	2010-08-04 22:00:32.373575999 -0400
-@@ -0,0 +1,1494 @@
-+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-+<HTML
-+><HEAD
-+><TITLE
-+>ping</TITLE
-+><META
-+NAME="GENERATOR"
-+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-+REL="HOME"
-+TITLE="System Manager's Manual: iputils"
-+HREF="index.html"><LINK
-+REL="PREVIOUS"
-+TITLE="System Manager's Manual: iputils"
-+HREF="index.html"><LINK
-+REL="NEXT"
-+TITLE="arping"
-+HREF="r437.html"></HEAD
-+><BODY
-+CLASS="REFENTRY"
-+BGCOLOR="#FFFFFF"
-+TEXT="#000000"
-+LINK="#0000FF"
-+VLINK="#840084"
-+ALINK="#0000FF"
-+><DIV
-+CLASS="NAVHEADER"
-+><TABLE
-+SUMMARY="Header navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TH
-+COLSPAN="3"
-+ALIGN="center"
-+>System Manager's Manual: iputils</TH
-+></TR
-+><TR
-+><TD
-+WIDTH="10%"
-+ALIGN="left"
-+VALIGN="bottom"
-+><A
-+HREF="index.html"
-+ACCESSKEY="P"
-+>Prev</A
-+></TD
-+><TD
-+WIDTH="80%"
-+ALIGN="center"
-+VALIGN="bottom"
-+></TD
-+><TD
-+WIDTH="10%"
-+ALIGN="right"
-+VALIGN="bottom"
-+><A
-+HREF="r437.html"
-+ACCESSKEY="N"
-+>Next</A
-+></TD
-+></TR
-+></TABLE
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"></DIV
-+><H1
-+><A
-+NAME="PING"
-+></A
-+>ping</H1
-+><DIV
-+CLASS="REFNAMEDIV"
-+><A
-+NAME="AEN8"
-+></A
-+><H2
-+>Name</H2
-+>ping, ping6&nbsp;--&nbsp;send ICMP ECHO_REQUEST to network hosts</DIV
-+><DIV
-+CLASS="REFSYNOPSISDIV"
-+><A
-+NAME="AEN11"
-+></A
-+><H2
-+>Synopsis</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>ping</B
-+>  [<CODE
-+CLASS="OPTION"
-+>-LRUbdfnqrvVaAB</CODE
-+>] [-c <TT
-+CLASS="REPLACEABLE"
-+><I
-+>count</I
-+></TT
-+>] [-m <TT
-+CLASS="REPLACEABLE"
-+><I
-+>mark</I
-+></TT
-+>] [-i <TT
-+CLASS="REPLACEABLE"
-+><I
-+>interval</I
-+></TT
-+>] [-l <TT
-+CLASS="REPLACEABLE"
-+><I
-+>preload</I
-+></TT
-+>] [-p <TT
-+CLASS="REPLACEABLE"
-+><I
-+>pattern</I
-+></TT
-+>] [-s <TT
-+CLASS="REPLACEABLE"
-+><I
-+>packetsize</I
-+></TT
-+>] [-t <TT
-+CLASS="REPLACEABLE"
-+><I
-+>ttl</I
-+></TT
-+>] [-w <TT
-+CLASS="REPLACEABLE"
-+><I
-+>deadline</I
-+></TT
-+>] [-F <TT
-+CLASS="REPLACEABLE"
-+><I
-+>flowlabel</I
-+></TT
-+>] [-I <TT
-+CLASS="REPLACEABLE"
-+><I
-+>interface</I
-+></TT
-+>] [-M <TT
-+CLASS="REPLACEABLE"
-+><I
-+>hint</I
-+></TT
-+>] [-N <TT
-+CLASS="REPLACEABLE"
-+><I
-+>nioption</I
-+></TT
-+>] [-Q <TT
-+CLASS="REPLACEABLE"
-+><I
-+>tos</I
-+></TT
-+>] [-S <TT
-+CLASS="REPLACEABLE"
-+><I
-+>sndbuf</I
-+></TT
-+>] [-T <TT
-+CLASS="REPLACEABLE"
-+><I
-+>timestamp option</I
-+></TT
-+>] [-W <TT
-+CLASS="REPLACEABLE"
-+><I
-+>timeout</I
-+></TT
-+>] [<TT
-+CLASS="REPLACEABLE"
-+><I
-+>hop</I
-+></TT
-+>...] {<TT
-+CLASS="REPLACEABLE"
-+><I
-+>destination</I
-+></TT
-+>}</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN52"
-+></A
-+><H2
-+>DESCRIPTION</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>ping</B
-+> uses the ICMP protocol's mandatory ECHO_REQUEST
-+datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway.
-+ECHO_REQUEST datagrams (``pings'') have an IP and ICMP
-+header, followed by a <CODE
-+CLASS="STRUCTNAME"
-+>struct timeval</CODE
-+> and then an arbitrary
-+number of ``pad'' bytes used to fill out the packet.</P
-+><P
-+><B
-+CLASS="COMMAND"
-+>ping6</B
-+> can also send Node Information Queries (RFC4620).</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN59"
-+></A
-+><H2
-+>OPTIONS</H2
-+><P
-+></P
-+><DIV
-+CLASS="VARIABLELIST"
-+><DL
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-a</CODE
-+></DT
-+><DD
-+><P
-+>Audible ping.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-A</CODE
-+></DT
-+><DD
-+><P
-+>Adaptive ping. Interpacket interval adapts to round-trip time, so that
-+effectively not more than one (or more, if preload is set) unanswered probes
-+present in the network. Minimal interval is 200msec for not super-user.
-+On networks with low rtt this mode is essentially equivalent to flood mode.  
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-b</CODE
-+></DT
-+><DD
-+><P
-+>Allow pinging a broadcast address.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-B</CODE
-+></DT
-+><DD
-+><P
-+>Do not allow <B
-+CLASS="COMMAND"
-+>ping</B
-+> to change source address of probes.
-+The address is bound to one selected when <B
-+CLASS="COMMAND"
-+>ping</B
-+> starts.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-m <TT
-+CLASS="REPLACEABLE"
-+><I
-+>mark</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>use <TT
-+CLASS="REPLACEABLE"
-+><I
-+>mark</I
-+></TT
-+> to tag the packets going out. This is useful
-+for variety of reasons within the kernel such as using policy
-+routing to select specific outbound processing.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+><A
-+NAME="PING.COUNT"
-+></A
-+>-c <TT
-+CLASS="REPLACEABLE"
-+><I
-+>count</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Stop after sending <TT
-+CLASS="REPLACEABLE"
-+><I
-+>count</I
-+></TT
-+> ECHO_REQUEST
-+packets. With 
-+<A
-+HREF="r3.html#PING.DEADLINE"
-+><TT
-+CLASS="REPLACEABLE"
-+><I
-+>deadline</I
-+></TT
-+></A
-+>
-+option, <B
-+CLASS="COMMAND"
-+>ping</B
-+> waits for
-+<TT
-+CLASS="REPLACEABLE"
-+><I
-+>count</I
-+></TT
-+> ECHO_REPLY packets, until the timeout expires.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-d</CODE
-+></DT
-+><DD
-+><P
-+>Set the <CODE
-+CLASS="CONSTANT"
-+>SO_DEBUG</CODE
-+> option on the socket being used.
-+Essentially, this socket option is not used by Linux kernel. 
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-F <TT
-+CLASS="REPLACEABLE"
-+><I
-+>flow label</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Allocate and set 20 bit flow label on echo request packets.
-+(Only <B
-+CLASS="COMMAND"
-+>ping6</B
-+>). If value is zero, kernel allocates random flow label.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-f</CODE
-+></DT
-+><DD
-+><P
-+>Flood ping. For every ECHO_REQUEST sent a period ``.'' is printed,
-+while for ever ECHO_REPLY received a backspace is printed.
-+This provides a rapid display of how many packets are being dropped.
-+If interval is not given, it sets interval to zero and
-+outputs packets as fast as they come back or one hundred times per second,
-+whichever is more.
-+Only the super-user may use this option with zero interval.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-i <TT
-+CLASS="REPLACEABLE"
-+><I
-+>interval</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Wait <TT
-+CLASS="REPLACEABLE"
-+><I
-+>interval</I
-+></TT
-+> seconds between sending each packet.
-+The default is to wait for one second between each packet normally,
-+or not to wait in flood mode. Only super-user may set interval
-+to values less 0.2 seconds.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-I <TT
-+CLASS="REPLACEABLE"
-+><I
-+>interface address</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Set source address to specified interface address. Argument
-+may be numeric IP address or name of device. When pinging IPv6
-+link-local address this option is required.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-l <TT
-+CLASS="REPLACEABLE"
-+><I
-+>preload</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>If <TT
-+CLASS="REPLACEABLE"
-+><I
-+>preload</I
-+></TT
-+> is specified,
-+<B
-+CLASS="COMMAND"
-+>ping</B
-+> sends that many packets not waiting for reply.
-+Only the super-user may select preload more than 3.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-L</CODE
-+></DT
-+><DD
-+><P
-+>Suppress loopback of multicast packets.  This flag only applies if the ping
-+destination is a multicast address.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-N <TT
-+CLASS="REPLACEABLE"
-+><I
-+>nioption</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Send ICMPv6 Node Information Queries (RFC4620), instead of Echo Request.
-+   <P
-+></P
-+><DIV
-+CLASS="VARIABLELIST"
-+><DL
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>name</CODE
-+></DT
-+><DD
-+><P
-+>Queries for Node Names.</P
-+></DD
-+></DL
-+></DIV
-+>
-+   <P
-+></P
-+><DIV
-+CLASS="VARIABLELIST"
-+><DL
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>ipv6</CODE
-+></DT
-+><DD
-+><P
-+>Queries for IPv6 Addresses. There are several IPv6 specific flags.
-+      <P
-+></P
-+><DIV
-+CLASS="VARIABLELIST"
-+><DL
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>ipv6-global</CODE
-+></DT
-+><DD
-+><P
-+>Request IPv6 global-scope addresses.</P
-+></DD
-+></DL
-+></DIV
-+>
-+      <P
-+></P
-+><DIV
-+CLASS="VARIABLELIST"
-+><DL
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>ipv6-sitelocal</CODE
-+></DT
-+><DD
-+><P
-+>Request IPv6 site-local addresses.</P
-+></DD
-+></DL
-+></DIV
-+>
-+      <P
-+></P
-+><DIV
-+CLASS="VARIABLELIST"
-+><DL
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>ipv6-linklocal</CODE
-+></DT
-+><DD
-+><P
-+>Request IPv6 link-local addresses.</P
-+></DD
-+></DL
-+></DIV
-+>
-+      <P
-+></P
-+><DIV
-+CLASS="VARIABLELIST"
-+><DL
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>ipv6-all</CODE
-+></DT
-+><DD
-+><P
-+>Request IPv6 addresses on other interfaces.</P
-+></DD
-+></DL
-+></DIV
-+>
-+     </P
-+></DD
-+></DL
-+></DIV
-+>
-+   <P
-+></P
-+><DIV
-+CLASS="VARIABLELIST"
-+><DL
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>ipv4</CODE
-+></DT
-+><DD
-+><P
-+>Queries for IPv4 Addresses.  There is one IPv4 specific flag.
-+      <P
-+></P
-+><DIV
-+CLASS="VARIABLELIST"
-+><DL
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>ipv4-all</CODE
-+></DT
-+><DD
-+><P
-+>Request IPv4 addresses on other interfaces.</P
-+></DD
-+></DL
-+></DIV
-+>
-+     </P
-+></DD
-+></DL
-+></DIV
-+>
-+   <P
-+></P
-+><DIV
-+CLASS="VARIABLELIST"
-+><DL
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>subject-ipv6=<TT
-+CLASS="REPLACEABLE"
-+><I
-+>ipv6addr</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>IPv6 subject address.</P
-+></DD
-+></DL
-+></DIV
-+>
-+   <P
-+></P
-+><DIV
-+CLASS="VARIABLELIST"
-+><DL
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>subject-ipv4=<TT
-+CLASS="REPLACEABLE"
-+><I
-+>ipv4addr</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>IPv4 subject address.</P
-+></DD
-+></DL
-+></DIV
-+>
-+   <P
-+></P
-+><DIV
-+CLASS="VARIABLELIST"
-+><DL
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>subject-name=<TT
-+CLASS="REPLACEABLE"
-+><I
-+>nodename</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Subject name.  If it contains more than one dot,
-+	fully-qualified domain name is assumed.</P
-+></DD
-+></DL
-+></DIV
-+>
-+   <P
-+></P
-+><DIV
-+CLASS="VARIABLELIST"
-+><DL
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>subject-fqdn=<TT
-+CLASS="REPLACEABLE"
-+><I
-+>nodename</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Subject name.  Fully-qualified domain name is
-+	always assumed.</P
-+></DD
-+></DL
-+></DIV
-+>
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-n</CODE
-+></DT
-+><DD
-+><P
-+>Numeric output only.
-+No attempt will be made to lookup symbolic names for host addresses.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-p <TT
-+CLASS="REPLACEABLE"
-+><I
-+>pattern</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>You may specify up to 16 ``pad'' bytes to fill out the packet you send.
-+This is useful for diagnosing data-dependent problems in a network.
-+For example, <CODE
-+CLASS="OPTION"
-+>-p ff</CODE
-+> will cause the sent packet
-+to be filled with all ones.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-D</CODE
-+></DT
-+><DD
-+><P
-+>Print timestamp (unix time + microseconds as in gettimeofday) before
-+each line.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-Q <TT
-+CLASS="REPLACEABLE"
-+><I
-+>tos</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Set Quality of Service -related bits in ICMP datagrams.  
-+<TT
-+CLASS="REPLACEABLE"
-+><I
-+>tos</I
-+></TT
-+> can be either decimal or hex number.
-+Traditionally (RFC1349), these have been interpreted as: 0 for reserved
-+(currently being redefined as congestion control), 1-4 for Type of Service
-+and 5-7 for Precedence.
-+Possible settings for Type of Service are: minimal cost: 0x02, 
-+reliability: 0x04, throughput: 0x08, low delay: 0x10.  Multiple TOS bits
-+should not be set simultaneously.  Possible settings for
-+special Precedence range from priority (0x20) to net control (0xe0).  You
-+must be root (<CODE
-+CLASS="CONSTANT"
-+>CAP_NET_ADMIN</CODE
-+> capability) to use Critical or
-+higher precedence value.  You cannot set
-+bit 0x01 (reserved) unless ECN has been enabled in the kernel.
-+In RFC2474, these fields has been redefined as 8-bit Differentiated
-+Services (DS), consisting of: bits 0-1 of separate data (ECN will be used,
-+here), and bits 2-7 of Differentiated Services Codepoint (DSCP).
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-q</CODE
-+></DT
-+><DD
-+><P
-+>Quiet output.
-+Nothing is displayed except the summary lines at startup time and
-+when finished.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-R</CODE
-+></DT
-+><DD
-+><P
-+>Record route.
-+Includes the RECORD_ROUTE option in the ECHO_REQUEST
-+packet and displays the route buffer on returned packets.
-+Note that the IP header is only large enough for nine such routes.
-+Many hosts ignore or discard this option.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-r</CODE
-+></DT
-+><DD
-+><P
-+>Bypass the normal routing tables and send directly to a host on an attached
-+interface.
-+If the host is not on a directly-attached network, an error is returned.
-+This option can be used to ping a local host through an interface
-+that has no route through it provided the option <CODE
-+CLASS="OPTION"
-+>-I</CODE
-+> is also
-+used.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-s <TT
-+CLASS="REPLACEABLE"
-+><I
-+>packetsize</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Specifies the number of data bytes to be sent.  
-+The default is 56, which translates into 64 ICMP
-+data bytes when combined with the 8 bytes of ICMP header data.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-S <TT
-+CLASS="REPLACEABLE"
-+><I
-+>sndbuf</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Set socket sndbuf. If not specified, it is selected to buffer
-+not more than one packet.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-t <TT
-+CLASS="REPLACEABLE"
-+><I
-+>ttl</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Set the IP Time to Live.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-T <TT
-+CLASS="REPLACEABLE"
-+><I
-+>timestamp option</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Set special IP timestamp options.
-+<TT
-+CLASS="REPLACEABLE"
-+><I
-+>timestamp option</I
-+></TT
-+> may be either 
-+<TT
-+CLASS="REPLACEABLE"
-+><I
-+>tsonly</I
-+></TT
-+> (only timestamps), 
-+<TT
-+CLASS="REPLACEABLE"
-+><I
-+>tsandaddr</I
-+></TT
-+> (timestamps and addresses) or 
-+<TT
-+CLASS="REPLACEABLE"
-+><I
-+>tsprespec host1 [host2 [host3 [host4]]]</I
-+></TT
-+>
-+(timestamp prespecified hops).
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-M <TT
-+CLASS="REPLACEABLE"
-+><I
-+>hint</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Select Path MTU Discovery strategy.
-+<TT
-+CLASS="REPLACEABLE"
-+><I
-+>hint</I
-+></TT
-+> may be either <TT
-+CLASS="REPLACEABLE"
-+><I
-+>do</I
-+></TT
-+>
-+(prohibit fragmentation, even local one), 
-+<TT
-+CLASS="REPLACEABLE"
-+><I
-+>want</I
-+></TT
-+> (do PMTU discovery, fragment locally when packet size
-+is large), or <TT
-+CLASS="REPLACEABLE"
-+><I
-+>dont</I
-+></TT
-+> (do not set DF flag).
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-U</CODE
-+></DT
-+><DD
-+><P
-+>Print full user-to-user latency (the old behaviour). Normally
-+<B
-+CLASS="COMMAND"
-+>ping</B
-+>
-+prints network round trip time, which can be different
-+f.e. due to DNS failures. 
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-v</CODE
-+></DT
-+><DD
-+><P
-+>Verbose output.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-V</CODE
-+></DT
-+><DD
-+><P
-+>Show version and exit.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+><A
-+NAME="PING.DEADLINE"
-+></A
-+>-w <TT
-+CLASS="REPLACEABLE"
-+><I
-+>deadline</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Specify a timeout, in seconds, before
-+<B
-+CLASS="COMMAND"
-+>ping</B
-+>
-+exits regardless of how many
-+packets have been sent or received. In this case
-+<B
-+CLASS="COMMAND"
-+>ping</B
-+>
-+does not stop after
-+<A
-+HREF="r3.html#PING.COUNT"
-+><TT
-+CLASS="REPLACEABLE"
-+><I
-+>count</I
-+></TT
-+></A
-+>
-+packet are sent, it waits either for
-+<A
-+HREF="r3.html#PING.DEADLINE"
-+><TT
-+CLASS="REPLACEABLE"
-+><I
-+>deadline</I
-+></TT
-+></A
-+>
-+expire or until
-+<A
-+HREF="r3.html#PING.COUNT"
-+><TT
-+CLASS="REPLACEABLE"
-+><I
-+>count</I
-+></TT
-+></A
-+>
-+probes are answered or for some error notification from network.   
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-W <TT
-+CLASS="REPLACEABLE"
-+><I
-+>timeout</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Time to wait for a response, in seconds. The option affects only timeout
-+in absense of any responses, otherwise <B
-+CLASS="COMMAND"
-+>ping</B
-+> waits for two RTTs.
-+  </P
-+></DD
-+></DL
-+></DIV
-+><P
-+>When using <B
-+CLASS="COMMAND"
-+>ping</B
-+> for fault isolation, it should first be run
-+on the local host, to verify that the local network interface is up
-+and running. Then, hosts and gateways further and further away should be
-+``pinged''. Round-trip times and packet loss statistics are computed.
-+If duplicate packets are received, they are not included in the packet
-+loss calculation, although the round trip time of these packets is used
-+in calculating the minimum/average/maximum round-trip time numbers.
-+When the specified number of packets have been sent (and received) or
-+if the program is terminated with a
-+<CODE
-+CLASS="CONSTANT"
-+>SIGINT</CODE
-+>, a brief summary is displayed. Shorter current statistics
-+can be obtained without termination of process with signal
-+<CODE
-+CLASS="CONSTANT"
-+>SIGQUIT</CODE
-+>.</P
-+><P
-+>If <B
-+CLASS="COMMAND"
-+>ping</B
-+> does not receive any reply packets at all it will
-+exit with code 1. If a packet 
-+<A
-+HREF="r3.html#PING.COUNT"
-+><TT
-+CLASS="REPLACEABLE"
-+><I
-+>count</I
-+></TT
-+></A
-+>
-+and
-+<A
-+HREF="r3.html#PING.DEADLINE"
-+><TT
-+CLASS="REPLACEABLE"
-+><I
-+>deadline</I
-+></TT
-+></A
-+>
-+are both specified, and fewer than
-+<A
-+HREF="r3.html#PING.COUNT"
-+><TT
-+CLASS="REPLACEABLE"
-+><I
-+>count</I
-+></TT
-+></A
-+>
-+packets are received by the time the
-+<A
-+HREF="r3.html#PING.DEADLINE"
-+><TT
-+CLASS="REPLACEABLE"
-+><I
-+>deadline</I
-+></TT
-+></A
-+>
-+has arrived, it will also exit with code 1. 
-+On other error it exits with code 2. Otherwise it exits with code 0. This
-+makes it possible to use the exit code to see if a host is alive or
-+not.</P
-+><P
-+>This program is intended for use in network testing, measurement and
-+management.
-+Because of the load it can impose on the network, it is unwise to use
-+<B
-+CLASS="COMMAND"
-+>ping</B
-+> during normal operations or from automated scripts.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN362"
-+></A
-+><H2
-+>ICMP PACKET DETAILS</H2
-+><P
-+>An IP header without options is 20 bytes.
-+An ICMP ECHO_REQUEST packet contains an additional 8 bytes worth
-+of ICMP header followed by an arbitrary amount of data.
-+When a <TT
-+CLASS="REPLACEABLE"
-+><I
-+>packetsize</I
-+></TT
-+> is given, this indicated the size of this
-+extra piece of data (the default is 56). Thus the amount of data received
-+inside of an IP packet of type ICMP ECHO_REPLY will always be 8 bytes
-+more than the requested data space (the ICMP header).</P
-+><P
-+>If the data space is at least of size of <CODE
-+CLASS="STRUCTNAME"
-+>struct timeval</CODE
-+>
-+<B
-+CLASS="COMMAND"
-+>ping</B
-+> uses the beginning bytes of this space to include
-+a timestamp which it uses in the computation of round trip times.
-+If the data space is shorter, no round trip times are given.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN369"
-+></A
-+><H2
-+>DUPLICATE AND DAMAGED PACKETS</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>ping</B
-+> will report duplicate and damaged packets.
-+Duplicate packets should never occur, and seem to be caused by
-+inappropriate link-level retransmissions.
-+Duplicates may occur in many situations and are rarely (if ever) a
-+good sign, although the presence of low levels of duplicates may not
-+always be cause for alarm.</P
-+><P
-+>Damaged packets are obviously serious cause for alarm and often
-+indicate broken hardware somewhere in the
-+<B
-+CLASS="COMMAND"
-+>ping</B
-+> packet's path (in the network or in the hosts).</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN375"
-+></A
-+><H2
-+>TRYING DIFFERENT DATA PATTERNS</H2
-+><P
-+>The (inter)network layer should never treat packets differently depending
-+on the data contained in the data portion.
-+Unfortunately, data-dependent problems have been known to sneak into
-+networks and remain undetected for long periods of time.
-+In many cases the particular pattern that will have problems is something
-+that doesn't have sufficient ``transitions'', such as all ones or all
-+zeros, or a pattern right at the edge, such as almost all zeros.
-+It isn't necessarily enough to specify a data pattern of all zeros (for
-+example) on the command line because the pattern that is of interest is
-+at the data link level, and the relationship between what you type and
-+what the controllers transmit can be complicated.</P
-+><P
-+>This means that if you have a data-dependent problem you will probably
-+have to do a lot of testing to find it.
-+If you are lucky, you may manage to find a file that either can't be sent
-+across your network or that takes much longer to transfer than other
-+similar length files.
-+You can then examine this file for repeated patterns that you can test
-+using the <CODE
-+CLASS="OPTION"
-+>-p</CODE
-+> option of <B
-+CLASS="COMMAND"
-+>ping</B
-+>.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN381"
-+></A
-+><H2
-+>TTL DETAILS</H2
-+><P
-+>The TTL value of an IP packet represents the maximum number of IP routers
-+that the packet can go through before being thrown away.
-+In current practice you can expect each router in the Internet to decrement
-+the TTL field by exactly one.</P
-+><P
-+>The TCP/IP specification states that the TTL field for TCP
-+packets should be set to 60, but many systems use smaller values
-+(4.3 BSD uses 30, 4.2 used 15).</P
-+><P
-+>The maximum possible value of this field is 255, and most Unix systems set
-+the TTL field of ICMP ECHO_REQUEST packets to 255.
-+This is why you will find you can ``ping'' some hosts, but not reach them
-+with
-+<SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>telnet</SPAN
-+>(1)</SPAN
-+>
-+or
-+<SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>ftp</SPAN
-+>(1)</SPAN
-+>.</P
-+><P
-+>In normal operation ping prints the ttl value from the packet it receives.
-+When a remote system receives a ping packet, it can do one of three things
-+with the TTL field in its response:</P
-+><P
-+></P
-+><UL
-+><LI
-+><P
-+>Not change it; this is what Berkeley Unix systems did before the
-+4.3BSD Tahoe release. In this case the TTL value in the received packet
-+will be 255 minus the number of routers in the round-trip path.
-+ </P
-+></LI
-+><LI
-+><P
-+>Set it to 255; this is what current Berkeley Unix systems do.
-+In this case the TTL value in the received packet will be 255 minus the
-+number of routers in the path <SPAN
-+CLASS="emphasis"
-+><I
-+CLASS="EMPHASIS"
-+>from</I
-+></SPAN
-+>
-+the remote system <SPAN
-+CLASS="emphasis"
-+><I
-+CLASS="EMPHASIS"
-+>to</I
-+></SPAN
-+> the <B
-+CLASS="COMMAND"
-+>ping</B
-+>ing host.
-+ </P
-+></LI
-+><LI
-+><P
-+>Set it to some other value. Some machines use the same value for
-+ICMP packets that they use for TCP packets, for example either 30 or 60.
-+Others may use completely wild values.
-+ </P
-+></LI
-+></UL
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN403"
-+></A
-+><H2
-+>BUGS</H2
-+><P
-+></P
-+><UL
-+><LI
-+><P
-+>Many Hosts and Gateways ignore the RECORD_ROUTE option.
-+ </P
-+></LI
-+><LI
-+><P
-+>The maximum IP header length is too small for options like
-+RECORD_ROUTE to be completely useful.
-+There's not much that that can be done about this, however.
-+ </P
-+></LI
-+><LI
-+><P
-+>Flood pinging is not recommended in general, and flood pinging the
-+broadcast address should only be done under very controlled conditions.
-+ </P
-+></LI
-+></UL
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN412"
-+></A
-+><H2
-+>SEE ALSO</H2
-+><P
-+><SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>netstat</SPAN
-+>(1)</SPAN
-+>,
-+<SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>ifconfig</SPAN
-+>(8)</SPAN
-+>.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN421"
-+></A
-+><H2
-+>HISTORY</H2
-+><P
-+>The <B
-+CLASS="COMMAND"
-+>ping</B
-+> command appeared in 4.3BSD.</P
-+><P
-+>The version described here is its descendant specific to Linux.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN426"
-+></A
-+><H2
-+>SECURITY</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>ping</B
-+> requires <CODE
-+CLASS="CONSTANT"
-+>CAP_NET_RAWIO</CODE
-+> capability
-+to be executed. It may be used as set-uid root.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN431"
-+></A
-+><H2
-+>AVAILABILITY</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>ping</B
-+> is part of <TT
-+CLASS="FILENAME"
-+>iputils</TT
-+> package
-+and the latest versions are  available in source form at
-+<A
-+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
-+TARGET="_top"
-+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="NAVFOOTER"
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"><TABLE
-+SUMMARY="Footer navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+><A
-+HREF="index.html"
-+ACCESSKEY="P"
-+>Prev</A
-+></TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+><A
-+HREF="index.html"
-+ACCESSKEY="H"
-+>Home</A
-+></TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+><A
-+HREF="r437.html"
-+ACCESSKEY="N"
-+>Next</A
-+></TD
-+></TR
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+>System Manager's Manual: iputils</TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+>&nbsp;</TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+>arping</TD
-+></TR
-+></TABLE
-+></DIV
-+></BODY
-+></HTML
-+>
-\ No newline at end of file
-diff -Naur iputils-s20100418.orig/doc/r437.html iputils-s20100418/doc/r437.html
---- iputils-s20100418.orig/doc/r437.html	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/r437.html	2010-08-04 22:00:32.385590132 -0400
-@@ -0,0 +1,598 @@
-+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-+<HTML
-+><HEAD
-+><TITLE
-+>arping</TITLE
-+><META
-+NAME="GENERATOR"
-+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-+REL="HOME"
-+TITLE="System Manager's Manual: iputils"
-+HREF="index.html"><LINK
-+REL="PREVIOUS"
-+TITLE="ping"
-+HREF="r3.html"><LINK
-+REL="NEXT"
-+TITLE="clockdiff"
-+HREF="r596.html"></HEAD
-+><BODY
-+CLASS="REFENTRY"
-+BGCOLOR="#FFFFFF"
-+TEXT="#000000"
-+LINK="#0000FF"
-+VLINK="#840084"
-+ALINK="#0000FF"
-+><DIV
-+CLASS="NAVHEADER"
-+><TABLE
-+SUMMARY="Header navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TH
-+COLSPAN="3"
-+ALIGN="center"
-+>System Manager's Manual: iputils</TH
-+></TR
-+><TR
-+><TD
-+WIDTH="10%"
-+ALIGN="left"
-+VALIGN="bottom"
-+><A
-+HREF="r3.html"
-+ACCESSKEY="P"
-+>Prev</A
-+></TD
-+><TD
-+WIDTH="80%"
-+ALIGN="center"
-+VALIGN="bottom"
-+></TD
-+><TD
-+WIDTH="10%"
-+ALIGN="right"
-+VALIGN="bottom"
-+><A
-+HREF="r596.html"
-+ACCESSKEY="N"
-+>Next</A
-+></TD
-+></TR
-+></TABLE
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"></DIV
-+><H1
-+><A
-+NAME="ARPING"
-+></A
-+>arping</H1
-+><DIV
-+CLASS="REFNAMEDIV"
-+><A
-+NAME="AEN442"
-+></A
-+><H2
-+>Name</H2
-+>arping&nbsp;--&nbsp;send ARP REQUEST to a neighbour host</DIV
-+><DIV
-+CLASS="REFSYNOPSISDIV"
-+><A
-+NAME="AEN445"
-+></A
-+><H2
-+>Synopsis</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>arping</B
-+>  [<CODE
-+CLASS="OPTION"
-+>-AbDfhqUV</CODE
-+>] [-c <TT
-+CLASS="REPLACEABLE"
-+><I
-+>count</I
-+></TT
-+>] [-w <TT
-+CLASS="REPLACEABLE"
-+><I
-+>deadline</I
-+></TT
-+>] [-s <TT
-+CLASS="REPLACEABLE"
-+><I
-+>source</I
-+></TT
-+>] {-I <TT
-+CLASS="REPLACEABLE"
-+><I
-+>interface</I
-+></TT
-+>} {<TT
-+CLASS="REPLACEABLE"
-+><I
-+>destination</I
-+></TT
-+>}</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN460"
-+></A
-+><H2
-+>DESCRIPTION</H2
-+><P
-+>Ping <TT
-+CLASS="REPLACEABLE"
-+><I
-+>destination</I
-+></TT
-+> on device <TT
-+CLASS="REPLACEABLE"
-+><I
-+>interface</I
-+></TT
-+> by ARP packets,
-+using source address <TT
-+CLASS="REPLACEABLE"
-+><I
-+>source</I
-+></TT
-+>.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN466"
-+></A
-+><H2
-+>OPTIONS</H2
-+><P
-+></P
-+><DIV
-+CLASS="VARIABLELIST"
-+><DL
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-A</CODE
-+></DT
-+><DD
-+><P
-+>The same as <CODE
-+CLASS="OPTION"
-+>-U</CODE
-+>, but ARP REPLY packets used instead
-+of ARP REQUEST.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-b</CODE
-+></DT
-+><DD
-+><P
-+>Send only MAC level broadcasts. Normally <B
-+CLASS="COMMAND"
-+>arping</B
-+> starts
-+from sending broadcast, and switch to unicast after reply received.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+><A
-+NAME="ARPING.COUNT"
-+></A
-+>-c <TT
-+CLASS="REPLACEABLE"
-+><I
-+>count</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Stop after sending <TT
-+CLASS="REPLACEABLE"
-+><I
-+>count</I
-+></TT
-+> ARP REQUEST
-+packets. With 
-+<A
-+HREF="r437.html#ARPING.DEADLINE"
-+><TT
-+CLASS="REPLACEABLE"
-+><I
-+>deadline</I
-+></TT
-+></A
-+>
-+option, <B
-+CLASS="COMMAND"
-+>arping</B
-+> waits for
-+<TT
-+CLASS="REPLACEABLE"
-+><I
-+>count</I
-+></TT
-+> ARP REPLY packets, until the timeout expires.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-D</CODE
-+></DT
-+><DD
-+><P
-+>Duplicate address detection mode (DAD). See 
-+<A
-+HREF="ftp://ftp.isi.edu/in-notes/rfc2131.txt"
-+TARGET="_top"
-+>RFC2131, 4.4.1</A
-+>.
-+Returns 0, if DAD succeeded i.e. no replies are received
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-f</CODE
-+></DT
-+><DD
-+><P
-+>Finish after the first reply confirming that target is alive.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+><A
-+NAME="OPT.INTERFACE"
-+></A
-+>-I <TT
-+CLASS="REPLACEABLE"
-+><I
-+>interface</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Name of network device where to send ARP REQUEST packets. This option
-+is required.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-h</CODE
-+></DT
-+><DD
-+><P
-+>Print help page and exit.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-q</CODE
-+></DT
-+><DD
-+><P
-+>Quiet output. Nothing is displayed.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+><A
-+NAME="OPT.SOURCE"
-+></A
-+>-s <TT
-+CLASS="REPLACEABLE"
-+><I
-+>source</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>IP source address to use in ARP packets.
-+If this option is absent, source address is:
-+   <P
-+></P
-+><UL
-+><LI
-+><P
-+>In DAD mode (with option <CODE
-+CLASS="OPTION"
-+>-D</CODE
-+>) set to 0.0.0.0.
-+    </P
-+></LI
-+><LI
-+><P
-+>In Unsolicited ARP mode (with options <CODE
-+CLASS="OPTION"
-+>-U</CODE
-+> or <CODE
-+CLASS="OPTION"
-+>-A</CODE
-+>)
-+set to <TT
-+CLASS="REPLACEABLE"
-+><I
-+>destination</I
-+></TT
-+>.
-+    </P
-+></LI
-+><LI
-+><P
-+>Otherwise, it is calculated from routing tables.
-+    </P
-+></LI
-+></UL
-+>
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-U</CODE
-+></DT
-+><DD
-+><P
-+>Unsolicited ARP mode to update neighbours' ARP caches.
-+No replies are expected.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-V</CODE
-+></DT
-+><DD
-+><P
-+>Print version of the program and exit.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+><A
-+NAME="ARPING.DEADLINE"
-+></A
-+>-w <TT
-+CLASS="REPLACEABLE"
-+><I
-+>deadline</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>Specify a timeout, in seconds, before
-+<B
-+CLASS="COMMAND"
-+>arping</B
-+>
-+exits regardless of how many
-+packets have been sent or received. In this case
-+<B
-+CLASS="COMMAND"
-+>arping</B
-+>
-+does not stop after
-+<A
-+HREF="r437.html#ARPING.COUNT"
-+><TT
-+CLASS="REPLACEABLE"
-+><I
-+>count</I
-+></TT
-+></A
-+>
-+packet are sent, it waits either for
-+<A
-+HREF="r437.html#ARPING.DEADLINE"
-+><TT
-+CLASS="REPLACEABLE"
-+><I
-+>deadline</I
-+></TT
-+></A
-+>
-+expire or until
-+<A
-+HREF="r437.html#ARPING.COUNT"
-+><TT
-+CLASS="REPLACEABLE"
-+><I
-+>count</I
-+></TT
-+></A
-+>
-+probes are answered.
-+  </P
-+></DD
-+></DL
-+></DIV
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN564"
-+></A
-+><H2
-+>SEE ALSO</H2
-+><P
-+><A
-+HREF="r3.html"
-+><SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>ping</SPAN
-+>(8)</SPAN
-+></A
-+>,
-+<A
-+HREF="r596.html"
-+><SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>clockdiff</SPAN
-+>(8)</SPAN
-+></A
-+>,
-+<A
-+HREF="r790.html"
-+><SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>tracepath</SPAN
-+>(8)</SPAN
-+></A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN579"
-+></A
-+><H2
-+>AUTHOR</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>arping</B
-+> was written by
-+<A
-+HREF="mailto:kuznet@ms2.inr.ac.ru"
-+TARGET="_top"
-+>Alexey Kuznetsov
-+&lt;kuznet@ms2.inr.ac.ru&gt;</A
-+>.
-+It is now maintained by
-+<A
-+HREF="mailto:yoshfuji@skbuff.net"
-+TARGET="_top"
-+>YOSHIFUJI Hideaki
-+&lt;yoshfuji@skbuff.net&gt;</A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN585"
-+></A
-+><H2
-+>SECURITY</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>arping</B
-+> requires <CODE
-+CLASS="CONSTANT"
-+>CAP_NET_RAWIO</CODE
-+> capability
-+to be executed. It is not recommended to be used as set-uid root,
-+because it allows user to modify ARP caches of neighbour hosts.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN590"
-+></A
-+><H2
-+>AVAILABILITY</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>arping</B
-+> is part of <TT
-+CLASS="FILENAME"
-+>iputils</TT
-+> package
-+and the latest versions are  available in source form at
-+<A
-+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
-+TARGET="_top"
-+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="NAVFOOTER"
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"><TABLE
-+SUMMARY="Footer navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+><A
-+HREF="r3.html"
-+ACCESSKEY="P"
-+>Prev</A
-+></TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+><A
-+HREF="index.html"
-+ACCESSKEY="H"
-+>Home</A
-+></TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+><A
-+HREF="r596.html"
-+ACCESSKEY="N"
-+>Next</A
-+></TD
-+></TR
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+>ping</TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+>&nbsp;</TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+>clockdiff</TD
-+></TR
-+></TABLE
-+></DIV
-+></BODY
-+></HTML
-+>
-\ No newline at end of file
-diff -Naur iputils-s20100418.orig/doc/r596.html iputils-s20100418/doc/r596.html
---- iputils-s20100418.orig/doc/r596.html	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/r596.html	2010-08-04 22:00:32.397576962 -0400
-@@ -0,0 +1,428 @@
-+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-+<HTML
-+><HEAD
-+><TITLE
-+>clockdiff</TITLE
-+><META
-+NAME="GENERATOR"
-+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-+REL="HOME"
-+TITLE="System Manager's Manual: iputils"
-+HREF="index.html"><LINK
-+REL="PREVIOUS"
-+TITLE="arping"
-+HREF="r437.html"><LINK
-+REL="NEXT"
-+TITLE="rarpd"
-+HREF="r691.html"></HEAD
-+><BODY
-+CLASS="REFENTRY"
-+BGCOLOR="#FFFFFF"
-+TEXT="#000000"
-+LINK="#0000FF"
-+VLINK="#840084"
-+ALINK="#0000FF"
-+><DIV
-+CLASS="NAVHEADER"
-+><TABLE
-+SUMMARY="Header navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TH
-+COLSPAN="3"
-+ALIGN="center"
-+>System Manager's Manual: iputils</TH
-+></TR
-+><TR
-+><TD
-+WIDTH="10%"
-+ALIGN="left"
-+VALIGN="bottom"
-+><A
-+HREF="r437.html"
-+ACCESSKEY="P"
-+>Prev</A
-+></TD
-+><TD
-+WIDTH="80%"
-+ALIGN="center"
-+VALIGN="bottom"
-+></TD
-+><TD
-+WIDTH="10%"
-+ALIGN="right"
-+VALIGN="bottom"
-+><A
-+HREF="r691.html"
-+ACCESSKEY="N"
-+>Next</A
-+></TD
-+></TR
-+></TABLE
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"></DIV
-+><H1
-+><A
-+NAME="CLOCKDIFF"
-+></A
-+>clockdiff</H1
-+><DIV
-+CLASS="REFNAMEDIV"
-+><A
-+NAME="AEN601"
-+></A
-+><H2
-+>Name</H2
-+>clockdiff&nbsp;--&nbsp;measure clock difference between hosts</DIV
-+><DIV
-+CLASS="REFSYNOPSISDIV"
-+><A
-+NAME="AEN604"
-+></A
-+><H2
-+>Synopsis</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>clockdiff</B
-+>  [<CODE
-+CLASS="OPTION"
-+>-o</CODE
-+>] [<CODE
-+CLASS="OPTION"
-+>-o1</CODE
-+>] {<TT
-+CLASS="REPLACEABLE"
-+><I
-+>destination</I
-+></TT
-+>}</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN613"
-+></A
-+><H2
-+>DESCRIPTION</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>clockdiff</B
-+> Measures clock difference between us and
-+<TT
-+CLASS="REPLACEABLE"
-+><I
-+>destination</I
-+></TT
-+> with 1 msec resolution using ICMP TIMESTAMP
-+<A
-+HREF="r596.html#CLOCKDIFF.ICMP-TIMESTAMP"
-+>[2]</A
-+>
-+packets or, optionally, IP TIMESTAMP option
-+<A
-+HREF="r596.html#CLOCKDIFF.IP-TIMESTAMP"
-+>[3]</A
-+>
-+option added to ICMP ECHO.
-+<A
-+HREF="r596.html#CLOCKDIFF.ICMP-ECHO"
-+>[1]</A
-+></P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN621"
-+></A
-+><H2
-+>OPTIONS</H2
-+><P
-+></P
-+><DIV
-+CLASS="VARIABLELIST"
-+><DL
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-o</CODE
-+></DT
-+><DD
-+><P
-+>Use IP TIMESTAMP with ICMP ECHO instead of ICMP TIMESTAMP
-+messages. It is useful with some destinations, which do not support
-+ICMP TIMESTAMP (f.e. Solaris &lt;2.4).
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-o1</CODE
-+></DT
-+><DD
-+><P
-+>Slightly different form of <CODE
-+CLASS="OPTION"
-+>-o</CODE
-+>, namely it uses three-term
-+IP TIMESTAMP with prespecified hop addresses instead of four term one.
-+What flavor works better depends on target host. Particularly,
-+<CODE
-+CLASS="OPTION"
-+>-o</CODE
-+> is better for Linux.
-+  </P
-+></DD
-+></DL
-+></DIV
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN636"
-+></A
-+><H2
-+>WARNINGS</H2
-+><P
-+></P
-+><UL
-+><LI
-+><P
-+>Some nodes (Cisco) use non-standard timestamps, which is allowed
-+by RFC, but makes timestamps mostly useless.
-+ </P
-+></LI
-+><LI
-+><P
-+>Some nodes generate messed timestamps (Solaris&gt;2.4), when
-+run <B
-+CLASS="COMMAND"
-+>xntpd</B
-+>. Seems, its IP stack uses a corrupted clock source,
-+which is synchronized to time-of-day clock periodically and jumps
-+randomly making timestamps mostly useless. Good news is that you can
-+use NTP in this case, which is even better.
-+ </P
-+></LI
-+><LI
-+><P
-+><B
-+CLASS="COMMAND"
-+>clockdiff</B
-+> shows difference in time modulo 24 days.
-+ </P
-+></LI
-+></UL
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN647"
-+></A
-+><H2
-+>SEE ALSO</H2
-+><P
-+><A
-+HREF="r3.html"
-+><SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>ping</SPAN
-+>(8)</SPAN
-+></A
-+>,
-+<A
-+HREF="r437.html"
-+><SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>arping</SPAN
-+>(8)</SPAN
-+></A
-+>,
-+<A
-+HREF="r790.html"
-+><SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>tracepath</SPAN
-+>(8)</SPAN
-+></A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN662"
-+></A
-+><H2
-+>REFERENCES</H2
-+><P
-+>[1] <A
-+NAME="CLOCKDIFF.ICMP-ECHO"
-+></A
-+>ICMP ECHO,
-+<A
-+HREF="ftp://ftp.isi.edu/in-notes/rfc792.txt"
-+TARGET="_top"
-+>RFC0792, page 14</A
-+>.</P
-+><P
-+>[2] <A
-+NAME="CLOCKDIFF.ICMP-TIMESTAMP"
-+></A
-+>ICMP TIMESTAMP,
-+<A
-+HREF="ftp://ftp.isi.edu/in-notes/rfc792.txt"
-+TARGET="_top"
-+>RFC0792, page 16</A
-+>.</P
-+><P
-+>[3] <A
-+NAME="CLOCKDIFF.IP-TIMESTAMP"
-+></A
-+>IP TIMESTAMP option,
-+<A
-+HREF="ftp://ftp.isi.edu/in-notes/rfc791.txt"
-+TARGET="_top"
-+>RFC0791, 3.1, page 16</A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN673"
-+></A
-+><H2
-+>AUTHOR</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>clockdiff</B
-+> was compiled by
-+<A
-+HREF="mailto:kuznet@ms2.inr.ac.ru"
-+TARGET="_top"
-+>Alexey Kuznetsov
-+&lt;kuznet@ms2.inr.ac.ru&gt;</A
-+>. It was based on code borrowed
-+from BSD <B
-+CLASS="COMMAND"
-+>timed</B
-+> daemon.
-+It is now maintained by
-+<A
-+HREF="mailto:yoshfuji@skbuff.net"
-+TARGET="_top"
-+>YOSHIFUJI Hideaki
-+&lt;yoshfuji@skbuff.net&gt;</A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN680"
-+></A
-+><H2
-+>SECURITY</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>clockdiff</B
-+> requires <CODE
-+CLASS="CONSTANT"
-+>CAP_NET_RAWIO</CODE
-+> capability
-+to be executed. It is safe to be used as set-uid root.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN685"
-+></A
-+><H2
-+>AVAILABILITY</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>clockdiff</B
-+> is part of <TT
-+CLASS="FILENAME"
-+>iputils</TT
-+> package
-+and the latest versions are  available in source form at
-+<A
-+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
-+TARGET="_top"
-+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="NAVFOOTER"
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"><TABLE
-+SUMMARY="Footer navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+><A
-+HREF="r437.html"
-+ACCESSKEY="P"
-+>Prev</A
-+></TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+><A
-+HREF="index.html"
-+ACCESSKEY="H"
-+>Home</A
-+></TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+><A
-+HREF="r691.html"
-+ACCESSKEY="N"
-+>Next</A
-+></TD
-+></TR
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+>arping</TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+>&nbsp;</TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+>rarpd</TD
-+></TR
-+></TABLE
-+></DIV
-+></BODY
-+></HTML
-+>
-\ No newline at end of file
-diff -Naur iputils-s20100418.orig/doc/r691.html iputils-s20100418/doc/r691.html
---- iputils-s20100418.orig/doc/r691.html	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/r691.html	2010-08-04 22:00:32.405576771 -0400
-@@ -0,0 +1,431 @@
-+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-+<HTML
-+><HEAD
-+><TITLE
-+>rarpd</TITLE
-+><META
-+NAME="GENERATOR"
-+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-+REL="HOME"
-+TITLE="System Manager's Manual: iputils"
-+HREF="index.html"><LINK
-+REL="PREVIOUS"
-+TITLE="clockdiff"
-+HREF="r596.html"><LINK
-+REL="NEXT"
-+TITLE="tracepath"
-+HREF="r790.html"></HEAD
-+><BODY
-+CLASS="REFENTRY"
-+BGCOLOR="#FFFFFF"
-+TEXT="#000000"
-+LINK="#0000FF"
-+VLINK="#840084"
-+ALINK="#0000FF"
-+><DIV
-+CLASS="NAVHEADER"
-+><TABLE
-+SUMMARY="Header navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TH
-+COLSPAN="3"
-+ALIGN="center"
-+>System Manager's Manual: iputils</TH
-+></TR
-+><TR
-+><TD
-+WIDTH="10%"
-+ALIGN="left"
-+VALIGN="bottom"
-+><A
-+HREF="r596.html"
-+ACCESSKEY="P"
-+>Prev</A
-+></TD
-+><TD
-+WIDTH="80%"
-+ALIGN="center"
-+VALIGN="bottom"
-+></TD
-+><TD
-+WIDTH="10%"
-+ALIGN="right"
-+VALIGN="bottom"
-+><A
-+HREF="r790.html"
-+ACCESSKEY="N"
-+>Next</A
-+></TD
-+></TR
-+></TABLE
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"></DIV
-+><H1
-+><A
-+NAME="RARPD"
-+></A
-+>rarpd</H1
-+><DIV
-+CLASS="REFNAMEDIV"
-+><A
-+NAME="AEN696"
-+></A
-+><H2
-+>Name</H2
-+>rarpd&nbsp;--&nbsp;answer RARP REQUESTs</DIV
-+><DIV
-+CLASS="REFSYNOPSISDIV"
-+><A
-+NAME="AEN699"
-+></A
-+><H2
-+>Synopsis</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>arping</B
-+>  [<CODE
-+CLASS="OPTION"
-+>-aAvde</CODE
-+>] [-b <TT
-+CLASS="REPLACEABLE"
-+><I
-+>bootdir</I
-+></TT
-+>] [<TT
-+CLASS="REPLACEABLE"
-+><I
-+>interface</I
-+></TT
-+>]</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN708"
-+></A
-+><H2
-+>DESCRIPTION</H2
-+><P
-+>Listens
-+<A
-+HREF="ftp://ftp.isi.edu/in-notes/rfc903.txt"
-+TARGET="_top"
-+>RARP</A
-+>
-+requests from clients. Provided MAC address of client
-+is found in <TT
-+CLASS="FILENAME"
-+>/etc/ethers</TT
-+> database and
-+obtained host name is resolvable to an IP address appropriate
-+for attached network, <B
-+CLASS="COMMAND"
-+>rarpd</B
-+> answers to client with RARPD
-+reply carrying an IP address.</P
-+><P
-+>To allow multiple boot servers on the network <B
-+CLASS="COMMAND"
-+>rarpd</B
-+>
-+optionally checks for presence Sun-like bootable image in TFTP directory.
-+It should have form <KBD
-+CLASS="USERINPUT"
-+>Hexadecimal_IP.ARCH</KBD
-+>, f.e. to load
-+sparc 193.233.7.98 <TT
-+CLASS="FILENAME"
-+>C1E90762.SUN4M</TT
-+> is linked to
-+an image appropriate for SUM4M in directory <TT
-+CLASS="FILENAME"
-+>/etc/tftpboot</TT
-+>.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN719"
-+></A
-+><H2
-+>WARNING</H2
-+><P
-+>This facility is deeply obsoleted by
-+<A
-+HREF="ftp://ftp.isi.edu/in-notes/rfc951.txt"
-+TARGET="_top"
-+>BOOTP</A
-+>
-+and later
-+<A
-+HREF="ftp://ftp.isi.edu/in-notes/rfc2131.txt"
-+TARGET="_top"
-+>DHCP</A
-+> protocols.
-+However, some clients really still need this to boot.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN724"
-+></A
-+><H2
-+>OPTIONS</H2
-+><P
-+></P
-+><DIV
-+CLASS="VARIABLELIST"
-+><DL
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-a</CODE
-+></DT
-+><DD
-+><P
-+>Listen on all the interfaces. Currently it is an internal
-+option, its function is overridden with <TT
-+CLASS="REPLACEABLE"
-+><I
-+>interface</I
-+></TT
-+>
-+argument. It should not be used.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-A</CODE
-+></DT
-+><DD
-+><P
-+>Listen not only RARP but also ARP messages, some rare clients
-+use ARP by some unknown reason.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-v</CODE
-+></DT
-+><DD
-+><P
-+>Be verbose.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-d</CODE
-+></DT
-+><DD
-+><P
-+>Debug mode. Do not go to background.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-e</CODE
-+></DT
-+><DD
-+><P
-+>Do not check for presence of a boot image, reply if MAC address
-+resolves to a valid IP address using <TT
-+CLASS="FILENAME"
-+>/etc/ethers</TT
-+>
-+database and DNS. 
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-b <TT
-+CLASS="REPLACEABLE"
-+><I
-+>bootdir</I
-+></TT
-+></CODE
-+></DT
-+><DD
-+><P
-+>TFTP boot directory. Default is <TT
-+CLASS="FILENAME"
-+>/etc/tftpboot</TT
-+>
-+  </P
-+></DD
-+></DL
-+></DIV
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN761"
-+></A
-+><H2
-+>SEE ALSO</H2
-+><P
-+><A
-+HREF="r437.html"
-+><SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>arping</SPAN
-+>(8)</SPAN
-+></A
-+>,
-+<A
-+HREF="r949.html"
-+><SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>tftpd</SPAN
-+>(8)</SPAN
-+></A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN772"
-+></A
-+><H2
-+>AUTHOR</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>rarpd</B
-+> was written by
-+<A
-+HREF="mailto:kuznet@ms2.inr.ac.ru"
-+TARGET="_top"
-+>Alexey Kuznetsov
-+&lt;kuznet@ms2.inr.ac.ru&gt;</A
-+>.
-+It is now maintained by
-+<A
-+HREF="mailto:yoshfuji@skbuff.net"
-+TARGET="_top"
-+>YOSHIFUJI Hideaki
-+&lt;yoshfuji@skbuff.net&gt;</A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN778"
-+></A
-+><H2
-+>SECURITY</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>rarpd</B
-+> requires <CODE
-+CLASS="CONSTANT"
-+>CAP_NET_RAWIO</CODE
-+> capability
-+to listen and send RARP and ARP packets. It also needs <CODE
-+CLASS="CONSTANT"
-+>CAP_NET_ADMIN</CODE
-+>
-+to give to kernel hint for ARP resolution; this is not strictly required,
-+but some (most of, to be more exact) clients are so badly broken that
-+are not able to answer ARP before they are finally booted. This is
-+not wonderful taking into account that clients using RARPD in 2002
-+are all unsupported relic creatures of 90's and even earlier.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN784"
-+></A
-+><H2
-+>AVAILABILITY</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>rarpd</B
-+> is part of <TT
-+CLASS="FILENAME"
-+>iputils</TT
-+> package
-+and the latest versions are  available in source form at
-+<A
-+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
-+TARGET="_top"
-+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="NAVFOOTER"
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"><TABLE
-+SUMMARY="Footer navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+><A
-+HREF="r596.html"
-+ACCESSKEY="P"
-+>Prev</A
-+></TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+><A
-+HREF="index.html"
-+ACCESSKEY="H"
-+>Home</A
-+></TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+><A
-+HREF="r790.html"
-+ACCESSKEY="N"
-+>Next</A
-+></TD
-+></TR
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+>clockdiff</TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+>&nbsp;</TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+>tracepath</TD
-+></TR
-+></TABLE
-+></DIV
-+></BODY
-+></HTML
-+>
-\ No newline at end of file
-diff -Naur iputils-s20100418.orig/doc/r790.html iputils-s20100418/doc/r790.html
---- iputils-s20100418.orig/doc/r790.html	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/r790.html	2010-08-04 22:00:32.417577090 -0400
-@@ -0,0 +1,426 @@
-+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-+<HTML
-+><HEAD
-+><TITLE
-+>tracepath</TITLE
-+><META
-+NAME="GENERATOR"
-+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-+REL="HOME"
-+TITLE="System Manager's Manual: iputils"
-+HREF="index.html"><LINK
-+REL="PREVIOUS"
-+TITLE="rarpd"
-+HREF="r691.html"><LINK
-+REL="NEXT"
-+TITLE="traceroute6"
-+HREF="r884.html"></HEAD
-+><BODY
-+CLASS="REFENTRY"
-+BGCOLOR="#FFFFFF"
-+TEXT="#000000"
-+LINK="#0000FF"
-+VLINK="#840084"
-+ALINK="#0000FF"
-+><DIV
-+CLASS="NAVHEADER"
-+><TABLE
-+SUMMARY="Header navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TH
-+COLSPAN="3"
-+ALIGN="center"
-+>System Manager's Manual: iputils</TH
-+></TR
-+><TR
-+><TD
-+WIDTH="10%"
-+ALIGN="left"
-+VALIGN="bottom"
-+><A
-+HREF="r691.html"
-+ACCESSKEY="P"
-+>Prev</A
-+></TD
-+><TD
-+WIDTH="80%"
-+ALIGN="center"
-+VALIGN="bottom"
-+></TD
-+><TD
-+WIDTH="10%"
-+ALIGN="right"
-+VALIGN="bottom"
-+><A
-+HREF="r884.html"
-+ACCESSKEY="N"
-+>Next</A
-+></TD
-+></TR
-+></TABLE
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"></DIV
-+><H1
-+><A
-+NAME="TRACEPATH"
-+></A
-+>tracepath</H1
-+><DIV
-+CLASS="REFNAMEDIV"
-+><A
-+NAME="AEN795"
-+></A
-+><H2
-+>Name</H2
-+>tracepath, tracepath6&nbsp;--&nbsp;traces path to a network host discovering MTU along this path</DIV
-+><DIV
-+CLASS="REFSYNOPSISDIV"
-+><A
-+NAME="AEN798"
-+></A
-+><H2
-+>Synopsis</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>tracepath</B
-+>  [-n] [-b] [-l <TT
-+CLASS="REPLACEABLE"
-+><I
-+>pktlen</I
-+></TT
-+>] {<TT
-+CLASS="REPLACEABLE"
-+><I
-+>destination</I
-+></TT
-+>} [<TT
-+CLASS="REPLACEABLE"
-+><I
-+>port</I
-+></TT
-+>]</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN809"
-+></A
-+><H2
-+>DESCRIPTION</H2
-+><P
-+>It traces path to <TT
-+CLASS="REPLACEABLE"
-+><I
-+>destination</I
-+></TT
-+> discovering MTU along this path.
-+It uses UDP port <TT
-+CLASS="REPLACEABLE"
-+><I
-+>port</I
-+></TT
-+> or some random port.
-+It is similar to <B
-+CLASS="COMMAND"
-+>traceroute</B
-+>, only does not not require superuser
-+privileges and has no fancy options.</P
-+><P
-+><B
-+CLASS="COMMAND"
-+>tracepath6</B
-+> is good replacement for <B
-+CLASS="COMMAND"
-+>traceroute6</B
-+>
-+and classic example of application of Linux error queues.
-+The situation with IPv4 is worse, because commercial
-+IP routers do not return enough information in icmp error messages.
-+Probably, it will change, when they will be updated.
-+For now it uses Van Jacobson's trick, sweeping a range
-+of UDP ports to maintain trace history.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN818"
-+></A
-+><H2
-+>OPTIONS</H2
-+><P
-+></P
-+><DIV
-+CLASS="VARIABLELIST"
-+><DL
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-n</CODE
-+></DT
-+><DD
-+><P
-+>Print primarily IP addresses numerically.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-b</CODE
-+></DT
-+><DD
-+><P
-+>Print both of host names and IP addresses.
-+  </P
-+></DD
-+><DT
-+><CODE
-+CLASS="OPTION"
-+>-l</CODE
-+></DT
-+><DD
-+><P
-+>Sets the initial packet length to <TT
-+CLASS="REPLACEABLE"
-+><I
-+>pktlen</I
-+></TT
-+> instead of
-+65536 for <B
-+CLASS="COMMAND"
-+>tracepath</B
-+> or 128000 for <B
-+CLASS="COMMAND"
-+>tracepath6</B
-+>.
-+  </P
-+></DD
-+></DL
-+></DIV
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN839"
-+></A
-+><H2
-+>OUTPUT</H2
-+><P
-+><P
-+CLASS="LITERALLAYOUT"
-+>root@mops:~&nbsp;#&nbsp;tracepath6&nbsp;3ffe:2400:0:109::2<br>
-+&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>
-+&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>
-+&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>
-+&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>
-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Resume:&nbsp;pmtu&nbsp;1480&nbsp;hops&nbsp;2&nbsp;back&nbsp;2</P
-+></P
-+><P
-+>The first column shows <TT
-+CLASS="LITERAL"
-+>TTL</TT
-+> of the probe, followed by colon.
-+Usually value of <TT
-+CLASS="LITERAL"
-+>TTL</TT
-+> is obtained from reply from network,
-+but sometimes reply does not contain necessary information and
-+we have to guess it. In this case the number is followed by ?.</P
-+><P
-+>The second column shows the network hop, which replied to the probe.
-+It is either address of router or word <TT
-+CLASS="LITERAL"
-+>[LOCALHOST]</TT
-+>, if
-+the probe was not sent to the network.</P
-+><P
-+>The rest of line shows miscellaneous information about path to
-+the correspinding hetwork hop. As rule it contains value of RTT.
-+Additionally, it can show Path MTU, when it changes.
-+If the path is asymmetric
-+or the probe finishes before it reach prescribed hop, difference
-+between number of hops in forward and backward direction is shown
-+folloing keyword <TT
-+CLASS="LITERAL"
-+>async</TT
-+>. This information is not reliable.
-+F.e. the third line shows asymmetry of 1, it is because the first probe
-+with TTL of 2 was rejected at the first hop due to Path MTU Discovery.</P
-+><P
-+>The last line summarizes information about all the path to the destination,
-+it shows detected Path MTU, amount of hops to the destination and our
-+guess about amount of hops from the destination to us, which can be
-+different when the path is asymmetric.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN851"
-+></A
-+><H2
-+>SEE ALSO</H2
-+><P
-+><SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>traceroute</SPAN
-+>(8)</SPAN
-+>,
-+<A
-+HREF="r884.html"
-+><SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>traceroute6</SPAN
-+>(8)</SPAN
-+></A
-+>,
-+<A
-+HREF="r3.html"
-+><SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>ping</SPAN
-+>(8)</SPAN
-+></A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN865"
-+></A
-+><H2
-+>AUTHOR</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>tracepath</B
-+> was written by
-+<A
-+HREF="mailto:kuznet@ms2.inr.ac.ru"
-+TARGET="_top"
-+>Alexey Kuznetsov
-+&lt;kuznet@ms2.inr.ac.ru&gt;</A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN870"
-+></A
-+><H2
-+>SECURITY</H2
-+><P
-+>No security issues.</P
-+><P
-+>This lapidary deserves to be elaborated.
-+<B
-+CLASS="COMMAND"
-+>tracepath</B
-+> is not a privileged program, unlike
-+<B
-+CLASS="COMMAND"
-+>traceroute</B
-+>, <B
-+CLASS="COMMAND"
-+>ping</B
-+> and other beasts of this kind.
-+<B
-+CLASS="COMMAND"
-+>tracepath</B
-+> may be executed by everyone who has some access
-+to network, enough to send UDP datagrams to investigated destination
-+using given port.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN878"
-+></A
-+><H2
-+>AVAILABILITY</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>tracepath</B
-+> is part of <TT
-+CLASS="FILENAME"
-+>iputils</TT
-+> package
-+and the latest versions are  available in source form at
-+<A
-+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
-+TARGET="_top"
-+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="NAVFOOTER"
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"><TABLE
-+SUMMARY="Footer navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+><A
-+HREF="r691.html"
-+ACCESSKEY="P"
-+>Prev</A
-+></TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+><A
-+HREF="index.html"
-+ACCESSKEY="H"
-+>Home</A
-+></TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+><A
-+HREF="r884.html"
-+ACCESSKEY="N"
-+>Next</A
-+></TD
-+></TR
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+>rarpd</TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+>&nbsp;</TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+>traceroute6</TD
-+></TR
-+></TABLE
-+></DIV
-+></BODY
-+></HTML
-+>
-\ No newline at end of file
-diff -Naur iputils-s20100418.orig/doc/r884.html iputils-s20100418/doc/r884.html
---- iputils-s20100418.orig/doc/r884.html	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/r884.html	2010-08-04 22:00:32.425576855 -0400
-@@ -0,0 +1,315 @@
-+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-+<HTML
-+><HEAD
-+><TITLE
-+>traceroute6</TITLE
-+><META
-+NAME="GENERATOR"
-+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-+REL="HOME"
-+TITLE="System Manager's Manual: iputils"
-+HREF="index.html"><LINK
-+REL="PREVIOUS"
-+TITLE="tracepath"
-+HREF="r790.html"><LINK
-+REL="NEXT"
-+TITLE="tftpd"
-+HREF="r949.html"></HEAD
-+><BODY
-+CLASS="REFENTRY"
-+BGCOLOR="#FFFFFF"
-+TEXT="#000000"
-+LINK="#0000FF"
-+VLINK="#840084"
-+ALINK="#0000FF"
-+><DIV
-+CLASS="NAVHEADER"
-+><TABLE
-+SUMMARY="Header navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TH
-+COLSPAN="3"
-+ALIGN="center"
-+>System Manager's Manual: iputils</TH
-+></TR
-+><TR
-+><TD
-+WIDTH="10%"
-+ALIGN="left"
-+VALIGN="bottom"
-+><A
-+HREF="r790.html"
-+ACCESSKEY="P"
-+>Prev</A
-+></TD
-+><TD
-+WIDTH="80%"
-+ALIGN="center"
-+VALIGN="bottom"
-+></TD
-+><TD
-+WIDTH="10%"
-+ALIGN="right"
-+VALIGN="bottom"
-+><A
-+HREF="r949.html"
-+ACCESSKEY="N"
-+>Next</A
-+></TD
-+></TR
-+></TABLE
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"></DIV
-+><H1
-+><A
-+NAME="TRACEROUTE6"
-+></A
-+>traceroute6</H1
-+><DIV
-+CLASS="REFNAMEDIV"
-+><A
-+NAME="AEN889"
-+></A
-+><H2
-+>Name</H2
-+>traceroute6&nbsp;--&nbsp;traces path to a network host</DIV
-+><DIV
-+CLASS="REFSYNOPSISDIV"
-+><A
-+NAME="AEN892"
-+></A
-+><H2
-+>Synopsis</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>traceroute6</B
-+>  [<CODE
-+CLASS="OPTION"
-+>-dnrvV</CODE
-+>] [-i <TT
-+CLASS="REPLACEABLE"
-+><I
-+>interface</I
-+></TT
-+>] [-m <TT
-+CLASS="REPLACEABLE"
-+><I
-+>max_ttl</I
-+></TT
-+>] [-p <TT
-+CLASS="REPLACEABLE"
-+><I
-+>port</I
-+></TT
-+>] [-q <TT
-+CLASS="REPLACEABLE"
-+><I
-+>max_probes</I
-+></TT
-+>] [-s <TT
-+CLASS="REPLACEABLE"
-+><I
-+>source</I
-+></TT
-+>] [-w <TT
-+CLASS="REPLACEABLE"
-+><I
-+>wait time</I
-+></TT
-+>] {<TT
-+CLASS="REPLACEABLE"
-+><I
-+>destination</I
-+></TT
-+>} [<TT
-+CLASS="REPLACEABLE"
-+><I
-+>size</I
-+></TT
-+>]</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN913"
-+></A
-+><H2
-+>DESCRIPTION</H2
-+><P
-+>Description can be found in 
-+<SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>traceroute</SPAN
-+>(8)</SPAN
-+>,
-+all the references to IP replaced to IPv6. It is needless to copy
-+the description from there.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN919"
-+></A
-+><H2
-+>SEE ALSO</H2
-+><P
-+><SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>traceroute</SPAN
-+>(8)</SPAN
-+>,
-+<SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>tracepath</SPAN
-+>(8)</SPAN
-+>,
-+<SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>ping</SPAN
-+>(8)</SPAN
-+>.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN931"
-+></A
-+><H2
-+>HISTORY</H2
-+><P
-+>This program has long history. Author of <B
-+CLASS="COMMAND"
-+>traceroute</B
-+>
-+is Van Jacobson and it first appeared in 1988. This clone is
-+based on a port of <B
-+CLASS="COMMAND"
-+>traceroute</B
-+> to IPv6 published
-+in NRL IPv6 distribution in 1996. In turn, it was ported
-+to Linux by Pedro Roque. After this it was kept in sync by    
-+<A
-+HREF="mailto:kuznet@ms2.inr.ac.ru"
-+TARGET="_top"
-+>Alexey Kuznetsov
-+&lt;kuznet@ms2.inr.ac.ru&gt;</A
-+>. And eventually entered
-+<B
-+CLASS="COMMAND"
-+>iputils</B
-+> package.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN938"
-+></A
-+><H2
-+>SECURITY</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>tracepath6</B
-+> requires <CODE
-+CLASS="CONSTANT"
-+>CAP_NET_RAWIO</CODE
-+> capability
-+to be executed. It is safe to be used as set-uid root.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN943"
-+></A
-+><H2
-+>AVAILABILITY</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>traceroute6</B
-+> is part of <TT
-+CLASS="FILENAME"
-+>iputils</TT
-+> package
-+and the latest versions are  available in source form at
-+<A
-+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
-+TARGET="_top"
-+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="NAVFOOTER"
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"><TABLE
-+SUMMARY="Footer navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+><A
-+HREF="r790.html"
-+ACCESSKEY="P"
-+>Prev</A
-+></TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+><A
-+HREF="index.html"
-+ACCESSKEY="H"
-+>Home</A
-+></TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+><A
-+HREF="r949.html"
-+ACCESSKEY="N"
-+>Next</A
-+></TD
-+></TR
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+>tracepath</TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+>&nbsp;</TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+>tftpd</TD
-+></TR
-+></TABLE
-+></DIV
-+></BODY
-+></HTML
-+>
-\ No newline at end of file
-diff -Naur iputils-s20100418.orig/doc/r949.html iputils-s20100418/doc/r949.html
---- iputils-s20100418.orig/doc/r949.html	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/r949.html	2010-08-04 22:00:32.433577358 -0400
-@@ -0,0 +1,376 @@
-+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-+<HTML
-+><HEAD
-+><TITLE
-+>tftpd</TITLE
-+><META
-+NAME="GENERATOR"
-+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-+REL="HOME"
-+TITLE="System Manager's Manual: iputils"
-+HREF="index.html"><LINK
-+REL="PREVIOUS"
-+TITLE="traceroute6"
-+HREF="r884.html"><LINK
-+REL="NEXT"
-+TITLE="rdisc"
-+HREF="r1022.html"></HEAD
-+><BODY
-+CLASS="REFENTRY"
-+BGCOLOR="#FFFFFF"
-+TEXT="#000000"
-+LINK="#0000FF"
-+VLINK="#840084"
-+ALINK="#0000FF"
-+><DIV
-+CLASS="NAVHEADER"
-+><TABLE
-+SUMMARY="Header navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TH
-+COLSPAN="3"
-+ALIGN="center"
-+>System Manager's Manual: iputils</TH
-+></TR
-+><TR
-+><TD
-+WIDTH="10%"
-+ALIGN="left"
-+VALIGN="bottom"
-+><A
-+HREF="r884.html"
-+ACCESSKEY="P"
-+>Prev</A
-+></TD
-+><TD
-+WIDTH="80%"
-+ALIGN="center"
-+VALIGN="bottom"
-+></TD
-+><TD
-+WIDTH="10%"
-+ALIGN="right"
-+VALIGN="bottom"
-+><A
-+HREF="r1022.html"
-+ACCESSKEY="N"
-+>Next</A
-+></TD
-+></TR
-+></TABLE
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"></DIV
-+><H1
-+><A
-+NAME="TFTPD"
-+></A
-+>tftpd</H1
-+><DIV
-+CLASS="REFNAMEDIV"
-+><A
-+NAME="AEN954"
-+></A
-+><H2
-+>Name</H2
-+>tftpd&nbsp;--&nbsp;Trivial File Transfer Protocol server</DIV
-+><DIV
-+CLASS="REFSYNOPSISDIV"
-+><A
-+NAME="AEN957"
-+></A
-+><H2
-+>Synopsis</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>tftpd</B
-+>  {<TT
-+CLASS="REPLACEABLE"
-+><I
-+>directory</I
-+></TT
-+>}</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN962"
-+></A
-+><H2
-+>DESCRIPTION</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>tftpd</B
-+> is a server which supports the DARPA
-+Trivial File Transfer Protocol
-+(<A
-+HREF="ftp://ftp.isi.edu/in-notes/rfc1350.txt"
-+TARGET="_top"
-+>RFC1350</A
-+>).
-+The TFTP server is started
-+by <SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>inetd</SPAN
-+>(8)</SPAN
-+>.</P
-+><P
-+><TT
-+CLASS="REPLACEABLE"
-+><I
-+>directory</I
-+></TT
-+> is required argument; if it is not given
-+<B
-+CLASS="COMMAND"
-+>tftpd</B
-+> aborts. This path is prepended to any file name requested
-+via TFTP protocol, effectively chrooting <B
-+CLASS="COMMAND"
-+>tftpd</B
-+> to this directory.
-+File names are validated not to escape out of this directory, however
-+administrator may configure such escape using symbolic links.</P
-+><P
-+>It is in difference of variants of <B
-+CLASS="COMMAND"
-+>tftpd</B
-+> usually distributed
-+with unix-like systems, which take a list of directories and match
-+file names to start from one of given prefixes or to some random
-+default, when no arguments were given. There are two reasons not to
-+behave in this way: first, it is inconvenient, clients are not expected
-+to know something about layout of filesystem on server host.
-+And second, TFTP protocol is not a tool for browsing of server's filesystem,
-+it is just an agent allowing to boot dumb clients. </P
-+><P
-+>In the case when <B
-+CLASS="COMMAND"
-+>tftpd</B
-+> is used together with
-+<A
-+HREF="r691.html"
-+><SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>rarpd</SPAN
-+>(8)</SPAN
-+></A
-+>,
-+tftp directories in these services should coincide and it is expected
-+that each client booted via TFTP has boot image corresponding
-+its IP address with an architecture suffix following Sun Microsystems
-+conventions. See 
-+<A
-+HREF="r691.html"
-+><SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>rarpd</SPAN
-+>(8)</SPAN
-+></A
-+>
-+for more details.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN986"
-+></A
-+><H2
-+>SECURITY</H2
-+><P
-+>TFTP protocol does not provide any authentication.
-+Due to this capital flaw <B
-+CLASS="COMMAND"
-+>tftpd</B
-+> is not able to restrict
-+access to files and will allow only publically readable
-+files to be accessed. Files may be written only if they already
-+exist and are publically writable.</P
-+><P
-+>Impact is evident, directory exported via TFTP <SPAN
-+CLASS="emphasis"
-+><I
-+CLASS="EMPHASIS"
-+>must not</I
-+></SPAN
-+>
-+contain sensitive information of any kind, everyone is allowed
-+to read it as soon as a client is allowed. Boot images do not contain
-+such information as rule, however you should think twice before
-+publishing f.e. Cisco IOS config files via TFTP, they contain
-+<SPAN
-+CLASS="emphasis"
-+><I
-+CLASS="EMPHASIS"
-+>unencrypted</I
-+></SPAN
-+> passwords and may contain some information
-+about the network, which you were not going to make public.</P
-+><P
-+>The <B
-+CLASS="COMMAND"
-+>tftpd</B
-+> server should be executed by <B
-+CLASS="COMMAND"
-+>inetd</B
-+>
-+with dropped root privileges, namely with a user ID giving minimal
-+access to files published in tftp directory. If it is executed
-+as superuser occasionally, <B
-+CLASS="COMMAND"
-+>tftpd</B
-+> drops its UID and GID
-+to 65534, which is most likely not the thing which you expect.
-+However, this is not very essential; remember, only files accessible
-+for everyone can be read or written via TFTP.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN997"
-+></A
-+><H2
-+>SEE ALSO</H2
-+><P
-+><A
-+HREF="r691.html"
-+><SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>rarpd</SPAN
-+>(8)</SPAN
-+></A
-+>,
-+<SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>tftp</SPAN
-+>(1)</SPAN
-+>,
-+<SPAN
-+CLASS="CITEREFENTRY"
-+><SPAN
-+CLASS="REFENTRYTITLE"
-+>inetd</SPAN
-+>(8)</SPAN
-+>.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN1010"
-+></A
-+><H2
-+>HISTORY</H2
-+><P
-+>The <B
-+CLASS="COMMAND"
-+>tftpd</B
-+> command appeared in 4.2BSD. The source in iputils
-+is cleaned up both syntactically (ANSIized) and semantically (UDP socket IO).</P
-+><P
-+>It is distributed with iputils mostly as good demo of an interesting feature
-+(<CODE
-+CLASS="CONSTANT"
-+>MSG_CONFIRM</CODE
-+>) allowing to boot long images by dumb clients
-+not answering ARP requests until they are finally booted.
-+However, this is full functional and can be used in production.</P
-+></DIV
-+><DIV
-+CLASS="REFSECT1"
-+><A
-+NAME="AEN1016"
-+></A
-+><H2
-+>AVAILABILITY</H2
-+><P
-+><B
-+CLASS="COMMAND"
-+>tftpd</B
-+> is part of <TT
-+CLASS="FILENAME"
-+>iputils</TT
-+> package
-+and the latest versions are  available in source form at
-+<A
-+HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
-+TARGET="_top"
-+>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
-+>.</P
-+></DIV
-+><DIV
-+CLASS="NAVFOOTER"
-+><HR
-+ALIGN="LEFT"
-+WIDTH="100%"><TABLE
-+SUMMARY="Footer navigation table"
-+WIDTH="100%"
-+BORDER="0"
-+CELLPADDING="0"
-+CELLSPACING="0"
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+><A
-+HREF="r884.html"
-+ACCESSKEY="P"
-+>Prev</A
-+></TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+><A
-+HREF="index.html"
-+ACCESSKEY="H"
-+>Home</A
-+></TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+><A
-+HREF="r1022.html"
-+ACCESSKEY="N"
-+>Next</A
-+></TD
-+></TR
-+><TR
-+><TD
-+WIDTH="33%"
-+ALIGN="left"
-+VALIGN="top"
-+>traceroute6</TD
-+><TD
-+WIDTH="34%"
-+ALIGN="center"
-+VALIGN="top"
-+>&nbsp;</TD
-+><TD
-+WIDTH="33%"
-+ALIGN="right"
-+VALIGN="top"
-+>rdisc</TD
-+></TR
-+></TABLE
-+></DIV
-+></BODY
-+></HTML
-+>
-\ No newline at end of file
-diff -Naur iputils-s20100418.orig/doc/rarpd.8 iputils-s20100418/doc/rarpd.8
---- iputils-s20100418.orig/doc/rarpd.8	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/rarpd.8	2010-08-04 22:00:25.334076349 -0400
-@@ -0,0 +1,84 @@
-+.\" This manpage has been automatically generated by docbook2man 
-+.\" from a DocBook document.  This tool can be found at:
-+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
-+.\" Please send any bug reports, improvements, comments, patches, 
-+.\" etc. to Steve Cheng <steve@ggi-project.org>.
-+.TH "RARPD" "8" "04 August 2010" "iputils-100418" "System Manager's Manual: iputils"
-+.SH NAME
-+rarpd \- answer RARP REQUESTs
-+.SH SYNOPSIS
-+
-+\fBarping\fR [\fB-aAvde\fR] [\fB-b \fIbootdir\fB\fR] [\fB\fIinterface\fB\fR]
-+
-+.SH "DESCRIPTION"
-+.PP
-+Listens
-+RARP
-+requests from clients. Provided MAC address of client
-+is found in \fI/etc/ethers\fR database and
-+obtained host name is resolvable to an IP address appropriate
-+for attached network, \fBrarpd\fR answers to client with RARPD
-+reply carrying an IP address.
-+.PP
-+To allow multiple boot servers on the network \fBrarpd\fR
-+optionally checks for presence Sun-like bootable image in TFTP directory.
-+It should have form \fBHexadecimal_IP.ARCH\fR, f.e. to load
-+sparc 193.233.7.98 \fIC1E90762.SUN4M\fR is linked to
-+an image appropriate for SUM4M in directory \fI/etc/tftpboot\fR.
-+.SH "WARNING"
-+.PP
-+This facility is deeply obsoleted by
-+BOOTP
-+and later
-+DHCP protocols.
-+However, some clients really still need this to boot.
-+.SH "OPTIONS"
-+.TP
-+\fB-a\fR
-+Listen on all the interfaces. Currently it is an internal
-+option, its function is overridden with \fIinterface\fR
-+argument. It should not be used.
-+.TP
-+\fB-A\fR
-+Listen not only RARP but also ARP messages, some rare clients
-+use ARP by some unknown reason.
-+.TP
-+\fB-v\fR
-+Be verbose.
-+.TP
-+\fB-d\fR
-+Debug mode. Do not go to background.
-+.TP
-+\fB-e\fR
-+Do not check for presence of a boot image, reply if MAC address
-+resolves to a valid IP address using \fI/etc/ethers\fR
-+database and DNS. 
-+.TP
-+\fB-b \fIbootdir\fB\fR
-+TFTP boot directory. Default is \fI/etc/tftpboot\fR
-+.SH "SEE ALSO"
-+.PP
-+\fBarping\fR(8),
-+\fBtftpd\fR(8).
-+.SH "AUTHOR"
-+.PP
-+\fBrarpd\fR was written by
-+Alexey Kuznetsov
-+<kuznet@ms2.inr.ac.ru>.
-+It is now maintained by
-+YOSHIFUJI Hideaki
-+<yoshfuji@skbuff.net>.
-+.SH "SECURITY"
-+.PP
-+\fBrarpd\fR requires CAP_NET_RAWIO capability
-+to listen and send RARP and ARP packets. It also needs CAP_NET_ADMIN
-+to give to kernel hint for ARP resolution; this is not strictly required,
-+but some (most of, to be more exact) clients are so badly broken that
-+are not able to answer ARP before they are finally booted. This is
-+not wonderful taking into account that clients using RARPD in 2002
-+are all unsupported relic creatures of 90's and even earlier.
-+.SH "AVAILABILITY"
-+.PP
-+\fBrarpd\fR is part of \fIiputils\fR package
-+and the latest versions are  available in source form at
-+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
-diff -Naur iputils-s20100418.orig/doc/rdisc.8 iputils-s20100418/doc/rdisc.8
---- iputils-s20100418.orig/doc/rdisc.8	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/rdisc.8	2010-08-04 22:00:25.602079120 -0400
-@@ -0,0 +1,110 @@
-+.\" This manpage has been automatically generated by docbook2man 
-+.\" from a DocBook document.  This tool can be found at:
-+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
-+.\" Please send any bug reports, improvements, comments, patches, 
-+.\" etc. to Steve Cheng <steve@ggi-project.org>.
-+.TH "RDISC" "8" "04 August 2010" "iputils-100418" "System Manager's Manual: iputils"
-+.SH NAME
-+rdisc \- network router discovery daemon
-+.SH SYNOPSIS
-+
-+\fBrdisc\fR [\fB-abdfstvV\fR] [\fB\fIsend_address\fB\fR] [\fB\fIreceive_address\fB\fR]
-+
-+.SH "DESCRIPTION"
-+.PP
-+\fBrdisc\fR implements client side of the ICMP router discover protocol.
-+\fBrdisc\fR is invoked at boot time to populate the network
-+routing tables with default routes. 
-+.PP
-+\fBrdisc\fR listens on the ALL_HOSTS (224.0.0.1) multicast address
-+(or \fIreceive_address\fR provided it is given) 
-+for ROUTER_ADVERTISE messages from routers. The received
-+messages are handled by first ignoring those listed router addresses
-+with which the host does not share a network. Among the remaining addresses
-+the ones with the highest preference are selected as default routers
-+and a default route is entered in the kernel routing table
-+for each one of them.
-+.PP
-+Optionally, \fBrdisc\fR can avoid waiting for routers to announce 
-+themselves by sending out a few ROUTER_SOLICITATION messages
-+to the ALL_ROUTERS (224.0.0.2) multicast address 
-+(or \fIsend_address\fR provided it is given) 
-+when it is started.
-+.PP
-+A timer is associated with each router address and the address will
-+no longer be considered for inclusion in the the routing tables if the 
-+timer expires before a new 
-+\fBadvertise\fR message is received from the router.
-+The address will also be excluded from consideration if the host receives an 
-+\fBadvertise\fR
-+message with the preference being maximally negative.
-+.PP
-+Server side of router discovery protocol is supported by Cisco IOS
-+and by any more or less complete UNIX routing daemon, f.e \fBgated\fR.
-+.SH "OPTIONS"
-+.TP
-+\fB-a\fR
-+Accept all routers independently of the preference they have in their 
-+\fBadvertise\fR messages.
-+Normally \fBrdisc\fR only accepts (and enters in the kernel routing
-+tables) the router or routers with the highest preference.
-+.TP
-+\fB-b\fR
-+Opposite to \fB-a\fR, i.e. install only router with the best
-+preference value. It is default behaviour.
-+.TP
-+\fB-d\fR
-+Send debugging messages to syslog.
-+.TP
-+\fB-f\fR
-+Run \fBrdisc\fR forever even if no routers are found.
-+Normally \fBrdisc\fR gives up if it has not received any 
-+\fBadvertise\fR message after after soliciting three times,
-+in which case it exits with a non-zero exit code.
-+If \fB-f\fR is not specified in the first form then 
-+\fB-s\fR must be specified.
-+.TP
-+\fB-s\fR
-+Send three \fBsolicitation\fR messages initially to quickly discover
-+the routers when the system is booted.
-+When \fB-s\fR is specified \fBrdisc\fR
-+exits with a non-zero exit code if it can not find any routers.
-+This can be overridden with the \fB-f\fR option.
-+.TP
-+\fB-t\fR
-+Test mode. Do not go to background.
-+.TP
-+\fB-v\fR
-+Be verbose i.e. send lots of debugging messages to syslog.
-+.TP
-+\fB-V\fR
-+Print version and exit.
-+.SH "HISTORY"
-+.PP
-+This program was developed by Sun Microsystems (see copyright
-+notice in source file). It was ported to Linux by
-+Alexey Kuznetsov
-+<kuznet@ms2.inr.ac.ru>.
-+It is now maintained by
-+YOSHIFUJI Hideaki
-+<yoshfuji@skbuff.net>.
-+.SH "SEE ALSO"
-+.PP
-+\fBicmp\fR(7),
-+\fBinet\fR(7),
-+\fBping\fR(8).
-+.SH "REFERENCES"
-+.PP
-+Deering, S.E.,ed "ICMP Router Discovery Messages",
-+RFC1256, Network Information Center, SRI International,
-+Menlo Park, Calif., September 1991.
-+.SH "SECURITY"
-+.PP
-+\fBrdisc\fR requires CAP_NET_RAWIO to listen
-+and send ICMP messages and capability CAP_NET_ADMIN
-+to update routing tables. 
-+.SH "AVAILABILITY"
-+.PP
-+\fBrdisc\fR is part of \fIiputils\fR package
-+and the latest versions are  available in source form at
-+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
-diff -Naur iputils-s20100418.orig/doc/tftpd.8 iputils-s20100418/doc/tftpd.8
---- iputils-s20100418.orig/doc/tftpd.8	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/tftpd.8	2010-08-04 22:00:25.782079442 -0400
-@@ -0,0 +1,85 @@
-+.\" This manpage has been automatically generated by docbook2man 
-+.\" from a DocBook document.  This tool can be found at:
-+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
-+.\" Please send any bug reports, improvements, comments, patches, 
-+.\" etc. to Steve Cheng <steve@ggi-project.org>.
-+.TH "TFTPD" "8" "04 August 2010" "iputils-100418" "System Manager's Manual: iputils"
-+.SH NAME
-+tftpd \- Trivial File Transfer Protocol server
-+.SH SYNOPSIS
-+
-+\fBtftpd\fR \fB\fIdirectory\fB\fR
-+
-+.SH "DESCRIPTION"
-+.PP
-+\fBtftpd\fR is a server which supports the DARPA
-+Trivial File Transfer Protocol
-+(RFC1350).
-+The TFTP server is started
-+by \fBinetd\fR(8).
-+.PP
-+\fIdirectory\fR is required argument; if it is not given
-+\fBtftpd\fR aborts. This path is prepended to any file name requested
-+via TFTP protocol, effectively chrooting \fBtftpd\fR to this directory.
-+File names are validated not to escape out of this directory, however
-+administrator may configure such escape using symbolic links.
-+.PP
-+It is in difference of variants of \fBtftpd\fR usually distributed
-+with unix-like systems, which take a list of directories and match
-+file names to start from one of given prefixes or to some random
-+default, when no arguments were given. There are two reasons not to
-+behave in this way: first, it is inconvenient, clients are not expected
-+to know something about layout of filesystem on server host.
-+And second, TFTP protocol is not a tool for browsing of server's filesystem,
-+it is just an agent allowing to boot dumb clients. 
-+.PP
-+In the case when \fBtftpd\fR is used together with
-+\fBrarpd\fR(8),
-+tftp directories in these services should coincide and it is expected
-+that each client booted via TFTP has boot image corresponding
-+its IP address with an architecture suffix following Sun Microsystems
-+conventions. See 
-+\fBrarpd\fR(8)
-+for more details.
-+.SH "SECURITY"
-+.PP
-+TFTP protocol does not provide any authentication.
-+Due to this capital flaw \fBtftpd\fR is not able to restrict
-+access to files and will allow only publically readable
-+files to be accessed. Files may be written only if they already
-+exist and are publically writable.
-+.PP
-+Impact is evident, directory exported via TFTP \fBmust not\fR
-+contain sensitive information of any kind, everyone is allowed
-+to read it as soon as a client is allowed. Boot images do not contain
-+such information as rule, however you should think twice before
-+publishing f.e. Cisco IOS config files via TFTP, they contain
-+\fBunencrypted\fR passwords and may contain some information
-+about the network, which you were not going to make public.
-+.PP
-+The \fBtftpd\fR server should be executed by \fBinetd\fR
-+with dropped root privileges, namely with a user ID giving minimal
-+access to files published in tftp directory. If it is executed
-+as superuser occasionally, \fBtftpd\fR drops its UID and GID
-+to 65534, which is most likely not the thing which you expect.
-+However, this is not very essential; remember, only files accessible
-+for everyone can be read or written via TFTP.
-+.SH "SEE ALSO"
-+.PP
-+\fBrarpd\fR(8),
-+\fBtftp\fR(1),
-+\fBinetd\fR(8).
-+.SH "HISTORY"
-+.PP
-+The \fBtftpd\fR command appeared in 4.2BSD. The source in iputils
-+is cleaned up both syntactically (ANSIized) and semantically (UDP socket IO).
-+.PP
-+It is distributed with iputils mostly as good demo of an interesting feature
-+(MSG_CONFIRM) allowing to boot long images by dumb clients
-+not answering ARP requests until they are finally booted.
-+However, this is full functional and can be used in production.
-+.SH "AVAILABILITY"
-+.PP
-+\fBtftpd\fR is part of \fIiputils\fR package
-+and the latest versions are  available in source form at
-+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
-diff -Naur iputils-s20100418.orig/doc/tracepath.8 iputils-s20100418/doc/tracepath.8
---- iputils-s20100418.orig/doc/tracepath.8	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/tracepath.8	2010-08-04 22:00:26.214078440 -0400
-@@ -0,0 +1,97 @@
-+.\" This manpage has been automatically generated by docbook2man 
-+.\" from a DocBook document.  This tool can be found at:
-+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
-+.\" Please send any bug reports, improvements, comments, patches, 
-+.\" etc. to Steve Cheng <steve@ggi-project.org>.
-+.TH "TRACEPATH" "8" "04 August 2010" "iputils-100418" "System Manager's Manual: iputils"
-+.SH NAME
-+tracepath, tracepath6 \- traces path to a network host discovering MTU along this path
-+.SH SYNOPSIS
-+
-+\fBtracepath\fR [\fB-n\fR] [\fB-b\fR] [\fB-l \fIpktlen\fB\fR] \fB\fIdestination\fB\fR [\fB\fIport\fB\fR]
-+
-+.SH "DESCRIPTION"
-+.PP
-+It traces path to \fIdestination\fR discovering MTU along this path.
-+It uses UDP port \fIport\fR or some random port.
-+It is similar to \fBtraceroute\fR, only does not not require superuser
-+privileges and has no fancy options.
-+.PP
-+\fBtracepath6\fR is good replacement for \fBtraceroute6\fR
-+and classic example of application of Linux error queues.
-+The situation with IPv4 is worse, because commercial
-+IP routers do not return enough information in icmp error messages.
-+Probably, it will change, when they will be updated.
-+For now it uses Van Jacobson's trick, sweeping a range
-+of UDP ports to maintain trace history.
-+.SH "OPTIONS"
-+.TP
-+\fB-n\fR
-+Print primarily IP addresses numerically.
-+.TP
-+\fB-b\fR
-+Print both of host names and IP addresses.
-+.TP
-+\fB-l\fR
-+Sets the initial packet length to \fIpktlen\fR instead of
-+65536 for \fBtracepath\fR or 128000 for \fBtracepath6\fR.
-+.SH "OUTPUT"
-+.PP
-+
-+.nf
-+root@mops:~ # tracepath6 3ffe:2400:0:109::2
-+ 1?: [LOCALHOST]                              pmtu 1500
-+ 1:  dust.inr.ac.ru                   0.411ms
-+ 2:  dust.inr.ac.ru        asymm  1   0.390ms pmtu 1480
-+ 2:  3ffe:2400:0:109::2               463.514ms reached
-+     Resume: pmtu 1480 hops 2 back 2
-+.fi
-+.PP
-+The first column shows TTL of the probe, followed by colon.
-+Usually value of TTL is obtained from reply from network,
-+but sometimes reply does not contain necessary information and
-+we have to guess it. In this case the number is followed by ?.
-+.PP
-+The second column shows the network hop, which replied to the probe.
-+It is either address of router or word [LOCALHOST], if
-+the probe was not sent to the network.
-+.PP
-+The rest of line shows miscellaneous information about path to
-+the correspinding hetwork hop. As rule it contains value of RTT.
-+Additionally, it can show Path MTU, when it changes.
-+If the path is asymmetric
-+or the probe finishes before it reach prescribed hop, difference
-+between number of hops in forward and backward direction is shown
-+folloing keyword async. This information is not reliable.
-+F.e. the third line shows asymmetry of 1, it is because the first probe
-+with TTL of 2 was rejected at the first hop due to Path MTU Discovery.
-+.PP
-+The last line summarizes information about all the path to the destination,
-+it shows detected Path MTU, amount of hops to the destination and our
-+guess about amount of hops from the destination to us, which can be
-+different when the path is asymmetric.
-+.SH "SEE ALSO"
-+.PP
-+\fBtraceroute\fR(8),
-+\fBtraceroute6\fR(8),
-+\fBping\fR(8).
-+.SH "AUTHOR"
-+.PP
-+\fBtracepath\fR was written by
-+Alexey Kuznetsov
-+<kuznet@ms2.inr.ac.ru>.
-+.SH "SECURITY"
-+.PP
-+No security issues.
-+.PP
-+This lapidary deserves to be elaborated.
-+\fBtracepath\fR is not a privileged program, unlike
-+\fBtraceroute\fR, \fBping\fR and other beasts of this kind.
-+\fBtracepath\fR may be executed by everyone who has some access
-+to network, enough to send UDP datagrams to investigated destination
-+using given port.
-+.SH "AVAILABILITY"
-+.PP
-+\fBtracepath\fR is part of \fIiputils\fR package
-+and the latest versions are  available in source form at
-+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
-diff -Naur iputils-s20100418.orig/doc/traceroute6.8 iputils-s20100418/doc/traceroute6.8
---- iputils-s20100418.orig/doc/traceroute6.8	1969-12-31 19:00:00.000000000 -0500
-+++ iputils-s20100418/doc/traceroute6.8	2010-08-04 22:00:26.173737598 -0400
-@@ -0,0 +1,42 @@
-+.\" This manpage has been automatically generated by docbook2man 
-+.\" from a DocBook document.  This tool can be found at:
-+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
-+.\" Please send any bug reports, improvements, comments, patches, 
-+.\" etc. to Steve Cheng <steve@ggi-project.org>.
-+.TH "TRACEROUTE6" "8" "04 August 2010" "iputils-100418" "System Manager's Manual: iputils"
-+.SH NAME
-+traceroute6 \- traces path to a network host
-+.SH SYNOPSIS
-+
-+\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]
-+
-+.SH "DESCRIPTION"
-+.PP
-+Description can be found in 
-+\fBtraceroute\fR(8),
-+all the references to IP replaced to IPv6. It is needless to copy
-+the description from there.
-+.SH "SEE ALSO"
-+.PP
-+\fBtraceroute\fR(8),
-+\fBtracepath\fR(8),
-+\fBping\fR(8).
-+.SH "HISTORY"
-+.PP
-+This program has long history. Author of \fBtraceroute\fR
-+is Van Jacobson and it first appeared in 1988. This clone is
-+based on a port of \fBtraceroute\fR to IPv6 published
-+in NRL IPv6 distribution in 1996. In turn, it was ported
-+to Linux by Pedro Roque. After this it was kept in sync by    
-+Alexey Kuznetsov
-+<kuznet@ms2.inr.ac.ru>. And eventually entered
-+\fBiputils\fR package.
-+.SH "SECURITY"
-+.PP
-+\fBtracepath6\fR requires CAP_NET_RAWIO capability
-+to be executed. It is safe to be used as set-uid root.
-+.SH "AVAILABILITY"
-+.PP
-+\fBtraceroute6\fR is part of \fIiputils\fR package
-+and the latest versions are  available in source form at
-+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
Index: tches/iputils-s20100418-fixes-1.patch
===================================================================
--- patches/iputils-s20100418-fixes-1.patch	(revision b575f2084b4e4297105cfca27bda908accc89c8c)
+++ 	(revision )
@@ -1,173 +1,0 @@
-diff -Naur iputils-s20100418.orig/Makefile iputils-s20100418/Makefile
---- iputils-s20100418.orig/Makefile	2010-04-18 00:45:45.000000000 -0400
-+++ iputils-s20100418/Makefile	2010-08-04 19:52:08.438080809 -0400
-@@ -16,7 +16,7 @@
- CCOPT=-D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -g
- CFLAGS=$(CCOPT) $(GLIBCFIX) $(DEFINES) 
- 
--IPV4_TARGETS=tracepath ping clockdiff rdisc arping tftpd rarpd
-+IPV4_TARGETS=tracepath ping arping clockdiff
- IPV6_TARGETS=tracepath6 traceroute6 ping6
- TARGETS=$(IPV4_TARGETS) $(IPV6_TARGETS)
- 
-diff -Naur iputils-s20100418.orig/arping.c iputils-s20100418/arping.c
---- iputils-s20100418.orig/arping.c	2010-04-18 00:45:45.000000000 -0400
-+++ iputils-s20100418/arping.c	2010-08-04 19:52:08.441575956 -0400
-@@ -182,12 +182,17 @@
- 	if (start.tv_sec==0)
- 		start = tv;
- 
--	if (count-- == 0 || (timeout && MS_TDIFF(tv,start) > timeout*1000 + 500))
-+	if (timeout && MS_TDIFF(tv,start) > timeout*1000 + 500)
- 		finish();
- 
--	if (last.tv_sec==0 || MS_TDIFF(tv,last) > 500) {
-+	if ((!timeout) && (count == 0))
-+		finish();
-+
-+	if ( count!=0  && (last.tv_sec==0 || MS_TDIFF(tv,last) > 500 ) ) {
- 		send_pack(s, src, dst,
- 			  (struct sockaddr_ll *)&me, (struct sockaddr_ll *)&he);
-+		if (count >= 0)
-+		    count--;
- 		if (count == 0 && unsolicited)
- 			finish();
- 	}
-diff -Naur iputils-s20100418.orig/doc/Makefile iputils-s20100418/doc/Makefile
---- iputils-s20100418.orig/doc/Makefile	2010-04-18 00:45:45.000000000 -0400
-+++ iputils-s20100418/doc/Makefile	2010-08-04 19:52:08.441575956 -0400
-@@ -6,7 +6,7 @@
- 
- html: $(HTMLFILES) iputils.html
- 
--man: $(MANFILES)
-+man: $(MANFILES) fix_sgml2man
- 
- # docbook scripts are incredibly dirty in the sense that they leak
- # lots of some strange temporary junk directories and files.
-@@ -33,6 +33,9 @@
- 	@set -e; cd tmp.db2man; nsgmls ../$< | sgmlspl ../docbook2man-spec.pl ;	mv $@ ..
- 	@-rm -rf tmp.db2man
- 
-+fix_sgml2man:
-+	@sed -i -e 's!\\fB\\fIdestination\\fB\\fR \[\\fB/\\fIport\\fB\\fR\]!\\fB\\fIdestination\\fB\\fR[\\fB/\\fIport\\fB\\fR]!g' tracepath.8
-+
- clean:
- 	@rm -rf $(MANFILES) $(HTMLFILES) iputils.html tmp.db2html tmp.db2man
- 
-diff -Naur iputils-s20100418.orig/doc/docbook2man-spec.pl iputils-s20100418/doc/docbook2man-spec.pl
---- iputils-s20100418.orig/doc/docbook2man-spec.pl	2010-04-18 00:45:45.000000000 -0400
-+++ iputils-s20100418/doc/docbook2man-spec.pl	2010-08-04 19:52:08.438080809 -0400
-@@ -428,7 +428,7 @@
- 	output ' ';
- 
- 	if($_[0]->attribute('CHOICE')->value =~ /opt/i) {
--		output '[ ';
-+		output '[';
- 	}
- 	bold_on();
- }
-@@ -441,7 +441,7 @@
- 		font_off();
- 	}
- 	if($_[0]->attribute('CHOICE')->value =~ /opt/i) {
--		output '] ';
-+		output ']';
- 	}
- }
- 
-diff -Naur iputils-s20100418.orig/ping.c iputils-s20100418/ping.c
---- iputils-s20100418.orig/ping.c	2010-04-18 00:45:45.000000000 -0400
-+++ iputils-s20100418/ping.c	2010-08-04 19:52:08.441575956 -0400
-@@ -250,7 +250,7 @@
- 			if (argc == 1)
- 				options |= F_NUMERIC;
- 		} else {
--			hp = gethostbyname(target);
-+			hp = gethostbyname2(target, AF_INET);
- 			if (!hp) {
- 				fprintf(stderr, "ping: unknown host %s\n", target);
- 				exit(2);
-@@ -883,9 +883,36 @@
- 		case ICMP_SR_FAILED:
- 			printf("Source Route Failed\n");
- 			break;
-+		case ICMP_NET_UNKNOWN:
-+			printf("Destination Net Unknown\n");
-+			break;
-+		case ICMP_HOST_UNKNOWN:
-+			printf("Destination Host Unknown\n");
-+			break;
-+		case ICMP_HOST_ISOLATED:
-+			printf("Source Host Isolated\n");
-+			break;
-+		case ICMP_NET_ANO:
-+			printf("Destination Net Prohibited\n");
-+			break;
-+		case ICMP_HOST_ANO:
-+			printf("Destination Host Prohibited\n");
-+			break;
-+		case ICMP_NET_UNR_TOS:
-+			printf("Destination Net Unreachable for Type of Service\n");
-+			break;
-+		case ICMP_HOST_UNR_TOS:
-+			printf("Destination Host Unreachable for Type of Service\n");
-+			break;
- 		case ICMP_PKT_FILTERED:
- 			printf("Packet filtered\n");
- 			break;
-+		case ICMP_PREC_VIOLATION:
-+			printf("Precedence Violation\n");
-+			break;
-+		case ICMP_PREC_CUTOFF:
-+			printf("Precedence Cutoff\n");
-+			break;
- 		default:
- 			printf("Dest Unreachable, Bad Code: %d\n", code);
- 			break;
-@@ -1032,7 +1059,7 @@
- 				i = j;
- 			i -= IPOPT_MINOFF;
- 			if (i <= 0)
--				continue;
-+				break;
- 			if (i == old_rrlen
- 			    && !strncmp((char *)cp, old_rr, i)
- 			    && !(options & F_FLOOD)) {
-@@ -1069,7 +1096,7 @@
- 				i = j;
- 			i -= 5;
- 			if (i <= 0)
--				continue;
-+				break;
- 			flags = *++cp;
- 			printf("\nTS: ");
- 			cp++;
-diff -Naur iputils-s20100418.orig/ping_common.c iputils-s20100418/ping_common.c
---- iputils-s20100418.orig/ping_common.c	2010-04-18 00:45:45.000000000 -0400
-+++ iputils-s20100418/ping_common.c	2010-08-04 19:52:08.433579291 -0400
-@@ -872,7 +872,8 @@
- 		printf("%spipe %d", comma, pipesize);
- 		comma = ", ";
- 	}
--	if (ntransmitted > 1 && (!interval || (options&(F_FLOOD|F_ADAPTIVE)))) {
-+	if (ntransmitted > 1 && nreceived &&
-+		(!interval || (options&(F_FLOOD|F_ADAPTIVE)))) {
- 		int ipg = (1000000*(long long)tv.tv_sec+tv.tv_usec)/(ntransmitted-1);
- 		printf("%sipg/ewma %d.%03d/%d.%03d ms",
- 		       comma, ipg/1000, ipg%1000, rtt/8000, (rtt/8)%1000);
-diff -Naur iputils-s20100418.orig/tracepath.c iputils-s20100418/tracepath.c
---- iputils-s20100418.orig/tracepath.c	2010-04-18 00:45:45.000000000 -0400
-+++ iputils-s20100418/tracepath.c	2010-08-04 19:52:08.438080809 -0400
-@@ -338,9 +338,9 @@
- 		base_port = atoi(p+1);
- 	} else
- 		base_port = 44444;
--	he = gethostbyname(argv[0]);
-+	he = gethostbyname2(argv[0], AF_INET);
- 	if (he == NULL) {
--		herror("gethostbyname");
-+		herror("gethostbyname2");
- 		exit(1);
- 	}
- 	memcpy(&target.sin_addr, he->h_addr, 4);
Index: patches/iputils-s20101006-doc-1.patch
===================================================================
--- patches/iputils-s20101006-doc-1.patch	(revision ecc1136c03ab82d05060a4dfccf51599109cc687)
+++ patches/iputils-s20101006-doc-1.patch	(revision ecc1136c03ab82d05060a4dfccf51599109cc687)
@@ -0,0 +1,6870 @@
+Submitted By: Joe Ciccone <jciccone@gmail.com>
+Date: 2011-01-08
+Initial Package Version: s20100418
+Upstream Status: Unknown
+Origin: Unknown
+Description: Contains Pregenerated Documentation
+
+
+diff -Naur iputils-s20101006.orig/doc/arping.8 iputils-s20101006/doc/arping.8
+--- iputils-s20101006.orig/doc/arping.8	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/arping.8	2011-01-08 20:09:50.402928174 -0500
+@@ -0,0 +1,110 @@
++.\" This manpage has been automatically generated by docbook2man 
++.\" from a DocBook document.  This tool can be found at:
++.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
++.\" Please send any bug reports, improvements, comments, patches, 
++.\" etc. to Steve Cheng <steve@ggi-project.org>.
++.TH "ARPING" "8" "08 January 2011" "iputils-101006" "System Manager's Manual: iputils"
++.SH NAME
++arping \- send ARP REQUEST to a neighbour host
++.SH SYNOPSIS
++
++\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
++
++.SH "DESCRIPTION"
++.PP
++Ping \fIdestination\fR on device \fIinterface\fR by ARP packets,
++using source address \fIsource\fR.
++.SH "OPTIONS"
++.TP
++\fB-A\fR
++The same as \fB-U\fR, but ARP REPLY packets used instead
++of ARP REQUEST.
++.TP
++\fB-b\fR
++Send only MAC level broadcasts. Normally \fBarping\fR starts
++from sending broadcast, and switch to unicast after reply received.
++.TP
++\fB-c \fIcount\fB\fR
++Stop after sending \fIcount\fR ARP REQUEST
++packets. With 
++\fIdeadline\fR
++option, \fBarping\fR waits for
++\fIcount\fR ARP REPLY packets, until the timeout expires.
++.TP
++\fB-D\fR
++Duplicate address detection mode (DAD). See 
++RFC2131, 4.4.1.
++Returns 0, if DAD succeeded i.e. no replies are received
++.TP
++\fB-f\fR
++Finish after the first reply confirming that target is alive.
++.TP
++\fB-I \fIinterface\fB\fR
++Name of network device where to send ARP REQUEST packets. This option
++is required.
++.TP
++\fB-h\fR
++Print help page and exit.
++.TP
++\fB-q\fR
++Quiet output. Nothing is displayed.
++.TP
++\fB-s \fIsource\fB\fR
++IP source address to use in ARP packets.
++If this option is absent, source address is:
++.RS
++.TP 0.2i
++\(bu
++In DAD mode (with option \fB-D\fR) set to 0.0.0.0.
++.TP 0.2i
++\(bu
++In Unsolicited ARP mode (with options \fB-U\fR or \fB-A\fR)
++set to \fIdestination\fR.
++.TP 0.2i
++\(bu
++Otherwise, it is calculated from routing tables.
++.RE
++.TP
++\fB-U\fR
++Unsolicited ARP mode to update neighbours' ARP caches.
++No replies are expected.
++.TP
++\fB-V\fR
++Print version of the program and exit.
++.TP
++\fB-w \fIdeadline\fB\fR
++Specify a timeout, in seconds, before
++\fBarping\fR
++exits regardless of how many
++packets have been sent or received. In this case
++\fBarping\fR
++does not stop after
++\fIcount\fR
++packet are sent, it waits either for
++\fIdeadline\fR
++expire or until
++\fIcount\fR
++probes are answered.
++.SH "SEE ALSO"
++.PP
++\fBping\fR(8),
++\fBclockdiff\fR(8),
++\fBtracepath\fR(8).
++.SH "AUTHOR"
++.PP
++\fBarping\fR was written by
++Alexey Kuznetsov
++<kuznet@ms2.inr.ac.ru>.
++It is now maintained by
++YOSHIFUJI Hideaki
++<yoshfuji@skbuff.net>.
++.SH "SECURITY"
++.PP
++\fBarping\fR requires CAP_NET_RAWIO capability
++to be executed. It is not recommended to be used as set-uid root,
++because it allows user to modify ARP caches of neighbour hosts.
++.SH "AVAILABILITY"
++.PP
++\fBarping\fR is part of \fIiputils\fR package
++and the latest versions are  available in source form at
++http://www.skbuff.net/iputils/iputils-current.tar.bz2.
+diff -Naur iputils-s20101006.orig/doc/clockdiff.8 iputils-s20101006/doc/clockdiff.8
+--- iputils-s20101006.orig/doc/clockdiff.8	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/clockdiff.8	2011-01-08 20:09:50.611280874 -0500
+@@ -0,0 +1,81 @@
++.\" This manpage has been automatically generated by docbook2man 
++.\" from a DocBook document.  This tool can be found at:
++.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
++.\" Please send any bug reports, improvements, comments, patches, 
++.\" etc. to Steve Cheng <steve@ggi-project.org>.
++.TH "CLOCKDIFF" "8" "08 January 2011" "iputils-101006" "System Manager's Manual: iputils"
++.SH NAME
++clockdiff \- measure clock difference between hosts
++.SH SYNOPSIS
++
++\fBclockdiff\fR [\fB-o\fR] [\fB-o1\fR] \fB\fIdestination\fB\fR
++
++.SH "DESCRIPTION"
++.PP
++\fBclockdiff\fR Measures clock difference between us and
++\fIdestination\fR with 1 msec resolution using ICMP TIMESTAMP
++[2]
++packets or, optionally, IP TIMESTAMP option
++[3]
++option added to ICMP ECHO.
++[1]
++.SH "OPTIONS"
++.TP
++\fB-o\fR
++Use IP TIMESTAMP with ICMP ECHO instead of ICMP TIMESTAMP
++messages. It is useful with some destinations, which do not support
++ICMP TIMESTAMP (f.e. Solaris <2.4).
++.TP
++\fB-o1\fR
++Slightly different form of \fB-o\fR, namely it uses three-term
++IP TIMESTAMP with prespecified hop addresses instead of four term one.
++What flavor works better depends on target host. Particularly,
++\fB-o\fR is better for Linux.
++.SH "WARNINGS"
++.TP 0.2i
++\(bu
++Some nodes (Cisco) use non-standard timestamps, which is allowed
++by RFC, but makes timestamps mostly useless.
++.TP 0.2i
++\(bu
++Some nodes generate messed timestamps (Solaris>2.4), when
++run \fBxntpd\fR. Seems, its IP stack uses a corrupted clock source,
++which is synchronized to time-of-day clock periodically and jumps
++randomly making timestamps mostly useless. Good news is that you can
++use NTP in this case, which is even better.
++.TP 0.2i
++\(bu
++\fBclockdiff\fR shows difference in time modulo 24 days.
++.SH "SEE ALSO"
++.PP
++\fBping\fR(8),
++\fBarping\fR(8),
++\fBtracepath\fR(8).
++.SH "REFERENCES"
++.PP
++[1] ICMP ECHO,
++RFC0792, page 14.
++.PP
++[2] ICMP TIMESTAMP,
++RFC0792, page 16.
++.PP
++[3] IP TIMESTAMP option,
++RFC0791, 3.1, page 16.
++.SH "AUTHOR"
++.PP
++\fBclockdiff\fR was compiled by
++Alexey Kuznetsov
++<kuznet@ms2.inr.ac.ru>. It was based on code borrowed
++from BSD \fBtimed\fR daemon.
++It is now maintained by
++YOSHIFUJI Hideaki
++<yoshfuji@skbuff.net>.
++.SH "SECURITY"
++.PP
++\fBclockdiff\fR requires CAP_NET_RAWIO capability
++to be executed. It is safe to be used as set-uid root.
++.SH "AVAILABILITY"
++.PP
++\fBclockdiff\fR is part of \fIiputils\fR package
++and the latest versions are  available in source form at
++http://www.skbuff.net/iputils/iputils-current.tar.bz2.
+diff -Naur iputils-s20101006.orig/doc/index.html iputils-s20101006/doc/index.html
+--- iputils-s20101006.orig/doc/index.html	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/index.html	2011-01-08 20:09:49.631531431 -0500
+@@ -0,0 +1,170 @@
++<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
++<HTML
++><HEAD
++><TITLE
++>System Manager's Manual: iputils</TITLE
++><META
++NAME="GENERATOR"
++CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
++REL="NEXT"
++TITLE="ping"
++HREF="r3.html"></HEAD
++><BODY
++CLASS="REFERENCE"
++BGCOLOR="#FFFFFF"
++TEXT="#000000"
++LINK="#0000FF"
++VLINK="#840084"
++ALINK="#0000FF"
++><DIV
++CLASS="NAVHEADER"
++><TABLE
++SUMMARY="Header navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TD
++WIDTH="10%"
++ALIGN="left"
++VALIGN="bottom"
++>&nbsp;</TD
++><TD
++WIDTH="80%"
++ALIGN="center"
++VALIGN="bottom"
++></TD
++><TD
++WIDTH="10%"
++ALIGN="right"
++VALIGN="bottom"
++><A
++HREF="r3.html"
++ACCESSKEY="N"
++>Next</A
++></TD
++></TR
++></TABLE
++><HR
++ALIGN="LEFT"
++WIDTH="100%"></DIV
++><DIV
++CLASS="REFERENCE"
++><A
++NAME="INDEX"
++></A
++><DIV
++CLASS="TITLEPAGE"
++><H1
++CLASS="TITLE"
++>I. System Manager's Manual: iputils</H1
++><DIV
++CLASS="TOC"
++><DL
++><DT
++><B
++>Table of Contents</B
++></DT
++><DT
++><A
++HREF="r3.html"
++>ping</A
++>&nbsp;--&nbsp;send ICMP ECHO_REQUEST to network hosts</DT
++><DT
++><A
++HREF="r437.html"
++>arping</A
++>&nbsp;--&nbsp;send ARP REQUEST to a neighbour host</DT
++><DT
++><A
++HREF="r596.html"
++>clockdiff</A
++>&nbsp;--&nbsp;measure clock difference between hosts</DT
++><DT
++><A
++HREF="r691.html"
++>rarpd</A
++>&nbsp;--&nbsp;answer RARP REQUESTs</DT
++><DT
++><A
++HREF="r790.html"
++>tracepath</A
++>&nbsp;--&nbsp;traces path to a network host discovering MTU along this path</DT
++><DT
++><A
++HREF="r884.html"
++>traceroute6</A
++>&nbsp;--&nbsp;traces path to a network host</DT
++><DT
++><A
++HREF="r949.html"
++>tftpd</A
++>&nbsp;--&nbsp;Trivial File Transfer Protocol server</DT
++><DT
++><A
++HREF="r1022.html"
++>rdisc</A
++>&nbsp;--&nbsp;network router discovery daemon</DT
++><DT
++><A
++HREF="r1144.html"
++>pg3</A
++>&nbsp;--&nbsp;send stream of UDP packets</DT
++></DL
++></DIV
++></DIV
++></DIV
++><DIV
++CLASS="NAVFOOTER"
++><HR
++ALIGN="LEFT"
++WIDTH="100%"><TABLE
++SUMMARY="Footer navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++>&nbsp;</TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++>&nbsp;</TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++><A
++HREF="r3.html"
++ACCESSKEY="N"
++>Next</A
++></TD
++></TR
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++>&nbsp;</TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++>&nbsp;</TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++>ping</TD
++></TR
++></TABLE
++></DIV
++></BODY
++></HTML
++>
+\ No newline at end of file
+diff -Naur iputils-s20101006.orig/doc/iputils.html iputils-s20101006/doc/iputils.html
+--- iputils-s20101006.orig/doc/iputils.html	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/iputils.html	2011-01-08 20:09:50.282802377 -0500
+@@ -0,0 +1,491 @@
++<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
++<HTML
++><HEAD
++><TITLE
++>iputils: documentation directory</TITLE
++><META
++NAME="GENERATOR"
++CONTENT="Modular DocBook HTML Stylesheet Version 1.79"></HEAD
++><BODY
++CLASS="ARTICLE"
++BGCOLOR="#FFFFFF"
++TEXT="#000000"
++LINK="#0000FF"
++VLINK="#840084"
++ALINK="#0000FF"
++><DIV
++CLASS="ARTICLE"
++><DIV
++CLASS="TITLEPAGE"
++><H1
++CLASS="TITLE"
++><A
++NAME="AEN2"
++>iputils: documentation directory</A
++></H1
++><HR></DIV
++><DIV
++CLASS="TOC"
++><DL
++><DT
++><B
++>Table of Contents</B
++></DT
++><DT
++>1. <A
++HREF="#AEN4"
++>Index</A
++></DT
++><DT
++>2. <A
++HREF="#AEN34"
++>Historical notes</A
++></DT
++><DT
++>3. <A
++HREF="#AEN89"
++>Installation notes</A
++></DT
++><DT
++>4. <A
++HREF="#AEN109"
++>Availability</A
++></DT
++><DT
++>5. <A
++HREF="#AEN114"
++>Copying</A
++></DT
++></DL
++></DIV
++><DIV
++CLASS="SECT1"
++><H2
++CLASS="SECT1"
++><A
++NAME="AEN4"
++>1. Index</A
++></H2
++><P
++></P
++><UL
++><LI
++><P
++>  <A
++HREF="ping.html"
++TARGET="_top"
++>ping, ping6</A
++>.
++ </P
++></LI
++><LI
++><P
++>  <A
++HREF="arping.html"
++TARGET="_top"
++>arping</A
++>.
++ </P
++></LI
++><LI
++><P
++>  <A
++HREF="clockdiff.html"
++TARGET="_top"
++>clockdiff</A
++>.
++ </P
++></LI
++><LI
++><P
++>  <A
++HREF="rarpd.html"
++TARGET="_top"
++>rarpd</A
++>.
++ </P
++></LI
++><LI
++><P
++>  <A
++HREF="tracepath.html"
++TARGET="_top"
++>tracepath, tracepath6</A
++>.
++ </P
++></LI
++><LI
++><P
++>  <A
++HREF="traceroute6.html"
++TARGET="_top"
++>traceroute6</A
++>.
++ </P
++></LI
++><LI
++><P
++>  <A
++HREF="rdisc.html"
++TARGET="_top"
++>rdisc</A
++>.
++ </P
++></LI
++><LI
++><P
++>  <A
++HREF="tftpd.html"
++TARGET="_top"
++>tftpd</A
++>.
++ </P
++></LI
++><LI
++><P
++>  <A
++HREF="pg3.html"
++TARGET="_top"
++>pg3, ipg, pgset</A
++>.
++ </P
++></LI
++></UL
++></DIV
++><DIV
++CLASS="SECT1"
++><HR><H2
++CLASS="SECT1"
++><A
++NAME="AEN34"
++>2. Historical notes</A
++></H2
++><P
++>This package appeared as a desperate attempt to bring some life
++to state of basic networking applets: <B
++CLASS="COMMAND"
++>ping</B
++>, <B
++CLASS="COMMAND"
++>traceroute</B
++>
++etc. Though it was known that port of BSD <B
++CLASS="COMMAND"
++>ping</B
++> to Linux
++was basically broken, neither maintainers of well known (and superb)
++Linux net-tools package nor maintainers of Linux distributions
++worried about fixing well known bugs, which were reported in linux-kernel
++and linux-net mail lists for ages, were identified and nevertheless
++not repaired. So, one day 1001th resuming of the subject happened
++to be the last straw to break camel's back, I just parsed my hard disks
++and collected a set of utilities, which shared the following properties:</P
++><P
++></P
++><UL
++><LI
++><P
++>Small
++ </P
++></LI
++><LI
++><P
++>Useful despite of this
++ </P
++></LI
++><LI
++><P
++>I never seen it was made right
++ </P
++></LI
++><LI
++><P
++>Not quite trivial
++ </P
++></LI
++><LI
++><P
++>Demonstrating some important feature of Linux 
++ </P
++></LI
++><LI
++><P
++>The last but not the least, I use it more or less regularly
++ </P
++></LI
++></UL
++><P
++>This utility set was not supposed to be a reference set or something like
++that. Most of them were cloned from some originals:
++<DIV
++CLASS="INFORMALTABLE"
++><P
++></P
++><A
++NAME="AEN54"
++></A
++><TABLE
++BORDER="1"
++CLASS="CALSTABLE"
++><COL><COL><TBODY
++><TR
++><TD
++>ping</TD
++><TD
++>cloned of an ancient NetTools-B-xx</TD
++></TR
++><TR
++><TD
++>ping6</TD
++><TD
++>cloned of a very old Pedro's utility set</TD
++></TR
++><TR
++><TD
++>traceroute6</TD
++><TD
++>cloned of NRL Sep 96 distribution</TD
++></TR
++><TR
++><TD
++>rdisc</TD
++><TD
++>cloned of SUN in.rdisc</TD
++></TR
++><TR
++><TD
++>clockdiff</TD
++><TD
++>broken out of some BSD timed</TD
++></TR
++><TR
++><TD
++>tftpd</TD
++><TD
++>it is clone of some ancient NetKit package</TD
++></TR
++></TBODY
++></TABLE
++><P
++></P
++></DIV
++></P
++><P
++>Also I added some utilities written from scratch, namely
++<B
++CLASS="COMMAND"
++>tracepath</B
++>, <B
++CLASS="COMMAND"
++>arping</B
++> and later <B
++CLASS="COMMAND"
++>rarpd</B
++>
++(the last one does not satisfy all the criteria, I used it two or three
++times).</P
++><P
++>Hesitated a bit I overcame temptation to add <B
++CLASS="COMMAND"
++>traceroute</B
++>.
++The variant released by LBNL to that time was mostly sane and bugs
++in it were mostly not specific to Linux, but main reason was that
++the latest version of LBNL <B
++CLASS="COMMAND"
++>traceroute</B
++> was not 
++<SPAN
++CLASS="emphasis"
++><I
++CLASS="EMPHASIS"
++>small</I
++></SPAN
++>, it consisted of several files,
++used a wicked (and failing with Linux :-)) autoconfiguration etc.
++So, instead I assembled to iputils a simplistic <B
++CLASS="COMMAND"
++>tracepath</B
++> utility
++and IPv6 version of traceroute, and published my 
++<A
++HREF="ftp://ftp.inr.ac.ru/ip-routing/lbl-tools"
++TARGET="_top"
++> patches</A
++>.
++to LBNL <B
++CLASS="COMMAND"
++>traceroute</B
++> separately.<A
++NAME="AEN86"
++HREF="#FTN.AEN86"
++><SPAN
++CLASS="footnote"
++>[1]</SPAN
++></A
++></P
++></DIV
++><DIV
++CLASS="SECT1"
++><HR><H2
++CLASS="SECT1"
++><A
++NAME="AEN89"
++>3. Installation notes</A
++></H2
++><P
++><KBD
++CLASS="USERINPUT"
++>make</KBD
++> to compile utilities. <KBD
++CLASS="USERINPUT"
++>make html</KBD
++> to prepare
++html documentation, <KBD
++CLASS="USERINPUT"
++>make man</KBD
++> if you prefer man pages.
++Nothing fancy, provided you have DocBook package installed.</P
++><P
++><KBD
++CLASS="USERINPUT"
++>make install</KBD
++> installs <SPAN
++CLASS="emphasis"
++><I
++CLASS="EMPHASIS"
++>only</I
++></SPAN
++> HTML documentation
++to <TT
++CLASS="FILENAME"
++>/usr/doc/iputils</TT
++>. It even does not try
++to install binaries and man pages. If you read historical
++notes above, the reason should be evident. Most of utilities
++intersect with utilities distributed in another packages, and
++making such target rewriting existing installation would be a crime
++from my side. The decision what variant of <B
++CLASS="COMMAND"
++>ping</B
++> is preferred,
++how to resolve the conflicts etc. is left to you or to person who
++assembled an rpm. I vote for variant from <B
++CLASS="COMMAND"
++>iputils</B
++> of course.</P
++><P
++>Anyway, select utilities which you like and install them to the places
++which you prefer together with their man pages.</P
++><P
++>It is possible that compilation will fail, if you use some
++funny Linux distribution mangling header files in some unexpected ways
++(expected ones are the ways of redhat of course :-)).
++I validate iputils against <A
++HREF="http://www.asplinux.ru"
++TARGET="_top"
++>asplinux</A
++>
++distribution, which is inevitably followed by validity with respect
++to <A
++HREF="http://www.redhat.com"
++TARGET="_top"
++>redhat</A
++>.
++If your distribution is one of widely known ones, suse or debian,
++it also will compile provided snapshot is elder than month or so and
++someone reported all the problems, if they took place at all.</P
++><P
++><SPAN
++CLASS="emphasis"
++><I
++CLASS="EMPHASIS"
++>Anyway, please, do not abuse me complaining about some compilation problems
++in any distribution different of asplinux or redhat.
++If you have a fix, please, send it to
++<A
++HREF="mailto:kuznet@ms2.inr.ac.ru"
++TARGET="_top"
++>me</A
++>,
++I will check that it does not break distributions mentioned above
++and apply it. But I am not going to undertake any investigations,
++bare reports are deemed to be routed to <TT
++CLASS="FILENAME"
++>/dev/null</TT
++>.</I
++></SPAN
++></P
++></DIV
++><DIV
++CLASS="SECT1"
++><HR><H2
++CLASS="SECT1"
++><A
++NAME="AEN109"
++>4. Availability</A
++></H2
++><P
++>The collection of documents is part of <TT
++CLASS="FILENAME"
++>iputils</TT
++> package
++and the latest versions are  available in source form at
++<A
++HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
++TARGET="_top"
++>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
++>.</P
++></DIV
++><DIV
++CLASS="SECT1"
++><HR><H2
++CLASS="SECT1"
++><A
++NAME="AEN114"
++>5. Copying</A
++></H2
++><P
++>Different files are copyrighted by different persons and organizations
++and distributed under different licenses. For details look into corresponding
++source files.</P
++></DIV
++></DIV
++><H3
++CLASS="FOOTNOTES"
++>Notes</H3
++><TABLE
++BORDER="0"
++CLASS="FOOTNOTES"
++WIDTH="100%"
++><TR
++><TD
++ALIGN="LEFT"
++VALIGN="TOP"
++WIDTH="5%"
++><A
++NAME="FTN.AEN86"
++HREF="#AEN86"
++><SPAN
++CLASS="footnote"
++>[1]</SPAN
++></A
++></TD
++><TD
++ALIGN="LEFT"
++VALIGN="TOP"
++WIDTH="95%"
++><P
++>This was mistake.
++Due to this <B
++CLASS="COMMAND"
++>traceroute</B
++> was in a sad state until recently.
++Good news, redhat-7.2 seems to add these patches to their traceroute
++rpm eventually. So, I think I will refrain of suicide for awhile.</P
++></TD
++></TR
++></TABLE
++></BODY
++></HTML
++>
+\ No newline at end of file
+diff -Naur iputils-s20101006.orig/doc/pg3.8 iputils-s20101006/doc/pg3.8
+--- iputils-s20101006.orig/doc/pg3.8	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/pg3.8	2011-01-08 20:09:50.890656148 -0500
+@@ -0,0 +1,86 @@
++.\" This manpage has been automatically generated by docbook2man 
++.\" from a DocBook document.  This tool can be found at:
++.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
++.\" Please send any bug reports, improvements, comments, patches, 
++.\" etc. to Steve Cheng <steve@ggi-project.org>.
++.TH "PG3" "8" "08 January 2011" "iputils-101006" "System Manager's Manual: iputils"
++.SH NAME
++pg3, ipg, pgset \- send stream of UDP packets
++.SH SYNOPSIS
++
++\fBsource ipg\fR
++
++
++\fBpg\fR
++
++
++\fBpgset\fR \fB\fICOMMAND\fB\fR
++
++.SH "DESCRIPTION"
++.PP
++\fBipg\fR is not a program, it is script which should be sourced
++to \fBbash\fR. When sourced it loads module \fIpg3\fR and
++exports a few of functions accessible from parent shell. These macros
++are \fBpg\fR to start packet injection and to get the results of run;
++and \fBpgset\fR to setup packet generator.
++.PP
++\fBpgset\fR can send the following commands to module \fIpg3\fR:
++.SH "COMMAND"
++.TP
++\fBodev \fIDEVICE\fB\fR
++Name of Ethernet device to test. See
++warning below.
++.TP
++\fBpkt_size \fIBYTES\fB\fR
++Size of packet to generate. The size includes all the headers: UDP, IP,
++MAC, but does not account for overhead internal to medium, i.e. FCS
++and various paddings.
++.TP
++\fBfrags \fINUMBER\fB\fR
++Each packet will contain \fINUMBER\fR of fragments.
++Maximal amount for linux-2.4 is 6. Far not all the devices support
++fragmented buffers.
++.TP
++\fBcount \fINUMBER\fB\fR
++Send stream of \fINUMBER\fR of packets and stop after this.
++.TP
++\fBipg \fITIME\fB\fR
++Introduce artificial delay between packets of \fITIME\fR
++microseconds.
++.TP
++\fBdst \fIIP_ADDRESS\fB\fR
++Select IP destination where the stream is sent to.
++Beware, never set this address at random. \fBpg3\fR is not a toy,
++it creates really tough stream. Default value is 0.0.0.0.
++.TP
++\fBdst \fIMAC_ADDRESS\fB\fR
++Select MAC destination where the stream is sent to.
++Default value is 00:00:00:00:00:00 in hope that this will not be received
++by any node on LAN.
++.TP
++\fBstop\fR
++Abort packet injection.
++.SH "WARNING"
++.PP
++When output device is set to some random device different
++of hardware Ethernet device, \fBpg3\fR will crash kernel.
++.PP
++Do not use it on VLAN, ethertap, VTUN and other devices,
++which emulate Ethernet not being real Ethernet in fact.
++.SH "AUTHOR"
++.PP
++\fBpg3\fR was written by Robert Olsson <robert.olsson@its.uu.se>.
++.SH "SECURITY"
++.PP
++This can be used only by superuser.
++.PP
++This tool creates floods of packets which is unlikely to be handled
++even by high-end machines. For example, it saturates gigabit link with
++60 byte packets when used with Intel's e1000. In face of such stream
++switches, routers and end hosts may deadlock, crash, explode.
++Use only in test lab environment.
++.SH "AVAILABILITY"
++.PP
++\fBpg3\fR is part of \fIiputils\fR package
++and the latest versions are  available in source form at
++http://www.skbuff.net/iputils/iputils-current.tar.bz2.
+diff -Naur iputils-s20101006.orig/doc/ping.8 iputils-s20101006/doc/ping.8
+--- iputils-s20101006.orig/doc/ping.8	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/ping.8	2011-01-08 20:09:50.986782167 -0500
+@@ -0,0 +1,408 @@
++.\" This manpage has been automatically generated by docbook2man 
++.\" from a DocBook document.  This tool can be found at:
++.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
++.\" Please send any bug reports, improvements, comments, patches, 
++.\" etc. to Steve Cheng <steve@ggi-project.org>.
++.TH "PING" "8" "08 January 2011" "iputils-101006" "System Manager's Manual: iputils"
++.SH NAME
++ping, ping6 \- send ICMP ECHO_REQUEST to network hosts
++.SH SYNOPSIS
++
++\fBping\fR [\fB-LRUbdfnqrvVaAB\fR] [\fB-c \fIcount\fB\fR] [\fB-m \fImark\fB\fR] [\fB-i \fIinterval\fB\fR] [\fB-l \fIpreload\fB\fR] [\fB-p \fIpattern\fB\fR] [\fB-s \fIpacketsize\fB\fR] [\fB-t \fIttl\fB\fR] [\fB-w \fIdeadline\fB\fR] [\fB-F \fIflowlabel\fB\fR] [\fB-I \fIinterface\fB\fR] [\fB-M \fIhint\fB\fR] [\fB-N \fInioption\fB\fR] [\fB-Q \fItos\fB\fR] [\fB-S \fIsndbuf\fB\fR] [\fB-T \fItimestamp option\fB\fR] [\fB-W \fItimeout\fB\fR] [\fB\fIhop\fB\fR\fI ...\fR] \fB\fIdestination\fB\fR
++
++.SH "DESCRIPTION"
++.PP
++\fBping\fR uses the ICMP protocol's mandatory ECHO_REQUEST
++datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway.
++ECHO_REQUEST datagrams (``pings'') have an IP and ICMP
++header, followed by a struct timeval and then an arbitrary
++number of ``pad'' bytes used to fill out the packet.
++.PP
++\fBping6\fR can also send Node Information Queries (RFC4620).
++.SH "OPTIONS"
++.TP
++\fB-a\fR
++Audible ping.
++.TP
++\fB-A\fR
++Adaptive ping. Interpacket interval adapts to round-trip time, so that
++effectively not more than one (or more, if preload is set) unanswered probes
++present in the network. Minimal interval is 200msec for not super-user.
++On networks with low rtt this mode is essentially equivalent to flood mode.  
++.TP
++\fB-b\fR
++Allow pinging a broadcast address.
++.TP
++\fB-B\fR
++Do not allow \fBping\fR to change source address of probes.
++The address is bound to one selected when \fBping\fR starts.
++.TP
++\fB-m \fImark\fB\fR
++use \fImark\fR to tag the packets going out. This is useful
++for variety of reasons within the kernel such as using policy
++routing to select specific outbound processing.
++.TP
++\fB-c \fIcount\fB\fR
++Stop after sending \fIcount\fR ECHO_REQUEST
++packets. With 
++\fIdeadline\fR
++option, \fBping\fR waits for
++\fIcount\fR ECHO_REPLY packets, until the timeout expires.
++.TP
++\fB-d\fR
++Set the SO_DEBUG option on the socket being used.
++Essentially, this socket option is not used by Linux kernel. 
++.TP
++\fB-F \fIflow label\fB\fR
++Allocate and set 20 bit flow label on echo request packets.
++(Only \fBping6\fR). If value is zero, kernel allocates random flow label.
++.TP
++\fB-f\fR
++Flood ping. For every ECHO_REQUEST sent a period ``.'' is printed,
++while for ever ECHO_REPLY received a backspace is printed.
++This provides a rapid display of how many packets are being dropped.
++If interval is not given, it sets interval to zero and
++outputs packets as fast as they come back or one hundred times per second,
++whichever is more.
++Only the super-user may use this option with zero interval.
++.TP
++\fB-i \fIinterval\fB\fR
++Wait \fIinterval\fR seconds between sending each packet.
++The default is to wait for one second between each packet normally,
++or not to wait in flood mode. Only super-user may set interval
++to values less 0.2 seconds.
++.TP
++\fB-I \fIinterface address\fB\fR
++Set source address to specified interface address. Argument
++may be numeric IP address or name of device. When pinging IPv6
++link-local address this option is required.
++.TP
++\fB-l \fIpreload\fB\fR
++If \fIpreload\fR is specified,
++\fBping\fR sends that many packets not waiting for reply.
++Only the super-user may select preload more than 3.
++.TP
++\fB-L\fR
++Suppress loopback of multicast packets.  This flag only applies if the ping
++destination is a multicast address.
++.TP
++\fB-N \fInioption\fB\fR
++Send ICMPv6 Node Information Queries (RFC4620), instead of Echo Request.
++.RS
++.TP
++\fBname\fR
++Queries for Node Names.
++.RE
++.RS
++.TP
++\fBipv6\fR
++Queries for IPv6 Addresses. There are several IPv6 specific flags.
++.RS
++.TP
++\fBipv6-global\fR
++Request IPv6 global-scope addresses.
++.RE
++.RS
++.TP
++\fBipv6-sitelocal\fR
++Request IPv6 site-local addresses.
++.RE
++.RS
++.TP
++\fBipv6-linklocal\fR
++Request IPv6 link-local addresses.
++.RE
++.RS
++.TP
++\fBipv6-all\fR
++Request IPv6 addresses on other interfaces.
++.RE
++.RE
++.RS
++.TP
++\fBipv4\fR
++Queries for IPv4 Addresses.  There is one IPv4 specific flag.
++.RS
++.TP
++\fBipv4-all\fR
++Request IPv4 addresses on other interfaces.
++.RE
++.RE
++.RS
++.TP
++\fBsubject-ipv6=\fIipv6addr\fB\fR
++IPv6 subject address.
++.RE
++.RS
++.TP
++\fBsubject-ipv4=\fIipv4addr\fB\fR
++IPv4 subject address.
++.RE
++.RS
++.TP
++\fBsubject-name=\fInodename\fB\fR
++Subject name.  If it contains more than one dot,
++fully-qualified domain name is assumed.
++.RE
++.RS
++.TP
++\fBsubject-fqdn=\fInodename\fB\fR
++Subject name.  Fully-qualified domain name is
++always assumed.
++.RE
++.TP
++\fB-n\fR
++Numeric output only.
++No attempt will be made to lookup symbolic names for host addresses.
++.TP
++\fB-p \fIpattern\fB\fR
++You may specify up to 16 ``pad'' bytes to fill out the packet you send.
++This is useful for diagnosing data-dependent problems in a network.
++For example, \fB-p ff\fR will cause the sent packet
++to be filled with all ones.
++.TP
++\fB-D\fR
++Print timestamp (unix time + microseconds as in gettimeofday) before
++each line.
++.TP
++\fB-Q \fItos\fB\fR
++Set Quality of Service -related bits in ICMP datagrams.  
++\fItos\fR can be either decimal or hex number.
++Traditionally (RFC1349), these have been interpreted as: 0 for reserved
++(currently being redefined as congestion control), 1-4 for Type of Service
++and 5-7 for Precedence.
++Possible settings for Type of Service are: minimal cost: 0x02, 
++reliability: 0x04, throughput: 0x08, low delay: 0x10.  Multiple TOS bits
++should not be set simultaneously.  Possible settings for
++special Precedence range from priority (0x20) to net control (0xe0).  You
++must be root (CAP_NET_ADMIN capability) to use Critical or
++higher precedence value.  You cannot set
++bit 0x01 (reserved) unless ECN has been enabled in the kernel.
++In RFC2474, these fields has been redefined as 8-bit Differentiated
++Services (DS), consisting of: bits 0-1 of separate data (ECN will be used,
++here), and bits 2-7 of Differentiated Services Codepoint (DSCP).
++.TP
++\fB-q\fR
++Quiet output.
++Nothing is displayed except the summary lines at startup time and
++when finished.
++.TP
++\fB-R\fR
++Record route.
++Includes the RECORD_ROUTE option in the ECHO_REQUEST
++packet and displays the route buffer on returned packets.
++Note that the IP header is only large enough for nine such routes.
++Many hosts ignore or discard this option.
++.TP
++\fB-r\fR
++Bypass the normal routing tables and send directly to a host on an attached
++interface.
++If the host is not on a directly-attached network, an error is returned.
++This option can be used to ping a local host through an interface
++that has no route through it provided the option \fB-I\fR is also
++used.
++.TP
++\fB-s \fIpacketsize\fB\fR
++Specifies the number of data bytes to be sent.  
++The default is 56, which translates into 64 ICMP
++data bytes when combined with the 8 bytes of ICMP header data.
++.TP
++\fB-S \fIsndbuf\fB\fR
++Set socket sndbuf. If not specified, it is selected to buffer
++not more than one packet.
++.TP
++\fB-t \fIttl\fB\fR
++Set the IP Time to Live.
++.TP
++\fB-T \fItimestamp option\fB\fR
++Set special IP timestamp options.
++\fItimestamp option\fR may be either 
++\fItsonly\fR (only timestamps), 
++\fItsandaddr\fR (timestamps and addresses) or 
++\fItsprespec host1 [host2 [host3 [host4]]]\fR
++(timestamp prespecified hops).
++.TP
++\fB-M \fIhint\fB\fR
++Select Path MTU Discovery strategy.
++\fIhint\fR may be either \fIdo\fR
++(prohibit fragmentation, even local one), 
++\fIwant\fR (do PMTU discovery, fragment locally when packet size
++is large), or \fIdont\fR (do not set DF flag).
++.TP
++\fB-U\fR
++Print full user-to-user latency (the old behaviour). Normally
++\fBping\fR
++prints network round trip time, which can be different
++f.e. due to DNS failures. 
++.TP
++\fB-v\fR
++Verbose output.
++.TP
++\fB-V\fR
++Show version and exit.
++.TP
++\fB-w \fIdeadline\fB\fR
++Specify a timeout, in seconds, before
++\fBping\fR
++exits regardless of how many
++packets have been sent or received. In this case
++\fBping\fR
++does not stop after
++\fIcount\fR
++packet are sent, it waits either for
++\fIdeadline\fR
++expire or until
++\fIcount\fR
++probes are answered or for some error notification from network.   
++.TP
++\fB-W \fItimeout\fB\fR
++Time to wait for a response, in seconds. The option affects only timeout
++in absense of any responses, otherwise \fBping\fR waits for two RTTs.
++.PP
++When using \fBping\fR for fault isolation, it should first be run
++on the local host, to verify that the local network interface is up
++and running. Then, hosts and gateways further and further away should be
++``pinged''. Round-trip times and packet loss statistics are computed.
++If duplicate packets are received, they are not included in the packet
++loss calculation, although the round trip time of these packets is used
++in calculating the minimum/average/maximum round-trip time numbers.
++When the specified number of packets have been sent (and received) or
++if the program is terminated with a
++SIGINT, a brief summary is displayed. Shorter current statistics
++can be obtained without termination of process with signal
++SIGQUIT.
++.PP
++If \fBping\fR does not receive any reply packets at all it will
++exit with code 1. If a packet 
++\fIcount\fR
++and
++\fIdeadline\fR
++are both specified, and fewer than
++\fIcount\fR
++packets are received by the time the
++\fIdeadline\fR
++has arrived, it will also exit with code 1. 
++On other error it exits with code 2. Otherwise it exits with code 0. This
++makes it possible to use the exit code to see if a host is alive or
++not.
++.PP
++This program is intended for use in network testing, measurement and
++management.
++Because of the load it can impose on the network, it is unwise to use
++\fBping\fR during normal operations or from automated scripts.
++.SH "ICMP PACKET DETAILS"
++.PP
++An IP header without options is 20 bytes.
++An ICMP ECHO_REQUEST packet contains an additional 8 bytes worth
++of ICMP header followed by an arbitrary amount of data.
++When a \fIpacketsize\fR is given, this indicated the size of this
++extra piece of data (the default is 56). Thus the amount of data received
++inside of an IP packet of type ICMP ECHO_REPLY will always be 8 bytes
++more than the requested data space (the ICMP header).
++.PP
++If the data space is at least of size of struct timeval
++\fBping\fR uses the beginning bytes of this space to include
++a timestamp which it uses in the computation of round trip times.
++If the data space is shorter, no round trip times are given.
++.SH "DUPLICATE AND DAMAGED PACKETS"
++.PP
++\fBping\fR will report duplicate and damaged packets.
++Duplicate packets should never occur, and seem to be caused by
++inappropriate link-level retransmissions.
++Duplicates may occur in many situations and are rarely (if ever) a
++good sign, although the presence of low levels of duplicates may not
++always be cause for alarm.
++.PP
++Damaged packets are obviously serious cause for alarm and often
++indicate broken hardware somewhere in the
++\fBping\fR packet's path (in the network or in the hosts).
++.SH "TRYING DIFFERENT DATA PATTERNS"
++.PP
++The (inter)network layer should never treat packets differently depending
++on the data contained in the data portion.
++Unfortunately, data-dependent problems have been known to sneak into
++networks and remain undetected for long periods of time.
++In many cases the particular pattern that will have problems is something
++that doesn't have sufficient ``transitions'', such as all ones or all
++zeros, or a pattern right at the edge, such as almost all zeros.
++It isn't necessarily enough to specify a data pattern of all zeros (for
++example) on the command line because the pattern that is of interest is
++at the data link level, and the relationship between what you type and
++what the controllers transmit can be complicated.
++.PP
++This means that if you have a data-dependent problem you will probably
++have to do a lot of testing to find it.
++If you are lucky, you may manage to find a file that either can't be sent
++across your network or that takes much longer to transfer than other
++similar length files.
++You can then examine this file for repeated patterns that you can test
++using the \fB-p\fR option of \fBping\fR.
++.SH "TTL DETAILS"
++.PP
++The TTL value of an IP packet represents the maximum number of IP routers
++that the packet can go through before being thrown away.
++In current practice you can expect each router in the Internet to decrement
++the TTL field by exactly one.
++.PP
++The TCP/IP specification states that the TTL field for TCP
++packets should be set to 60, but many systems use smaller values
++(4.3 BSD uses 30, 4.2 used 15).
++.PP
++The maximum possible value of this field is 255, and most Unix systems set
++the TTL field of ICMP ECHO_REQUEST packets to 255.
++This is why you will find you can ``ping'' some hosts, but not reach them
++with
++\fBtelnet\fR(1)
++or
++\fBftp\fR(1).
++.PP
++In normal operation ping prints the ttl value from the packet it receives.
++When a remote system receives a ping packet, it can do one of three things
++with the TTL field in its response:
++.TP 0.2i
++\(bu
++Not change it; this is what Berkeley Unix systems did before the
++4.3BSD Tahoe release. In this case the TTL value in the received packet
++will be 255 minus the number of routers in the round-trip path.
++.TP 0.2i
++\(bu
++Set it to 255; this is what current Berkeley Unix systems do.
++In this case the TTL value in the received packet will be 255 minus the
++number of routers in the path \fBfrom\fR
++the remote system \fBto\fR the \fBping\fRing host.
++.TP 0.2i
++\(bu
++Set it to some other value. Some machines use the same value for
++ICMP packets that they use for TCP packets, for example either 30 or 60.
++Others may use completely wild values.
++.SH "BUGS"
++.TP 0.2i
++\(bu
++Many Hosts and Gateways ignore the RECORD_ROUTE option.
++.TP 0.2i
++\(bu
++The maximum IP header length is too small for options like
++RECORD_ROUTE to be completely useful.
++There's not much that that can be done about this, however.
++.TP 0.2i
++\(bu
++Flood pinging is not recommended in general, and flood pinging the
++broadcast address should only be done under very controlled conditions.
++.SH "SEE ALSO"
++.PP
++\fBnetstat\fR(1),
++\fBifconfig\fR(8).
++.SH "HISTORY"
++.PP
++The \fBping\fR command appeared in 4.3BSD.
++.PP
++The version described here is its descendant specific to Linux.
++.SH "SECURITY"
++.PP
++\fBping\fR requires CAP_NET_RAWIO capability
++to be executed. It may be used as set-uid root.
++.SH "AVAILABILITY"
++.PP
++\fBping\fR is part of \fIiputils\fR package
++and the latest versions are  available in source form at
++http://www.skbuff.net/iputils/iputils-current.tar.bz2.
+diff -Naur iputils-s20101006.orig/doc/r1022.html iputils-s20101006/doc/r1022.html
+--- iputils-s20101006.orig/doc/r1022.html	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/r1022.html	2011-01-08 20:09:49.623373190 -0500
+@@ -0,0 +1,511 @@
++<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
++<HTML
++><HEAD
++><TITLE
++>rdisc</TITLE
++><META
++NAME="GENERATOR"
++CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
++REL="HOME"
++TITLE="System Manager's Manual: iputils"
++HREF="index.html"><LINK
++REL="PREVIOUS"
++TITLE="tftpd"
++HREF="r949.html"><LINK
++REL="NEXT"
++TITLE="pg3"
++HREF="r1144.html"></HEAD
++><BODY
++CLASS="REFENTRY"
++BGCOLOR="#FFFFFF"
++TEXT="#000000"
++LINK="#0000FF"
++VLINK="#840084"
++ALINK="#0000FF"
++><DIV
++CLASS="NAVHEADER"
++><TABLE
++SUMMARY="Header navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TH
++COLSPAN="3"
++ALIGN="center"
++>System Manager's Manual: iputils</TH
++></TR
++><TR
++><TD
++WIDTH="10%"
++ALIGN="left"
++VALIGN="bottom"
++><A
++HREF="r949.html"
++ACCESSKEY="P"
++>Prev</A
++></TD
++><TD
++WIDTH="80%"
++ALIGN="center"
++VALIGN="bottom"
++></TD
++><TD
++WIDTH="10%"
++ALIGN="right"
++VALIGN="bottom"
++><A
++HREF="r1144.html"
++ACCESSKEY="N"
++>Next</A
++></TD
++></TR
++></TABLE
++><HR
++ALIGN="LEFT"
++WIDTH="100%"></DIV
++><H1
++><A
++NAME="RDISC"
++></A
++>rdisc</H1
++><DIV
++CLASS="REFNAMEDIV"
++><A
++NAME="AEN1027"
++></A
++><H2
++>Name</H2
++>rdisc&nbsp;--&nbsp;network router discovery daemon</DIV
++><DIV
++CLASS="REFSYNOPSISDIV"
++><A
++NAME="AEN1030"
++></A
++><H2
++>Synopsis</H2
++><P
++><B
++CLASS="COMMAND"
++>rdisc</B
++>  [<CODE
++CLASS="OPTION"
++>-abdfstvV</CODE
++>] [<TT
++CLASS="REPLACEABLE"
++><I
++>send_address</I
++></TT
++>] [<TT
++CLASS="REPLACEABLE"
++><I
++>receive_address</I
++></TT
++>]</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN1039"
++></A
++><H2
++>DESCRIPTION</H2
++><P
++><B
++CLASS="COMMAND"
++>rdisc</B
++> implements client side of the ICMP router discover protocol.
++<B
++CLASS="COMMAND"
++>rdisc</B
++> is invoked at boot time to populate the network
++routing tables with default routes. </P
++><P
++><B
++CLASS="COMMAND"
++>rdisc</B
++> listens on the ALL_HOSTS (224.0.0.1) multicast address
++(or <TT
++CLASS="REPLACEABLE"
++><I
++>receive_address</I
++></TT
++> provided it is given) 
++for ROUTER_ADVERTISE messages from routers. The received
++messages are handled by first ignoring those listed router addresses
++with which the host does not share a network. Among the remaining addresses
++the ones with the highest preference are selected as default routers
++and a default route is entered in the kernel routing table
++for each one of them.</P
++><P
++>Optionally, <B
++CLASS="COMMAND"
++>rdisc</B
++> can avoid waiting for routers to announce 
++themselves by sending out a few ROUTER_SOLICITATION messages
++to the ALL_ROUTERS (224.0.0.2) multicast address 
++(or <TT
++CLASS="REPLACEABLE"
++><I
++>send_address</I
++></TT
++> provided it is given) 
++when it is started.</P
++><P
++>A timer is associated with each router address and the address will
++no longer be considered for inclusion in the the routing tables if the 
++timer expires before a new 
++<SPAN
++CLASS="emphasis"
++><I
++CLASS="EMPHASIS"
++>advertise</I
++></SPAN
++> message is received from the router.
++The address will also be excluded from consideration if the host receives an 
++<SPAN
++CLASS="emphasis"
++><I
++CLASS="EMPHASIS"
++>advertise</I
++></SPAN
++>
++message with the preference being maximally negative.</P
++><P
++>Server side of router discovery protocol is supported by Cisco IOS
++and by any more or less complete UNIX routing daemon, f.e <B
++CLASS="COMMAND"
++>gated</B
++>.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN1055"
++></A
++><H2
++>OPTIONS</H2
++><P
++></P
++><DIV
++CLASS="VARIABLELIST"
++><DL
++><DT
++><CODE
++CLASS="OPTION"
++>-a</CODE
++></DT
++><DD
++><P
++>Accept all routers independently of the preference they have in their 
++<SPAN
++CLASS="emphasis"
++><I
++CLASS="EMPHASIS"
++>advertise</I
++></SPAN
++> messages.
++Normally <B
++CLASS="COMMAND"
++>rdisc</B
++> only accepts (and enters in the kernel routing
++tables) the router or routers with the highest preference.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-b</CODE
++></DT
++><DD
++><P
++>Opposite to <CODE
++CLASS="OPTION"
++>-a</CODE
++>, i.e. install only router with the best
++preference value. It is default behaviour.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-d</CODE
++></DT
++><DD
++><P
++>Send debugging messages to syslog.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-f</CODE
++></DT
++><DD
++><P
++>Run <B
++CLASS="COMMAND"
++>rdisc</B
++> forever even if no routers are found.
++Normally <B
++CLASS="COMMAND"
++>rdisc</B
++> gives up if it has not received any 
++<SPAN
++CLASS="emphasis"
++><I
++CLASS="EMPHASIS"
++>advertise</I
++></SPAN
++> message after after soliciting three times,
++in which case it exits with a non-zero exit code.
++If <CODE
++CLASS="OPTION"
++>-f</CODE
++> is not specified in the first form then 
++<CODE
++CLASS="OPTION"
++>-s</CODE
++> must be specified.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-s</CODE
++></DT
++><DD
++><P
++>Send three <SPAN
++CLASS="emphasis"
++><I
++CLASS="EMPHASIS"
++>solicitation</I
++></SPAN
++> messages initially to quickly discover
++the routers when the system is booted.
++When <CODE
++CLASS="OPTION"
++>-s</CODE
++> is specified <B
++CLASS="COMMAND"
++>rdisc</B
++>
++exits with a non-zero exit code if it can not find any routers.
++This can be overridden with the <CODE
++CLASS="OPTION"
++>-f</CODE
++> option.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-t</CODE
++></DT
++><DD
++><P
++>Test mode. Do not go to background.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-v</CODE
++></DT
++><DD
++><P
++>Be verbose i.e. send lots of debugging messages to syslog.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-V</CODE
++></DT
++><DD
++><P
++>Print version and exit.
++  </P
++></DD
++></DL
++></DIV
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN1110"
++></A
++><H2
++>HISTORY</H2
++><P
++>This program was developed by Sun Microsystems (see copyright
++notice in source file). It was ported to Linux by
++<A
++HREF="mailto:kuznet@ms2.inr.ac.ru"
++TARGET="_top"
++>Alexey Kuznetsov
++&lt;kuznet@ms2.inr.ac.ru&gt;</A
++>.
++It is now maintained by
++<A
++HREF="mailto:yoshfuji@skbuff.net"
++TARGET="_top"
++>YOSHIFUJI Hideaki
++&lt;yoshfuji@skbuff.net&gt;</A
++>.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN1115"
++></A
++><H2
++>SEE ALSO</H2
++><P
++><SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>icmp</SPAN
++>(7)</SPAN
++>,
++<SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>inet</SPAN
++>(7)</SPAN
++>,
++<A
++HREF="r3.html"
++><SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>ping</SPAN
++>(8)</SPAN
++></A
++>.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN1128"
++></A
++><H2
++>REFERENCES</H2
++><P
++>Deering, S.E.,ed "ICMP Router Discovery Messages",
++<A
++HREF="ftp://ftp.isi.edu/in-notes/rfc1256.txt"
++TARGET="_top"
++>RFC1256</A
++>, Network Information Center, SRI International,
++Menlo Park, Calif., September 1991.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN1132"
++></A
++><H2
++>SECURITY</H2
++><P
++><B
++CLASS="COMMAND"
++>rdisc</B
++> requires <CODE
++CLASS="CONSTANT"
++>CAP_NET_RAWIO</CODE
++> to listen
++and send ICMP messages and capability <CODE
++CLASS="CONSTANT"
++>CAP_NET_ADMIN</CODE
++>
++to update routing tables. </P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN1138"
++></A
++><H2
++>AVAILABILITY</H2
++><P
++><B
++CLASS="COMMAND"
++>rdisc</B
++> is part of <TT
++CLASS="FILENAME"
++>iputils</TT
++> package
++and the latest versions are  available in source form at
++<A
++HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
++TARGET="_top"
++>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
++>.</P
++></DIV
++><DIV
++CLASS="NAVFOOTER"
++><HR
++ALIGN="LEFT"
++WIDTH="100%"><TABLE
++SUMMARY="Footer navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++><A
++HREF="r949.html"
++ACCESSKEY="P"
++>Prev</A
++></TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++><A
++HREF="index.html"
++ACCESSKEY="H"
++>Home</A
++></TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++><A
++HREF="r1144.html"
++ACCESSKEY="N"
++>Next</A
++></TD
++></TR
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++>tftpd</TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++>&nbsp;</TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++>pg3</TD
++></TR
++></TABLE
++></DIV
++></BODY
++></HTML
++>
+\ No newline at end of file
+diff -Naur iputils-s20101006.orig/doc/r1144.html iputils-s20101006/doc/r1144.html
+--- iputils-s20101006.orig/doc/r1144.html	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/r1144.html	2011-01-08 20:09:49.631531431 -0500
+@@ -0,0 +1,428 @@
++<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
++<HTML
++><HEAD
++><TITLE
++>pg3</TITLE
++><META
++NAME="GENERATOR"
++CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
++REL="HOME"
++TITLE="System Manager's Manual: iputils"
++HREF="index.html"><LINK
++REL="PREVIOUS"
++TITLE="rdisc"
++HREF="r1022.html"></HEAD
++><BODY
++CLASS="REFENTRY"
++BGCOLOR="#FFFFFF"
++TEXT="#000000"
++LINK="#0000FF"
++VLINK="#840084"
++ALINK="#0000FF"
++><DIV
++CLASS="NAVHEADER"
++><TABLE
++SUMMARY="Header navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TH
++COLSPAN="3"
++ALIGN="center"
++>System Manager's Manual: iputils</TH
++></TR
++><TR
++><TD
++WIDTH="10%"
++ALIGN="left"
++VALIGN="bottom"
++><A
++HREF="r1022.html"
++ACCESSKEY="P"
++>Prev</A
++></TD
++><TD
++WIDTH="80%"
++ALIGN="center"
++VALIGN="bottom"
++></TD
++><TD
++WIDTH="10%"
++ALIGN="right"
++VALIGN="bottom"
++>&nbsp;</TD
++></TR
++></TABLE
++><HR
++ALIGN="LEFT"
++WIDTH="100%"></DIV
++><H1
++><A
++NAME="PG3"
++></A
++>pg3</H1
++><DIV
++CLASS="REFNAMEDIV"
++><A
++NAME="AEN1149"
++></A
++><H2
++>Name</H2
++>pg3, ipg, pgset&nbsp;--&nbsp;send stream of UDP packets</DIV
++><DIV
++CLASS="REFSYNOPSISDIV"
++><A
++NAME="AEN1152"
++></A
++><H2
++>Synopsis</H2
++><P
++><B
++CLASS="COMMAND"
++>source ipg</B
++> </P
++><P
++><B
++CLASS="COMMAND"
++>pg</B
++> </P
++><P
++><B
++CLASS="COMMAND"
++>pgset</B
++>  {<TT
++CLASS="REPLACEABLE"
++><I
++>COMMAND</I
++></TT
++>}</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN1161"
++></A
++><H2
++>DESCRIPTION</H2
++><P
++><B
++CLASS="COMMAND"
++>ipg</B
++> is not a program, it is script which should be sourced
++to <B
++CLASS="COMMAND"
++>bash</B
++>. When sourced it loads module <TT
++CLASS="FILENAME"
++>pg3</TT
++> and
++exports a few of functions accessible from parent shell. These macros
++are <B
++CLASS="COMMAND"
++>pg</B
++> to start packet injection and to get the results of run;
++and <B
++CLASS="COMMAND"
++>pgset</B
++> to setup packet generator.</P
++><P
++><B
++CLASS="COMMAND"
++>pgset</B
++> can send the following commands to module <TT
++CLASS="FILENAME"
++>pg3</TT
++>:</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN1172"
++></A
++><H2
++>COMMAND</H2
++><P
++></P
++><DIV
++CLASS="VARIABLELIST"
++><DL
++><DT
++><CODE
++CLASS="OPTION"
++>odev <TT
++CLASS="REPLACEABLE"
++><I
++>DEVICE</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Name of Ethernet device to test. See
++<A
++HREF="r1144.html#PG3.WARNING"
++>warning</A
++> below.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>pkt_size <TT
++CLASS="REPLACEABLE"
++><I
++>BYTES</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Size of packet to generate. The size includes all the headers: UDP, IP,
++MAC, but does not account for overhead internal to medium, i.e. FCS
++and various paddings.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>frags <TT
++CLASS="REPLACEABLE"
++><I
++>NUMBER</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Each packet will contain <TT
++CLASS="REPLACEABLE"
++><I
++>NUMBER</I
++></TT
++> of fragments.
++Maximal amount for linux-2.4 is 6. Far not all the devices support
++fragmented buffers.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>count <TT
++CLASS="REPLACEABLE"
++><I
++>NUMBER</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Send stream of <TT
++CLASS="REPLACEABLE"
++><I
++>NUMBER</I
++></TT
++> of packets and stop after this.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>ipg <TT
++CLASS="REPLACEABLE"
++><I
++>TIME</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Introduce artificial delay between packets of <TT
++CLASS="REPLACEABLE"
++><I
++>TIME</I
++></TT
++>
++microseconds.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>dst <TT
++CLASS="REPLACEABLE"
++><I
++>IP_ADDRESS</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Select IP destination where the stream is sent to.
++Beware, never set this address at random. <B
++CLASS="COMMAND"
++>pg3</B
++> is not a toy,
++it creates really tough stream. Default value is 0.0.0.0.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>dst <TT
++CLASS="REPLACEABLE"
++><I
++>MAC_ADDRESS</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Select MAC destination where the stream is sent to.
++Default value is 00:00:00:00:00:00 in hope that this will not be received
++by any node on LAN.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>stop</CODE
++></DT
++><DD
++><P
++>Abort packet injection.
++  </P
++></DD
++></DL
++></DIV
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="PG3.WARNING"
++></A
++><H2
++>WARNING</H2
++><P
++>When output device is set to some random device different
++of hardware Ethernet device, <B
++CLASS="COMMAND"
++>pg3</B
++> will crash kernel.</P
++><P
++>Do not use it on VLAN, ethertap, VTUN and other devices,
++which emulate Ethernet not being real Ethernet in fact.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN1232"
++></A
++><H2
++>AUTHOR</H2
++><P
++><B
++CLASS="COMMAND"
++>pg3</B
++> was written by <A
++HREF="mailto:robert.olsson@its.uu.se"
++TARGET="_top"
++>Robert Olsson &lt;robert.olsson@its.uu.se&gt;</A
++>.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN1237"
++></A
++><H2
++>SECURITY</H2
++><P
++>This can be used only by superuser.</P
++><P
++>This tool creates floods of packets which is unlikely to be handled
++even by high-end machines. For example, it saturates gigabit link with
++60 byte packets when used with Intel's e1000. In face of such stream
++switches, routers and end hosts may deadlock, crash, explode.
++Use only in test lab environment.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN1241"
++></A
++><H2
++>AVAILABILITY</H2
++><P
++><B
++CLASS="COMMAND"
++>pg3</B
++> is part of <TT
++CLASS="FILENAME"
++>iputils</TT
++> package
++and the latest versions are  available in source form at
++<A
++HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
++TARGET="_top"
++>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
++>.</P
++></DIV
++><DIV
++CLASS="NAVFOOTER"
++><HR
++ALIGN="LEFT"
++WIDTH="100%"><TABLE
++SUMMARY="Footer navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++><A
++HREF="r1022.html"
++ACCESSKEY="P"
++>Prev</A
++></TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++><A
++HREF="index.html"
++ACCESSKEY="H"
++>Home</A
++></TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++>&nbsp;</TD
++></TR
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++>rdisc</TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++>&nbsp;</TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++>&nbsp;</TD
++></TR
++></TABLE
++></DIV
++></BODY
++></HTML
++>
+\ No newline at end of file
+diff -Naur iputils-s20101006.orig/doc/r3.html iputils-s20101006/doc/r3.html
+--- iputils-s20101006.orig/doc/r3.html	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/r3.html	2011-01-08 20:09:49.558814956 -0500
+@@ -0,0 +1,1494 @@
++<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
++<HTML
++><HEAD
++><TITLE
++>ping</TITLE
++><META
++NAME="GENERATOR"
++CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
++REL="HOME"
++TITLE="System Manager's Manual: iputils"
++HREF="index.html"><LINK
++REL="PREVIOUS"
++TITLE="System Manager's Manual: iputils"
++HREF="index.html"><LINK
++REL="NEXT"
++TITLE="arping"
++HREF="r437.html"></HEAD
++><BODY
++CLASS="REFENTRY"
++BGCOLOR="#FFFFFF"
++TEXT="#000000"
++LINK="#0000FF"
++VLINK="#840084"
++ALINK="#0000FF"
++><DIV
++CLASS="NAVHEADER"
++><TABLE
++SUMMARY="Header navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TH
++COLSPAN="3"
++ALIGN="center"
++>System Manager's Manual: iputils</TH
++></TR
++><TR
++><TD
++WIDTH="10%"
++ALIGN="left"
++VALIGN="bottom"
++><A
++HREF="index.html"
++ACCESSKEY="P"
++>Prev</A
++></TD
++><TD
++WIDTH="80%"
++ALIGN="center"
++VALIGN="bottom"
++></TD
++><TD
++WIDTH="10%"
++ALIGN="right"
++VALIGN="bottom"
++><A
++HREF="r437.html"
++ACCESSKEY="N"
++>Next</A
++></TD
++></TR
++></TABLE
++><HR
++ALIGN="LEFT"
++WIDTH="100%"></DIV
++><H1
++><A
++NAME="PING"
++></A
++>ping</H1
++><DIV
++CLASS="REFNAMEDIV"
++><A
++NAME="AEN8"
++></A
++><H2
++>Name</H2
++>ping, ping6&nbsp;--&nbsp;send ICMP ECHO_REQUEST to network hosts</DIV
++><DIV
++CLASS="REFSYNOPSISDIV"
++><A
++NAME="AEN11"
++></A
++><H2
++>Synopsis</H2
++><P
++><B
++CLASS="COMMAND"
++>ping</B
++>  [<CODE
++CLASS="OPTION"
++>-LRUbdfnqrvVaAB</CODE
++>] [-c <TT
++CLASS="REPLACEABLE"
++><I
++>count</I
++></TT
++>] [-m <TT
++CLASS="REPLACEABLE"
++><I
++>mark</I
++></TT
++>] [-i <TT
++CLASS="REPLACEABLE"
++><I
++>interval</I
++></TT
++>] [-l <TT
++CLASS="REPLACEABLE"
++><I
++>preload</I
++></TT
++>] [-p <TT
++CLASS="REPLACEABLE"
++><I
++>pattern</I
++></TT
++>] [-s <TT
++CLASS="REPLACEABLE"
++><I
++>packetsize</I
++></TT
++>] [-t <TT
++CLASS="REPLACEABLE"
++><I
++>ttl</I
++></TT
++>] [-w <TT
++CLASS="REPLACEABLE"
++><I
++>deadline</I
++></TT
++>] [-F <TT
++CLASS="REPLACEABLE"
++><I
++>flowlabel</I
++></TT
++>] [-I <TT
++CLASS="REPLACEABLE"
++><I
++>interface</I
++></TT
++>] [-M <TT
++CLASS="REPLACEABLE"
++><I
++>hint</I
++></TT
++>] [-N <TT
++CLASS="REPLACEABLE"
++><I
++>nioption</I
++></TT
++>] [-Q <TT
++CLASS="REPLACEABLE"
++><I
++>tos</I
++></TT
++>] [-S <TT
++CLASS="REPLACEABLE"
++><I
++>sndbuf</I
++></TT
++>] [-T <TT
++CLASS="REPLACEABLE"
++><I
++>timestamp option</I
++></TT
++>] [-W <TT
++CLASS="REPLACEABLE"
++><I
++>timeout</I
++></TT
++>] [<TT
++CLASS="REPLACEABLE"
++><I
++>hop</I
++></TT
++>...] {<TT
++CLASS="REPLACEABLE"
++><I
++>destination</I
++></TT
++>}</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN52"
++></A
++><H2
++>DESCRIPTION</H2
++><P
++><B
++CLASS="COMMAND"
++>ping</B
++> uses the ICMP protocol's mandatory ECHO_REQUEST
++datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway.
++ECHO_REQUEST datagrams (``pings'') have an IP and ICMP
++header, followed by a <CODE
++CLASS="STRUCTNAME"
++>struct timeval</CODE
++> and then an arbitrary
++number of ``pad'' bytes used to fill out the packet.</P
++><P
++><B
++CLASS="COMMAND"
++>ping6</B
++> can also send Node Information Queries (RFC4620).</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN59"
++></A
++><H2
++>OPTIONS</H2
++><P
++></P
++><DIV
++CLASS="VARIABLELIST"
++><DL
++><DT
++><CODE
++CLASS="OPTION"
++>-a</CODE
++></DT
++><DD
++><P
++>Audible ping.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-A</CODE
++></DT
++><DD
++><P
++>Adaptive ping. Interpacket interval adapts to round-trip time, so that
++effectively not more than one (or more, if preload is set) unanswered probes
++present in the network. Minimal interval is 200msec for not super-user.
++On networks with low rtt this mode is essentially equivalent to flood mode.  
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-b</CODE
++></DT
++><DD
++><P
++>Allow pinging a broadcast address.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-B</CODE
++></DT
++><DD
++><P
++>Do not allow <B
++CLASS="COMMAND"
++>ping</B
++> to change source address of probes.
++The address is bound to one selected when <B
++CLASS="COMMAND"
++>ping</B
++> starts.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-m <TT
++CLASS="REPLACEABLE"
++><I
++>mark</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>use <TT
++CLASS="REPLACEABLE"
++><I
++>mark</I
++></TT
++> to tag the packets going out. This is useful
++for variety of reasons within the kernel such as using policy
++routing to select specific outbound processing.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++><A
++NAME="PING.COUNT"
++></A
++>-c <TT
++CLASS="REPLACEABLE"
++><I
++>count</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Stop after sending <TT
++CLASS="REPLACEABLE"
++><I
++>count</I
++></TT
++> ECHO_REQUEST
++packets. With 
++<A
++HREF="r3.html#PING.DEADLINE"
++><TT
++CLASS="REPLACEABLE"
++><I
++>deadline</I
++></TT
++></A
++>
++option, <B
++CLASS="COMMAND"
++>ping</B
++> waits for
++<TT
++CLASS="REPLACEABLE"
++><I
++>count</I
++></TT
++> ECHO_REPLY packets, until the timeout expires.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-d</CODE
++></DT
++><DD
++><P
++>Set the <CODE
++CLASS="CONSTANT"
++>SO_DEBUG</CODE
++> option on the socket being used.
++Essentially, this socket option is not used by Linux kernel. 
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-F <TT
++CLASS="REPLACEABLE"
++><I
++>flow label</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Allocate and set 20 bit flow label on echo request packets.
++(Only <B
++CLASS="COMMAND"
++>ping6</B
++>). If value is zero, kernel allocates random flow label.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-f</CODE
++></DT
++><DD
++><P
++>Flood ping. For every ECHO_REQUEST sent a period ``.'' is printed,
++while for ever ECHO_REPLY received a backspace is printed.
++This provides a rapid display of how many packets are being dropped.
++If interval is not given, it sets interval to zero and
++outputs packets as fast as they come back or one hundred times per second,
++whichever is more.
++Only the super-user may use this option with zero interval.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-i <TT
++CLASS="REPLACEABLE"
++><I
++>interval</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Wait <TT
++CLASS="REPLACEABLE"
++><I
++>interval</I
++></TT
++> seconds between sending each packet.
++The default is to wait for one second between each packet normally,
++or not to wait in flood mode. Only super-user may set interval
++to values less 0.2 seconds.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-I <TT
++CLASS="REPLACEABLE"
++><I
++>interface address</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Set source address to specified interface address. Argument
++may be numeric IP address or name of device. When pinging IPv6
++link-local address this option is required.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-l <TT
++CLASS="REPLACEABLE"
++><I
++>preload</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>If <TT
++CLASS="REPLACEABLE"
++><I
++>preload</I
++></TT
++> is specified,
++<B
++CLASS="COMMAND"
++>ping</B
++> sends that many packets not waiting for reply.
++Only the super-user may select preload more than 3.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-L</CODE
++></DT
++><DD
++><P
++>Suppress loopback of multicast packets.  This flag only applies if the ping
++destination is a multicast address.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-N <TT
++CLASS="REPLACEABLE"
++><I
++>nioption</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Send ICMPv6 Node Information Queries (RFC4620), instead of Echo Request.
++   <P
++></P
++><DIV
++CLASS="VARIABLELIST"
++><DL
++><DT
++><CODE
++CLASS="OPTION"
++>name</CODE
++></DT
++><DD
++><P
++>Queries for Node Names.</P
++></DD
++></DL
++></DIV
++>
++   <P
++></P
++><DIV
++CLASS="VARIABLELIST"
++><DL
++><DT
++><CODE
++CLASS="OPTION"
++>ipv6</CODE
++></DT
++><DD
++><P
++>Queries for IPv6 Addresses. There are several IPv6 specific flags.
++      <P
++></P
++><DIV
++CLASS="VARIABLELIST"
++><DL
++><DT
++><CODE
++CLASS="OPTION"
++>ipv6-global</CODE
++></DT
++><DD
++><P
++>Request IPv6 global-scope addresses.</P
++></DD
++></DL
++></DIV
++>
++      <P
++></P
++><DIV
++CLASS="VARIABLELIST"
++><DL
++><DT
++><CODE
++CLASS="OPTION"
++>ipv6-sitelocal</CODE
++></DT
++><DD
++><P
++>Request IPv6 site-local addresses.</P
++></DD
++></DL
++></DIV
++>
++      <P
++></P
++><DIV
++CLASS="VARIABLELIST"
++><DL
++><DT
++><CODE
++CLASS="OPTION"
++>ipv6-linklocal</CODE
++></DT
++><DD
++><P
++>Request IPv6 link-local addresses.</P
++></DD
++></DL
++></DIV
++>
++      <P
++></P
++><DIV
++CLASS="VARIABLELIST"
++><DL
++><DT
++><CODE
++CLASS="OPTION"
++>ipv6-all</CODE
++></DT
++><DD
++><P
++>Request IPv6 addresses on other interfaces.</P
++></DD
++></DL
++></DIV
++>
++     </P
++></DD
++></DL
++></DIV
++>
++   <P
++></P
++><DIV
++CLASS="VARIABLELIST"
++><DL
++><DT
++><CODE
++CLASS="OPTION"
++>ipv4</CODE
++></DT
++><DD
++><P
++>Queries for IPv4 Addresses.  There is one IPv4 specific flag.
++      <P
++></P
++><DIV
++CLASS="VARIABLELIST"
++><DL
++><DT
++><CODE
++CLASS="OPTION"
++>ipv4-all</CODE
++></DT
++><DD
++><P
++>Request IPv4 addresses on other interfaces.</P
++></DD
++></DL
++></DIV
++>
++     </P
++></DD
++></DL
++></DIV
++>
++   <P
++></P
++><DIV
++CLASS="VARIABLELIST"
++><DL
++><DT
++><CODE
++CLASS="OPTION"
++>subject-ipv6=<TT
++CLASS="REPLACEABLE"
++><I
++>ipv6addr</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>IPv6 subject address.</P
++></DD
++></DL
++></DIV
++>
++   <P
++></P
++><DIV
++CLASS="VARIABLELIST"
++><DL
++><DT
++><CODE
++CLASS="OPTION"
++>subject-ipv4=<TT
++CLASS="REPLACEABLE"
++><I
++>ipv4addr</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>IPv4 subject address.</P
++></DD
++></DL
++></DIV
++>
++   <P
++></P
++><DIV
++CLASS="VARIABLELIST"
++><DL
++><DT
++><CODE
++CLASS="OPTION"
++>subject-name=<TT
++CLASS="REPLACEABLE"
++><I
++>nodename</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Subject name.  If it contains more than one dot,
++	fully-qualified domain name is assumed.</P
++></DD
++></DL
++></DIV
++>
++   <P
++></P
++><DIV
++CLASS="VARIABLELIST"
++><DL
++><DT
++><CODE
++CLASS="OPTION"
++>subject-fqdn=<TT
++CLASS="REPLACEABLE"
++><I
++>nodename</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Subject name.  Fully-qualified domain name is
++	always assumed.</P
++></DD
++></DL
++></DIV
++>
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-n</CODE
++></DT
++><DD
++><P
++>Numeric output only.
++No attempt will be made to lookup symbolic names for host addresses.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-p <TT
++CLASS="REPLACEABLE"
++><I
++>pattern</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>You may specify up to 16 ``pad'' bytes to fill out the packet you send.
++This is useful for diagnosing data-dependent problems in a network.
++For example, <CODE
++CLASS="OPTION"
++>-p ff</CODE
++> will cause the sent packet
++to be filled with all ones.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-D</CODE
++></DT
++><DD
++><P
++>Print timestamp (unix time + microseconds as in gettimeofday) before
++each line.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-Q <TT
++CLASS="REPLACEABLE"
++><I
++>tos</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Set Quality of Service -related bits in ICMP datagrams.  
++<TT
++CLASS="REPLACEABLE"
++><I
++>tos</I
++></TT
++> can be either decimal or hex number.
++Traditionally (RFC1349), these have been interpreted as: 0 for reserved
++(currently being redefined as congestion control), 1-4 for Type of Service
++and 5-7 for Precedence.
++Possible settings for Type of Service are: minimal cost: 0x02, 
++reliability: 0x04, throughput: 0x08, low delay: 0x10.  Multiple TOS bits
++should not be set simultaneously.  Possible settings for
++special Precedence range from priority (0x20) to net control (0xe0).  You
++must be root (<CODE
++CLASS="CONSTANT"
++>CAP_NET_ADMIN</CODE
++> capability) to use Critical or
++higher precedence value.  You cannot set
++bit 0x01 (reserved) unless ECN has been enabled in the kernel.
++In RFC2474, these fields has been redefined as 8-bit Differentiated
++Services (DS), consisting of: bits 0-1 of separate data (ECN will be used,
++here), and bits 2-7 of Differentiated Services Codepoint (DSCP).
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-q</CODE
++></DT
++><DD
++><P
++>Quiet output.
++Nothing is displayed except the summary lines at startup time and
++when finished.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-R</CODE
++></DT
++><DD
++><P
++>Record route.
++Includes the RECORD_ROUTE option in the ECHO_REQUEST
++packet and displays the route buffer on returned packets.
++Note that the IP header is only large enough for nine such routes.
++Many hosts ignore or discard this option.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-r</CODE
++></DT
++><DD
++><P
++>Bypass the normal routing tables and send directly to a host on an attached
++interface.
++If the host is not on a directly-attached network, an error is returned.
++This option can be used to ping a local host through an interface
++that has no route through it provided the option <CODE
++CLASS="OPTION"
++>-I</CODE
++> is also
++used.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-s <TT
++CLASS="REPLACEABLE"
++><I
++>packetsize</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Specifies the number of data bytes to be sent.  
++The default is 56, which translates into 64 ICMP
++data bytes when combined with the 8 bytes of ICMP header data.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-S <TT
++CLASS="REPLACEABLE"
++><I
++>sndbuf</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Set socket sndbuf. If not specified, it is selected to buffer
++not more than one packet.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-t <TT
++CLASS="REPLACEABLE"
++><I
++>ttl</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Set the IP Time to Live.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-T <TT
++CLASS="REPLACEABLE"
++><I
++>timestamp option</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Set special IP timestamp options.
++<TT
++CLASS="REPLACEABLE"
++><I
++>timestamp option</I
++></TT
++> may be either 
++<TT
++CLASS="REPLACEABLE"
++><I
++>tsonly</I
++></TT
++> (only timestamps), 
++<TT
++CLASS="REPLACEABLE"
++><I
++>tsandaddr</I
++></TT
++> (timestamps and addresses) or 
++<TT
++CLASS="REPLACEABLE"
++><I
++>tsprespec host1 [host2 [host3 [host4]]]</I
++></TT
++>
++(timestamp prespecified hops).
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-M <TT
++CLASS="REPLACEABLE"
++><I
++>hint</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Select Path MTU Discovery strategy.
++<TT
++CLASS="REPLACEABLE"
++><I
++>hint</I
++></TT
++> may be either <TT
++CLASS="REPLACEABLE"
++><I
++>do</I
++></TT
++>
++(prohibit fragmentation, even local one), 
++<TT
++CLASS="REPLACEABLE"
++><I
++>want</I
++></TT
++> (do PMTU discovery, fragment locally when packet size
++is large), or <TT
++CLASS="REPLACEABLE"
++><I
++>dont</I
++></TT
++> (do not set DF flag).
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-U</CODE
++></DT
++><DD
++><P
++>Print full user-to-user latency (the old behaviour). Normally
++<B
++CLASS="COMMAND"
++>ping</B
++>
++prints network round trip time, which can be different
++f.e. due to DNS failures. 
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-v</CODE
++></DT
++><DD
++><P
++>Verbose output.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-V</CODE
++></DT
++><DD
++><P
++>Show version and exit.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++><A
++NAME="PING.DEADLINE"
++></A
++>-w <TT
++CLASS="REPLACEABLE"
++><I
++>deadline</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Specify a timeout, in seconds, before
++<B
++CLASS="COMMAND"
++>ping</B
++>
++exits regardless of how many
++packets have been sent or received. In this case
++<B
++CLASS="COMMAND"
++>ping</B
++>
++does not stop after
++<A
++HREF="r3.html#PING.COUNT"
++><TT
++CLASS="REPLACEABLE"
++><I
++>count</I
++></TT
++></A
++>
++packet are sent, it waits either for
++<A
++HREF="r3.html#PING.DEADLINE"
++><TT
++CLASS="REPLACEABLE"
++><I
++>deadline</I
++></TT
++></A
++>
++expire or until
++<A
++HREF="r3.html#PING.COUNT"
++><TT
++CLASS="REPLACEABLE"
++><I
++>count</I
++></TT
++></A
++>
++probes are answered or for some error notification from network.   
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-W <TT
++CLASS="REPLACEABLE"
++><I
++>timeout</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Time to wait for a response, in seconds. The option affects only timeout
++in absense of any responses, otherwise <B
++CLASS="COMMAND"
++>ping</B
++> waits for two RTTs.
++  </P
++></DD
++></DL
++></DIV
++><P
++>When using <B
++CLASS="COMMAND"
++>ping</B
++> for fault isolation, it should first be run
++on the local host, to verify that the local network interface is up
++and running. Then, hosts and gateways further and further away should be
++``pinged''. Round-trip times and packet loss statistics are computed.
++If duplicate packets are received, they are not included in the packet
++loss calculation, although the round trip time of these packets is used
++in calculating the minimum/average/maximum round-trip time numbers.
++When the specified number of packets have been sent (and received) or
++if the program is terminated with a
++<CODE
++CLASS="CONSTANT"
++>SIGINT</CODE
++>, a brief summary is displayed. Shorter current statistics
++can be obtained without termination of process with signal
++<CODE
++CLASS="CONSTANT"
++>SIGQUIT</CODE
++>.</P
++><P
++>If <B
++CLASS="COMMAND"
++>ping</B
++> does not receive any reply packets at all it will
++exit with code 1. If a packet 
++<A
++HREF="r3.html#PING.COUNT"
++><TT
++CLASS="REPLACEABLE"
++><I
++>count</I
++></TT
++></A
++>
++and
++<A
++HREF="r3.html#PING.DEADLINE"
++><TT
++CLASS="REPLACEABLE"
++><I
++>deadline</I
++></TT
++></A
++>
++are both specified, and fewer than
++<A
++HREF="r3.html#PING.COUNT"
++><TT
++CLASS="REPLACEABLE"
++><I
++>count</I
++></TT
++></A
++>
++packets are received by the time the
++<A
++HREF="r3.html#PING.DEADLINE"
++><TT
++CLASS="REPLACEABLE"
++><I
++>deadline</I
++></TT
++></A
++>
++has arrived, it will also exit with code 1. 
++On other error it exits with code 2. Otherwise it exits with code 0. This
++makes it possible to use the exit code to see if a host is alive or
++not.</P
++><P
++>This program is intended for use in network testing, measurement and
++management.
++Because of the load it can impose on the network, it is unwise to use
++<B
++CLASS="COMMAND"
++>ping</B
++> during normal operations or from automated scripts.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN362"
++></A
++><H2
++>ICMP PACKET DETAILS</H2
++><P
++>An IP header without options is 20 bytes.
++An ICMP ECHO_REQUEST packet contains an additional 8 bytes worth
++of ICMP header followed by an arbitrary amount of data.
++When a <TT
++CLASS="REPLACEABLE"
++><I
++>packetsize</I
++></TT
++> is given, this indicated the size of this
++extra piece of data (the default is 56). Thus the amount of data received
++inside of an IP packet of type ICMP ECHO_REPLY will always be 8 bytes
++more than the requested data space (the ICMP header).</P
++><P
++>If the data space is at least of size of <CODE
++CLASS="STRUCTNAME"
++>struct timeval</CODE
++>
++<B
++CLASS="COMMAND"
++>ping</B
++> uses the beginning bytes of this space to include
++a timestamp which it uses in the computation of round trip times.
++If the data space is shorter, no round trip times are given.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN369"
++></A
++><H2
++>DUPLICATE AND DAMAGED PACKETS</H2
++><P
++><B
++CLASS="COMMAND"
++>ping</B
++> will report duplicate and damaged packets.
++Duplicate packets should never occur, and seem to be caused by
++inappropriate link-level retransmissions.
++Duplicates may occur in many situations and are rarely (if ever) a
++good sign, although the presence of low levels of duplicates may not
++always be cause for alarm.</P
++><P
++>Damaged packets are obviously serious cause for alarm and often
++indicate broken hardware somewhere in the
++<B
++CLASS="COMMAND"
++>ping</B
++> packet's path (in the network or in the hosts).</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN375"
++></A
++><H2
++>TRYING DIFFERENT DATA PATTERNS</H2
++><P
++>The (inter)network layer should never treat packets differently depending
++on the data contained in the data portion.
++Unfortunately, data-dependent problems have been known to sneak into
++networks and remain undetected for long periods of time.
++In many cases the particular pattern that will have problems is something
++that doesn't have sufficient ``transitions'', such as all ones or all
++zeros, or a pattern right at the edge, such as almost all zeros.
++It isn't necessarily enough to specify a data pattern of all zeros (for
++example) on the command line because the pattern that is of interest is
++at the data link level, and the relationship between what you type and
++what the controllers transmit can be complicated.</P
++><P
++>This means that if you have a data-dependent problem you will probably
++have to do a lot of testing to find it.
++If you are lucky, you may manage to find a file that either can't be sent
++across your network or that takes much longer to transfer than other
++similar length files.
++You can then examine this file for repeated patterns that you can test
++using the <CODE
++CLASS="OPTION"
++>-p</CODE
++> option of <B
++CLASS="COMMAND"
++>ping</B
++>.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN381"
++></A
++><H2
++>TTL DETAILS</H2
++><P
++>The TTL value of an IP packet represents the maximum number of IP routers
++that the packet can go through before being thrown away.
++In current practice you can expect each router in the Internet to decrement
++the TTL field by exactly one.</P
++><P
++>The TCP/IP specification states that the TTL field for TCP
++packets should be set to 60, but many systems use smaller values
++(4.3 BSD uses 30, 4.2 used 15).</P
++><P
++>The maximum possible value of this field is 255, and most Unix systems set
++the TTL field of ICMP ECHO_REQUEST packets to 255.
++This is why you will find you can ``ping'' some hosts, but not reach them
++with
++<SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>telnet</SPAN
++>(1)</SPAN
++>
++or
++<SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>ftp</SPAN
++>(1)</SPAN
++>.</P
++><P
++>In normal operation ping prints the ttl value from the packet it receives.
++When a remote system receives a ping packet, it can do one of three things
++with the TTL field in its response:</P
++><P
++></P
++><UL
++><LI
++><P
++>Not change it; this is what Berkeley Unix systems did before the
++4.3BSD Tahoe release. In this case the TTL value in the received packet
++will be 255 minus the number of routers in the round-trip path.
++ </P
++></LI
++><LI
++><P
++>Set it to 255; this is what current Berkeley Unix systems do.
++In this case the TTL value in the received packet will be 255 minus the
++number of routers in the path <SPAN
++CLASS="emphasis"
++><I
++CLASS="EMPHASIS"
++>from</I
++></SPAN
++>
++the remote system <SPAN
++CLASS="emphasis"
++><I
++CLASS="EMPHASIS"
++>to</I
++></SPAN
++> the <B
++CLASS="COMMAND"
++>ping</B
++>ing host.
++ </P
++></LI
++><LI
++><P
++>Set it to some other value. Some machines use the same value for
++ICMP packets that they use for TCP packets, for example either 30 or 60.
++Others may use completely wild values.
++ </P
++></LI
++></UL
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN403"
++></A
++><H2
++>BUGS</H2
++><P
++></P
++><UL
++><LI
++><P
++>Many Hosts and Gateways ignore the RECORD_ROUTE option.
++ </P
++></LI
++><LI
++><P
++>The maximum IP header length is too small for options like
++RECORD_ROUTE to be completely useful.
++There's not much that that can be done about this, however.
++ </P
++></LI
++><LI
++><P
++>Flood pinging is not recommended in general, and flood pinging the
++broadcast address should only be done under very controlled conditions.
++ </P
++></LI
++></UL
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN412"
++></A
++><H2
++>SEE ALSO</H2
++><P
++><SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>netstat</SPAN
++>(1)</SPAN
++>,
++<SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>ifconfig</SPAN
++>(8)</SPAN
++>.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN421"
++></A
++><H2
++>HISTORY</H2
++><P
++>The <B
++CLASS="COMMAND"
++>ping</B
++> command appeared in 4.3BSD.</P
++><P
++>The version described here is its descendant specific to Linux.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN426"
++></A
++><H2
++>SECURITY</H2
++><P
++><B
++CLASS="COMMAND"
++>ping</B
++> requires <CODE
++CLASS="CONSTANT"
++>CAP_NET_RAWIO</CODE
++> capability
++to be executed. It may be used as set-uid root.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN431"
++></A
++><H2
++>AVAILABILITY</H2
++><P
++><B
++CLASS="COMMAND"
++>ping</B
++> is part of <TT
++CLASS="FILENAME"
++>iputils</TT
++> package
++and the latest versions are  available in source form at
++<A
++HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
++TARGET="_top"
++>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
++>.</P
++></DIV
++><DIV
++CLASS="NAVFOOTER"
++><HR
++ALIGN="LEFT"
++WIDTH="100%"><TABLE
++SUMMARY="Footer navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++><A
++HREF="index.html"
++ACCESSKEY="P"
++>Prev</A
++></TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++><A
++HREF="index.html"
++ACCESSKEY="H"
++>Home</A
++></TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++><A
++HREF="r437.html"
++ACCESSKEY="N"
++>Next</A
++></TD
++></TR
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++>System Manager's Manual: iputils</TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++>&nbsp;</TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++>arping</TD
++></TR
++></TABLE
++></DIV
++></BODY
++></HTML
++>
+\ No newline at end of file
+diff -Naur iputils-s20101006.orig/doc/r437.html iputils-s20101006/doc/r437.html
+--- iputils-s20101006.orig/doc/r437.html	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/r437.html	2011-01-08 20:09:49.571531343 -0500
+@@ -0,0 +1,598 @@
++<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
++<HTML
++><HEAD
++><TITLE
++>arping</TITLE
++><META
++NAME="GENERATOR"
++CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
++REL="HOME"
++TITLE="System Manager's Manual: iputils"
++HREF="index.html"><LINK
++REL="PREVIOUS"
++TITLE="ping"
++HREF="r3.html"><LINK
++REL="NEXT"
++TITLE="clockdiff"
++HREF="r596.html"></HEAD
++><BODY
++CLASS="REFENTRY"
++BGCOLOR="#FFFFFF"
++TEXT="#000000"
++LINK="#0000FF"
++VLINK="#840084"
++ALINK="#0000FF"
++><DIV
++CLASS="NAVHEADER"
++><TABLE
++SUMMARY="Header navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TH
++COLSPAN="3"
++ALIGN="center"
++>System Manager's Manual: iputils</TH
++></TR
++><TR
++><TD
++WIDTH="10%"
++ALIGN="left"
++VALIGN="bottom"
++><A
++HREF="r3.html"
++ACCESSKEY="P"
++>Prev</A
++></TD
++><TD
++WIDTH="80%"
++ALIGN="center"
++VALIGN="bottom"
++></TD
++><TD
++WIDTH="10%"
++ALIGN="right"
++VALIGN="bottom"
++><A
++HREF="r596.html"
++ACCESSKEY="N"
++>Next</A
++></TD
++></TR
++></TABLE
++><HR
++ALIGN="LEFT"
++WIDTH="100%"></DIV
++><H1
++><A
++NAME="ARPING"
++></A
++>arping</H1
++><DIV
++CLASS="REFNAMEDIV"
++><A
++NAME="AEN442"
++></A
++><H2
++>Name</H2
++>arping&nbsp;--&nbsp;send ARP REQUEST to a neighbour host</DIV
++><DIV
++CLASS="REFSYNOPSISDIV"
++><A
++NAME="AEN445"
++></A
++><H2
++>Synopsis</H2
++><P
++><B
++CLASS="COMMAND"
++>arping</B
++>  [<CODE
++CLASS="OPTION"
++>-AbDfhqUV</CODE
++>] [-c <TT
++CLASS="REPLACEABLE"
++><I
++>count</I
++></TT
++>] [-w <TT
++CLASS="REPLACEABLE"
++><I
++>deadline</I
++></TT
++>] [-s <TT
++CLASS="REPLACEABLE"
++><I
++>source</I
++></TT
++>] {-I <TT
++CLASS="REPLACEABLE"
++><I
++>interface</I
++></TT
++>} {<TT
++CLASS="REPLACEABLE"
++><I
++>destination</I
++></TT
++>}</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN460"
++></A
++><H2
++>DESCRIPTION</H2
++><P
++>Ping <TT
++CLASS="REPLACEABLE"
++><I
++>destination</I
++></TT
++> on device <TT
++CLASS="REPLACEABLE"
++><I
++>interface</I
++></TT
++> by ARP packets,
++using source address <TT
++CLASS="REPLACEABLE"
++><I
++>source</I
++></TT
++>.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN466"
++></A
++><H2
++>OPTIONS</H2
++><P
++></P
++><DIV
++CLASS="VARIABLELIST"
++><DL
++><DT
++><CODE
++CLASS="OPTION"
++>-A</CODE
++></DT
++><DD
++><P
++>The same as <CODE
++CLASS="OPTION"
++>-U</CODE
++>, but ARP REPLY packets used instead
++of ARP REQUEST.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-b</CODE
++></DT
++><DD
++><P
++>Send only MAC level broadcasts. Normally <B
++CLASS="COMMAND"
++>arping</B
++> starts
++from sending broadcast, and switch to unicast after reply received.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++><A
++NAME="ARPING.COUNT"
++></A
++>-c <TT
++CLASS="REPLACEABLE"
++><I
++>count</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Stop after sending <TT
++CLASS="REPLACEABLE"
++><I
++>count</I
++></TT
++> ARP REQUEST
++packets. With 
++<A
++HREF="r437.html#ARPING.DEADLINE"
++><TT
++CLASS="REPLACEABLE"
++><I
++>deadline</I
++></TT
++></A
++>
++option, <B
++CLASS="COMMAND"
++>arping</B
++> waits for
++<TT
++CLASS="REPLACEABLE"
++><I
++>count</I
++></TT
++> ARP REPLY packets, until the timeout expires.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-D</CODE
++></DT
++><DD
++><P
++>Duplicate address detection mode (DAD). See 
++<A
++HREF="ftp://ftp.isi.edu/in-notes/rfc2131.txt"
++TARGET="_top"
++>RFC2131, 4.4.1</A
++>.
++Returns 0, if DAD succeeded i.e. no replies are received
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-f</CODE
++></DT
++><DD
++><P
++>Finish after the first reply confirming that target is alive.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++><A
++NAME="OPT.INTERFACE"
++></A
++>-I <TT
++CLASS="REPLACEABLE"
++><I
++>interface</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Name of network device where to send ARP REQUEST packets. This option
++is required.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-h</CODE
++></DT
++><DD
++><P
++>Print help page and exit.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-q</CODE
++></DT
++><DD
++><P
++>Quiet output. Nothing is displayed.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++><A
++NAME="OPT.SOURCE"
++></A
++>-s <TT
++CLASS="REPLACEABLE"
++><I
++>source</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>IP source address to use in ARP packets.
++If this option is absent, source address is:
++   <P
++></P
++><UL
++><LI
++><P
++>In DAD mode (with option <CODE
++CLASS="OPTION"
++>-D</CODE
++>) set to 0.0.0.0.
++    </P
++></LI
++><LI
++><P
++>In Unsolicited ARP mode (with options <CODE
++CLASS="OPTION"
++>-U</CODE
++> or <CODE
++CLASS="OPTION"
++>-A</CODE
++>)
++set to <TT
++CLASS="REPLACEABLE"
++><I
++>destination</I
++></TT
++>.
++    </P
++></LI
++><LI
++><P
++>Otherwise, it is calculated from routing tables.
++    </P
++></LI
++></UL
++>
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-U</CODE
++></DT
++><DD
++><P
++>Unsolicited ARP mode to update neighbours' ARP caches.
++No replies are expected.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-V</CODE
++></DT
++><DD
++><P
++>Print version of the program and exit.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++><A
++NAME="ARPING.DEADLINE"
++></A
++>-w <TT
++CLASS="REPLACEABLE"
++><I
++>deadline</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>Specify a timeout, in seconds, before
++<B
++CLASS="COMMAND"
++>arping</B
++>
++exits regardless of how many
++packets have been sent or received. In this case
++<B
++CLASS="COMMAND"
++>arping</B
++>
++does not stop after
++<A
++HREF="r437.html#ARPING.COUNT"
++><TT
++CLASS="REPLACEABLE"
++><I
++>count</I
++></TT
++></A
++>
++packet are sent, it waits either for
++<A
++HREF="r437.html#ARPING.DEADLINE"
++><TT
++CLASS="REPLACEABLE"
++><I
++>deadline</I
++></TT
++></A
++>
++expire or until
++<A
++HREF="r437.html#ARPING.COUNT"
++><TT
++CLASS="REPLACEABLE"
++><I
++>count</I
++></TT
++></A
++>
++probes are answered.
++  </P
++></DD
++></DL
++></DIV
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN564"
++></A
++><H2
++>SEE ALSO</H2
++><P
++><A
++HREF="r3.html"
++><SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>ping</SPAN
++>(8)</SPAN
++></A
++>,
++<A
++HREF="r596.html"
++><SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>clockdiff</SPAN
++>(8)</SPAN
++></A
++>,
++<A
++HREF="r790.html"
++><SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>tracepath</SPAN
++>(8)</SPAN
++></A
++>.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN579"
++></A
++><H2
++>AUTHOR</H2
++><P
++><B
++CLASS="COMMAND"
++>arping</B
++> was written by
++<A
++HREF="mailto:kuznet@ms2.inr.ac.ru"
++TARGET="_top"
++>Alexey Kuznetsov
++&lt;kuznet@ms2.inr.ac.ru&gt;</A
++>.
++It is now maintained by
++<A
++HREF="mailto:yoshfuji@skbuff.net"
++TARGET="_top"
++>YOSHIFUJI Hideaki
++&lt;yoshfuji@skbuff.net&gt;</A
++>.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN585"
++></A
++><H2
++>SECURITY</H2
++><P
++><B
++CLASS="COMMAND"
++>arping</B
++> requires <CODE
++CLASS="CONSTANT"
++>CAP_NET_RAWIO</CODE
++> capability
++to be executed. It is not recommended to be used as set-uid root,
++because it allows user to modify ARP caches of neighbour hosts.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN590"
++></A
++><H2
++>AVAILABILITY</H2
++><P
++><B
++CLASS="COMMAND"
++>arping</B
++> is part of <TT
++CLASS="FILENAME"
++>iputils</TT
++> package
++and the latest versions are  available in source form at
++<A
++HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
++TARGET="_top"
++>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
++>.</P
++></DIV
++><DIV
++CLASS="NAVFOOTER"
++><HR
++ALIGN="LEFT"
++WIDTH="100%"><TABLE
++SUMMARY="Footer navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++><A
++HREF="r3.html"
++ACCESSKEY="P"
++>Prev</A
++></TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++><A
++HREF="index.html"
++ACCESSKEY="H"
++>Home</A
++></TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++><A
++HREF="r596.html"
++ACCESSKEY="N"
++>Next</A
++></TD
++></TR
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++>ping</TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++>&nbsp;</TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++>clockdiff</TD
++></TR
++></TABLE
++></DIV
++></BODY
++></HTML
++>
+\ No newline at end of file
+diff -Naur iputils-s20101006.orig/doc/r596.html iputils-s20101006/doc/r596.html
+--- iputils-s20101006.orig/doc/r596.html	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/r596.html	2011-01-08 20:09:49.582999920 -0500
+@@ -0,0 +1,428 @@
++<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
++<HTML
++><HEAD
++><TITLE
++>clockdiff</TITLE
++><META
++NAME="GENERATOR"
++CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
++REL="HOME"
++TITLE="System Manager's Manual: iputils"
++HREF="index.html"><LINK
++REL="PREVIOUS"
++TITLE="arping"
++HREF="r437.html"><LINK
++REL="NEXT"
++TITLE="rarpd"
++HREF="r691.html"></HEAD
++><BODY
++CLASS="REFENTRY"
++BGCOLOR="#FFFFFF"
++TEXT="#000000"
++LINK="#0000FF"
++VLINK="#840084"
++ALINK="#0000FF"
++><DIV
++CLASS="NAVHEADER"
++><TABLE
++SUMMARY="Header navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TH
++COLSPAN="3"
++ALIGN="center"
++>System Manager's Manual: iputils</TH
++></TR
++><TR
++><TD
++WIDTH="10%"
++ALIGN="left"
++VALIGN="bottom"
++><A
++HREF="r437.html"
++ACCESSKEY="P"
++>Prev</A
++></TD
++><TD
++WIDTH="80%"
++ALIGN="center"
++VALIGN="bottom"
++></TD
++><TD
++WIDTH="10%"
++ALIGN="right"
++VALIGN="bottom"
++><A
++HREF="r691.html"
++ACCESSKEY="N"
++>Next</A
++></TD
++></TR
++></TABLE
++><HR
++ALIGN="LEFT"
++WIDTH="100%"></DIV
++><H1
++><A
++NAME="CLOCKDIFF"
++></A
++>clockdiff</H1
++><DIV
++CLASS="REFNAMEDIV"
++><A
++NAME="AEN601"
++></A
++><H2
++>Name</H2
++>clockdiff&nbsp;--&nbsp;measure clock difference between hosts</DIV
++><DIV
++CLASS="REFSYNOPSISDIV"
++><A
++NAME="AEN604"
++></A
++><H2
++>Synopsis</H2
++><P
++><B
++CLASS="COMMAND"
++>clockdiff</B
++>  [<CODE
++CLASS="OPTION"
++>-o</CODE
++>] [<CODE
++CLASS="OPTION"
++>-o1</CODE
++>] {<TT
++CLASS="REPLACEABLE"
++><I
++>destination</I
++></TT
++>}</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN613"
++></A
++><H2
++>DESCRIPTION</H2
++><P
++><B
++CLASS="COMMAND"
++>clockdiff</B
++> Measures clock difference between us and
++<TT
++CLASS="REPLACEABLE"
++><I
++>destination</I
++></TT
++> with 1 msec resolution using ICMP TIMESTAMP
++<A
++HREF="r596.html#CLOCKDIFF.ICMP-TIMESTAMP"
++>[2]</A
++>
++packets or, optionally, IP TIMESTAMP option
++<A
++HREF="r596.html#CLOCKDIFF.IP-TIMESTAMP"
++>[3]</A
++>
++option added to ICMP ECHO.
++<A
++HREF="r596.html#CLOCKDIFF.ICMP-ECHO"
++>[1]</A
++></P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN621"
++></A
++><H2
++>OPTIONS</H2
++><P
++></P
++><DIV
++CLASS="VARIABLELIST"
++><DL
++><DT
++><CODE
++CLASS="OPTION"
++>-o</CODE
++></DT
++><DD
++><P
++>Use IP TIMESTAMP with ICMP ECHO instead of ICMP TIMESTAMP
++messages. It is useful with some destinations, which do not support
++ICMP TIMESTAMP (f.e. Solaris &lt;2.4).
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-o1</CODE
++></DT
++><DD
++><P
++>Slightly different form of <CODE
++CLASS="OPTION"
++>-o</CODE
++>, namely it uses three-term
++IP TIMESTAMP with prespecified hop addresses instead of four term one.
++What flavor works better depends on target host. Particularly,
++<CODE
++CLASS="OPTION"
++>-o</CODE
++> is better for Linux.
++  </P
++></DD
++></DL
++></DIV
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN636"
++></A
++><H2
++>WARNINGS</H2
++><P
++></P
++><UL
++><LI
++><P
++>Some nodes (Cisco) use non-standard timestamps, which is allowed
++by RFC, but makes timestamps mostly useless.
++ </P
++></LI
++><LI
++><P
++>Some nodes generate messed timestamps (Solaris&gt;2.4), when
++run <B
++CLASS="COMMAND"
++>xntpd</B
++>. Seems, its IP stack uses a corrupted clock source,
++which is synchronized to time-of-day clock periodically and jumps
++randomly making timestamps mostly useless. Good news is that you can
++use NTP in this case, which is even better.
++ </P
++></LI
++><LI
++><P
++><B
++CLASS="COMMAND"
++>clockdiff</B
++> shows difference in time modulo 24 days.
++ </P
++></LI
++></UL
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN647"
++></A
++><H2
++>SEE ALSO</H2
++><P
++><A
++HREF="r3.html"
++><SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>ping</SPAN
++>(8)</SPAN
++></A
++>,
++<A
++HREF="r437.html"
++><SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>arping</SPAN
++>(8)</SPAN
++></A
++>,
++<A
++HREF="r790.html"
++><SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>tracepath</SPAN
++>(8)</SPAN
++></A
++>.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN662"
++></A
++><H2
++>REFERENCES</H2
++><P
++>[1] <A
++NAME="CLOCKDIFF.ICMP-ECHO"
++></A
++>ICMP ECHO,
++<A
++HREF="ftp://ftp.isi.edu/in-notes/rfc792.txt"
++TARGET="_top"
++>RFC0792, page 14</A
++>.</P
++><P
++>[2] <A
++NAME="CLOCKDIFF.ICMP-TIMESTAMP"
++></A
++>ICMP TIMESTAMP,
++<A
++HREF="ftp://ftp.isi.edu/in-notes/rfc792.txt"
++TARGET="_top"
++>RFC0792, page 16</A
++>.</P
++><P
++>[3] <A
++NAME="CLOCKDIFF.IP-TIMESTAMP"
++></A
++>IP TIMESTAMP option,
++<A
++HREF="ftp://ftp.isi.edu/in-notes/rfc791.txt"
++TARGET="_top"
++>RFC0791, 3.1, page 16</A
++>.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN673"
++></A
++><H2
++>AUTHOR</H2
++><P
++><B
++CLASS="COMMAND"
++>clockdiff</B
++> was compiled by
++<A
++HREF="mailto:kuznet@ms2.inr.ac.ru"
++TARGET="_top"
++>Alexey Kuznetsov
++&lt;kuznet@ms2.inr.ac.ru&gt;</A
++>. It was based on code borrowed
++from BSD <B
++CLASS="COMMAND"
++>timed</B
++> daemon.
++It is now maintained by
++<A
++HREF="mailto:yoshfuji@skbuff.net"
++TARGET="_top"
++>YOSHIFUJI Hideaki
++&lt;yoshfuji@skbuff.net&gt;</A
++>.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN680"
++></A
++><H2
++>SECURITY</H2
++><P
++><B
++CLASS="COMMAND"
++>clockdiff</B
++> requires <CODE
++CLASS="CONSTANT"
++>CAP_NET_RAWIO</CODE
++> capability
++to be executed. It is safe to be used as set-uid root.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN685"
++></A
++><H2
++>AVAILABILITY</H2
++><P
++><B
++CLASS="COMMAND"
++>clockdiff</B
++> is part of <TT
++CLASS="FILENAME"
++>iputils</TT
++> package
++and the latest versions are  available in source form at
++<A
++HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
++TARGET="_top"
++>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
++>.</P
++></DIV
++><DIV
++CLASS="NAVFOOTER"
++><HR
++ALIGN="LEFT"
++WIDTH="100%"><TABLE
++SUMMARY="Footer navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++><A
++HREF="r437.html"
++ACCESSKEY="P"
++>Prev</A
++></TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++><A
++HREF="index.html"
++ACCESSKEY="H"
++>Home</A
++></TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++><A
++HREF="r691.html"
++ACCESSKEY="N"
++>Next</A
++></TD
++></TR
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++>arping</TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++>&nbsp;</TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++>rarpd</TD
++></TR
++></TABLE
++></DIV
++></BODY
++></HTML
++>
+\ No newline at end of file
+diff -Naur iputils-s20101006.orig/doc/r691.html iputils-s20101006/doc/r691.html
+--- iputils-s20101006.orig/doc/r691.html	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/r691.html	2011-01-08 20:09:49.590918871 -0500
+@@ -0,0 +1,431 @@
++<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
++<HTML
++><HEAD
++><TITLE
++>rarpd</TITLE
++><META
++NAME="GENERATOR"
++CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
++REL="HOME"
++TITLE="System Manager's Manual: iputils"
++HREF="index.html"><LINK
++REL="PREVIOUS"
++TITLE="clockdiff"
++HREF="r596.html"><LINK
++REL="NEXT"
++TITLE="tracepath"
++HREF="r790.html"></HEAD
++><BODY
++CLASS="REFENTRY"
++BGCOLOR="#FFFFFF"
++TEXT="#000000"
++LINK="#0000FF"
++VLINK="#840084"
++ALINK="#0000FF"
++><DIV
++CLASS="NAVHEADER"
++><TABLE
++SUMMARY="Header navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TH
++COLSPAN="3"
++ALIGN="center"
++>System Manager's Manual: iputils</TH
++></TR
++><TR
++><TD
++WIDTH="10%"
++ALIGN="left"
++VALIGN="bottom"
++><A
++HREF="r596.html"
++ACCESSKEY="P"
++>Prev</A
++></TD
++><TD
++WIDTH="80%"
++ALIGN="center"
++VALIGN="bottom"
++></TD
++><TD
++WIDTH="10%"
++ALIGN="right"
++VALIGN="bottom"
++><A
++HREF="r790.html"
++ACCESSKEY="N"
++>Next</A
++></TD
++></TR
++></TABLE
++><HR
++ALIGN="LEFT"
++WIDTH="100%"></DIV
++><H1
++><A
++NAME="RARPD"
++></A
++>rarpd</H1
++><DIV
++CLASS="REFNAMEDIV"
++><A
++NAME="AEN696"
++></A
++><H2
++>Name</H2
++>rarpd&nbsp;--&nbsp;answer RARP REQUESTs</DIV
++><DIV
++CLASS="REFSYNOPSISDIV"
++><A
++NAME="AEN699"
++></A
++><H2
++>Synopsis</H2
++><P
++><B
++CLASS="COMMAND"
++>arping</B
++>  [<CODE
++CLASS="OPTION"
++>-aAvde</CODE
++>] [-b <TT
++CLASS="REPLACEABLE"
++><I
++>bootdir</I
++></TT
++>] [<TT
++CLASS="REPLACEABLE"
++><I
++>interface</I
++></TT
++>]</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN708"
++></A
++><H2
++>DESCRIPTION</H2
++><P
++>Listens
++<A
++HREF="ftp://ftp.isi.edu/in-notes/rfc903.txt"
++TARGET="_top"
++>RARP</A
++>
++requests from clients. Provided MAC address of client
++is found in <TT
++CLASS="FILENAME"
++>/etc/ethers</TT
++> database and
++obtained host name is resolvable to an IP address appropriate
++for attached network, <B
++CLASS="COMMAND"
++>rarpd</B
++> answers to client with RARPD
++reply carrying an IP address.</P
++><P
++>To allow multiple boot servers on the network <B
++CLASS="COMMAND"
++>rarpd</B
++>
++optionally checks for presence Sun-like bootable image in TFTP directory.
++It should have form <KBD
++CLASS="USERINPUT"
++>Hexadecimal_IP.ARCH</KBD
++>, f.e. to load
++sparc 193.233.7.98 <TT
++CLASS="FILENAME"
++>C1E90762.SUN4M</TT
++> is linked to
++an image appropriate for SUM4M in directory <TT
++CLASS="FILENAME"
++>/etc/tftpboot</TT
++>.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN719"
++></A
++><H2
++>WARNING</H2
++><P
++>This facility is deeply obsoleted by
++<A
++HREF="ftp://ftp.isi.edu/in-notes/rfc951.txt"
++TARGET="_top"
++>BOOTP</A
++>
++and later
++<A
++HREF="ftp://ftp.isi.edu/in-notes/rfc2131.txt"
++TARGET="_top"
++>DHCP</A
++> protocols.
++However, some clients really still need this to boot.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN724"
++></A
++><H2
++>OPTIONS</H2
++><P
++></P
++><DIV
++CLASS="VARIABLELIST"
++><DL
++><DT
++><CODE
++CLASS="OPTION"
++>-a</CODE
++></DT
++><DD
++><P
++>Listen on all the interfaces. Currently it is an internal
++option, its function is overridden with <TT
++CLASS="REPLACEABLE"
++><I
++>interface</I
++></TT
++>
++argument. It should not be used.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-A</CODE
++></DT
++><DD
++><P
++>Listen not only RARP but also ARP messages, some rare clients
++use ARP by some unknown reason.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-v</CODE
++></DT
++><DD
++><P
++>Be verbose.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-d</CODE
++></DT
++><DD
++><P
++>Debug mode. Do not go to background.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-e</CODE
++></DT
++><DD
++><P
++>Do not check for presence of a boot image, reply if MAC address
++resolves to a valid IP address using <TT
++CLASS="FILENAME"
++>/etc/ethers</TT
++>
++database and DNS. 
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-b <TT
++CLASS="REPLACEABLE"
++><I
++>bootdir</I
++></TT
++></CODE
++></DT
++><DD
++><P
++>TFTP boot directory. Default is <TT
++CLASS="FILENAME"
++>/etc/tftpboot</TT
++>
++  </P
++></DD
++></DL
++></DIV
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN761"
++></A
++><H2
++>SEE ALSO</H2
++><P
++><A
++HREF="r437.html"
++><SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>arping</SPAN
++>(8)</SPAN
++></A
++>,
++<A
++HREF="r949.html"
++><SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>tftpd</SPAN
++>(8)</SPAN
++></A
++>.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN772"
++></A
++><H2
++>AUTHOR</H2
++><P
++><B
++CLASS="COMMAND"
++>rarpd</B
++> was written by
++<A
++HREF="mailto:kuznet@ms2.inr.ac.ru"
++TARGET="_top"
++>Alexey Kuznetsov
++&lt;kuznet@ms2.inr.ac.ru&gt;</A
++>.
++It is now maintained by
++<A
++HREF="mailto:yoshfuji@skbuff.net"
++TARGET="_top"
++>YOSHIFUJI Hideaki
++&lt;yoshfuji@skbuff.net&gt;</A
++>.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN778"
++></A
++><H2
++>SECURITY</H2
++><P
++><B
++CLASS="COMMAND"
++>rarpd</B
++> requires <CODE
++CLASS="CONSTANT"
++>CAP_NET_RAWIO</CODE
++> capability
++to listen and send RARP and ARP packets. It also needs <CODE
++CLASS="CONSTANT"
++>CAP_NET_ADMIN</CODE
++>
++to give to kernel hint for ARP resolution; this is not strictly required,
++but some (most of, to be more exact) clients are so badly broken that
++are not able to answer ARP before they are finally booted. This is
++not wonderful taking into account that clients using RARPD in 2002
++are all unsupported relic creatures of 90's and even earlier.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN784"
++></A
++><H2
++>AVAILABILITY</H2
++><P
++><B
++CLASS="COMMAND"
++>rarpd</B
++> is part of <TT
++CLASS="FILENAME"
++>iputils</TT
++> package
++and the latest versions are  available in source form at
++<A
++HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
++TARGET="_top"
++>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
++>.</P
++></DIV
++><DIV
++CLASS="NAVFOOTER"
++><HR
++ALIGN="LEFT"
++WIDTH="100%"><TABLE
++SUMMARY="Footer navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++><A
++HREF="r596.html"
++ACCESSKEY="P"
++>Prev</A
++></TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++><A
++HREF="index.html"
++ACCESSKEY="H"
++>Home</A
++></TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++><A
++HREF="r790.html"
++ACCESSKEY="N"
++>Next</A
++></TD
++></TR
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++>clockdiff</TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++>&nbsp;</TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++>tracepath</TD
++></TR
++></TABLE
++></DIV
++></BODY
++></HTML
++>
+\ No newline at end of file
+diff -Naur iputils-s20101006.orig/doc/r790.html iputils-s20101006/doc/r790.html
+--- iputils-s20101006.orig/doc/r790.html	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/r790.html	2011-01-08 20:09:49.602668583 -0500
+@@ -0,0 +1,426 @@
++<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
++<HTML
++><HEAD
++><TITLE
++>tracepath</TITLE
++><META
++NAME="GENERATOR"
++CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
++REL="HOME"
++TITLE="System Manager's Manual: iputils"
++HREF="index.html"><LINK
++REL="PREVIOUS"
++TITLE="rarpd"
++HREF="r691.html"><LINK
++REL="NEXT"
++TITLE="traceroute6"
++HREF="r884.html"></HEAD
++><BODY
++CLASS="REFENTRY"
++BGCOLOR="#FFFFFF"
++TEXT="#000000"
++LINK="#0000FF"
++VLINK="#840084"
++ALINK="#0000FF"
++><DIV
++CLASS="NAVHEADER"
++><TABLE
++SUMMARY="Header navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TH
++COLSPAN="3"
++ALIGN="center"
++>System Manager's Manual: iputils</TH
++></TR
++><TR
++><TD
++WIDTH="10%"
++ALIGN="left"
++VALIGN="bottom"
++><A
++HREF="r691.html"
++ACCESSKEY="P"
++>Prev</A
++></TD
++><TD
++WIDTH="80%"
++ALIGN="center"
++VALIGN="bottom"
++></TD
++><TD
++WIDTH="10%"
++ALIGN="right"
++VALIGN="bottom"
++><A
++HREF="r884.html"
++ACCESSKEY="N"
++>Next</A
++></TD
++></TR
++></TABLE
++><HR
++ALIGN="LEFT"
++WIDTH="100%"></DIV
++><H1
++><A
++NAME="TRACEPATH"
++></A
++>tracepath</H1
++><DIV
++CLASS="REFNAMEDIV"
++><A
++NAME="AEN795"
++></A
++><H2
++>Name</H2
++>tracepath, tracepath6&nbsp;--&nbsp;traces path to a network host discovering MTU along this path</DIV
++><DIV
++CLASS="REFSYNOPSISDIV"
++><A
++NAME="AEN798"
++></A
++><H2
++>Synopsis</H2
++><P
++><B
++CLASS="COMMAND"
++>tracepath</B
++>  [-n] [-b] [-l <TT
++CLASS="REPLACEABLE"
++><I
++>pktlen</I
++></TT
++>] {<TT
++CLASS="REPLACEABLE"
++><I
++>destination</I
++></TT
++>} [<TT
++CLASS="REPLACEABLE"
++><I
++>port</I
++></TT
++>]</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN809"
++></A
++><H2
++>DESCRIPTION</H2
++><P
++>It traces path to <TT
++CLASS="REPLACEABLE"
++><I
++>destination</I
++></TT
++> discovering MTU along this path.
++It uses UDP port <TT
++CLASS="REPLACEABLE"
++><I
++>port</I
++></TT
++> or some random port.
++It is similar to <B
++CLASS="COMMAND"
++>traceroute</B
++>, only does not require superuser
++privileges and has no fancy options.</P
++><P
++><B
++CLASS="COMMAND"
++>tracepath6</B
++> is good replacement for <B
++CLASS="COMMAND"
++>traceroute6</B
++>
++and classic example of application of Linux error queues.
++The situation with IPv4 is worse, because commercial
++IP routers do not return enough information in icmp error messages.
++Probably, it will change, when they will be updated.
++For now it uses Van Jacobson's trick, sweeping a range
++of UDP ports to maintain trace history.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN818"
++></A
++><H2
++>OPTIONS</H2
++><P
++></P
++><DIV
++CLASS="VARIABLELIST"
++><DL
++><DT
++><CODE
++CLASS="OPTION"
++>-n</CODE
++></DT
++><DD
++><P
++>Print primarily IP addresses numerically.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-b</CODE
++></DT
++><DD
++><P
++>Print both of host names and IP addresses.
++  </P
++></DD
++><DT
++><CODE
++CLASS="OPTION"
++>-l</CODE
++></DT
++><DD
++><P
++>Sets the initial packet length to <TT
++CLASS="REPLACEABLE"
++><I
++>pktlen</I
++></TT
++> instead of
++65536 for <B
++CLASS="COMMAND"
++>tracepath</B
++> or 128000 for <B
++CLASS="COMMAND"
++>tracepath6</B
++>.
++  </P
++></DD
++></DL
++></DIV
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN839"
++></A
++><H2
++>OUTPUT</H2
++><P
++><P
++CLASS="LITERALLAYOUT"
++>root@mops:~&nbsp;#&nbsp;tracepath6&nbsp;3ffe:2400:0:109::2<br>
++&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>
++&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>
++&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>
++&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>
++&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Resume:&nbsp;pmtu&nbsp;1480&nbsp;hops&nbsp;2&nbsp;back&nbsp;2</P
++></P
++><P
++>The first column shows <TT
++CLASS="LITERAL"
++>TTL</TT
++> of the probe, followed by colon.
++Usually value of <TT
++CLASS="LITERAL"
++>TTL</TT
++> is obtained from reply from network,
++but sometimes reply does not contain necessary information and
++we have to guess it. In this case the number is followed by ?.</P
++><P
++>The second column shows the network hop, which replied to the probe.
++It is either address of router or word <TT
++CLASS="LITERAL"
++>[LOCALHOST]</TT
++>, if
++the probe was not sent to the network.</P
++><P
++>The rest of line shows miscellaneous information about path to
++the correspinding hetwork hop. As rule it contains value of RTT.
++Additionally, it can show Path MTU, when it changes.
++If the path is asymmetric
++or the probe finishes before it reach prescribed hop, difference
++between number of hops in forward and backward direction is shown
++following keyword <TT
++CLASS="LITERAL"
++>async</TT
++>. This information is not reliable.
++F.e. the third line shows asymmetry of 1, it is because the first probe
++with TTL of 2 was rejected at the first hop due to Path MTU Discovery.</P
++><P
++>The last line summarizes information about all the path to the destination,
++it shows detected Path MTU, amount of hops to the destination and our
++guess about amount of hops from the destination to us, which can be
++different when the path is asymmetric.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN851"
++></A
++><H2
++>SEE ALSO</H2
++><P
++><SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>traceroute</SPAN
++>(8)</SPAN
++>,
++<A
++HREF="r884.html"
++><SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>traceroute6</SPAN
++>(8)</SPAN
++></A
++>,
++<A
++HREF="r3.html"
++><SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>ping</SPAN
++>(8)</SPAN
++></A
++>.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN865"
++></A
++><H2
++>AUTHOR</H2
++><P
++><B
++CLASS="COMMAND"
++>tracepath</B
++> was written by
++<A
++HREF="mailto:kuznet@ms2.inr.ac.ru"
++TARGET="_top"
++>Alexey Kuznetsov
++&lt;kuznet@ms2.inr.ac.ru&gt;</A
++>.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN870"
++></A
++><H2
++>SECURITY</H2
++><P
++>No security issues.</P
++><P
++>This lapidary deserves to be elaborated.
++<B
++CLASS="COMMAND"
++>tracepath</B
++> is not a privileged program, unlike
++<B
++CLASS="COMMAND"
++>traceroute</B
++>, <B
++CLASS="COMMAND"
++>ping</B
++> and other beasts of this kind.
++<B
++CLASS="COMMAND"
++>tracepath</B
++> may be executed by everyone who has some access
++to network, enough to send UDP datagrams to investigated destination
++using given port.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN878"
++></A
++><H2
++>AVAILABILITY</H2
++><P
++><B
++CLASS="COMMAND"
++>tracepath</B
++> is part of <TT
++CLASS="FILENAME"
++>iputils</TT
++> package
++and the latest versions are  available in source form at
++<A
++HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
++TARGET="_top"
++>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
++>.</P
++></DIV
++><DIV
++CLASS="NAVFOOTER"
++><HR
++ALIGN="LEFT"
++WIDTH="100%"><TABLE
++SUMMARY="Footer navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++><A
++HREF="r691.html"
++ACCESSKEY="P"
++>Prev</A
++></TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++><A
++HREF="index.html"
++ACCESSKEY="H"
++>Home</A
++></TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++><A
++HREF="r884.html"
++ACCESSKEY="N"
++>Next</A
++></TD
++></TR
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++>rarpd</TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++>&nbsp;</TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++>traceroute6</TD
++></TR
++></TABLE
++></DIV
++></BODY
++></HTML
++>
+\ No newline at end of file
+diff -Naur iputils-s20101006.orig/doc/r884.html iputils-s20101006/doc/r884.html
+--- iputils-s20101006.orig/doc/r884.html	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/r884.html	2011-01-08 20:09:49.606677412 -0500
+@@ -0,0 +1,315 @@
++<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
++<HTML
++><HEAD
++><TITLE
++>traceroute6</TITLE
++><META
++NAME="GENERATOR"
++CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
++REL="HOME"
++TITLE="System Manager's Manual: iputils"
++HREF="index.html"><LINK
++REL="PREVIOUS"
++TITLE="tracepath"
++HREF="r790.html"><LINK
++REL="NEXT"
++TITLE="tftpd"
++HREF="r949.html"></HEAD
++><BODY
++CLASS="REFENTRY"
++BGCOLOR="#FFFFFF"
++TEXT="#000000"
++LINK="#0000FF"
++VLINK="#840084"
++ALINK="#0000FF"
++><DIV
++CLASS="NAVHEADER"
++><TABLE
++SUMMARY="Header navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TH
++COLSPAN="3"
++ALIGN="center"
++>System Manager's Manual: iputils</TH
++></TR
++><TR
++><TD
++WIDTH="10%"
++ALIGN="left"
++VALIGN="bottom"
++><A
++HREF="r790.html"
++ACCESSKEY="P"
++>Prev</A
++></TD
++><TD
++WIDTH="80%"
++ALIGN="center"
++VALIGN="bottom"
++></TD
++><TD
++WIDTH="10%"
++ALIGN="right"
++VALIGN="bottom"
++><A
++HREF="r949.html"
++ACCESSKEY="N"
++>Next</A
++></TD
++></TR
++></TABLE
++><HR
++ALIGN="LEFT"
++WIDTH="100%"></DIV
++><H1
++><A
++NAME="TRACEROUTE6"
++></A
++>traceroute6</H1
++><DIV
++CLASS="REFNAMEDIV"
++><A
++NAME="AEN889"
++></A
++><H2
++>Name</H2
++>traceroute6&nbsp;--&nbsp;traces path to a network host</DIV
++><DIV
++CLASS="REFSYNOPSISDIV"
++><A
++NAME="AEN892"
++></A
++><H2
++>Synopsis</H2
++><P
++><B
++CLASS="COMMAND"
++>traceroute6</B
++>  [<CODE
++CLASS="OPTION"
++>-dnrvV</CODE
++>] [-i <TT
++CLASS="REPLACEABLE"
++><I
++>interface</I
++></TT
++>] [-m <TT
++CLASS="REPLACEABLE"
++><I
++>max_ttl</I
++></TT
++>] [-p <TT
++CLASS="REPLACEABLE"
++><I
++>port</I
++></TT
++>] [-q <TT
++CLASS="REPLACEABLE"
++><I
++>max_probes</I
++></TT
++>] [-s <TT
++CLASS="REPLACEABLE"
++><I
++>source</I
++></TT
++>] [-w <TT
++CLASS="REPLACEABLE"
++><I
++>wait time</I
++></TT
++>] {<TT
++CLASS="REPLACEABLE"
++><I
++>destination</I
++></TT
++>} [<TT
++CLASS="REPLACEABLE"
++><I
++>size</I
++></TT
++>]</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN913"
++></A
++><H2
++>DESCRIPTION</H2
++><P
++>Description can be found in 
++<SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>traceroute</SPAN
++>(8)</SPAN
++>,
++all the references to IP replaced to IPv6. It is needless to copy
++the description from there.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN919"
++></A
++><H2
++>SEE ALSO</H2
++><P
++><SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>traceroute</SPAN
++>(8)</SPAN
++>,
++<SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>tracepath</SPAN
++>(8)</SPAN
++>,
++<SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>ping</SPAN
++>(8)</SPAN
++>.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN931"
++></A
++><H2
++>HISTORY</H2
++><P
++>This program has long history. Author of <B
++CLASS="COMMAND"
++>traceroute</B
++>
++is Van Jacobson and it first appeared in 1988. This clone is
++based on a port of <B
++CLASS="COMMAND"
++>traceroute</B
++> to IPv6 published
++in NRL IPv6 distribution in 1996. In turn, it was ported
++to Linux by Pedro Roque. After this it was kept in sync by    
++<A
++HREF="mailto:kuznet@ms2.inr.ac.ru"
++TARGET="_top"
++>Alexey Kuznetsov
++&lt;kuznet@ms2.inr.ac.ru&gt;</A
++>. And eventually entered
++<B
++CLASS="COMMAND"
++>iputils</B
++> package.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN938"
++></A
++><H2
++>SECURITY</H2
++><P
++><B
++CLASS="COMMAND"
++>tracepath6</B
++> requires <CODE
++CLASS="CONSTANT"
++>CAP_NET_RAWIO</CODE
++> capability
++to be executed. It is safe to be used as set-uid root.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN943"
++></A
++><H2
++>AVAILABILITY</H2
++><P
++><B
++CLASS="COMMAND"
++>traceroute6</B
++> is part of <TT
++CLASS="FILENAME"
++>iputils</TT
++> package
++and the latest versions are  available in source form at
++<A
++HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
++TARGET="_top"
++>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
++>.</P
++></DIV
++><DIV
++CLASS="NAVFOOTER"
++><HR
++ALIGN="LEFT"
++WIDTH="100%"><TABLE
++SUMMARY="Footer navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++><A
++HREF="r790.html"
++ACCESSKEY="P"
++>Prev</A
++></TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++><A
++HREF="index.html"
++ACCESSKEY="H"
++>Home</A
++></TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++><A
++HREF="r949.html"
++ACCESSKEY="N"
++>Next</A
++></TD
++></TR
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++>tracepath</TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++>&nbsp;</TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++>tftpd</TD
++></TR
++></TABLE
++></DIV
++></BODY
++></HTML
++>
+\ No newline at end of file
+diff -Naur iputils-s20101006.orig/doc/r949.html iputils-s20101006/doc/r949.html
+--- iputils-s20101006.orig/doc/r949.html	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/r949.html	2011-01-08 20:09:49.614834740 -0500
+@@ -0,0 +1,376 @@
++<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
++<HTML
++><HEAD
++><TITLE
++>tftpd</TITLE
++><META
++NAME="GENERATOR"
++CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
++REL="HOME"
++TITLE="System Manager's Manual: iputils"
++HREF="index.html"><LINK
++REL="PREVIOUS"
++TITLE="traceroute6"
++HREF="r884.html"><LINK
++REL="NEXT"
++TITLE="rdisc"
++HREF="r1022.html"></HEAD
++><BODY
++CLASS="REFENTRY"
++BGCOLOR="#FFFFFF"
++TEXT="#000000"
++LINK="#0000FF"
++VLINK="#840084"
++ALINK="#0000FF"
++><DIV
++CLASS="NAVHEADER"
++><TABLE
++SUMMARY="Header navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TH
++COLSPAN="3"
++ALIGN="center"
++>System Manager's Manual: iputils</TH
++></TR
++><TR
++><TD
++WIDTH="10%"
++ALIGN="left"
++VALIGN="bottom"
++><A
++HREF="r884.html"
++ACCESSKEY="P"
++>Prev</A
++></TD
++><TD
++WIDTH="80%"
++ALIGN="center"
++VALIGN="bottom"
++></TD
++><TD
++WIDTH="10%"
++ALIGN="right"
++VALIGN="bottom"
++><A
++HREF="r1022.html"
++ACCESSKEY="N"
++>Next</A
++></TD
++></TR
++></TABLE
++><HR
++ALIGN="LEFT"
++WIDTH="100%"></DIV
++><H1
++><A
++NAME="TFTPD"
++></A
++>tftpd</H1
++><DIV
++CLASS="REFNAMEDIV"
++><A
++NAME="AEN954"
++></A
++><H2
++>Name</H2
++>tftpd&nbsp;--&nbsp;Trivial File Transfer Protocol server</DIV
++><DIV
++CLASS="REFSYNOPSISDIV"
++><A
++NAME="AEN957"
++></A
++><H2
++>Synopsis</H2
++><P
++><B
++CLASS="COMMAND"
++>tftpd</B
++>  {<TT
++CLASS="REPLACEABLE"
++><I
++>directory</I
++></TT
++>}</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN962"
++></A
++><H2
++>DESCRIPTION</H2
++><P
++><B
++CLASS="COMMAND"
++>tftpd</B
++> is a server which supports the DARPA
++Trivial File Transfer Protocol
++(<A
++HREF="ftp://ftp.isi.edu/in-notes/rfc1350.txt"
++TARGET="_top"
++>RFC1350</A
++>).
++The TFTP server is started
++by <SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>inetd</SPAN
++>(8)</SPAN
++>.</P
++><P
++><TT
++CLASS="REPLACEABLE"
++><I
++>directory</I
++></TT
++> is required argument; if it is not given
++<B
++CLASS="COMMAND"
++>tftpd</B
++> aborts. This path is prepended to any file name requested
++via TFTP protocol, effectively chrooting <B
++CLASS="COMMAND"
++>tftpd</B
++> to this directory.
++File names are validated not to escape out of this directory, however
++administrator may configure such escape using symbolic links.</P
++><P
++>It is in difference of variants of <B
++CLASS="COMMAND"
++>tftpd</B
++> usually distributed
++with unix-like systems, which take a list of directories and match
++file names to start from one of given prefixes or to some random
++default, when no arguments were given. There are two reasons not to
++behave in this way: first, it is inconvenient, clients are not expected
++to know something about layout of filesystem on server host.
++And second, TFTP protocol is not a tool for browsing of server's filesystem,
++it is just an agent allowing to boot dumb clients. </P
++><P
++>In the case when <B
++CLASS="COMMAND"
++>tftpd</B
++> is used together with
++<A
++HREF="r691.html"
++><SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>rarpd</SPAN
++>(8)</SPAN
++></A
++>,
++tftp directories in these services should coincide and it is expected
++that each client booted via TFTP has boot image corresponding
++its IP address with an architecture suffix following Sun Microsystems
++conventions. See 
++<A
++HREF="r691.html"
++><SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>rarpd</SPAN
++>(8)</SPAN
++></A
++>
++for more details.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN986"
++></A
++><H2
++>SECURITY</H2
++><P
++>TFTP protocol does not provide any authentication.
++Due to this capital flaw <B
++CLASS="COMMAND"
++>tftpd</B
++> is not able to restrict
++access to files and will allow only publically readable
++files to be accessed. Files may be written only if they already
++exist and are publically writable.</P
++><P
++>Impact is evident, directory exported via TFTP <SPAN
++CLASS="emphasis"
++><I
++CLASS="EMPHASIS"
++>must not</I
++></SPAN
++>
++contain sensitive information of any kind, everyone is allowed
++to read it as soon as a client is allowed. Boot images do not contain
++such information as rule, however you should think twice before
++publishing f.e. Cisco IOS config files via TFTP, they contain
++<SPAN
++CLASS="emphasis"
++><I
++CLASS="EMPHASIS"
++>unencrypted</I
++></SPAN
++> passwords and may contain some information
++about the network, which you were not going to make public.</P
++><P
++>The <B
++CLASS="COMMAND"
++>tftpd</B
++> server should be executed by <B
++CLASS="COMMAND"
++>inetd</B
++>
++with dropped root privileges, namely with a user ID giving minimal
++access to files published in tftp directory. If it is executed
++as superuser occasionally, <B
++CLASS="COMMAND"
++>tftpd</B
++> drops its UID and GID
++to 65534, which is most likely not the thing which you expect.
++However, this is not very essential; remember, only files accessible
++for everyone can be read or written via TFTP.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN997"
++></A
++><H2
++>SEE ALSO</H2
++><P
++><A
++HREF="r691.html"
++><SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>rarpd</SPAN
++>(8)</SPAN
++></A
++>,
++<SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>tftp</SPAN
++>(1)</SPAN
++>,
++<SPAN
++CLASS="CITEREFENTRY"
++><SPAN
++CLASS="REFENTRYTITLE"
++>inetd</SPAN
++>(8)</SPAN
++>.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN1010"
++></A
++><H2
++>HISTORY</H2
++><P
++>The <B
++CLASS="COMMAND"
++>tftpd</B
++> command appeared in 4.2BSD. The source in iputils
++is cleaned up both syntactically (ANSIized) and semantically (UDP socket IO).</P
++><P
++>It is distributed with iputils mostly as good demo of an interesting feature
++(<CODE
++CLASS="CONSTANT"
++>MSG_CONFIRM</CODE
++>) allowing to boot long images by dumb clients
++not answering ARP requests until they are finally booted.
++However, this is full functional and can be used in production.</P
++></DIV
++><DIV
++CLASS="REFSECT1"
++><A
++NAME="AEN1016"
++></A
++><H2
++>AVAILABILITY</H2
++><P
++><B
++CLASS="COMMAND"
++>tftpd</B
++> is part of <TT
++CLASS="FILENAME"
++>iputils</TT
++> package
++and the latest versions are  available in source form at
++<A
++HREF="http://www.skbuff.net/iputils/iputils-current.tar.bz2"
++TARGET="_top"
++>http://www.skbuff.net/iputils/iputils-current.tar.bz2</A
++>.</P
++></DIV
++><DIV
++CLASS="NAVFOOTER"
++><HR
++ALIGN="LEFT"
++WIDTH="100%"><TABLE
++SUMMARY="Footer navigation table"
++WIDTH="100%"
++BORDER="0"
++CELLPADDING="0"
++CELLSPACING="0"
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++><A
++HREF="r884.html"
++ACCESSKEY="P"
++>Prev</A
++></TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++><A
++HREF="index.html"
++ACCESSKEY="H"
++>Home</A
++></TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++><A
++HREF="r1022.html"
++ACCESSKEY="N"
++>Next</A
++></TD
++></TR
++><TR
++><TD
++WIDTH="33%"
++ALIGN="left"
++VALIGN="top"
++>traceroute6</TD
++><TD
++WIDTH="34%"
++ALIGN="center"
++VALIGN="top"
++>&nbsp;</TD
++><TD
++WIDTH="33%"
++ALIGN="right"
++VALIGN="top"
++>rdisc</TD
++></TR
++></TABLE
++></DIV
++></BODY
++></HTML
++>
+\ No newline at end of file
+diff -Naur iputils-s20101006.orig/doc/rarpd.8 iputils-s20101006/doc/rarpd.8
+--- iputils-s20101006.orig/doc/rarpd.8	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/rarpd.8	2011-01-08 20:09:51.270811811 -0500
+@@ -0,0 +1,84 @@
++.\" This manpage has been automatically generated by docbook2man 
++.\" from a DocBook document.  This tool can be found at:
++.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
++.\" Please send any bug reports, improvements, comments, patches, 
++.\" etc. to Steve Cheng <steve@ggi-project.org>.
++.TH "RARPD" "8" "08 January 2011" "iputils-101006" "System Manager's Manual: iputils"
++.SH NAME
++rarpd \- answer RARP REQUESTs
++.SH SYNOPSIS
++
++\fBarping\fR [\fB-aAvde\fR] [\fB-b \fIbootdir\fB\fR] [\fB\fIinterface\fB\fR]
++
++.SH "DESCRIPTION"
++.PP
++Listens
++RARP
++requests from clients. Provided MAC address of client
++is found in \fI/etc/ethers\fR database and
++obtained host name is resolvable to an IP address appropriate
++for attached network, \fBrarpd\fR answers to client with RARPD
++reply carrying an IP address.
++.PP
++To allow multiple boot servers on the network \fBrarpd\fR
++optionally checks for presence Sun-like bootable image in TFTP directory.
++It should have form \fBHexadecimal_IP.ARCH\fR, f.e. to load
++sparc 193.233.7.98 \fIC1E90762.SUN4M\fR is linked to
++an image appropriate for SUM4M in directory \fI/etc/tftpboot\fR.
++.SH "WARNING"
++.PP
++This facility is deeply obsoleted by
++BOOTP
++and later
++DHCP protocols.
++However, some clients really still need this to boot.
++.SH "OPTIONS"
++.TP
++\fB-a\fR
++Listen on all the interfaces. Currently it is an internal
++option, its function is overridden with \fIinterface\fR
++argument. It should not be used.
++.TP
++\fB-A\fR
++Listen not only RARP but also ARP messages, some rare clients
++use ARP by some unknown reason.
++.TP
++\fB-v\fR
++Be verbose.
++.TP
++\fB-d\fR
++Debug mode. Do not go to background.
++.TP
++\fB-e\fR
++Do not check for presence of a boot image, reply if MAC address
++resolves to a valid IP address using \fI/etc/ethers\fR
++database and DNS. 
++.TP
++\fB-b \fIbootdir\fB\fR
++TFTP boot directory. Default is \fI/etc/tftpboot\fR
++.SH "SEE ALSO"
++.PP
++\fBarping\fR(8),
++\fBtftpd\fR(8).
++.SH "AUTHOR"
++.PP
++\fBrarpd\fR was written by
++Alexey Kuznetsov
++<kuznet@ms2.inr.ac.ru>.
++It is now maintained by
++YOSHIFUJI Hideaki
++<yoshfuji@skbuff.net>.
++.SH "SECURITY"
++.PP
++\fBrarpd\fR requires CAP_NET_RAWIO capability
++to listen and send RARP and ARP packets. It also needs CAP_NET_ADMIN
++to give to kernel hint for ARP resolution; this is not strictly required,
++but some (most of, to be more exact) clients are so badly broken that
++are not able to answer ARP before they are finally booted. This is
++not wonderful taking into account that clients using RARPD in 2002
++are all unsupported relic creatures of 90's and even earlier.
++.SH "AVAILABILITY"
++.PP
++\fBrarpd\fR is part of \fIiputils\fR package
++and the latest versions are  available in source form at
++http://www.skbuff.net/iputils/iputils-current.tar.bz2.
+diff -Naur iputils-s20101006.orig/doc/rdisc.8 iputils-s20101006/doc/rdisc.8
+--- iputils-s20101006.orig/doc/rdisc.8	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/rdisc.8	2011-01-08 20:09:51.527155543 -0500
+@@ -0,0 +1,110 @@
++.\" This manpage has been automatically generated by docbook2man 
++.\" from a DocBook document.  This tool can be found at:
++.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
++.\" Please send any bug reports, improvements, comments, patches, 
++.\" etc. to Steve Cheng <steve@ggi-project.org>.
++.TH "RDISC" "8" "08 January 2011" "iputils-101006" "System Manager's Manual: iputils"
++.SH NAME
++rdisc \- network router discovery daemon
++.SH SYNOPSIS
++
++\fBrdisc\fR [\fB-abdfstvV\fR] [\fB\fIsend_address\fB\fR] [\fB\fIreceive_address\fB\fR]
++
++.SH "DESCRIPTION"
++.PP
++\fBrdisc\fR implements client side of the ICMP router discover protocol.
++\fBrdisc\fR is invoked at boot time to populate the network
++routing tables with default routes. 
++.PP
++\fBrdisc\fR listens on the ALL_HOSTS (224.0.0.1) multicast address
++(or \fIreceive_address\fR provided it is given) 
++for ROUTER_ADVERTISE messages from routers. The received
++messages are handled by first ignoring those listed router addresses
++with which the host does not share a network. Among the remaining addresses
++the ones with the highest preference are selected as default routers
++and a default route is entered in the kernel routing table
++for each one of them.
++.PP
++Optionally, \fBrdisc\fR can avoid waiting for routers to announce 
++themselves by sending out a few ROUTER_SOLICITATION messages
++to the ALL_ROUTERS (224.0.0.2) multicast address 
++(or \fIsend_address\fR provided it is given) 
++when it is started.
++.PP
++A timer is associated with each router address and the address will
++no longer be considered for inclusion in the the routing tables if the 
++timer expires before a new 
++\fBadvertise\fR message is received from the router.
++The address will also be excluded from consideration if the host receives an 
++\fBadvertise\fR
++message with the preference being maximally negative.
++.PP
++Server side of router discovery protocol is supported by Cisco IOS
++and by any more or less complete UNIX routing daemon, f.e \fBgated\fR.
++.SH "OPTIONS"
++.TP
++\fB-a\fR
++Accept all routers independently of the preference they have in their 
++\fBadvertise\fR messages.
++Normally \fBrdisc\fR only accepts (and enters in the kernel routing
++tables) the router or routers with the highest preference.
++.TP
++\fB-b\fR
++Opposite to \fB-a\fR, i.e. install only router with the best
++preference value. It is default behaviour.
++.TP
++\fB-d\fR
++Send debugging messages to syslog.
++.TP
++\fB-f\fR
++Run \fBrdisc\fR forever even if no routers are found.
++Normally \fBrdisc\fR gives up if it has not received any 
++\fBadvertise\fR message after after soliciting three times,
++in which case it exits with a non-zero exit code.
++If \fB-f\fR is not specified in the first form then 
++\fB-s\fR must be specified.
++.TP
++\fB-s\fR
++Send three \fBsolicitation\fR messages initially to quickly discover
++the routers when the system is booted.
++When \fB-s\fR is specified \fBrdisc\fR
++exits with a non-zero exit code if it can not find any routers.
++This can be overridden with the \fB-f\fR option.
++.TP
++\fB-t\fR
++Test mode. Do not go to background.
++.TP
++\fB-v\fR
++Be verbose i.e. send lots of debugging messages to syslog.
++.TP
++\fB-V\fR
++Print version and exit.
++.SH "HISTORY"
++.PP
++This program was developed by Sun Microsystems (see copyright
++notice in source file). It was ported to Linux by
++Alexey Kuznetsov
++<kuznet@ms2.inr.ac.ru>.
++It is now maintained by
++YOSHIFUJI Hideaki
++<yoshfuji@skbuff.net>.
++.SH "SEE ALSO"
++.PP
++\fBicmp\fR(7),
++\fBinet\fR(7),
++\fBping\fR(8).
++.SH "REFERENCES"
++.PP
++Deering, S.E.,ed "ICMP Router Discovery Messages",
++RFC1256, Network Information Center, SRI International,
++Menlo Park, Calif., September 1991.
++.SH "SECURITY"
++.PP
++\fBrdisc\fR requires CAP_NET_RAWIO to listen
++and send ICMP messages and capability CAP_NET_ADMIN
++to update routing tables. 
++.SH "AVAILABILITY"
++.PP
++\fBrdisc\fR is part of \fIiputils\fR package
++and the latest versions are  available in source form at
++http://www.skbuff.net/iputils/iputils-current.tar.bz2.
+diff -Naur iputils-s20101006.orig/doc/tftpd.8 iputils-s20101006/doc/tftpd.8
+--- iputils-s20101006.orig/doc/tftpd.8	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/tftpd.8	2011-01-08 20:09:51.723407498 -0500
+@@ -0,0 +1,85 @@
++.\" This manpage has been automatically generated by docbook2man 
++.\" from a DocBook document.  This tool can be found at:
++.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
++.\" Please send any bug reports, improvements, comments, patches, 
++.\" etc. to Steve Cheng <steve@ggi-project.org>.
++.TH "TFTPD" "8" "08 January 2011" "iputils-101006" "System Manager's Manual: iputils"
++.SH NAME
++tftpd \- Trivial File Transfer Protocol server
++.SH SYNOPSIS
++
++\fBtftpd\fR \fB\fIdirectory\fB\fR
++
++.SH "DESCRIPTION"
++.PP
++\fBtftpd\fR is a server which supports the DARPA
++Trivial File Transfer Protocol
++(RFC1350).
++The TFTP server is started
++by \fBinetd\fR(8).
++.PP
++\fIdirectory\fR is required argument; if it is not given
++\fBtftpd\fR aborts. This path is prepended to any file name requested
++via TFTP protocol, effectively chrooting \fBtftpd\fR to this directory.
++File names are validated not to escape out of this directory, however
++administrator may configure such escape using symbolic links.
++.PP
++It is in difference of variants of \fBtftpd\fR usually distributed
++with unix-like systems, which take a list of directories and match
++file names to start from one of given prefixes or to some random
++default, when no arguments were given. There are two reasons not to
++behave in this way: first, it is inconvenient, clients are not expected
++to know something about layout of filesystem on server host.
++And second, TFTP protocol is not a tool for browsing of server's filesystem,
++it is just an agent allowing to boot dumb clients. 
++.PP
++In the case when \fBtftpd\fR is used together with
++\fBrarpd\fR(8),
++tftp directories in these services should coincide and it is expected
++that each client booted via TFTP has boot image corresponding
++its IP address with an architecture suffix following Sun Microsystems
++conventions. See 
++\fBrarpd\fR(8)
++for more details.
++.SH "SECURITY"
++.PP
++TFTP protocol does not provide any authentication.
++Due to this capital flaw \fBtftpd\fR is not able to restrict
++access to files and will allow only publically readable
++files to be accessed. Files may be written only if they already
++exist and are publically writable.
++.PP
++Impact is evident, directory exported via TFTP \fBmust not\fR
++contain sensitive information of any kind, everyone is allowed
++to read it as soon as a client is allowed. Boot images do not contain
++such information as rule, however you should think twice before
++publishing f.e. Cisco IOS config files via TFTP, they contain
++\fBunencrypted\fR passwords and may contain some information
++about the network, which you were not going to make public.
++.PP
++The \fBtftpd\fR server should be executed by \fBinetd\fR
++with dropped root privileges, namely with a user ID giving minimal
++access to files published in tftp directory. If it is executed
++as superuser occasionally, \fBtftpd\fR drops its UID and GID
++to 65534, which is most likely not the thing which you expect.
++However, this is not very essential; remember, only files accessible
++for everyone can be read or written via TFTP.
++.SH "SEE ALSO"
++.PP
++\fBrarpd\fR(8),
++\fBtftp\fR(1),
++\fBinetd\fR(8).
++.SH "HISTORY"
++.PP
++The \fBtftpd\fR command appeared in 4.2BSD. The source in iputils
++is cleaned up both syntactically (ANSIized) and semantically (UDP socket IO).
++.PP
++It is distributed with iputils mostly as good demo of an interesting feature
++(MSG_CONFIRM) allowing to boot long images by dumb clients
++not answering ARP requests until they are finally booted.
++However, this is full functional and can be used in production.
++.SH "AVAILABILITY"
++.PP
++\fBtftpd\fR is part of \fIiputils\fR package
++and the latest versions are  available in source form at
++http://www.skbuff.net/iputils/iputils-current.tar.bz2.
+diff -Naur iputils-s20101006.orig/doc/tracepath.8 iputils-s20101006/doc/tracepath.8
+--- iputils-s20101006.orig/doc/tracepath.8	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/tracepath.8	2011-01-08 20:09:52.154780955 -0500
+@@ -0,0 +1,97 @@
++.\" This manpage has been automatically generated by docbook2man 
++.\" from a DocBook document.  This tool can be found at:
++.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
++.\" Please send any bug reports, improvements, comments, patches, 
++.\" etc. to Steve Cheng <steve@ggi-project.org>.
++.TH "TRACEPATH" "8" "08 January 2011" "iputils-101006" "System Manager's Manual: iputils"
++.SH NAME
++tracepath, tracepath6 \- traces path to a network host discovering MTU along this path
++.SH SYNOPSIS
++
++\fBtracepath\fR [\fB-n\fR] [\fB-b\fR] [\fB-l \fIpktlen\fB\fR] \fB\fIdestination\fB\fR [\fB\fIport\fB\fR]
++
++.SH "DESCRIPTION"
++.PP
++It traces path to \fIdestination\fR discovering MTU along this path.
++It uses UDP port \fIport\fR or some random port.
++It is similar to \fBtraceroute\fR, only does not require superuser
++privileges and has no fancy options.
++.PP
++\fBtracepath6\fR is good replacement for \fBtraceroute6\fR
++and classic example of application of Linux error queues.
++The situation with IPv4 is worse, because commercial
++IP routers do not return enough information in icmp error messages.
++Probably, it will change, when they will be updated.
++For now it uses Van Jacobson's trick, sweeping a range
++of UDP ports to maintain trace history.
++.SH "OPTIONS"
++.TP
++\fB-n\fR
++Print primarily IP addresses numerically.
++.TP
++\fB-b\fR
++Print both of host names and IP addresses.
++.TP
++\fB-l\fR
++Sets the initial packet length to \fIpktlen\fR instead of
++65536 for \fBtracepath\fR or 128000 for \fBtracepath6\fR.
++.SH "OUTPUT"
++.PP
++
++.nf
++root@mops:~ # tracepath6 3ffe:2400:0:109::2
++ 1?: [LOCALHOST]                              pmtu 1500
++ 1:  dust.inr.ac.ru                   0.411ms
++ 2:  dust.inr.ac.ru        asymm  1   0.390ms pmtu 1480
++ 2:  3ffe:2400:0:109::2               463.514ms reached
++     Resume: pmtu 1480 hops 2 back 2
++.fi
++.PP
++The first column shows TTL of the probe, followed by colon.
++Usually value of TTL is obtained from reply from network,
++but sometimes reply does not contain necessary information and
++we have to guess it. In this case the number is followed by ?.
++.PP
++The second column shows the network hop, which replied to the probe.
++It is either address of router or word [LOCALHOST], if
++the probe was not sent to the network.
++.PP
++The rest of line shows miscellaneous information about path to
++the correspinding hetwork hop. As rule it contains value of RTT.
++Additionally, it can show Path MTU, when it changes.
++If the path is asymmetric
++or the probe finishes before it reach prescribed hop, difference
++between number of hops in forward and backward direction is shown
++following keyword async. This information is not reliable.
++F.e. the third line shows asymmetry of 1, it is because the first probe
++with TTL of 2 was rejected at the first hop due to Path MTU Discovery.
++.PP
++The last line summarizes information about all the path to the destination,
++it shows detected Path MTU, amount of hops to the destination and our
++guess about amount of hops from the destination to us, which can be
++different when the path is asymmetric.
++.SH "SEE ALSO"
++.PP
++\fBtraceroute\fR(8),
++\fBtraceroute6\fR(8),
++\fBping\fR(8).
++.SH "AUTHOR"
++.PP
++\fBtracepath\fR was written by
++Alexey Kuznetsov
++<kuznet@ms2.inr.ac.ru>.
++.SH "SECURITY"
++.PP
++No security issues.
++.PP
++This lapidary deserves to be elaborated.
++\fBtracepath\fR is not a privileged program, unlike
++\fBtraceroute\fR, \fBping\fR and other beasts of this kind.
++\fBtracepath\fR may be executed by everyone who has some access
++to network, enough to send UDP datagrams to investigated destination
++using given port.
++.SH "AVAILABILITY"
++.PP
++\fBtracepath\fR is part of \fIiputils\fR package
++and the latest versions are  available in source form at
++http://www.skbuff.net/iputils/iputils-current.tar.bz2.
+diff -Naur iputils-s20101006.orig/doc/traceroute6.8 iputils-s20101006/doc/traceroute6.8
+--- iputils-s20101006.orig/doc/traceroute6.8	1969-12-31 19:00:00.000000000 -0500
++++ iputils-s20101006/doc/traceroute6.8	2011-01-08 20:09:52.114781859 -0500
+@@ -0,0 +1,42 @@
++.\" This manpage has been automatically generated by docbook2man 
++.\" from a DocBook document.  This tool can be found at:
++.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
++.\" Please send any bug reports, improvements, comments, patches, 
++.\" etc. to Steve Cheng <steve@ggi-project.org>.
++.TH "TRACEROUTE6" "8" "08 January 2011" "iputils-101006" "System Manager's Manual: iputils"
++.SH NAME
++traceroute6 \- traces path to a network host
++.SH SYNOPSIS
++
++\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]
++
++.SH "DESCRIPTION"
++.PP
++Description can be found in 
++\fBtraceroute\fR(8),
++all the references to IP replaced to IPv6. It is needless to copy
++the description from there.
++.SH "SEE ALSO"
++.PP
++\fBtraceroute\fR(8),
++\fBtracepath\fR(8),
++\fBping\fR(8).
++.SH "HISTORY"
++.PP
++This program has long history. Author of \fBtraceroute\fR
++is Van Jacobson and it first appeared in 1988. This clone is
++based on a port of \fBtraceroute\fR to IPv6 published
++in NRL IPv6 distribution in 1996. In turn, it was ported
++to Linux by Pedro Roque. After this it was kept in sync by    
++Alexey Kuznetsov
++<kuznet@ms2.inr.ac.ru>. And eventually entered
++\fBiputils\fR package.
++.SH "SECURITY"
++.PP
++\fBtracepath6\fR requires CAP_NET_RAWIO capability
++to be executed. It is safe to be used as set-uid root.
++.SH "AVAILABILITY"
++.PP
++\fBtraceroute6\fR is part of \fIiputils\fR package
++and the latest versions are  available in source form at
++http://www.skbuff.net/iputils/iputils-current.tar.bz2.
Index: patches/iputils-s20101006-fixes-1.patch
===================================================================
--- patches/iputils-s20101006-fixes-1.patch	(revision ecc1136c03ab82d05060a4dfccf51599109cc687)
+++ patches/iputils-s20101006-fixes-1.patch	(revision ecc1136c03ab82d05060a4dfccf51599109cc687)
@@ -0,0 +1,162 @@
+Submitted By: Joe Ciccone <jciccone@gmail.com>
+Date: 2011-01-08
+Initial Package Version: s20100418
+Upstream Status: Unknown
+Origin: Unknown
+Description: Contains Fixes for Various Issues
+
+diff -Naur iputils-s20101006.orig/Makefile iputils-s20101006/Makefile
+--- iputils-s20101006.orig/Makefile	2010-10-06 07:59:20.000000000 -0400
++++ iputils-s20101006/Makefile	2011-01-08 20:06:05.039019429 -0500
+@@ -16,7 +16,7 @@
+ CCOPT=-D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall -g
+ CFLAGS=$(CCOPT) $(GLIBCFIX) $(DEFINES) 
+ 
+-IPV4_TARGETS=tracepath ping clockdiff rdisc arping tftpd rarpd
++IPV4_TARGETS=tracepath ping arping clockdiff
+ IPV6_TARGETS=tracepath6 traceroute6 ping6
+ TARGETS=$(IPV4_TARGETS) $(IPV6_TARGETS)
+ 
+diff -Naur iputils-s20101006.orig/arping.c iputils-s20101006/arping.c
+--- iputils-s20101006.orig/arping.c	2010-10-06 07:59:20.000000000 -0400
++++ iputils-s20101006/arping.c	2011-01-08 20:06:05.039019429 -0500
+@@ -182,12 +182,17 @@
+ 	if (start.tv_sec==0)
+ 		start = tv;
+ 
+-	if (count-- == 0 || (timeout && MS_TDIFF(tv,start) > timeout*1000 + 500))
++	if (timeout && MS_TDIFF(tv,start) > timeout*1000 + 500)
+ 		finish();
+ 
+-	if (last.tv_sec==0 || MS_TDIFF(tv,last) > 500) {
++	if ((!timeout) && (count == 0))
++		finish();
++
++	if ( count!=0  && (last.tv_sec==0 || MS_TDIFF(tv,last) > 500 ) ) {
+ 		send_pack(s, src, dst,
+ 			  (struct sockaddr_ll *)&me, (struct sockaddr_ll *)&he);
++		if (count >= 0)
++		    count--;
+ 		if (count == 0 && unsolicited)
+ 			finish();
+ 	}
+diff -Naur iputils-s20101006.orig/doc/Makefile iputils-s20101006/doc/Makefile
+--- iputils-s20101006.orig/doc/Makefile	2010-10-06 07:59:20.000000000 -0400
++++ iputils-s20101006/doc/Makefile	2011-01-08 20:06:05.039019429 -0500
+@@ -6,7 +6,7 @@
+ 
+ html: $(HTMLFILES) iputils.html
+ 
+-man: $(MANFILES)
++man: $(MANFILES) fix_sgml2man
+ 
+ # docbook scripts are incredibly dirty in the sense that they leak
+ # lots of some strange temporary junk directories and files.
+@@ -33,6 +33,9 @@
+ 	@set -e; cd tmp.db2man; nsgmls ../$< | sgmlspl ../docbook2man-spec.pl ;	mv $@ ..
+ 	@-rm -rf tmp.db2man
+ 
++fix_sgml2man:
++	@sed -i -e 's!\\fB\\fIdestination\\fB\\fR \[\\fB/\\fIport\\fB\\fR\]!\\fB\\fIdestination\\fB\\fR[\\fB/\\fIport\\fB\\fR]!g' tracepath.8
++
+ clean:
+ 	@rm -rf $(MANFILES) $(HTMLFILES) iputils.html tmp.db2html tmp.db2man
+ 
+diff -Naur iputils-s20101006.orig/doc/docbook2man-spec.pl iputils-s20101006/doc/docbook2man-spec.pl
+--- iputils-s20101006.orig/doc/docbook2man-spec.pl	2010-10-06 07:59:20.000000000 -0400
++++ iputils-s20101006/doc/docbook2man-spec.pl	2011-01-08 20:06:05.039019429 -0500
+@@ -428,7 +428,7 @@
+ 	output ' ';
+ 
+ 	if($_[0]->attribute('CHOICE')->value =~ /opt/i) {
+-		output '[ ';
++		output '[';
+ 	}
+ 	bold_on();
+ }
+@@ -441,7 +441,7 @@
+ 		font_off();
+ 	}
+ 	if($_[0]->attribute('CHOICE')->value =~ /opt/i) {
+-		output '] ';
++		output ']';
+ 	}
+ }
+ 
+diff -Naur iputils-s20101006.orig/ping.c iputils-s20101006/ping.c
+--- iputils-s20101006.orig/ping.c	2010-10-06 07:59:20.000000000 -0400
++++ iputils-s20101006/ping.c	2011-01-08 20:06:05.039019429 -0500
+@@ -250,7 +250,7 @@
+ 			if (argc == 1)
+ 				options |= F_NUMERIC;
+ 		} else {
+-			hp = gethostbyname(target);
++			hp = gethostbyname2(target, AF_INET);
+ 			if (!hp) {
+ 				fprintf(stderr, "ping: unknown host %s\n", target);
+ 				exit(2);
+@@ -883,9 +883,36 @@
+ 		case ICMP_SR_FAILED:
+ 			printf("Source Route Failed\n");
+ 			break;
++		case ICMP_NET_UNKNOWN:
++			printf("Destination Net Unknown\n");
++			break;
++		case ICMP_HOST_UNKNOWN:
++			printf("Destination Host Unknown\n");
++			break;
++		case ICMP_HOST_ISOLATED:
++			printf("Source Host Isolated\n");
++			break;
++		case ICMP_NET_ANO:
++			printf("Destination Net Prohibited\n");
++			break;
++		case ICMP_HOST_ANO:
++			printf("Destination Host Prohibited\n");
++			break;
++		case ICMP_NET_UNR_TOS:
++			printf("Destination Net Unreachable for Type of Service\n");
++			break;
++		case ICMP_HOST_UNR_TOS:
++			printf("Destination Host Unreachable for Type of Service\n");
++			break;
+ 		case ICMP_PKT_FILTERED:
+ 			printf("Packet filtered\n");
+ 			break;
++		case ICMP_PREC_VIOLATION:
++			printf("Precedence Violation\n");
++			break;
++		case ICMP_PREC_CUTOFF:
++			printf("Precedence Cutoff\n");
++			break;
+ 		default:
+ 			printf("Dest Unreachable, Bad Code: %d\n", code);
+ 			break;
+diff -Naur iputils-s20101006.orig/ping_common.c iputils-s20101006/ping_common.c
+--- iputils-s20101006.orig/ping_common.c	2010-10-06 07:59:20.000000000 -0400
++++ iputils-s20101006/ping_common.c	2011-01-08 20:06:05.039019429 -0500
+@@ -872,7 +872,8 @@
+ 		printf("%spipe %d", comma, pipesize);
+ 		comma = ", ";
+ 	}
+-	if (ntransmitted > 1 && (!interval || (options&(F_FLOOD|F_ADAPTIVE)))) {
++	if (ntransmitted > 1 && nreceived &&
++		(!interval || (options&(F_FLOOD|F_ADAPTIVE)))) {
+ 		int ipg = (1000000*(long long)tv.tv_sec+tv.tv_usec)/(ntransmitted-1);
+ 		printf("%sipg/ewma %d.%03d/%d.%03d ms",
+ 		       comma, ipg/1000, ipg%1000, rtt/8000, (rtt/8)%1000);
+diff -Naur iputils-s20101006.orig/tracepath.c iputils-s20101006/tracepath.c
+--- iputils-s20101006.orig/tracepath.c	2010-10-06 07:59:20.000000000 -0400
++++ iputils-s20101006/tracepath.c	2011-01-08 20:06:05.039019429 -0500
+@@ -338,9 +338,9 @@
+ 		base_port = atoi(p+1);
+ 	} else
+ 		base_port = 44444;
+-	he = gethostbyname(argv[0]);
++	he = gethostbyname2(argv[0], AF_INET);
+ 	if (he == NULL) {
+-		herror("gethostbyname");
++		herror("gethostbyname2");
+ 		exit(1);
+ 	}
+ 	memcpy(&target.sin_addr, he->h_addr, 4);
