Index: create.patch.sh
===================================================================
--- create.patch.sh (nonexistent)
+++ create.patch.sh (revision 5)
@@ -0,0 +1,15 @@
+#!/bin/sh
+
+VERSION=20210202
+
+tar --files-from=file.list -xJvf ../iputils-$VERSION.tar.xz
+mv iputils-$VERSION iputils-$VERSION-orig
+
+cp -rf ./iputils-$VERSION-new ./iputils-$VERSION
+
+diff --unified -Nr iputils-$VERSION-orig iputils-$VERSION > iputils-$VERSION-docbook-revert.patch
+
+mv iputils-$VERSION-docbook-revert.patch ../patches
+
+rm -rf ./iputils-$VERSION
+rm -rf ./iputils-$VERSION-orig
Property changes on: create.patch.sh
___________________________________________________________________
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Index: file.list
===================================================================
--- file.list (nonexistent)
+++ file.list (revision 5)
@@ -0,0 +1,12 @@
+iputils-20210202/doc/arping.xml
+iputils-20210202/doc/clockdiff.xml
+iputils-20210202/doc/custom-html.xsl
+iputils-20210202/doc/custom-man.xsl
+iputils-20210202/doc/meson.build
+iputils-20210202/doc/ninfod.xml
+iputils-20210202/doc/ping.xml
+iputils-20210202/doc/rarpd.xml
+iputils-20210202/doc/rdisc.xml
+iputils-20210202/doc/tftpd.xml
+iputils-20210202/doc/tracepath.xml
+iputils-20210202/doc/traceroute6.xml
Index: iputils-20210202-new/doc/arping.xml
===================================================================
--- iputils-20210202-new/doc/arping.xml (nonexistent)
+++ iputils-20210202-new/doc/arping.xml (revision 5)
@@ -0,0 +1,266 @@
+<refentry xmlns:db="http://docbook.org/ns/docbook" version="5.0"
+xml:id="man.arping">
+
+ <refentryinfo>
+ <title>arping</title>
+ <productname>iputils</productname>
+ </refentryinfo>
+
+ <refmeta>
+ <refentrytitle>
+ <application>arping</application>
+ </refentrytitle>
+ <manvolnum>8</manvolnum>
+ <refmiscinfo class='manual'>iputils</refmiscinfo>
+ </refmeta>
+
+ <refnamediv>
+ <refname>arping</refname>
+ <refpurpose>send ARP REQUEST to a neighbour host</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv>
+ <cmdsynopsis sepchar=" ">
+ <command>arping</command>
+ <arg choice="opt" rep="norepeat">
+ <option>-AbDfhqUV</option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-c
+ <replaceable>count</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-w
+ <replaceable>deadline</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-i
+ <replaceable>interval</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-s
+ <replaceable>source</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-I
+ <replaceable>interface</replaceable></option>
+ </arg>
+ <arg choice="req" rep="norepeat">destination</arg>
+ </cmdsynopsis>
+ </refsynopsisdiv>
+
+ <refsection>
+ <info>
+ <title>DESCRIPTION</title>
+ </info>
+ <para>Ping
+ <emphasis remap="I">destination</emphasis> on device
+ <emphasis remap="I">interface</emphasis> by ARP packets, using
+ source address
+ <emphasis remap="I">source</emphasis>.</para>
+ </refsection>
+
+ <refsection>
+ <info>
+ <title>OPTIONS</title>
+ </info>
+ <variablelist remap='TP'>
+ <varlistentry>
+ <term>
+ <option>-A</option>
+ </term>
+ <listitem>
+ <para>The same as
+ <option>-U</option>, but ARP REPLY packets used instead
+ of ARP REQUEST.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-b</option>
+ </term>
+ <listitem>
+ <para>Send only MAC level broadcasts. Normally
+ <command>arping</command> starts from sending broadcast,
+ and switch to unicast after reply received.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-c
+ <replaceable>count</replaceable></option>
+ </term>
+ <listitem>
+ <para>Stop after sending
+ <emphasis remap="I">count</emphasis> ARP REQUEST packets.
+ With
+ <emphasis remap="I">deadline</emphasis> option, instead
+ wait for
+ <emphasis remap="I">count</emphasis> ARP REPLY packets, or
+ until the timeout expires.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-D</option>
+ </term>
+ <listitem>
+ <para>Duplicate address detection mode (DAD). See
+ RFC2131, 4.4.1. Returns 0, if DAD succeeded i.e. no
+ replies are received.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-f</option>
+ </term>
+ <listitem>
+ <para>Finish after the first reply confirming that target
+ is alive.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-I
+ <replaceable>interface</replaceable></option>
+ </term>
+ <listitem>
+ <para>Name of network device where to send ARP REQUEST
+ packets.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-h</option>
+ </term>
+ <listitem>
+ <para>Print help page and exit.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-q</option>
+ </term>
+ <listitem>
+ <para>Quiet output. Nothing is displayed.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-s
+ <replaceable>source</replaceable></option>
+ </term>
+ <listitem>
+ <para>IP source address to use in ARP packets. If this
+ option is absent, source address is:</para>
+ <variablelist remap='TP'>
+ <varlistentry>
+ <listitem>
+ <para>• In DAD mode (with option
+ <option>-D</option>) set to 0.0.0.0.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <listitem>
+ <para>• In Unsolicited ARP mode (with options
+ <option>-U</option> or
+ <option>-A</option>) set to
+ <emphasis remap='I'>destination</emphasis>.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <listitem>
+ <para>• Otherwise, it is calculated from routing
+ tables.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-U</option>
+ </term>
+ <listitem>
+ <para>Unsolicited ARP mode to update neighbours' ARP
+ caches. No replies are expected.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-V</option>
+ </term>
+ <listitem>
+ <para>Print version of the program and exit.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-w
+ <replaceable>deadline</replaceable></option>
+ </term>
+ <listitem>
+ <para>Specify a timeout, in seconds, before
+ <command>arping</command> exits regardless of how many
+ packets have been sent or received. In this case
+ <command>arping</command> does not stop after
+ <emphasis remap='I'>count</emphasis> packet are sent, it
+ waits either for
+ <emphasis remap='I'>deadline</emphasis> expire or until
+ <emphasis remap='I'>count</emphasis> probes are
+ answered.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-i
+ <replaceable>interval</replaceable></option>
+ </term>
+ <listitem>
+ <para>Specify an interval, in seconds, between
+ packets.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsection>
+
+ <refsect1 id='see_also'>
+ <title>SEE ALSO</title>
+ <para>
+ <citerefentry>
+ <refentrytitle>ping</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>,
+ <citerefentry>
+ <refentrytitle>clockdiff</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>,
+ <citerefentry>
+ <refentrytitle>tracepath</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>.</para>
+ </refsect1>
+
+ <refsect1 id='author'>
+ <title>AUTHOR</title>
+ <para>
+ <command>arping</command> was written by Alexey Kuznetsov
+ <kuznet@ms2.inr.ac.ru>.</para>
+ </refsect1>
+
+ <refsect1 id='security'>
+ <title>SECURITY</title>
+ <para>
+ <command>arping</command> requires CAP_NET_RAW 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.</para>
+ </refsect1>
+
+ <refsect1 id='availability'>
+ <title>AVAILABILITY</title>
+ <para>
+ <command>arping</command> is part of
+ <emphasis remap='I'>iputils</emphasis> package.</para>
+ </refsect1>
+</refentry>
Index: iputils-20210202-new/doc/clockdiff.xml
===================================================================
--- iputils-20210202-new/doc/clockdiff.xml (nonexistent)
+++ iputils-20210202-new/doc/clockdiff.xml (revision 5)
@@ -0,0 +1,211 @@
+<refentry xmlns:db="http://docbook.org/ns/docbook" version="5.0"
+xml:id="man.clockdiff">
+
+ <refentryinfo>
+ <title>clockdiff</title>
+ <productname>iputils</productname>
+ </refentryinfo>
+
+ <refmeta>
+ <refentrytitle>
+ <application>clockdiff</application>
+ </refentrytitle>
+ <manvolnum>8</manvolnum>
+ <refmiscinfo class='manual'>iputils</refmiscinfo>
+ </refmeta>
+
+ <refnamediv>
+ <refname>clockdiff</refname>
+ <refpurpose>measure clock difference between hosts</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv>
+ <cmdsynopsis sepchar=" ">
+ <command>clockdiff</command>
+ <arg choice="opt" rep="norepeat">
+ <option>-o</option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-o1</option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>--time-format
+ <replaceable>ctime iso</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-V</option>
+ </arg>
+ <arg choice="req" rep="norepeat">destination</arg>
+ </cmdsynopsis>
+ </refsynopsisdiv>
+
+ <refsection>
+ <info>
+ <title>DESCRIPTION</title>
+ </info>
+ <para>
+ <command>clockdiff</command> Measures clock difference between
+ us and
+ <emphasis remap="I">destination</emphasis> with 1 msec
+ resolution using ICMP TIMESTAMP [2] packets or, optionally, IP
+ TIMESTAMP option [3] option added to ICMP ECHO. [1]</para>
+ </refsection>
+
+ <refsection>
+ <info>
+ <title>OPTIONS</title>
+ </info>
+ <variablelist remap='TP'>
+ <varlistentry>
+ <term>
+ <option>-o</option>
+ </term>
+ <listitem>
+ <para>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).</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-o1</option>
+ </term>
+ <listitem>
+ <para>Slightly different form of
+ <option>-o</option>, 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,
+ <option>-o</option> is better for Linux.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-T</option>
+ </term>
+ <term>
+ <option>--time-format <replaceable>ctime iso</replaceable></option>
+ </term>
+ <listitem>
+ <para>Print time stamp in output either ISO-8601 format or
+ classical ctime format. The ctime format is default. The ISO
+ time stamp includes timezone, and is easier to parse.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-I</option>
+ </term>
+ <listitem>
+ <para>Alias of <option>--time-format <replaceable>iso</replaceable>
+ </option> option and argument.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-h</option>
+ </term>
+ <term>
+ <option>--help</option>
+ </term>
+ <listitem>
+ <para>Print help and exit.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-V</option>
+ </term>
+ <term>
+ <option>--version</option>
+ </term>
+ <listitem>
+ <para>Print version and exit.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsection>
+
+ <refsection xml:id="warnings">
+ <info>
+ <title>WARNINGS</title>
+ </info>
+ <variablelist remap="TP">
+ <varlistentry>
+ <listitem>
+ <para>• Some nodes (Cisco) use non-standard timestamps,
+ which is allowed by RFC, but makes timestamps mostly
+ useless.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <listitem>
+ <para>• Some nodes generate messed timestamps
+ (Solaris>2.4), when run
+ <command>xntpd</command>. 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.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <listitem>
+ <para>•
+ <command>clockdiff</command> shows difference in time
+ modulo 24 days.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsection>
+
+ <refsect1 id='see_also'>
+ <title>SEE ALSO</title>
+ <para>
+ <citerefentry>
+ <refentrytitle>ping</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>,
+ <citerefentry>
+ <refentrytitle>arping</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>,
+ <citerefentry>
+ <refentrytitle>tracepath</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>.</para>
+ </refsect1>
+
+ <refsection xml:id="references">
+ <info>
+ <title>REFERENCES</title>
+ </info>
+ <para>[1] ICMP ECHO, RFC0792, page 14.</para>
+ <para>[2] ICMP TIMESTAMP, RFC0792, page 16.</para>
+ <para>[3] IP TIMESTAMP option, RFC0791, 3.1, page 16.</para>
+ </refsection>
+
+ <refsect1 id='author'>
+ <title>AUTHOR</title>
+ <para>
+ <command>clockdiff</command> was compiled by Alexey Kuznetsov
+ <kuznet@ms2.inr.ac.ru>. It was based on code borrowed
+ from BSD
+ <command>timed</command> daemon.</para>
+ </refsect1>
+
+ <refsect1 id='security'>
+ <title>SECURITY</title>
+ <para>
+ <command>clockdiff</command> requires CAP_NET_RAW capability to
+ be executed. It is safe to be used as set-uid root.</para>
+ </refsect1>
+
+ <refsect1 id='availability'>
+ <title>AVAILABILITY</title>
+ <para>
+ <command>clockdiff</command> is part of
+ <emphasis remap='I'>iputils</emphasis> package.</para>
+ </refsect1>
+</refentry>
Index: iputils-20210202-new/doc/custom-html.xsl
===================================================================
--- iputils-20210202-new/doc/custom-html.xsl (nonexistent)
+++ iputils-20210202-new/doc/custom-html.xsl (revision 5)
@@ -0,0 +1,279 @@
+<?xml version='1.0'?> <!--*-nxml-*-->
+
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
+
+<xsl:import href="http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl"/>
+<!--
+ - The docbook stylesheet injects empty anchor tags into generated HTML, identified by an auto-generated ID.
+ - Ask the docbook stylesheet to generate reproducible output when generating (these) ID values.
+ - This makes the output of this stylesheet reproducible across identical invocations on the same input,
+ - which is an easy and significant win for achieving reproducible builds.
+ -
+ - It may be even better to strip the empty anchors from the document output in addition to turning on consistent IDs,
+ - for this stylesheet contains its own custom ID logic (for generating permalinks) already.
+ -->
+<xsl:param name="generate.consistent.ids" select="1"/>
+
+<!-- translate man page references to links to html pages -->
+<xsl:template match="citerefentry[not(@project)]">
+ <a>
+ <xsl:attribute name="href">
+ <xsl:value-of select="refentrytitle"/><xsl:text>.html#</xsl:text>
+ <xsl:value-of select="refentrytitle/@target"/>
+ </xsl:attribute>
+ <xsl:call-template name="inline.charseq"/>
+ </a>
+</xsl:template>
+
+<xsl:template match="citerefentry[@project='man-pages'] | citerefentry[manvolnum='2'] | citerefentry[manvolnum='4']">
+ <a>
+ <xsl:attribute name="href">
+ <xsl:text>http://man7.org/linux/man-pages/man</xsl:text>
+ <xsl:value-of select="manvolnum"/>
+ <xsl:text>/</xsl:text>
+ <xsl:value-of select="refentrytitle"/>
+ <xsl:text>.</xsl:text>
+ <xsl:value-of select="manvolnum"/>
+ <xsl:text>.html</xsl:text>
+ </xsl:attribute>
+ <xsl:call-template name="inline.charseq"/>
+ </a>
+</xsl:template>
+
+<xsl:template match="citerefentry[@project='die-net']">
+ <a>
+ <xsl:attribute name="href">
+ <xsl:text>http://linux.die.net/man/</xsl:text>
+ <xsl:value-of select="manvolnum"/>
+ <xsl:text>/</xsl:text>
+ <xsl:value-of select="refentrytitle"/>
+ </xsl:attribute>
+ <xsl:call-template name="inline.charseq"/>
+ </a>
+</xsl:template>
+
+<xsl:template match="citerefentry[@project='mankier']">
+ <a>
+ <xsl:attribute name="href">
+ <xsl:text>https://www.mankier.com/</xsl:text>
+ <xsl:value-of select="manvolnum"/>
+ <xsl:text>/</xsl:text>
+ <xsl:value-of select="refentrytitle"/>
+ </xsl:attribute>
+ <xsl:call-template name="inline.charseq"/>
+ </a>
+</xsl:template>
+
+<xsl:template match="citerefentry[@project='archlinux']">
+ <a>
+ <xsl:attribute name="href">
+ <xsl:text>https://www.archlinux.org/</xsl:text>
+ <xsl:value-of select="refentrytitle"/>
+ <xsl:text>/</xsl:text>
+ <xsl:value-of select="refentrytitle"/>
+ <xsl:text>.</xsl:text>
+ <xsl:value-of select="manvolnum"/>
+ <xsl:text>.html</xsl:text>
+ </xsl:attribute>
+ <xsl:call-template name="inline.charseq"/>
+ </a>
+</xsl:template>
+
+<xsl:template match="citerefentry[@project='freebsd']">
+ <a>
+ <xsl:attribute name="href">
+ <xsl:text>https://www.freebsd.org/cgi/man.cgi?</xsl:text>
+ <xsl:value-of select="refentrytitle"/>
+ <xsl:text>(</xsl:text>
+ <xsl:value-of select="manvolnum"/>
+ <xsl:text>)</xsl:text>
+ </xsl:attribute>
+ <xsl:call-template name="inline.charseq"/>
+ </a>
+</xsl:template>
+
+<xsl:template match="citerefentry[@project='dbus']">
+ <a>
+ <xsl:attribute name="href">
+ <xsl:text>http://dbus.freedesktop.org/doc/</xsl:text>
+ <xsl:value-of select="refentrytitle"/>
+ <xsl:text>.</xsl:text>
+ <xsl:value-of select="manvolnum"/>
+ <xsl:text>.html</xsl:text>
+ </xsl:attribute>
+ <xsl:call-template name="inline.charseq"/>
+ </a>
+</xsl:template>
+
+<!--
+ - helper template to do conflict resolution between various headings with the same inferred ID attribute/tag from the headerlink template
+ - this conflict resolution is necessary to prevent malformed HTML output (multiple ID attributes with the same value)
+ - and it fixes xsltproc warnings during compilation of HTML man pages
+ -
+ - A simple top-to-bottom numbering scheme is implemented for nodes with the same ID value to derive unique ID values for HTML output.
+ - It uses two parameters:
+ templateID the proposed ID string to use which must be checked for conflicts
+ keyNode the context node which 'produced' the given templateID.
+ -
+ - Conflicts are detected solely based on keyNode, templateID is not taken into account for that purpose.
+ -->
+<xsl:template name="generateID">
+ <!-- node which generatedID needs to assume as the 'source' of the ID -->
+ <xsl:param name="keyNode"/>
+ <!-- suggested value for generatedID output, a contextually meaningful ID string -->
+ <xsl:param name="templateID"/>
+ <xsl:variable name="conflictSource" select="preceding::refsect1/title|preceding::refsect1/info/title|
+ preceding::refsect2/title|preceding::refsect2/info/title|
+ preceding::varlistentry/term[1]"/>
+ <xsl:variable name="conflictCount" select="count($conflictSource[. = $keyNode])"/>
+ <xsl:choose>
+ <!-- special case conflictCount = 0 to preserve compatibility with URLs generated by previous versions of this XSL stylesheet where possible -->
+ <xsl:when test="$conflictCount = 0">
+ <xsl:value-of select="$templateID"/>
+ </xsl:when>
+ <xsl:otherwise>
+ <xsl:value-of select="concat($templateID, $conflictCount)"/>
+ </xsl:otherwise>
+ </xsl:choose>
+</xsl:template>
+
+<!--
+ - a helper template to abstract over the structure of generated subheading + permalink HTML output
+ - It helps reduce tedious repetition and groups all actual markup output (as opposed to URL/ID logic) in a single location.
+ -->
+<xsl:template name="permalink">
+ <xsl:param name="nodeType"/> <!-- local name of the element node to generate, e.g. 'h2' for <h2></h2> -->
+ <xsl:param name="nodeContent"/> <!-- nodeset to apply further templates to obtain the content of the subheading/term -->
+ <xsl:param name="linkTitle"/> <!-- value for title attribute of generated permalink, e.g. 'this is a permalink' -->
+
+ <!-- parameters passed to generateID template, otherwise unused. -->
+ <xsl:param name="keyNode"/>
+ <xsl:param name="templateID"/>
+
+ <!--
+ - If stable URLs with fragment markers (references to the ID) turn out not to be important:
+ - generatedID could simply take the value of generate-id(), and various other helper templates may be dropped entirely.
+ - Alternatively, if xsltproc is patched to generate reproducible generate-id() output, the same simplifications can be
+ - applied at the cost of breaking compatibility with URLs generated from output of previous versions of this stylesheet.
+ -->
+ <xsl:variable name="generatedID">
+ <xsl:call-template name="generateID">
+ <xsl:with-param name="keyNode" select="$keyNode"/>
+ <xsl:with-param name="templateID" select="$templateID"/>
+ </xsl:call-template>
+ </xsl:variable>
+
+ <xsl:element name="{$nodeType}">
+ <xsl:attribute name="id">
+ <xsl:value-of select="$generatedID"/>
+ </xsl:attribute>
+ <xsl:apply-templates select="$nodeContent"/>
+ <a class="headerlink" title="{$linkTitle}" href="#{$generatedID}">¶</a>
+ </xsl:element>
+</xsl:template>
+
+<!-- simple wrapper around permalink to avoid repeating common info for each level of subheading covered by the permalink logic (h2, h3) -->
+<xsl:template name="headerlink">
+ <xsl:param name="nodeType"/>
+ <xsl:call-template name="permalink">
+ <xsl:with-param name="nodeType" select="$nodeType"/>
+ <xsl:with-param name="linkTitle" select="'Permalink to this headline'"/>
+ <xsl:with-param name="nodeContent" select="node()"/>
+ <xsl:with-param name="keyNode" select="."/>
+ <!--
+ - To retain compatibility with IDs generated by previous versions of the template, inline.charseq must be called.
+ - The purpose of that template is to generate markup (according to docbook documentation its purpose is to mark/format something as plain text).
+ - The only reason to call this template is to get the auto-generated text such as brackets ([]) before flattening it.
+ -->
+ <xsl:with-param name="templateID">
+ <xsl:call-template name="inline.charseq"/>
+ </xsl:with-param>
+ </xsl:call-template>
+</xsl:template>
+
+<xsl:template match="refsect1/title|refsect1/info/title">
+ <!-- the ID is output in the block.object call for refsect1 -->
+ <xsl:call-template name="headerlink">
+ <xsl:with-param name="nodeType" select="'h2'"/>
+ </xsl:call-template>
+</xsl:template>
+
+<xsl:template match="refsect2/title|refsect2/info/title">
+ <xsl:call-template name="headerlink">
+ <xsl:with-param name="nodeType" select="'h3'"/>
+ </xsl:call-template>
+</xsl:template>
+
+<xsl:template match="varlistentry">
+ <xsl:call-template name="permalink">
+ <xsl:with-param name="nodeType" select="'dt'"/>
+ <xsl:with-param name="linkTitle" select="'Permalink to this term'"/>
+ <xsl:with-param name="nodeContent" select="term"/>
+ <xsl:with-param name="keyNode" select="term[1]"/>
+ <!--
+ - To retain compatibility with IDs generated by previous versions of the template, inline.charseq must be called.
+ - The purpose of that template is to generate markup (according to docbook documentation its purpose is to mark/format something as plain text).
+ - The only reason to call this template is to get the auto-generated text such as brackets ([]) before flattening it.
+ -->
+ <xsl:with-param name="templateID">
+ <xsl:call-template name="inline.charseq">
+ <xsl:with-param name="content" select="term[1]"/>
+ </xsl:call-template>
+ </xsl:with-param>
+ </xsl:call-template>
+ <dd>
+ <xsl:apply-templates select="listitem"/>
+ </dd>
+</xsl:template>
+
+
+<!-- add Index link at top of page -->
+<xsl:template name="user.header.content">
+ <style>
+ a.headerlink {
+ color: #c60f0f;
+ font-size: 0.8em;
+ padding: 0 4px 0 4px;
+ text-decoration: none;
+ visibility: hidden;
+ }
+
+ a.headerlink:hover {
+ background-color: #c60f0f;
+ color: white;
+ }
+
+ h1:hover > a.headerlink, h2:hover > a.headerlink, h3:hover > a.headerlink, dt:hover > a.headerlink {
+ visibility: visible;
+ }
+ </style>
+
+ <a>
+ <xsl:attribute name="href">
+ <xsl:text>index.html</xsl:text>
+ </xsl:attribute>
+ <xsl:text>Index </xsl:text>
+ </a>·
+ <a>
+ <xsl:attribute name="href">
+ <xsl:text>iputils.directives.html</xsl:text>
+ </xsl:attribute>
+ <xsl:text>Directives </xsl:text>
+ </a>
+
+ <span style="float:right">
+ <xsl:text>iputils </xsl:text>
+ <xsl:value-of select="$iputils.version"/>
+ </span>
+ <hr/>
+</xsl:template>
+
+<xsl:template match="literal">
+ <xsl:text>"</xsl:text>
+ <xsl:call-template name="inline.monoseq"/>
+ <xsl:text>"</xsl:text>
+</xsl:template>
+
+<xsl:output method="html" encoding="UTF-8" indent="no"/>
+
+</xsl:stylesheet>
Index: iputils-20210202-new/doc/custom-man.xsl
===================================================================
--- iputils-20210202-new/doc/custom-man.xsl (nonexistent)
+++ iputils-20210202-new/doc/custom-man.xsl (revision 5)
@@ -0,0 +1,46 @@
+<?xml version='1.0'?> <!--*-nxml-*-->
+
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ xmlns:exsl="http://exslt.org/common"
+ extension-element-prefixes="exsl"
+ version="1.0">
+
+<xsl:import href="http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl"/>
+
+<xsl:template name="top.comment" />
+
+<xsl:template name="TH.title.line">
+ <xsl:param name="title"/>
+ <xsl:param name="section"/>
+ <xsl:param name="extra1"/>
+ <xsl:param name="extra2"/>
+ <xsl:param name="extra3"/>
+
+ <xsl:call-template name="mark.subheading"/>
+ <xsl:text>.TH "</xsl:text>
+ <xsl:call-template name="string.upper">
+ <xsl:with-param name="string">
+ <xsl:value-of select="normalize-space($title)"/>
+ </xsl:with-param>
+ </xsl:call-template>
+ <xsl:text>" "</xsl:text>
+ <xsl:value-of select="normalize-space($section)"/>
+ <xsl:text>" "" "iputils </xsl:text>
+ <xsl:value-of select="$iputils.version"/>
+ <xsl:text>" "</xsl:text>
+ <xsl:value-of select="normalize-space($extra3)"/>
+ <xsl:text>" </xsl:text>
+ <xsl:call-template name="mark.subheading"/>
+
+</xsl:template>
+
+<xsl:template match="literal">
+ <xsl:if test="$man.hyphenate.computer.inlines = 0">
+ <xsl:call-template name="suppress.hyphenation"/>
+ </xsl:if>
+ <xsl:text>"</xsl:text>
+ <xsl:call-template name="inline.monoseq"/>
+ <xsl:text>"</xsl:text>
+</xsl:template>
+
+</xsl:stylesheet>
Index: iputils-20210202-new/doc/meson.build
===================================================================
--- iputils-20210202-new/doc/meson.build (nonexistent)
+++ iputils-20210202-new/doc/meson.build (revision 5)
@@ -0,0 +1,105 @@
+manpages = []
+custom_man_xsl = files('custom-man.xsl')
+custom_html_xsl = files('custom-html.xsl')
+
+if build_arping == true
+ manpages += ['arping']
+endif
+
+if build_clockdiff == true
+ manpages += ['clockdiff']
+endif
+
+if build_ping == true
+ manpages += ['ping']
+endif
+
+if build_rarpd == true
+ manpages += ['rarpd']
+endif
+
+if build_rdisc == true
+ manpages += ['rdisc']
+endif
+
+if build_tftpd == true
+ manpages += ['tftpd']
+endif
+
+if build_tracepath == true
+ manpages += ['tracepath']
+endif
+
+if build_traceroute6 == true
+ manpages += ['traceroute6']
+endif
+
+if build_ninfod == true
+ manpages += ['ninfod']
+endif
+
+xsltproc = find_program('xsltproc', required : false)
+xsltproc_args = [
+ '--nonet',
+ '--stringparam', 'man.output.quietly', '1',
+ '--stringparam', 'funcsynopsis.style', 'ansi',
+ '--stringparam', 'man.th.extra1.suppress', '1',
+ '--stringparam', 'iputils.version', meson.project_version(),
+]
+
+if xsltproc.found()
+ doc_targets = []
+ if build_mans
+ doc_targets += ['manpages']
+ endif
+ if build_html_mans
+ doc_targets += ['html']
+ endif
+ xsltproc_works = true
+ foreach doc_target : doc_targets
+ xsl = 'http://docbook.sourceforge.net/release/xsl-ns/current/' + doc_target + '/docbook.xsl'
+ testrun = run_command([xsltproc, '--nonet', xsl])
+ endforeach
+endif
+
+if xsltproc_works == false
+ message('Docs cannot be built: xsltproc does not work correctly')
+ build_mans = false
+ build_html_mans = false
+endif
+
+if build_mans
+ foreach man : manpages
+ custom_target(man + '.8',
+ output : man + '.8',
+ input : man + '.xml',
+ command : [
+ xsltproc,
+ '-o', '@OUTPUT@',
+ xsltproc_args,
+ custom_man_xsl,
+ '@INPUT@',
+ ],
+ install : true,
+ install_dir : join_paths(get_option('mandir'), 'man8'),
+ )
+ endforeach
+endif
+
+if build_html_mans and xsltproc_works
+ foreach man : manpages
+ custom_target(man + '.html',
+ output : man + '.html',
+ input : man + '.xml',
+ command : [
+ xsltproc,
+ '-o', '@OUTPUT@',
+ xsltproc_args,
+ custom_html_xsl,
+ '@INPUT@',
+ ],
+ install : true,
+ install_dir : join_paths(get_option('datadir'), meson.project_name()),
+ )
+ endforeach
+endif
Index: iputils-20210202-new/doc/ninfod.xml
===================================================================
--- iputils-20210202-new/doc/ninfod.xml (nonexistent)
+++ iputils-20210202-new/doc/ninfod.xml (revision 5)
@@ -0,0 +1,168 @@
+<refentry xmlns:db="http://docbook.org/ns/docbook" version="5.0"
+xml:id="man.ninfod">
+
+ <refentryinfo>
+ <title>ninfod</title>
+ <productname>iputils</productname>
+ </refentryinfo>
+
+ <refmeta>
+ <refentrytitle>
+ <application>ninfod</application>
+ </refentrytitle>
+ <manvolnum>8</manvolnum>
+ <refmiscinfo class='manual'>iputils</refmiscinfo>
+ </refmeta>
+
+ <refnamediv>
+ <refname>ninfod</refname>
+ <refpurpose>Respond to IPv6 Node Information
+ Queries</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv>
+ <cmdsynopsis sepchar=" ">
+ <command>ninfod</command>
+ <arg choice="opt" rep="norepeat">
+ <option>-dhv</option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-p
+ <replaceable>pidfile</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-u
+ <replaceable>user</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-v</option>
+ </arg>
+ </cmdsynopsis>
+ </refsynopsisdiv>
+
+ <refsection>
+ <info>
+ <title>DESCRIPTION</title>
+ </info>
+ <para>Responds to IPv6 Node Information Queries (RFC4620) from
+ clients. Queries can be sent by various implementations of
+ <command>ping</command> command.</para>
+ </refsection>
+
+ <refsection>
+ <info>
+ <title>OPTIONS</title>
+ </info>
+ <variablelist remap="TP">
+ <varlistentry>
+ <term>
+ <option>-d</option>
+ </term>
+ <listitem>
+ <para>Debug mode. Do not go background.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-h</option>
+ </term>
+ <listitem>
+ <para>Show help.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-v</option>
+ </term>
+ <listitem>
+ <para>Verbose mode.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-u</option>
+ <emphasis remap="I">user</emphasis>
+ </term>
+ <listitem>
+ <para>Run as another user.
+ <emphasis remap="I">user</emphasis> can either be username
+ or user ID.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-p</option>
+ <emphasis remap="I">pidfile</emphasis>
+ </term>
+ <listitem>
+ <para>File for process-id storage.
+ <emphasis remap="I">user</emphasis> is required to be able
+ to create the file.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-V</option>
+ </term>
+ <listitem>
+ <para>Print version and exit.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsection>
+
+ <refsection xml:id="see_also">
+ <info>
+ <title>SEE ALSO</title>
+ </info>
+ <para>
+ <citerefentry>
+ <refentrytitle>ping</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>.</para>
+ </refsection>
+
+ <refsection xml:id="author">
+ <info>
+ <title>AUTHOR</title>
+ </info>
+ <para>
+ <command>ninfod</command> was written by USAGI/WIDE
+ Project.</para>
+ </refsection>
+
+ <refsection xml:id="copying">
+ <info>
+ <title>COPYING</title>
+ </info>
+ <literallayout>
+Copyright (C) 2012 YOSHIFUJI Hideaki.
+Copyright (C) 2002 USAGI/WIDE Project.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+3. Neither the name of the project nor the names of its contributors
+ may be used to endorse or promote products derived from this software
+ without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS “AS IS” AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.
+ </literallayout>
+ </refsection>
+</refentry>
Index: iputils-20210202-new/doc/ping.xml
===================================================================
--- iputils-20210202-new/doc/ping.xml (nonexistent)
+++ iputils-20210202-new/doc/ping.xml (revision 5)
@@ -0,0 +1,939 @@
+<refentry xmlns:db="http://docbook.org/ns/docbook" version="5.0"
+xml:id="man.ping">
+
+ <refentryinfo>
+ <title>ping</title>
+ <productname>iputils</productname>
+ </refentryinfo>
+
+ <refmeta>
+ <refentrytitle>
+ <application>ping</application>
+ </refentrytitle>
+ <manvolnum>8</manvolnum>
+ <refmiscinfo class='manual'>iputils</refmiscinfo>
+ </refmeta>
+
+ <refnamediv>
+ <refname>ping</refname>
+ <refpurpose>send ICMP ECHO_REQUEST to network
+ hosts</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv>
+ <cmdsynopsis sepchar=" ">
+ <command>ping</command>
+ <arg choice="opt" rep="norepeat">
+ <option>-aAbBdDfhLnOqrRUvV46</option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-c
+ <replaceable>count</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-F
+ <replaceable>flowlabel</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-i
+ <replaceable>interval</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-I
+ <replaceable>interface</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-l
+ <replaceable>preload</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-m
+ <replaceable>mark</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-M
+ <replaceable>pmtudisc_option</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-N
+ <replaceable>nodeinfo_option</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-w
+ <replaceable>deadline</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-W
+ <replaceable>timeout</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-p
+ <replaceable>pattern</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-Q
+ <replaceable>tos</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-s
+ <replaceable>packetsize</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-S
+ <replaceable>sndbuf</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-t
+ <replaceable>ttl</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-T
+ <replaceable>timestamp option</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">hop...</arg>
+ <arg choice="req" rep="norepeat">destination</arg>
+ </cmdsynopsis>
+ </refsynopsisdiv>
+
+ <refsection>
+ <info>
+ <title>DESCRIPTION</title>
+ </info>
+ <para>
+ <command>ping</command> 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.</para>
+ <para>
+ <command>ping</command> works with both IPv4 and IPv6. Using
+ only one of them explicitly can be enforced by specifying
+ <option>-4</option> or
+ <option>-6</option>.</para>
+ <para>
+ <command>ping</command> can also send IPv6 Node Information
+ Queries (RFC4620). Intermediate
+ <emphasis remap="I">hop</emphasis>s may not be allowed, because
+ IPv6 source routing was deprecated (RFC5095).</para>
+ </refsection>
+
+ <refsection>
+ <info>
+ <title>OPTIONS</title>
+ </info>
+ <variablelist remap="TP">
+ <varlistentry>
+ <term>
+ <option>-4</option>
+ </term>
+ <listitem>
+ <para>Use IPv4 only.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-6</option>
+ </term>
+ <listitem>
+ <para>Use IPv6 only.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-a</option>
+ </term>
+ <listitem>
+ <para>Audible ping.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-A</option>
+ </term>
+ <listitem>
+ <para>Adaptive ping. Interpacket interval adapts to
+ round-trip time, so that effectively not more than one
+ (or more, if preload is set) unanswered probe is present
+ in the network. Minimal interval is 200msec unless
+ super-user. On networks with low RTT this mode is
+ essentially equivalent to flood mode.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-b</option>
+ </term>
+ <listitem>
+ <para>Allow pinging a broadcast address.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-B</option>
+ </term>
+ <listitem>
+ <para>Do not allow
+ <command>ping</command> to change source address of
+ probes. The address is bound to one selected when
+ <command>ping</command> starts.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-c</option>
+ <emphasis remap="I">count</emphasis>
+ </term>
+ <listitem>
+ <para>Stop after sending
+ <emphasis remap="I">count</emphasis> ECHO_REQUEST packets.
+ With
+ <emphasis remap="I">deadline</emphasis> option,
+ <command>ping</command> waits for
+ <emphasis remap="I">count</emphasis> ECHO_REPLY packets,
+ until the timeout expires.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-d</option>
+ </term>
+ <listitem>
+ <para>Set the SO_DEBUG option on the socket being used.
+ Essentially, this socket option is not used by Linux
+ kernel.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-D</option>
+ </term>
+ <listitem>
+ <para>Print timestamp (unix time + microseconds as in
+ gettimeofday) before each line.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-f</option>
+ </term>
+ <listitem>
+ <para>Flood ping. For every ECHO_REQUEST sent a period
+ “.” is printed, while for every 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.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-F</option>
+ <emphasis remap="I">flow label</emphasis>
+ </term>
+ <listitem>
+ <para>IPv6 only. Allocate and set 20 bit flow label (in
+ hex) on echo request packets. If value is zero, kernel
+ allocates random flow label.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-h</option>
+ </term>
+ <listitem>
+ <para>Show help.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-i</option>
+ <emphasis remap="I">interval</emphasis>
+ </term>
+ <listitem>
+ <para>Wait
+ <emphasis remap="I">interval</emphasis> seconds between
+ sending each packet. Real number allowed with dot as
+ a decimal separator (regardless locale setup).
+ 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 than 0.2 seconds.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-I</option>
+ <emphasis remap="I">interface</emphasis>
+ </term>
+ <listitem>
+ <para>
+ <emphasis remap="I">interface</emphasis> is either an
+ address, an interface name or a VRF name. If
+ <emphasis remap="I">interface</emphasis> is an address, it
+ sets source address to specified interface address. If
+ <emphasis remap="I">interface</emphasis> is an interface
+ name, it sets source interface to specified interface.
+ If <emphasis remap="I">interface</emphasis> is a VRF
+ name, each packet is routed using the corresponding
+ routing table; in this case, the <option>-I</option> option
+ can be repeated to specify a source address.
+ NOTE: For IPv6, when doing ping to a link-local scope
+ address, link specification (by the '%'-notation in
+ <emphasis remap="I">destination</emphasis>, or by this
+ option) can be used but it is no longer required.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-l</option>
+ <emphasis remap="I">preload</emphasis>
+ </term>
+ <listitem>
+ <para>If
+ <emphasis remap="I">preload</emphasis> is specified,
+ <command>ping</command> sends that many packets not
+ waiting for reply. Only the super-user may select preload
+ more than 3.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-L</option>
+ </term>
+ <listitem>
+ <para>Suppress loopback of multicast packets. This flag
+ only applies if the ping destination is a multicast
+ address.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-m</option>
+ <emphasis remap="I">mark</emphasis>
+ </term>
+ <listitem>
+ <para>use
+ <emphasis remap="I">mark</emphasis> 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.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-M</option>
+ <emphasis remap="I">pmtudisc_opt</emphasis>
+ </term>
+ <listitem>
+ <para>Select Path MTU Discovery strategy.
+ <emphasis remap="I">pmtudisc_option</emphasis> may be
+ either
+ <emphasis remap="I">do</emphasis> (prohibit fragmentation,
+ even local one),
+ <emphasis remap="I">want</emphasis> (do PMTU discovery,
+ fragment locally when packet size is large), or
+ <emphasis remap="I">dont</emphasis> (do not set DF
+ flag).</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-N</option>
+ <emphasis remap="I">nodeinfo_option</emphasis>
+ </term>
+ <listitem>
+ <para>IPv6 only. Send ICMPv6 Node Information Queries
+ (RFC4620), instead of Echo Request. CAP_NET_RAW
+ capability is required.</para>
+ <variablelist remap="TP">
+ <varlistentry>
+ <term>
+ <emphasis remap="B">help</emphasis>
+ </term>
+ <listitem>
+ <para>Show help for NI support.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <variablelist remap="TP">
+ <varlistentry>
+ <term>
+ <emphasis remap="B">name</emphasis>
+ </term>
+ <listitem>
+ <para>Queries for Node Names.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <variablelist remap="TP">
+ <varlistentry>
+ <term>
+ <emphasis remap="B">ipv6</emphasis>
+ </term>
+ <listitem>
+ <para>Queries for IPv6 Addresses. There are several
+ IPv6 specific flags.</para>
+ <variablelist remap="TP">
+ <varlistentry>
+ <term>
+ <emphasis remap="B">ipv6-global</emphasis>
+ </term>
+ <listitem>
+ <para>Request IPv6 global-scope
+ addresses.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <variablelist remap="TP">
+ <varlistentry>
+ <term>
+ <emphasis remap="B">ipv6-sitelocal</emphasis>
+ </term>
+ <listitem>
+ <para>Request IPv6 site-local
+ addresses.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <variablelist remap="TP">
+ <varlistentry>
+ <term>
+ <emphasis remap="B">ipv6-linklocal</emphasis>
+ </term>
+ <listitem>
+ <para>Request IPv6 link-local
+ addresses.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <variablelist remap="TP">
+ <varlistentry>
+ <term>
+ <emphasis remap="B">ipv6-all</emphasis>
+ </term>
+ <listitem>
+ <para>Request IPv6 addresses on other
+ interfaces.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <variablelist remap="TP">
+ <varlistentry>
+ <term>
+ <emphasis remap="B">ipv4</emphasis>
+ </term>
+ <listitem>
+ <para>Queries for IPv4 Addresses. There is one IPv4
+ specific flag.</para>
+ <variablelist remap="TP">
+ <varlistentry>
+ <term>
+ <emphasis remap="B">ipv4-all</emphasis>
+ </term>
+ <listitem>
+ <para>Request IPv4 addresses on other
+ interfaces.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <variablelist remap="TP">
+ <varlistentry>
+ <term>
+ <emphasis remap="B">subject-ipv6=</emphasis><emphasis remap="I">ipv6addr</emphasis>
+ </term>
+ <listitem>
+ <para>IPv6 subject address.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <variablelist remap="TP">
+ <varlistentry>
+ <term>
+ <emphasis remap="B">subject-ipv4=</emphasis><emphasis remap="I">ipv4addr</emphasis>
+ </term>
+ <listitem>
+ <para>IPv4 subject address.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <variablelist remap="TP">
+ <varlistentry>
+ <term>
+ <emphasis remap="B">subject-name=</emphasis><emphasis remap="I">nodename</emphasis>
+ </term>
+ <listitem>
+ <para>Subject name. If it contains more than one
+ dot, fully-qualified domain name is assumed.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <variablelist remap="TP">
+ <varlistentry>
+ <term>
+ <emphasis remap="B">subject-fqdn=</emphasis><emphasis remap="I">nodename</emphasis>
+ </term>
+ <listitem>
+ <para>Subject name. Fully-qualified domain name is
+ always assumed.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-n</option>
+ </term>
+ <listitem>
+ <para>Numeric output only. No attempt will be made to
+ lookup symbolic names for host addresses.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-O</option>
+ </term>
+ <listitem>
+ <para>Report outstanding ICMP ECHO reply before sending
+ next packet. This is useful together with the timestamp
+ <option>-D</option> to log output to a diagnostic file and
+ search for missing answers.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-p</option>
+ <emphasis remap="I">pattern</emphasis>
+ </term>
+ <listitem>
+ <para>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,
+ <option>-p ff</option> will cause the sent packet to be
+ filled with all ones.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-q</option>
+ </term>
+ <listitem>
+ <para>Quiet output. Nothing is displayed except the
+ summary lines at startup time and when finished.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-Q</option>
+ <emphasis remap="I">tos</emphasis>
+ </term>
+ <listitem>
+ <para>Set Quality of Service -related bits in ICMP
+ datagrams.
+ <emphasis remap="I">tos</emphasis> can be decimal
+ (<command>ping</command> only) or hex number.</para>
+ <para>In RFC2474, these fields are interpreted as 8-bit
+ Differentiated Services (DS), consisting of: bits 0-1 (2
+ lowest bits) of separate data, and bits 2-7 (highest 6
+ bits) of Differentiated Services Codepoint (DSCP). In
+ RFC2481 and RFC3168, bits 0-1 are used for ECN.</para>
+ <para>Historically (RFC1349, obsoleted by RFC2474), these
+ were interpreted as: bit 0 (lowest bit) for reserved
+ (currently being redefined as congestion control), 1-4
+ for Type of Service and bits 5-7 (highest bits) for
+ Precedence.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-r</option>
+ </term>
+ <listitem>
+ <para>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
+ <option>-I</option> is also used.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-R</option>
+ </term>
+ <listitem>
+ <para>
+ <command>ping</command> only. 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.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-s</option>
+ <emphasis remap="I">packetsize</emphasis>
+ </term>
+ <listitem>
+ <para>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.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-S</option>
+ <emphasis remap="I">sndbuf</emphasis>
+ </term>
+ <listitem>
+ <para>Set socket sndbuf. If not specified, it is selected
+ to buffer not more than one packet.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-t</option>
+ <emphasis remap="I">ttl</emphasis>
+ </term>
+ <listitem>
+ <para>
+ <command>ping</command> only. Set the IP Time to
+ Live.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-T</option>
+ <emphasis remap="I">timestamp option</emphasis>
+ </term>
+ <listitem>
+ <para>Set special IP timestamp options.
+ <emphasis remap="I">timestamp option</emphasis> may be
+ either
+ <emphasis remap="I">tsonly</emphasis> (only timestamps),
+ <emphasis remap="I">tsandaddr</emphasis> (timestamps and
+ addresses) or
+ <emphasis remap="I">tsprespec host1 [host2 [host3
+ [host4]]]</emphasis> (timestamp prespecified hops).</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-U</option>
+ </term>
+ <listitem>
+ <para>Print full user-to-user latency (the old
+ behaviour). Normally
+ <command>ping</command> prints network round trip time,
+ which can be different f.e. due to DNS failures.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-v</option>
+ </term>
+ <listitem>
+ <para>Verbose output. Do not suppress DUP replies when pinging
+ multicast address.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-V</option>
+ </term>
+ <listitem>
+ <para>Show version and exit.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-w</option>
+ <emphasis remap="I">deadline</emphasis>
+ </term>
+ <listitem>
+ <para>Specify a timeout, in seconds, before
+ <command>ping</command> exits regardless of how many
+ packets have been sent or received. In this case
+ <command>ping</command> does not stop after
+ <emphasis remap="I">count</emphasis> packet are sent, it
+ waits either for
+ <emphasis remap="I">deadline</emphasis> expire or until
+ <emphasis remap="I">count</emphasis> probes are answered
+ or for some error notification from network.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-W</option>
+ <emphasis remap="I">timeout</emphasis>
+ </term>
+ <listitem>
+ <para>Time to wait for a response, in seconds. The option
+ affects only timeout in absence of any responses,
+ otherwise
+ <command>ping</command> waits for two RTTs.
+ Real number allowed with dot as a decimal separator
+ (regardless locale setup).
+ 0 means infinite timeout.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>When using
+ <command>ping</command> 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/mdev round-trip time
+ numbers.</para>
+ <para>Population standard deviation (mdev), essentially an
+ average of how far each ping RTT is from the mean RTT. The
+ higher mdev is, the more variable the RTT is (over time).
+ With a high RTT
+ variability, you will have speed issues with bulk transfers
+ (they will take longer than is strictly speaking necessary, as
+ the variability will eventually cause the sender to wait for
+ ACKs) and you will have middling to poor VoIP quality.</para>
+ <para>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.</para>
+ <para>If
+ <command>ping</command> does not receive any reply packets at
+ all it will exit with code 1. If a packet
+ <emphasis remap="I">count</emphasis> and
+ <emphasis remap="I">deadline</emphasis> are both specified, and
+ fewer than
+ <emphasis remap="I">count</emphasis> packets are received by the
+ time the
+ <emphasis remap="I">deadline</emphasis> 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.</para>
+ <para>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
+ <command>ping</command> during normal operations or from
+ automated scripts.</para>
+ </refsection>
+
+ <refsection xml:id="icmp_packet_details">
+ <info>
+ <title>ICMP PACKET DETAILS</title>
+ </info>
+ <para>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
+ <emphasis remap="I">packetsize</emphasis> is given, this
+ indicates 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).</para>
+ <para>If the data space is at least of size of struct timeval
+ <command>ping</command> 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.</para>
+ </refsection>
+
+ <refsection xml:id="duplicate_and_damaged_packets">
+ <info>
+ <title>DUPLICATE AND DAMAGED PACKETS</title>
+ </info>
+ <para>
+ <command>ping</command> 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.</para>
+ <para>Damaged packets are obviously serious cause for alarm and
+ often indicate broken hardware somewhere in the
+ <command>ping</command> packet's path (in the network or in the
+ hosts).</para>
+ </refsection>
+
+ <refsection xml:id="trying_different_data_patterns">
+ <info>
+ <title>TRYING DIFFERENT DATA PATTERNS</title>
+ </info>
+ <para>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.</para>
+ <para>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
+ <option>-p</option> option of
+ <command>ping</command>.</para>
+ </refsection>
+
+ <refsection xml:id="ttl_details">
+ <info>
+ <title>TTL DETAILS</title>
+ </info>
+ <para>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.</para>
+ <para>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).</para>
+ <para>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
+ <citerefentry>
+ <refentrytitle>telnet</refentrytitle>
+ <manvolnum>1</manvolnum>
+ </citerefentry> or
+ <citerefentry>
+ <refentrytitle>ftp</refentrytitle>
+ <manvolnum>1</manvolnum>
+ </citerefentry>.</para>
+ <para>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:</para>
+ <variablelist remap="TP">
+ <varlistentry>
+ <listitem>
+ <para>• 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.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <listitem>
+ <para>• 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
+ <emphasis remap="B">from</emphasis> the remote system
+ <emphasis remap="B">to</emphasis> the
+ <command>ping</command>ing host.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <listitem>
+ <para>• 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.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsection>
+
+ <refsection xml:id="bugs">
+ <info>
+ <title>BUGS</title>
+ </info>
+ <variablelist remap="TP">
+ <varlistentry>
+ <listitem>
+ <para>• Many Hosts and Gateways ignore the RECORD_ROUTE
+ option.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <listitem>
+ <para>• The maximum IP header length is too small for
+ options like RECORD_ROUTE to be completely useful.
+ There's not much that can be done about this,
+ however.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <listitem>
+ <para>• Flood pinging is not recommended in general, and
+ flood pinging the broadcast address should only be done
+ under very controlled conditions.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsection>
+
+ <refsection xml:id="see_also">
+ <info>
+ <title>SEE ALSO</title>
+ </info>
+ <para>
+ <citerefentry>
+ <refentrytitle>ip</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>,
+ <citerefentry>
+ <refentrytitle>ss</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>.</para>
+ </refsection>
+
+ <refsection xml:id="history">
+ <info>
+ <title>HISTORY</title>
+ </info>
+ <para>The
+ <command>ping</command> command appeared in 4.3BSD.</para>
+ <para>The version described here is its descendant specific to
+ Linux.</para>
+ <para>As of version s20150815, the
+ <emphasis remap="B">ping6</emphasis> binary doesn't exist
+ anymore. It has been merged into
+ <command>ping</command>. Creating a symlink named
+ <emphasis remap="B">ping6</emphasis> pointing to
+ <command>ping</command> will result in the same functionality as
+ before.</para>
+ </refsection>
+
+ <refsection xml:id="security">
+ <info>
+ <title>SECURITY</title>
+ </info>
+ <para>
+ <command>ping</command> requires CAP_NET_RAW capability to be
+ executed 1) if the program is used for non-echo queries (See
+ <option>-N</option> option), or 2) if kernel does not support
+ non-raw ICMP sockets, or 3) if the user is not allowed to
+ create an ICMP echo socket. The program may be used as set-uid
+ root.</para>
+ </refsection>
+
+ <refsection xml:id="availability">
+ <info>
+ <title>AVAILABILITY</title>
+ </info>
+ <para>
+ <command>ping</command> is part of
+ <emphasis remap="I">iputils</emphasis> package.</para>
+ </refsection>
+</refentry>
Index: iputils-20210202-new/doc/rarpd.xml
===================================================================
--- iputils-20210202-new/doc/rarpd.xml (nonexistent)
+++ iputils-20210202-new/doc/rarpd.xml (revision 5)
@@ -0,0 +1,184 @@
+<refentry xmlns:db="http://docbook.org/ns/docbook" version="5.0"
+xml:id="man.rarpd">
+
+ <refentryinfo>
+ <title>rarpd</title>
+ <productname>iputils</productname>
+ </refentryinfo>
+
+ <refmeta>
+ <refentrytitle>
+ <application>rarpd</application>
+ </refentrytitle>
+ <manvolnum>8</manvolnum>
+ <refmiscinfo class='manual'>iputils</refmiscinfo>
+ </refmeta>
+
+ <refnamediv>
+ <refname>rarpd</refname>
+ <refpurpose>answer RARP REQUESTs</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv>
+ <cmdsynopsis sepchar=" ">
+ <command>rarpd</command>
+ <arg choice="opt" rep="norepeat">
+ <option>-AadevV</option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-b
+ <replaceable>bootdir</replaceable></option>
+ </arg>
+ <arg choice="req" rep="norepeat">interface</arg>
+ </cmdsynopsis>
+ </refsynopsisdiv>
+
+ <refsection xml:id="description">
+ <info>
+ <title>DESCRIPTION</title>
+ </info>
+ <para>Listens for RARP requests broadcasted by clients. If the MAC address
+ of the client is found in <filename>/etc/ethers</filename> and the obtained
+ hostname is resolvable to a valid IP address from the attached network,
+ <command>rarpd</command> answers to the client with a RARPD reply
+ and provides an IP address.</para>
+
+ <para>To allow multiple boot servers on the network
+ <command>rarpd</command> optionally checks if a Sun-like
+ bootable image in the TFTP directory is present. It should be formatted like
+ <emphasis remap="B">Hexadecimal_IP.ARCH</emphasis>. For example: To
+ load sparc 193.233.7.98,
+ <emphasis remap="I">C1E90762.SUN4M</emphasis> is linked to an
+ image appropriate for SUN4M in the directory
+ <filename>/etc/tftpboot</filename>.</para>
+ </refsection>
+
+ <refsection xml:id="warning">
+ <info>
+ <title>WARNING</title>
+ </info>
+ <para>This facility is deeply obsoleted by BOOTP and later DHCP
+ protocols. However, some clients actually still need this to
+ boot.</para>
+ </refsection>
+
+ <refsection xml:id="options">
+ <info>
+ <title>OPTIONS</title>
+ </info>
+ <variablelist remap="TP">
+ <varlistentry>
+ <term>
+ <option>-a</option>
+ </term>
+ <listitem>
+ <para>Listen on all available interfaces. Currently it is an
+ internal option, its function is overwritten with the
+ <emphasis remap="I">interface</emphasis> argument. It
+ should not be used.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-A</option>
+ </term>
+ <listitem>
+ <para>Listen not only to RARP but also ARP messages. Some
+ rare clients use ARP for some unknown reason.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-v</option>
+ </term>
+ <listitem>
+ <para>Be verbose.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-d</option>
+ </term>
+ <listitem>
+ <para>Debug mode. Do not go to background.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-e</option>
+ </term>
+ <listitem>
+ <para>Do not check for the presence of a boot image. Reply if
+ MAC address resolves to a valid IP address using
+ <filename>/etc/ethers</filename> database and DNS.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-b</option>
+ <emphasis remap="I">bootdir</emphasis>
+ </term>
+ <listitem>
+ <para>TFTP boot directory. Default is
+ <filename>/etc/tftpboot</filename></para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-V</option>
+ </term>
+ <listitem>
+ <para>Print version and exit.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsection>
+
+ <refsection xml:id="see_also">
+ <info>
+ <title>SEE ALSO</title>
+ </info>
+ <para>
+ <citerefentry>
+ <refentrytitle>arping</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>,
+ <citerefentry>
+ <refentrytitle>tftpd</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>.</para>
+ </refsection>
+
+ <refsection xml:id="author">
+ <info>
+ <title>AUTHOR</title>
+ </info>
+ <para>
+ <command>rarpd</command> was written by Alexey Kuznetsov
+ <kuznet@ms2.inr.ac.ru>.</para>
+ </refsection>
+
+ <refsection xml:id="security">
+ <info>
+ <title>SECURITY</title>
+ </info>
+ <para>
+ <command>rarpd</command> requires CAP_NET_RAW capability to
+ listen and send RARP and ARP packets. It also needs
+ CAP_NET_ADMIN to assist the kernel with ARP resolution; this
+ is not strictly required, but some (to be more exact: most) of
+ the clients are so badly broken that they are not able to answer
+ to ARP before they are fully booted. This is no surprise, taking
+ into account that clients using RARPD in 2002 are all
+ unsupported relic creatures of the 90's and even earlier.</para>
+ </refsection>
+
+ <refsection xml:id="availability">
+ <info>
+ <title>AVAILABILITY</title>
+ </info>
+ <para>
+ <emphasis remap="B">rarpd</emphasis> is part of the
+ <emphasis remap="I">iputils</emphasis> package.</para>
+ </refsection>
+</refentry>
Index: iputils-20210202-new/doc/rdisc.xml
===================================================================
--- iputils-20210202-new/doc/rdisc.xml (nonexistent)
+++ iputils-20210202-new/doc/rdisc.xml (revision 5)
@@ -0,0 +1,265 @@
+<refentry xmlns:db="http://docbook.org/ns/docbook" version="5.0"
+xml:id="man.rdisc">
+
+ <refentryinfo>
+ <title>rdisc</title>
+ <productname>iputils</productname>
+ </refentryinfo>
+
+ <refmeta>
+ <refentrytitle>
+ <application>rdisc</application>
+ </refentrytitle>
+ <manvolnum>8</manvolnum>
+ <refmiscinfo class='manual'>iputils</refmiscinfo>
+ </refmeta>
+
+ <refnamediv>
+ <refname>rdisc</refname>
+ <refpurpose>network router discovery daemon</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv>
+ <cmdsynopsis>
+ <command>rdisc</command>
+ <arg choice="opt" rep="norepeat">
+ <option>-abdfrstvV</option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-p
+ <replaceable>preference</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-T
+ <replaceable>max_interval</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">send_address</arg>
+ <arg choice="opt" rep="norepeat">receive_address</arg>
+ </cmdsynopsis>
+ </refsynopsisdiv>
+
+ <refsection xml:id="description">
+ <info>
+ <title>DESCRIPTION</title>
+ </info>
+ <para>
+ <command>rdisc</command> implements client side of the ICMP
+ Internet Router Discovery Protocol (IRDP).
+ <command>rdisc</command> is invoked at boot time to populate the
+ network routing tables with default routes.</para>
+ <para>
+ <command>rdisc</command> listens on the ALL_HOSTS (224.0.0.1)
+ multicast address (or
+ <emphasis remap="I">receive_address</emphasis> if it is provided)
+ 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.</para>
+ <para>Optionally,
+ <command>rdisc</command> 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
+ <emphasis remap="I">send_address</emphasis> if it is provided)
+ when it is started.</para>
+ <para>A timer is associated with each router address and the
+ address will no longer be considered for inclusion in the
+ routing tables if the timer expires before a new
+ <emphasis remap="B">advertise</emphasis> message is received
+ from the router. The address will also be excluded from
+ consideration if the received
+ <emphasis remap="B">advertise</emphasis> message has a
+ preference of maximum negative.</para>
+ <para>Server side of router discovery protocol is supported by
+ Cisco IOS and by any more or less complete UNIX routing daemon,
+ for example
+ <emphasis remap="B">gated</emphasis>. If compiled with
+ ENABLE_RDISC_SERVER, <command>rdisc</command> can act as
+ responder.</para>
+ </refsection>
+
+ <refsection xml:id="options">
+ <info>
+ <title>OPTIONS</title>
+ </info>
+ <variablelist remap="TP">
+ <varlistentry>
+ <term>
+ <option>-a</option>
+ </term>
+ <listitem>
+ <para>Accept all routers independently of the preference
+ they have in their
+ <emphasis remap="B">advertise</emphasis> messages.
+ Normally
+ <command>rdisc</command> only accepts (and enters in the
+ kernel routing tables) the router or routers with the
+ highest preference.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-b</option>
+ </term>
+ <listitem>
+ <para>Opposite to
+ <option>-a</option>, i.e. install only router with the
+ best preference value. This is the default behaviour.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-d</option>
+ </term>
+ <listitem>
+ <para>Send debugging messages to syslog.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-f</option>
+ </term>
+ <listitem>
+ <para>Keep
+ <command>rdisc</command> running in the background even
+ if no routers are found. Normally
+ <command>rdisc</command> gives up if it has not received
+ any
+ <emphasis remap="B">advertise</emphasis> message after
+ soliciting three times. In this case it exits with
+ a non-zero exit code. If
+ <option>-f</option> is not specified in the first form
+ then
+ <option>-s</option> must be specified.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-r</option>
+ </term>
+ <listitem>
+ <para>Responder mode, available only if compiled with
+ ENABLE_RDISC_SERVER.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-s</option>
+ </term>
+ <listitem>
+ <para>Send three
+ <emphasis remap="B">solicitation</emphasis> messages
+ initially to quickly discover the routers when the system
+ is booted. When
+ <option>-s</option> is specified
+ <command>rdisc</command> exits with a non-zero exit code
+ if it can not find any routers. This can be overridden
+ with the
+ <option>-f</option> option.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-p</option>
+ <emphasis remap="I">preference</emphasis>
+ </term>
+ <listitem>
+ <para>Set preference in advertisement messages. Available only
+ with -r option.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-T</option>
+ <emphasis remap="I">max_interval</emphasis>
+ </term>
+ <listitem>
+ <para>Set maximum advertisement interval in seconds.
+ Default is 600. Available only with -r
+ option.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-t</option>
+ </term>
+ <listitem>
+ <para>Test mode. Do not go to background.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-v</option>
+ </term>
+ <listitem>
+ <para>Be verbose and send lots of debugging messages to
+ syslog.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-V</option>
+ </term>
+ <listitem>
+ <para>Print version and exit.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsection>
+
+ <refsection xml:id="history">
+ <info>
+ <title>HISTORY</title>
+ </info>
+ <para>This program was developed by Sun Microsystems (see
+ copyright notice in source file). It was ported to Linux by
+ Alexey Kuznetsov <email>kuznet@ms2.inr.ac.ru</email>.</para>
+ </refsection>
+
+ <refsection xml:id="see_also">
+ <info>
+ <title>SEE ALSO</title>
+ </info>
+ <para>
+ <citerefentry>
+ <refentrytitle>icmp</refentrytitle>
+ <manvolnum>7</manvolnum>
+ </citerefentry>,
+ <citerefentry>
+ <refentrytitle>inet</refentrytitle>
+ <manvolnum>7</manvolnum>
+ </citerefentry>,
+ <citerefentry>
+ <refentrytitle>ping</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>.</para>
+ </refsection>
+
+ <refsection xml:id="references">
+ <info>
+ <title>REFERENCES</title>
+ </info>
+ <para>RFC1256 ICMP Router Discovery Messages. S. Deering, Ed..
+ September 1991.</para>
+ </refsection>
+
+ <refsection xml:id="security">
+ <info>
+ <title>SECURITY</title>
+ </info>
+ <para>
+ <command>rdisc</command> requires CAP_NET_RAW to listen and send
+ ICMP messages and capability CAP_NET_ADMIN to update routing
+ tables.</para>
+ </refsection>
+
+ <refsection xml:id="availability">
+ <info>
+ <title>AVAILABILITY</title>
+ </info>
+ <para>
+ <command>rdisc</command> is part of
+ <emphasis remap="I">iputils</emphasis> package.</para>
+ </refsection>
+</refentry>
Index: iputils-20210202-new/doc/tftpd.xml
===================================================================
--- iputils-20210202-new/doc/tftpd.xml (nonexistent)
+++ iputils-20210202-new/doc/tftpd.xml (revision 5)
@@ -0,0 +1,152 @@
+<refentry xmlns:db="http://docbook.org/ns/docbook" version="5.0"
+xml:id="man.tftpd">
+
+ <refentryinfo>
+ <title>tftpd</title>
+ <productname>iputils</productname>
+ </refentryinfo>
+
+ <refmeta>
+ <refentrytitle>
+ <application>tftpd</application>
+ </refentrytitle>
+ <manvolnum>8</manvolnum>
+ <refmiscinfo class='manual'>iputils</refmiscinfo>
+ </refmeta>
+
+ <refnamediv>
+ <refname>tftpd</refname>
+ <refpurpose>Trivial File Transfer Protocol server</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv xml:id="synopsis">
+ <cmdsynopsis>
+ <command>tftpd</command>
+ <arg choice="opt" rep="norepeat">-V</arg>
+ <arg choice="plain" rep="norepeat">
+ <replaceable>directory</replaceable>
+ </arg>
+ <sbr />
+ </cmdsynopsis>
+ </refsynopsisdiv>
+
+ <refsection xml:id="description">
+ <info>
+ <title>DESCRIPTION</title>
+ </info>
+ <para>
+ <command>tftpd</command> is a server which supports the DARPA
+ Trivial File Transfer Protocol (RFC1350). The TFTP server is
+ started by
+ <citerefentry>
+ <refentrytitle>inetd</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>.</para>
+ <para>
+ <emphasis remap="I">directory</emphasis> is required argument;
+ if it is not given
+ <command>tftpd</command> aborts. This path is prepended to any
+ file name requested via TFTP protocol, effectively chrooting
+ <command>tftpd</command> to this directory. File names are
+ validated not to escape out of this directory, however
+ administrator may configure such escape using symbolic
+ links.</para>
+ <para>It is in difference of variants of
+ <command>tftpd</command> 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.</para>
+ <para>In the case when
+ <command>tftpd</command> is used together with
+ <citerefentry>
+ <refentrytitle>rarpd</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>, 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
+ <citerefentry>
+ <refentrytitle>rarpd</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry> for more details.</para>
+ </refsection>
+
+ <refsection xml:id="security">
+ <info>
+ <title>SECURITY</title>
+ </info>
+ <para>TFTP protocol does not provide any authentication. Due to
+ this capital flaw
+ <command>tftpd</command> is not able to restrict access to files
+ and will allow only publicly readable files to be accessed.
+ Files may be written only if they already exist and are
+ publicly writable.</para>
+ <para>Impact is evident, directory exported via TFTP
+ <emphasis remap="B">must not</emphasis> 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
+ <emphasis remap="B">unencrypted</emphasis> passwords and may
+ contain some information about the network, which you were not
+ going to make public.</para>
+ <para>The
+ <command>tftpd</command> server should be executed by
+ <emphasis remap="B">inetd</emphasis> 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,
+ <command>tftpd</command> 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.</para>
+ </refsection>
+
+ <refsection xml:id="see_also">
+ <info>
+ <title>SEE ALSO</title>
+ </info>
+ <para>
+ <citerefentry>
+ <refentrytitle>rarpd</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>,
+ <citerefentry>
+ <refentrytitle>tftp</refentrytitle>
+ <manvolnum>1</manvolnum>
+ </citerefentry>,
+ <citerefentry>
+ <refentrytitle>inetd</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>.</para>
+ </refsection>
+
+ <refsection xml:id="history">
+ <info>
+ <title>HISTORY</title>
+ </info>
+ <para>The
+ <command>tftpd</command> command appeared in 4.2BSD. The source
+ in iputils is cleaned up both syntactically (ANSIized) and
+ semantically (UDP socket IO).</para>
+ <para>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.</para>
+ </refsection>
+
+ <refsection xml:id="availability">
+ <info>
+ <title>AVAILABILITY</title>
+ </info>
+ <para>
+ <command>tftpd</command> is part of
+ <emphasis remap="I">iputils</emphasis> package.</para>
+ </refsection>
+</refentry>
Index: iputils-20210202-new/doc/tracepath.xml
===================================================================
--- iputils-20210202-new/doc/tracepath.xml (nonexistent)
+++ iputils-20210202-new/doc/tracepath.xml (revision 5)
@@ -0,0 +1,232 @@
+<refentry xmlns:db="http://docbook.org/ns/docbook" version="5.0"
+xml:id="man.tracepath">
+
+ <refentryinfo>
+ <title>tracepath</title>
+ <productname>iputils</productname>
+ </refentryinfo>
+
+ <refmeta>
+ <refentrytitle><application>tracepath</application></refentrytitle>
+ <manvolnum>8</manvolnum>
+ <refmiscinfo class='manual'>iputils</refmiscinfo>
+ </refmeta>
+
+ <refnamediv>
+ <refname><application>tracepath</application></refname>
+ <refpurpose>traces path to a network host discovering MTU along
+ this path</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv>
+ <cmdsynopsis sepchar=" ">
+ <command>tracepath</command>
+ <arg choice="opt" rep="norepeat">
+ <option>-4</option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-6</option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-n</option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-b</option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-l
+ <replaceable>pktlen</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-m
+ <replaceable>max_hops</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-p
+ <replaceable>port</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-V</option>
+ </arg>
+ <arg choice="req" rep="norepeat">destination</arg>
+ </cmdsynopsis>
+ </refsynopsisdiv>
+
+ <refsection>
+ <info>
+ <title>DESCRIPTION</title>
+ </info>
+ <para>It traces the network path to
+ <emphasis remap='I'>destination</emphasis> discovering MTU along
+ this path. It uses UDP port
+ <emphasis remap='I'>port</emphasis> or some random port. It is
+ similar to
+ <emphasis remap='B'>traceroute</emphasis>. However, it does not
+ require superuser privileges and has no fancy options.</para>
+ <para>
+ <emphasis remap='B'>tracepath -6</emphasis> is a good replacement
+ for
+ <emphasis remap='B'>traceroute6</emphasis> 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 are updated. For now it uses Van Jacobson's
+ trick, sweeping a range of UDP ports to maintain trace
+ history.</para>
+ </refsection>
+
+ <refsection>
+ <info>
+ <title>OPTIONS</title>
+ </info>
+ <variablelist remap='TP'>
+ <varlistentry>
+ <term>
+ <option>-4</option>
+ </term>
+ <listitem>
+ <para>Use IPv4 only.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-6</option>
+ </term>
+ <listitem>
+ <para>Use IPv6 only.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-n</option>
+ </term>
+ <listitem>
+ <para>Print primarily IP addresses numerically.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-b</option>
+ </term>
+ <listitem>
+ <para>Print both: Host names and IP addresses.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-l</option>
+ </term>
+ <listitem>
+ <para>Sets the initial packet length to
+ <emphasis remap='I'>pktlen</emphasis> instead of 65535 for
+ <emphasis remap='B'>IPv4</emphasis> or 128000 for
+ <emphasis remap='B'>IPv6</emphasis>.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-m</option>
+ </term>
+ <listitem>
+ <para>Set maximum hops (or maximum TTLs) to
+ <emphasis remap='I'>max_hops</emphasis> instead of
+ 30.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-p</option>
+ </term>
+ <listitem>
+ <para>Sets the initial destination port to use.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <option>-V</option>
+ </term>
+ <listitem>
+ <para>Print version and exit.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsection>
+
+ <refsect1 id='output'>
+ <title>OUTPUT</title>
+ <literallayout remap='.nf'>
+root@mops:~ # tracepath -6 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
+ </literallayout>
+ <para>The first column shows the TTL of the probe, followed by
+ colon. Usually the value of TTL is obtained from the reply from
+ the network, but sometimes it does not contain the necessary
+ information and we have to guess it. In this case the number is
+ followed by ?.</para>
+ <para>The second column shows the network hop which replied to
+ the probe. It is either the address of the router or the word
+ [LOCALHOST], if the probe was not sent to the network.</para>
+ <para>The rest of the line shows miscellaneous information about
+ the path to the corresponding network hop. It contains
+ the value of RTT, and additionally it can show Path MTU when it
+ changes. If the path is asymmetric or the probe finishes before
+ it reaches the prescribed hop, the difference between number of
+ hops in forward and return direction is shown next to the
+ keyword "async". This information is not reliable, e.g. the
+ third line shows asymmetry of 1. This is because the first probe
+ with TTL of 2 was rejected at the first hop due to Path MTU
+ Discovery.</para>
+ <para>The last line summarizes information about all the paths
+ to the destination. It shows detected Path MTU, amount of hops
+ to the destination and our guess about the number of hops from
+ the destination to us, which can be different when the path is
+ asymmetric.</para>
+ </refsect1>
+
+ <refsect1 id='see_also'>
+ <title>SEE ALSO</title>
+ <para>
+ <citerefentry>
+ <refentrytitle>traceroute</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>,
+ <citerefentry>
+ <refentrytitle>traceroute6</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>,
+ <citerefentry>
+ <refentrytitle>ping</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>.</para>
+ </refsect1>
+
+ <refsect1 id='author'>
+ <title>AUTHOR</title>
+ <para>
+ <command>tracepath</command> was written by Alexey Kuznetsov
+ <kuznet@ms2.inr.ac.ru>.</para>
+ </refsect1>
+
+ <refsect1 id='security'>
+ <title>SECURITY</title>
+ <para>No security issues.</para>
+ <para>This lapidary deserves to be elaborated.
+ <command>tracepath</command> is not a privileged program, unlike
+ <command>traceroute</command>,
+ <command>ping</command> and other beasts of their kind.
+ <command>tracepath</command> may be executed by everyone who has
+ enough access to the network to send UDP datagrams to the
+ desired destination using the given port.</para>
+ </refsect1>
+
+ <refsect1 id='availability'>
+ <title>AVAILABILITY</title>
+ <para>
+ <command>tracepath</command> is part of
+ <emphasis remap='I'>iputils</emphasis> package.</para>
+ </refsect1>
+</refentry>
Index: iputils-20210202-new/doc/traceroute6.xml
===================================================================
--- iputils-20210202-new/doc/traceroute6.xml (nonexistent)
+++ iputils-20210202-new/doc/traceroute6.xml (revision 5)
@@ -0,0 +1,111 @@
+<refentry xmlns:db="http://docbook.org/ns/docbook" version="5.0"
+xml:id="man.traceroute6">
+
+ <refentryinfo>
+ <title>traceroute6</title>
+ <productname>iputils</productname>
+ </refentryinfo>
+
+ <refmeta>
+ <refentrytitle>
+ <application>traceroute6</application>
+ </refentrytitle>
+ <manvolnum>8</manvolnum>
+ <refmiscinfo class='manual'>iputils</refmiscinfo>
+ </refmeta>
+
+ <refnamediv>
+ <refname>traceroute6</refname>
+ <refpurpose>traces path to a network host</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv>
+ <cmdsynopsis sepchar=" ">
+ <command>traceroute6</command>
+ <arg choice="opt" rep="norepeat">
+ <option>-dnrvV</option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-i
+ <replaceable>interface</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-m
+ <replaceable>max_ttl</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-p
+ <replaceable>port</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-q
+ <replaceable>max_probes</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-s
+ <replaceable>source</replaceable></option>
+ </arg>
+ <arg choice="opt" rep="norepeat">
+ <option>-w
+ <replaceable>wait time</replaceable></option>
+ </arg>
+ <arg choice="req" rep="norepeat">destination</arg>
+ <arg choice="opt" rep="norepeat">size</arg>
+ </cmdsynopsis>
+ </refsynopsisdiv>
+
+ <refsection>
+ <info>
+ <title>DESCRIPTION</title>
+ </info>
+ <para>Description can be found in
+ <citerefentry>
+ <refentrytitle>traceroute</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>, all the references to IP replaced to IPv6.
+ It is needless to copy the description from there.</para>
+ </refsection>
+
+ <refsect1 id='see_also'>
+ <title>SEE ALSO</title>
+ <para>
+ <citerefentry>
+ <refentrytitle>traceroute</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>,
+ <citerefentry>
+ <refentrytitle>tracepath</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>,
+ <citerefentry>
+ <refentrytitle>ping</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>.</para>
+ </refsect1>
+
+ <refsect1 id='history'>
+ <title>HISTORY</title>
+ <para>This program has long history. Author of
+ <command>traceroute</command> is Van Jacobson and it first
+ appeared in 1988. This clone is based on a port of
+ <command>traceroute</command> 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
+ <emphasis remap="B">iputils</emphasis> package.</para>
+ </refsect1>
+
+ <refsect1 id='security'>
+ <title>SECURITY</title>
+ <para>
+ <command>traceroute6</command> requires CAP_NET_RAW capability
+ to be executed. It is safe to be used as set-uid root.</para>
+ </refsect1>
+
+ <refsect1 id='availability'>
+ <title>AVAILABILITY</title>
+ <para>
+ <command>traceroute6</command> is part of
+ <emphasis remap='I'>iputils</emphasis> package.</para>
+ </refsect1>
+</refentry>
Index: iputils-20210202-new/doc
===================================================================
--- iputils-20210202-new/doc (nonexistent)
+++ iputils-20210202-new/doc (revision 5)
Property changes on: iputils-20210202-new/doc
___________________________________________________________________
Added: svn:ignore
## -0,0 +1,73 ##
+
+# install dir
+dist
+
+# Target build dirs
+.a1x-newlib
+.a2x-newlib
+.at91sam7s-newlib
+
+.build-machine
+
+.a1x-glibc
+.a2x-glibc
+.h3-glibc
+.h5-glibc
+.i586-glibc
+.i686-glibc
+.imx6-glibc
+.jz47xx-glibc
+.makefile
+.am335x-glibc
+.omap543x-glibc
+.p5600-glibc
+.power8-glibc
+.power8le-glibc
+.power9-glibc
+.power9le-glibc
+.m1000-glibc
+.riscv64-glibc
+.rk328x-glibc
+.rk33xx-glibc
+.rk339x-glibc
+.s8xx-glibc
+.s9xx-glibc
+.x86_64-glibc
+
+# Hidden files (each file)
+.makefile
+.dist
+.rootfs
+
+# src & hw requires
+.src_requires
+.src_requires_depend
+.requires
+.requires_depend
+
+# Tarballs
+*.gz
+*.bz2
+*.lz
+*.xz
+*.tgz
+*.txz
+
+# Signatures
+*.asc
+*.sig
+*.sign
+*.sha1sum
+
+# Patches
+*.patch
+
+# Descriptions
+*.dsc
+*.txt
+
+# Default linux config files
+*.defconfig
+
+# backup copies
+*~
Index: iputils-20210202-new
===================================================================
--- iputils-20210202-new (nonexistent)
+++ iputils-20210202-new (revision 5)
Property changes on: iputils-20210202-new
___________________________________________________________________
Added: svn:ignore
## -0,0 +1,73 ##
+
+# install dir
+dist
+
+# Target build dirs
+.a1x-newlib
+.a2x-newlib
+.at91sam7s-newlib
+
+.build-machine
+
+.a1x-glibc
+.a2x-glibc
+.h3-glibc
+.h5-glibc
+.i586-glibc
+.i686-glibc
+.imx6-glibc
+.jz47xx-glibc
+.makefile
+.am335x-glibc
+.omap543x-glibc
+.p5600-glibc
+.power8-glibc
+.power8le-glibc
+.power9-glibc
+.power9le-glibc
+.m1000-glibc
+.riscv64-glibc
+.rk328x-glibc
+.rk33xx-glibc
+.rk339x-glibc
+.s8xx-glibc
+.s9xx-glibc
+.x86_64-glibc
+
+# Hidden files (each file)
+.makefile
+.dist
+.rootfs
+
+# src & hw requires
+.src_requires
+.src_requires_depend
+.requires
+.requires_depend
+
+# Tarballs
+*.gz
+*.bz2
+*.lz
+*.xz
+*.tgz
+*.txz
+
+# Signatures
+*.asc
+*.sig
+*.sign
+*.sha1sum
+
+# Patches
+*.patch
+
+# Descriptions
+*.dsc
+*.txt
+
+# Default linux config files
+*.defconfig
+
+# backup copies
+*~
Index: .
===================================================================
--- . (nonexistent)
+++ . (revision 5)
Property changes on: .
___________________________________________________________________
Added: svn:ignore
## -0,0 +1,73 ##
+
+# install dir
+dist
+
+# Target build dirs
+.a1x-newlib
+.a2x-newlib
+.at91sam7s-newlib
+
+.build-machine
+
+.a1x-glibc
+.a2x-glibc
+.h3-glibc
+.h5-glibc
+.i586-glibc
+.i686-glibc
+.imx6-glibc
+.jz47xx-glibc
+.makefile
+.am335x-glibc
+.omap543x-glibc
+.p5600-glibc
+.power8-glibc
+.power8le-glibc
+.power9-glibc
+.power9le-glibc
+.m1000-glibc
+.riscv64-glibc
+.rk328x-glibc
+.rk33xx-glibc
+.rk339x-glibc
+.s8xx-glibc
+.s9xx-glibc
+.x86_64-glibc
+
+# Hidden files (each file)
+.makefile
+.dist
+.rootfs
+
+# src & hw requires
+.src_requires
+.src_requires_depend
+.requires
+.requires_depend
+
+# Tarballs
+*.gz
+*.bz2
+*.lz
+*.xz
+*.tgz
+*.txz
+
+# Signatures
+*.asc
+*.sig
+*.sign
+*.sha1sum
+
+# Patches
+*.patch
+
+# Descriptions
+*.dsc
+*.txt
+
+# Default linux config files
+*.defconfig
+
+# backup copies
+*~
Radix cross Linux
The main Radix cross Linux repository contains the build scripts of packages, which have the most complete and common functionality for desktop machines
452 Commits
2 Branches
1 Tag