source: patches/iputils-s20150815-build-1.patch @ 8673d375

systemd
Last change on this file since 8673d375 was 9163b06, checked in by William Harrington <kb0iic@…>, 9 years ago

Remove old iputils patch and add new iputils build patch.

  • Property mode set to 100644
File size: 45.7 KB
  • iputils-s20150815

    Submitted By: William Harrington <kb0iic at cross-lfs dot org>
    Date: 2015-08-30
    Initial Package Version: s20150815
    Upstream Status: Applied
    Origin: git://git.linux-ipv6.org/gitroot/iputils.git
    Description: Edits Makefile USE_ Variables and includes man pages.
    
    diff -Naur iputils-s20150815.orig/Makefile iputils-s20150815/Makefile
    old new  
    2727# sysfs support (with libsysfs - deprecated) [no|yes|static]
    2828USE_SYSFS=no
    2929# IDN support  [yes|no|static]
    30 USE_IDN=yes
     30USE_IDN=no
    3131
    3232# Do not use getifaddrs [no|yes|static]
    3333WITHOUT_IFADDRS=no
     
    3535ARPING_DEFAULT_DEVICE=
    3636
    3737# nettle library for ipv6 ping [yes|no|static]
    38 USE_NETTLE=yes
     38USE_NETTLE=no
    3939# libgcrypt library for ipv6 ping [no|yes|static]
    4040USE_GCRYPT=no
    4141# Crypto library for ping6 [shared|static|no]
  • iputils-s20150815

    diff -Naur iputils-s20150815.orig/doc/arping.8 iputils-s20150815/doc/arping.8
    old new  
     1.\" This manpage has been automatically generated by docbook2man
     2.\" from a DocBook document.  This tool can be found at:
     3.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
     4.\" Please send any bug reports, improvements, comments, patches,
     5.\" etc. to Steve Cheng <steve@ggi-project.org>.
     6.TH "ARPING" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
     7.SH NAME
     8arping \- send ARP REQUEST to a neighbour host
     9.SH SYNOPSIS
     10
     11\fBarping\fR [\fB-AbDfhqUV\fR] [\fB-c \fIcount\fB\fR] [\fB-w \fIdeadline\fB\fR] [\fB-s \fIsource\fB\fR] \fB-I \fIinterface\fB\fR \fB\fIdestination\fB\fR
     12
     13.SH "DESCRIPTION"
     14.PP
     15Ping \fIdestination\fR on device \fIinterface\fR by ARP packets,
     16using source address \fIsource\fR.
     17.SH "OPTIONS"
     18.TP
     19\fB-A\fR
     20The same as \fB-U\fR, but ARP REPLY packets used instead
     21of ARP REQUEST.
     22.TP
     23\fB-b\fR
     24Send only MAC level broadcasts. Normally \fBarping\fR starts
     25from sending broadcast, and switch to unicast after reply received.
     26.TP
     27\fB-c \fIcount\fB\fR
     28Stop after sending \fIcount\fR ARP REQUEST
     29packets. With
     30\fIdeadline\fR
     31option, instead wait for
     32\fIcount\fR ARP REPLY packets, or until the timeout expires.
     33.TP
     34\fB-D\fR
     35Duplicate address detection mode (DAD). See
     36RFC2131, 4.4.1.
     37Returns 0, if DAD succeeded i.e. no replies are received
     38.TP
     39\fB-f\fR
     40Finish after the first reply confirming that target is alive.
     41.TP
     42\fB-I \fIinterface\fB\fR
     43Name of network device where to send ARP REQUEST packets.
     44.TP
     45\fB-h\fR
     46Print help page and exit.
     47.TP
     48\fB-q\fR
     49Quiet output. Nothing is displayed.
     50.TP
     51\fB-s \fIsource\fB\fR
     52IP source address to use in ARP packets.
     53If this option is absent, source address is:
     54.RS
     55.TP 0.2i
     56\(bu
     57In DAD mode (with option \fB-D\fR) set to 0.0.0.0.
     58.TP 0.2i
     59\(bu
     60In Unsolicited ARP mode (with options \fB-U\fR or \fB-A\fR)
     61set to \fIdestination\fR.
     62.TP 0.2i
     63\(bu
     64Otherwise, it is calculated from routing tables.
     65.RE
     66.TP
     67\fB-U\fR
     68Unsolicited ARP mode to update neighbours' ARP caches.
     69No replies are expected.
     70.TP
     71\fB-V\fR
     72Print version of the program and exit.
     73.TP
     74\fB-w \fIdeadline\fB\fR
     75Specify a timeout, in seconds, before
     76\fBarping\fR
     77exits regardless of how many
     78packets have been sent or received. In this case
     79\fBarping\fR
     80does not stop after
     81\fIcount\fR
     82packet are sent, it waits either for
     83\fIdeadline\fR
     84expire or until
     85\fIcount\fR
     86probes are answered.
     87.SH "SEE ALSO"
     88.PP
     89\fBping\fR(8),
     90\fBclockdiff\fR(8),
     91\fBtracepath\fR(8).
     92.SH "AUTHOR"
     93.PP
     94\fBarping\fR was written by
     95Alexey Kuznetsov
     96<kuznet@ms2.inr.ac.ru>.
     97It is now maintained by
     98YOSHIFUJI Hideaki
     99<yoshfuji@skbuff.net>.
     100.SH "SECURITY"
     101.PP
     102\fBarping\fR requires CAP_NET_RAW capability
     103to be executed. It is not recommended to be used as set-uid root,
     104because it allows user to modify ARP caches of neighbour hosts.
     105.SH "AVAILABILITY"
     106.PP
     107\fBarping\fR is part of \fIiputils\fR package
     108and the latest versions are  available in source form at
     109http://www.skbuff.net/iputils/iputils-current.tar.bz2.
  • iputils-s20150815

    diff -Naur iputils-s20150815.orig/doc/clockdiff.8 iputils-s20150815/doc/clockdiff.8
    old new  
     1.\" This manpage has been automatically generated by docbook2man
     2.\" from a DocBook document.  This tool can be found at:
     3.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
     4.\" Please send any bug reports, improvements, comments, patches,
     5.\" etc. to Steve Cheng <steve@ggi-project.org>.
     6.TH "CLOCKDIFF" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
     7.SH NAME
     8clockdiff \- measure clock difference between hosts
     9.SH SYNOPSIS
     10
     11\fBclockdiff\fR [\fB-o\fR] [\fB-o1\fR] \fB\fIdestination\fB\fR
     12
     13.SH "DESCRIPTION"
     14.PP
     15\fBclockdiff\fR Measures clock difference between us and
     16\fIdestination\fR with 1 msec resolution using ICMP TIMESTAMP
     17[2]
     18packets or, optionally, IP TIMESTAMP option
     19[3]
     20option added to ICMP ECHO.
     21[1]
     22.SH "OPTIONS"
     23.TP
     24\fB-o\fR
     25Use IP TIMESTAMP with ICMP ECHO instead of ICMP TIMESTAMP
     26messages. It is useful with some destinations, which do not support
     27ICMP TIMESTAMP (f.e. Solaris <2.4).
     28.TP
     29\fB-o1\fR
     30Slightly different form of \fB-o\fR, namely it uses three-term
     31IP TIMESTAMP with prespecified hop addresses instead of four term one.
     32What flavor works better depends on target host. Particularly,
     33\fB-o\fR is better for Linux.
     34.SH "WARNINGS"
     35.TP 0.2i
     36\(bu
     37Some nodes (Cisco) use non-standard timestamps, which is allowed
     38by RFC, but makes timestamps mostly useless.
     39.TP 0.2i
     40\(bu
     41Some nodes generate messed timestamps (Solaris>2.4), when
     42run \fBxntpd\fR. Seems, its IP stack uses a corrupted clock source,
     43which is synchronized to time-of-day clock periodically and jumps
     44randomly making timestamps mostly useless. Good news is that you can
     45use NTP in this case, which is even better.
     46.TP 0.2i
     47\(bu
     48\fBclockdiff\fR shows difference in time modulo 24 days.
     49.SH "SEE ALSO"
     50.PP
     51\fBping\fR(8),
     52\fBarping\fR(8),
     53\fBtracepath\fR(8).
     54.SH "REFERENCES"
     55.PP
     56[1] ICMP ECHO,
     57RFC0792, page 14.
     58.PP
     59[2] ICMP TIMESTAMP,
     60RFC0792, page 16.
     61.PP
     62[3] IP TIMESTAMP option,
     63RFC0791, 3.1, page 16.
     64.SH "AUTHOR"
     65.PP
     66\fBclockdiff\fR was compiled by
     67Alexey Kuznetsov
     68<kuznet@ms2.inr.ac.ru>. It was based on code borrowed
     69from BSD \fBtimed\fR daemon.
     70It is now maintained by
     71YOSHIFUJI Hideaki
     72<yoshfuji@skbuff.net>.
     73.SH "SECURITY"
     74.PP
     75\fBclockdiff\fR requires CAP_NET_RAW capability
     76to be executed. It is safe to be used as set-uid root.
     77.SH "AVAILABILITY"
     78.PP
     79\fBclockdiff\fR is part of \fIiputils\fR package
     80and the latest versions are  available in source form at
     81http://www.skbuff.net/iputils/iputils-current.tar.bz2.
  • iputils-s20150815

    diff -Naur iputils-s20150815.orig/doc/ninfod.8 iputils-s20150815/doc/ninfod.8
    old new  
     1.\" This manpage has been automatically generated by docbook2man
     2.\" from a DocBook document.  This tool can be found at:
     3.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
     4.\" Please send any bug reports, improvements, comments, patches,
     5.\" etc. to Steve Cheng <steve@ggi-project.org>.
     6.TH "NINFOD" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
     7.SH NAME
     8ninfod \- Respond to IPv6 Node Information Queries
     9.SH SYNOPSIS
     10
     11\fBninfod\fR [\fB-dhv\fR] [\fB-p \fIpidfile\fB\fR] [\fB-u \fIuser\fB\fR]
     12
     13.SH "DESCRIPTION"
     14.PP
     15Responds to IPv6 Node Information Queries (RFC4620) from clients.
     16Queries can be sent by various implementations of \fBping6\fR command.
     17.SH "OPTIONS"
     18.TP
     19\fB-a\fR
     20Debug mode.  Do not go background.
     21.TP
     22\fB-h\fR
     23Show help.
     24.TP
     25\fB-v\fR
     26Verbose mode.
     27.TP
     28\fB-u \fIuser\fB\fR
     29Run as another user.
     30\fIuser\fR can either be username or user ID.
     31.TP
     32\fB-p \fIpidfile\fB\fR
     33File for process-id storage.
     34\fIuser\fR is required to be able to create the file.
     35.SH "SEE ALSO"
     36.PP
     37\fBping\fR(8).
     38.SH "AUTHOR"
     39.PP
     40\fBninfod\fR was written by USAGI/WIDE Project.
     41.SH "COPYING"
     42.PP
     43
     44.nf
     45Copyright (C) 2012 YOSHIFUJI Hideaki.
     46Copyright (C) 2002 USAGI/WIDE Project.
     47All rights reserved.
     48
     49Redistribution and use in source and binary forms, with or without
     50modification, are permitted provided that the following conditions
     51are met:
     521. Redistributions of source code must retain the above copyright
     53   notice, this list of conditions and the following disclaimer.
     542. Redistributions in binary form must reproduce the above copyright
     55   notice, this list of conditions and the following disclaimer in the
     56   documentation and/or other materials provided with the distribution.
     573. Neither the name of the project nor the names of its contributors
     58   may be used to endorse or promote products derived from this software
     59   without specific prior written permission.
     60
     61THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND
     62ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
     63IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
     64ARE DISCLAIMED.  IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE
     65FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
     66DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
     67OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
     68HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
     69LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
     70OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
     71SUCH DAMAGE.
     72.fi
  • iputils-s20150815

    diff -Naur iputils-s20150815.orig/doc/pg3.8 iputils-s20150815/doc/pg3.8
    old new  
     1.\" This manpage has been automatically generated by docbook2man
     2.\" from a DocBook document.  This tool can be found at:
     3.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
     4.\" Please send any bug reports, improvements, comments, patches,
     5.\" etc. to Steve Cheng <steve@ggi-project.org>.
     6.TH "PG3" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
     7.SH NAME
     8pg3, ipg, pgset \- send stream of UDP packets
     9.SH SYNOPSIS
     10
     11\fBsource ipg\fR
     12
     13
     14\fBpg\fR
     15
     16
     17\fBpgset\fR \fB\fICOMMAND\fB\fR
     18
     19.SH "DESCRIPTION"
     20.PP
     21\fBipg\fR is not a program, it is script which should be sourced
     22to \fBbash\fR. When sourced it loads module \fIpg3\fR and
     23exports a few of functions accessible from parent shell. These macros
     24are \fBpg\fR to start packet injection and to get the results of run;
     25and \fBpgset\fR to setup packet generator.
     26.PP
     27\fBpgset\fR can send the following commands to module \fIpg3\fR:
     28.SH "COMMAND"
     29.TP
     30\fBodev \fIDEVICE\fB\fR
     31Name of Ethernet device to test. See
     32warning below.
     33.TP
     34\fBpkt_size \fIBYTES\fB\fR
     35Size of packet to generate. The size includes all the headers: UDP, IP,
     36MAC, but does not account for overhead internal to medium, i.e. FCS
     37and various paddings.
     38.TP
     39\fBfrags \fINUMBER\fB\fR
     40Each packet will contain \fINUMBER\fR of fragments.
     41Maximal amount for linux-2.4 is 6. Far not all the devices support
     42fragmented buffers.
     43.TP
     44\fBcount \fINUMBER\fB\fR
     45Send stream of \fINUMBER\fR of packets and stop after this.
     46.TP
     47\fBipg \fITIME\fB\fR
     48Introduce artificial delay between packets of \fITIME\fR
     49microseconds.
     50.TP
     51\fBdst \fIIP_ADDRESS\fB\fR
     52Select IP destination where the stream is sent to.
     53Beware, never set this address at random. \fBpg3\fR is not a toy,
     54it creates really tough stream. Default value is 0.0.0.0.
     55.TP
     56\fBdst \fIMAC_ADDRESS\fB\fR
     57Select MAC destination where the stream is sent to.
     58Default value is 00:00:00:00:00:00 in hope that this will not be received
     59by any node on LAN.
     60.TP
     61\fBstop\fR
     62Abort packet injection.
     63.SH "WARNING"
     64.PP
     65When output device is set to some random device different
     66of hardware Ethernet device, \fBpg3\fR will crash kernel.
     67.PP
     68Do not use it on VLAN, ethertap, VTUN and other devices,
     69which emulate Ethernet not being real Ethernet in fact.
     70.SH "AUTHOR"
     71.PP
     72\fBpg3\fR was written by Robert Olsson <robert.olsson@its.uu.se>.
     73.SH "SECURITY"
     74.PP
     75This can be used only by superuser.
     76.PP
     77This tool creates floods of packets which is unlikely to be handled
     78even by high-end machines. For example, it saturates gigabit link with
     7960 byte packets when used with Intel's e1000. In face of such stream
     80switches, routers and end hosts may deadlock, crash, explode.
     81Use only in test lab environment.
     82.SH "AVAILABILITY"
     83.PP
     84\fBpg3\fR is part of \fIiputils\fR package
     85and the latest versions are  available in source form at
     86http://www.skbuff.net/iputils/iputils-current.tar.bz2.
  • iputils-s20150815

    diff -Naur iputils-s20150815.orig/doc/ping.8 iputils-s20150815/doc/ping.8
    old new  
     1.\" This manpage has been automatically generated by docbook2man
     2.\" from a DocBook document.  This tool can be found at:
     3.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
     4.\" Please send any bug reports, improvements, comments, patches,
     5.\" etc. to Steve Cheng <steve@ggi-project.org>.
     6.TH "PING" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
     7.SH NAME
     8ping, ping6 \- send ICMP ECHO_REQUEST to network hosts
     9.SH SYNOPSIS
     10
     11\fBping\fR [\fB-aAbBdDfhLnOqrRUvV6\fR] [\fB-c \fIcount\fB\fR] [\fB-F \fIflowlabel\fB\fR] [\fB-i \fIinterval\fB\fR] [\fB-I \fIinterface\fB\fR] [\fB-l \fIpreload\fB\fR] [\fB-m \fImark\fB\fR] [\fB-M \fIpmtudisc_option\fB\fR] [\fB-N \fInodeinfo_option\fB\fR] [\fB-w \fIdeadline\fB\fR] [\fB-W \fItimeout\fB\fR] [\fB-p \fIpattern\fB\fR] [\fB-Q \fItos\fB\fR] [\fB-s \fIpacketsize\fB\fR] [\fB-S \fIsndbuf\fB\fR] [\fB-t \fIttl\fB\fR] [\fB-T \fItimestamp option\fB\fR] [\fB\fIhop\fB\fR\fI ...\fR] \fB\fIdestination\fB\fR
     12
     13.SH "DESCRIPTION"
     14.PP
     15\fBping\fR uses the ICMP protocol's mandatory ECHO_REQUEST
     16datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway.
     17ECHO_REQUEST datagrams (``pings'') have an IP and ICMP
     18header, followed by a struct timeval and then an arbitrary
     19number of ``pad'' bytes used to fill out the packet.
     20.PP
     21\fBping6\fR is IPv6 version of \fBping\fR, and can also send Node Information Queries (RFC4620).
     22Intermediate \fIhop\fRs may not be allowed, because IPv6 source routing was deprecated (RFC5095).
     23.SH "OPTIONS"
     24.TP
     25\fB-a\fR
     26Audible ping.
     27.TP
     28\fB-A\fR
     29Adaptive ping. Interpacket interval adapts to round-trip time, so that
     30effectively not more than one (or more, if preload is set) unanswered probe
     31is present in the network. Minimal interval is 200msec for not super-user.
     32On networks with low rtt this mode is essentially equivalent to flood mode. 
     33.TP
     34\fB-b\fR
     35Allow pinging a broadcast address.
     36.TP
     37\fB-B\fR
     38Do not allow \fBping\fR to change source address of probes.
     39The address is bound to one selected when \fBping\fR starts.
     40.TP
     41\fB-c \fIcount\fB\fR
     42Stop after sending \fIcount\fR ECHO_REQUEST
     43packets. With
     44\fIdeadline\fR
     45option, \fBping\fR waits for
     46\fIcount\fR ECHO_REPLY packets, until the timeout expires.
     47.TP
     48\fB-d\fR
     49Set the SO_DEBUG option on the socket being used.
     50Essentially, this socket option is not used by Linux kernel.
     51.TP
     52\fB-D\fR
     53Print timestamp (unix time + microseconds as in gettimeofday) before
     54each line.
     55.TP
     56\fB-f\fR
     57Flood ping. For every ECHO_REQUEST sent a period ``.'' is printed,
     58while for ever ECHO_REPLY received a backspace is printed.
     59This provides a rapid display of how many packets are being dropped.
     60If interval is not given, it sets interval to zero and
     61outputs packets as fast as they come back or one hundred times per second,
     62whichever is more.
     63Only the super-user may use this option with zero interval.
     64.TP
     65\fB-F \fIflow label\fB\fR
     66\fBping6\fR only.
     67Allocate and set 20 bit flow label (in hex) on echo request packets.
     68If value is zero, kernel allocates random flow label.
     69.TP
     70\fB-h\fR
     71Show help.
     72.TP
     73\fB-i \fIinterval\fB\fR
     74Wait \fIinterval\fR seconds between sending each packet.
     75The default is to wait for one second between each packet normally,
     76or not to wait in flood mode. Only super-user may set interval
     77to values less 0.2 seconds.
     78.TP
     79\fB-I \fIinterface\fB\fR
     80\fIinterface\fR is either an address, or an interface name.
     81If \fIinterface\fR is an address, it sets source address
     82to specified interface address.
     83If \fIinterface\fR in an interface name, it sets
     84source interface to specified interface.
     85For \fBping6\fR, when doing ping to a link-local scope
     86address, link specification (by the '%'-notation in
     87\fIdestination\fR, or by this option) is required.
     88.TP
     89\fB-l \fIpreload\fB\fR
     90If \fIpreload\fR is specified,
     91\fBping\fR sends that many packets not waiting for reply.
     92Only the super-user may select preload more than 3.
     93.TP
     94\fB-L\fR
     95Suppress loopback of multicast packets.  This flag only applies if the ping
     96destination is a multicast address.
     97.TP
     98\fB-m \fImark\fB\fR
     99use \fImark\fR to tag the packets going out. This is useful
     100for variety of reasons within the kernel such as using policy
     101routing to select specific outbound processing.
     102.TP
     103\fB-M \fIpmtudisc_opt\fB\fR
     104Select Path MTU Discovery strategy.
     105\fIpmtudisc_option\fR may be either \fIdo\fR
     106(prohibit fragmentation, even local one),
     107\fIwant\fR (do PMTU discovery, fragment locally when packet size
     108is large), or \fIdont\fR (do not set DF flag).
     109.TP
     110\fB-N \fInodeinfo_option\fB\fR
     111\fBping6\fR only.
     112Send ICMPv6 Node Information Queries (RFC4620), instead of Echo Request.
     113CAP_NET_RAW capability is required.
     114.RS
     115.TP
     116\fBhelp\fR
     117Show help for NI support.
     118.RE
     119.RS
     120.TP
     121\fBname\fR
     122Queries for Node Names.
     123.RE
     124.RS
     125.TP
     126\fBipv6\fR
     127Queries for IPv6 Addresses. There are several IPv6 specific flags.
     128.RS
     129.TP
     130\fBipv6-global\fR
     131Request IPv6 global-scope addresses.
     132.RE
     133.RS
     134.TP
     135\fBipv6-sitelocal\fR
     136Request IPv6 site-local addresses.
     137.RE
     138.RS
     139.TP
     140\fBipv6-linklocal\fR
     141Request IPv6 link-local addresses.
     142.RE
     143.RS
     144.TP
     145\fBipv6-all\fR
     146Request IPv6 addresses on other interfaces.
     147.RE
     148.RE
     149.RS
     150.TP
     151\fBipv4\fR
     152Queries for IPv4 Addresses.  There is one IPv4 specific flag.
     153.RS
     154.TP
     155\fBipv4-all\fR
     156Request IPv4 addresses on other interfaces.
     157.RE
     158.RE
     159.RS
     160.TP
     161\fBsubject-ipv6=\fIipv6addr\fB\fR
     162IPv6 subject address.
     163.RE
     164.RS
     165.TP
     166\fBsubject-ipv4=\fIipv4addr\fB\fR
     167IPv4 subject address.
     168.RE
     169.RS
     170.TP
     171\fBsubject-name=\fInodename\fB\fR
     172Subject name.  If it contains more than one dot,
     173fully-qualified domain name is assumed.
     174.RE
     175.RS
     176.TP
     177\fBsubject-fqdn=\fInodename\fB\fR
     178Subject name.  Fully-qualified domain name is
     179always assumed.
     180.RE
     181.TP
     182\fB-n\fR
     183Numeric output only.
     184No attempt will be made to lookup symbolic names for host addresses.
     185.TP
     186\fB-O\fR
     187Report outstanding ICMP ECHO reply before sending next packet.
     188This is useful together with the timestamp \fB-D\fR to
     189log output to a diagnostic file and search for missing answers.
     190.TP
     191\fB-p \fIpattern\fB\fR
     192You may specify up to 16 ``pad'' bytes to fill out the packet you send.
     193This is useful for diagnosing data-dependent problems in a network.
     194For example, \fB-p ff\fR will cause the sent packet
     195to be filled with all ones.
     196.TP
     197\fB-q\fR
     198Quiet output.
     199Nothing is displayed except the summary lines at startup time and
     200when finished.
     201.TP
     202\fB-Q \fItos\fB\fR
     203Set Quality of Service -related bits in ICMP datagrams.
     204\fItos\fR can be decimal (\fBping\fR only) or hex number.
     205
     206In RFC2474, these fields are interpreted as 8-bit Differentiated
     207Services (DS), consisting of: bits 0-1 (2 lowest bits) of separate
     208data, and bits 2-7 (highest 6 bits) of Differentiated Services
     209Codepoint (DSCP).  In RFC2481 and RFC3168, bits 0-1 are used for ECN.
     210
     211Historically (RFC1349, obsoleted by RFC2474), these were interpreted
     212as: bit 0 (lowest bit) for reserved (currently being redefined as
     213congestion control), 1-4 for Type of Service and bits 5-7
     214(highest bits) for Precedence.
     215.TP
     216\fB-r\fR
     217Bypass the normal routing tables and send directly to a host on an attached
     218interface.
     219If the host is not on a directly-attached network, an error is returned.
     220This option can be used to ping a local host through an interface
     221that has no route through it provided the option \fB-I\fR is also
     222used.
     223.TP
     224\fB-R\fR
     225\fBping\fR only.
     226Record route.
     227Includes the RECORD_ROUTE option in the ECHO_REQUEST
     228packet and displays the route buffer on returned packets.
     229Note that the IP header is only large enough for nine such routes.
     230Many hosts ignore or discard this option.
     231.TP
     232\fB-s \fIpacketsize\fB\fR
     233Specifies the number of data bytes to be sent. 
     234The default is 56, which translates into 64 ICMP
     235data bytes when combined with the 8 bytes of ICMP header data.
     236.TP
     237\fB-S \fIsndbuf\fB\fR
     238Set socket sndbuf. If not specified, it is selected to buffer
     239not more than one packet.
     240.TP
     241\fB-t \fIttl\fB\fR
     242\fBping\fR only.
     243Set the IP Time to Live.
     244.TP
     245\fB-T \fItimestamp option\fB\fR
     246Set special IP timestamp options.
     247\fItimestamp option\fR may be either
     248\fItsonly\fR (only timestamps),
     249\fItsandaddr\fR (timestamps and addresses) or
     250\fItsprespec host1 [host2 [host3 [host4]]]\fR
     251(timestamp prespecified hops).
     252.TP
     253\fB-U\fR
     254Print full user-to-user latency (the old behaviour). Normally
     255\fBping\fR
     256prints network round trip time, which can be different
     257f.e. due to DNS failures.
     258.TP
     259\fB-v\fR
     260Verbose output.
     261.TP
     262\fB-V\fR
     263Show version and exit.
     264.TP
     265\fB-w \fIdeadline\fB\fR
     266Specify a timeout, in seconds, before
     267\fBping\fR
     268exits regardless of how many
     269packets have been sent or received. In this case
     270\fBping\fR
     271does not stop after
     272\fIcount\fR
     273packet are sent, it waits either for
     274\fIdeadline\fR
     275expire or until
     276\fIcount\fR
     277probes are answered or for some error notification from network.   
     278.TP
     279\fB-W \fItimeout\fB\fR
     280Time to wait for a response, in seconds. The option affects only timeout
     281in absence of any responses, otherwise \fBping\fR waits for two RTTs.
     282.PP
     283When using \fBping\fR for fault isolation, it should first be run
     284on the local host, to verify that the local network interface is up
     285and running. Then, hosts and gateways further and further away should be
     286``pinged''. Round-trip times and packet loss statistics are computed.
     287If duplicate packets are received, they are not included in the packet
     288loss calculation, although the round trip time of these packets is used
     289in calculating the minimum/average/maximum round-trip time numbers.
     290When the specified number of packets have been sent (and received) or
     291if the program is terminated with a
     292SIGINT, a brief summary is displayed. Shorter current statistics
     293can be obtained without termination of process with signal
     294SIGQUIT.
     295.PP
     296If \fBping\fR does not receive any reply packets at all it will
     297exit with code 1. If a packet
     298\fIcount\fR
     299and
     300\fIdeadline\fR
     301are both specified, and fewer than
     302\fIcount\fR
     303packets are received by the time the
     304\fIdeadline\fR
     305has arrived, it will also exit with code 1.
     306On other error it exits with code 2. Otherwise it exits with code 0. This
     307makes it possible to use the exit code to see if a host is alive or
     308not.
     309.PP
     310This program is intended for use in network testing, measurement and
     311management.
     312Because of the load it can impose on the network, it is unwise to use
     313\fBping\fR during normal operations or from automated scripts.
     314.SH "ICMP PACKET DETAILS"
     315.PP
     316An IP header without options is 20 bytes.
     317An ICMP ECHO_REQUEST packet contains an additional 8 bytes worth
     318of ICMP header followed by an arbitrary amount of data.
     319When a \fIpacketsize\fR is given, this indicated the size of this
     320extra piece of data (the default is 56). Thus the amount of data received
     321inside of an IP packet of type ICMP ECHO_REPLY will always be 8 bytes
     322more than the requested data space (the ICMP header).
     323.PP
     324If the data space is at least of size of struct timeval
     325\fBping\fR uses the beginning bytes of this space to include
     326a timestamp which it uses in the computation of round trip times.
     327If the data space is shorter, no round trip times are given.
     328.SH "DUPLICATE AND DAMAGED PACKETS"
     329.PP
     330\fBping\fR will report duplicate and damaged packets.
     331Duplicate packets should never occur, and seem to be caused by
     332inappropriate link-level retransmissions.
     333Duplicates may occur in many situations and are rarely (if ever) a
     334good sign, although the presence of low levels of duplicates may not
     335always be cause for alarm.
     336.PP
     337Damaged packets are obviously serious cause for alarm and often
     338indicate broken hardware somewhere in the
     339\fBping\fR packet's path (in the network or in the hosts).
     340.SH "TRYING DIFFERENT DATA PATTERNS"
     341.PP
     342The (inter)network layer should never treat packets differently depending
     343on the data contained in the data portion.
     344Unfortunately, data-dependent problems have been known to sneak into
     345networks and remain undetected for long periods of time.
     346In many cases the particular pattern that will have problems is something
     347that doesn't have sufficient ``transitions'', such as all ones or all
     348zeros, or a pattern right at the edge, such as almost all zeros.
     349It isn't necessarily enough to specify a data pattern of all zeros (for
     350example) on the command line because the pattern that is of interest is
     351at the data link level, and the relationship between what you type and
     352what the controllers transmit can be complicated.
     353.PP
     354This means that if you have a data-dependent problem you will probably
     355have to do a lot of testing to find it.
     356If you are lucky, you may manage to find a file that either can't be sent
     357across your network or that takes much longer to transfer than other
     358similar length files.
     359You can then examine this file for repeated patterns that you can test
     360using the \fB-p\fR option of \fBping\fR.
     361.SH "TTL DETAILS"
     362.PP
     363The TTL value of an IP packet represents the maximum number of IP routers
     364that the packet can go through before being thrown away.
     365In current practice you can expect each router in the Internet to decrement
     366the TTL field by exactly one.
     367.PP
     368The TCP/IP specification states that the TTL field for TCP
     369packets should be set to 60, but many systems use smaller values
     370(4.3 BSD uses 30, 4.2 used 15).
     371.PP
     372The maximum possible value of this field is 255, and most Unix systems set
     373the TTL field of ICMP ECHO_REQUEST packets to 255.
     374This is why you will find you can ``ping'' some hosts, but not reach them
     375with
     376\fBtelnet\fR(1)
     377or
     378\fBftp\fR(1).
     379.PP
     380In normal operation ping prints the TTL value from the packet it receives.
     381When a remote system receives a ping packet, it can do one of three things
     382with the TTL field in its response:
     383.TP 0.2i
     384\(bu
     385Not change it; this is what Berkeley Unix systems did before the
     3864.3BSD Tahoe release. In this case the TTL value in the received packet
     387will be 255 minus the number of routers in the round-trip path.
     388.TP 0.2i
     389\(bu
     390Set it to 255; this is what current Berkeley Unix systems do.
     391In this case the TTL value in the received packet will be 255 minus the
     392number of routers in the path \fBfrom\fR
     393the remote system \fBto\fR the \fBping\fRing host.
     394.TP 0.2i
     395\(bu
     396Set it to some other value. Some machines use the same value for
     397ICMP packets that they use for TCP packets, for example either 30 or 60.
     398Others may use completely wild values.
     399.SH "BUGS"
     400.TP 0.2i
     401\(bu
     402Many Hosts and Gateways ignore the RECORD_ROUTE option.
     403.TP 0.2i
     404\(bu
     405The maximum IP header length is too small for options like
     406RECORD_ROUTE to be completely useful.
     407There's not much that can be done about this, however.
     408.TP 0.2i
     409\(bu
     410Flood pinging is not recommended in general, and flood pinging the
     411broadcast address should only be done under very controlled conditions.
     412.SH "SEE ALSO"
     413.PP
     414\fBnetstat\fR(1),
     415\fBifconfig\fR(8).
     416.SH "HISTORY"
     417.PP
     418The \fBping\fR command appeared in 4.3BSD.
     419.PP
     420The version described here is its descendant specific to Linux.
     421.SH "SECURITY"
     422.PP
     423\fBping\fR requires CAP_NET_RAW capability
     424to be executed 1) if the program is used for non-echo queries
     425(See \fB-N\fR option), or 2) if kernel does not
     426support non-raw ICMP sockets, or 3) if the user is not allowed
     427to create an ICMP echo socket.  The program may be used as
     428set-uid root.
     429.SH "AVAILABILITY"
     430.PP
     431\fBping\fR is part of \fIiputils\fR package
     432and the latest versions are  available in source form at
     433http://www.skbuff.net/iputils/iputils-current.tar.bz2.
  • iputils-s20150815

    diff -Naur iputils-s20150815.orig/doc/rarpd.8 iputils-s20150815/doc/rarpd.8
    old new  
     1.\" This manpage has been automatically generated by docbook2man
     2.\" from a DocBook document.  This tool can be found at:
     3.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
     4.\" Please send any bug reports, improvements, comments, patches,
     5.\" etc. to Steve Cheng <steve@ggi-project.org>.
     6.TH "RARPD" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
     7.SH NAME
     8rarpd \- answer RARP REQUESTs
     9.SH SYNOPSIS
     10
     11\fBarping\fR [\fB-aAvde\fR] [\fB-b \fIbootdir\fB\fR] [\fB\fIinterface\fB\fR]
     12
     13.SH "DESCRIPTION"
     14.PP
     15Listens
     16RARP
     17requests from clients. Provided MAC address of client
     18is found in \fI/etc/ethers\fR database and
     19obtained host name is resolvable to an IP address appropriate
     20for attached network, \fBrarpd\fR answers to client with RARPD
     21reply carrying an IP address.
     22.PP
     23To allow multiple boot servers on the network \fBrarpd\fR
     24optionally checks for presence Sun-like bootable image in TFTP directory.
     25It should have form \fBHexadecimal_IP.ARCH\fR, f.e. to load
     26sparc 193.233.7.98 \fIC1E90762.SUN4M\fR is linked to
     27an image appropriate for SUM4M in directory \fI/etc/tftpboot\fR.
     28.SH "WARNING"
     29.PP
     30This facility is deeply obsoleted by
     31BOOTP
     32and later
     33DHCP protocols.
     34However, some clients really still need this to boot.
     35.SH "OPTIONS"
     36.TP
     37\fB-a\fR
     38Listen on all the interfaces. Currently it is an internal
     39option, its function is overridden with \fIinterface\fR
     40argument. It should not be used.
     41.TP
     42\fB-A\fR
     43Listen not only RARP but also ARP messages, some rare clients
     44use ARP by some unknown reason.
     45.TP
     46\fB-v\fR
     47Be verbose.
     48.TP
     49\fB-d\fR
     50Debug mode. Do not go to background.
     51.TP
     52\fB-e\fR
     53Do not check for presence of a boot image, reply if MAC address
     54resolves to a valid IP address using \fI/etc/ethers\fR
     55database and DNS.
     56.TP
     57\fB-b \fIbootdir\fB\fR
     58TFTP boot directory. Default is \fI/etc/tftpboot\fR
     59.SH "SEE ALSO"
     60.PP
     61\fBarping\fR(8),
     62\fBtftpd\fR(8).
     63.SH "AUTHOR"
     64.PP
     65\fBrarpd\fR was written by
     66Alexey Kuznetsov
     67<kuznet@ms2.inr.ac.ru>.
     68It is now maintained by
     69YOSHIFUJI Hideaki
     70<yoshfuji@skbuff.net>.
     71.SH "SECURITY"
     72.PP
     73\fBrarpd\fR requires CAP_NET_RAW capability
     74to listen and send RARP and ARP packets. It also needs CAP_NET_ADMIN
     75to give to kernel hint for ARP resolution; this is not strictly required,
     76but some (most of, to be more exact) clients are so badly broken that
     77are not able to answer ARP before they are finally booted. This is
     78not wonderful taking into account that clients using RARPD in 2002
     79are all unsupported relic creatures of 90's and even earlier.
     80.SH "AVAILABILITY"
     81.PP
     82\fBrarpd\fR is part of \fIiputils\fR package
     83and the latest versions are  available in source form at
     84http://www.skbuff.net/iputils/iputils-current.tar.bz2.
  • iputils-s20150815

    diff -Naur iputils-s20150815.orig/doc/rdisc.8 iputils-s20150815/doc/rdisc.8
    old new  
     1.\" This manpage has been automatically generated by docbook2man
     2.\" from a DocBook document.  This tool can be found at:
     3.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
     4.\" Please send any bug reports, improvements, comments, patches,
     5.\" etc. to Steve Cheng <steve@ggi-project.org>.
     6.TH "RDISC" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
     7.SH NAME
     8rdisc \- network router discovery daemon
     9.SH SYNOPSIS
     10
     11\fBrdisc\fR [\fB-abdfrstvV\fR] [\fB-p \fIpreference\fB\fR] [\fB-T \fImax_interval\fB\fR] [\fB\fIsend_address\fB\fR] [\fB\fIreceive_address\fB\fR]
     12
     13.SH "DESCRIPTION"
     14.PP
     15\fBrdisc\fR implements client side of the ICMP router discover protocol.
     16\fBrdisc\fR is invoked at boot time to populate the network
     17routing tables with default routes.
     18.PP
     19\fBrdisc\fR listens on the ALL_HOSTS (224.0.0.1) multicast address
     20(or \fIreceive_address\fR provided it is given)
     21for ROUTER_ADVERTISE messages from routers. The received
     22messages are handled by first ignoring those listed router addresses
     23with which the host does not share a network. Among the remaining addresses
     24the ones with the highest preference are selected as default routers
     25and a default route is entered in the kernel routing table
     26for each one of them.
     27.PP
     28Optionally, \fBrdisc\fR can avoid waiting for routers to announce
     29themselves by sending out a few ROUTER_SOLICITATION messages
     30to the ALL_ROUTERS (224.0.0.2) multicast address
     31(or \fIsend_address\fR provided it is given)
     32when it is started.
     33.PP
     34A timer is associated with each router address and the address will
     35no longer be considered for inclusion in the the routing tables if the
     36timer expires before a new
     37\fBadvertise\fR message is received from the router.
     38The address will also be excluded from consideration if the host receives an
     39\fBadvertise\fR
     40message with the preference being maximally negative.
     41.PP
     42Server side of router discovery protocol is supported by Cisco IOS
     43and by any more or less complete UNIX routing daemon, f.e \fBgated\fR.
     44Or, \fBrdisc\fR can act as responder, if compiled with -DRDISC_SERVER.
     45.SH "OPTIONS"
     46.TP
     47\fB-a\fR
     48Accept all routers independently of the preference they have in their
     49\fBadvertise\fR messages.
     50Normally \fBrdisc\fR only accepts (and enters in the kernel routing
     51tables) the router or routers with the highest preference.
     52.TP
     53\fB-b\fR
     54Opposite to \fB-a\fR, i.e. install only router with the best
     55preference value. It is default behaviour.
     56.TP
     57\fB-d\fR
     58Send debugging messages to syslog.
     59.TP
     60\fB-f\fR
     61Run \fBrdisc\fR forever even if no routers are found.
     62Normally \fBrdisc\fR gives up if it has not received any
     63\fBadvertise\fR message after after soliciting three times,
     64in which case it exits with a non-zero exit code.
     65If \fB-f\fR is not specified in the first form then
     66\fB-s\fR must be specified.
     67.TP
     68\fB-r\fR
     69Responder mode, available only if compiled with -DRDISC_SERVER.
     70.TP
     71\fB-s\fR
     72Send three \fBsolicitation\fR messages initially to quickly discover
     73the routers when the system is booted.
     74When \fB-s\fR is specified \fBrdisc\fR
     75exits with a non-zero exit code if it can not find any routers.
     76This can be overridden with the \fB-f\fR option.
     77.TP
     78\fB-p \fIpreference\fB\fR
     79Set preference in advertisement.
     80Available only with -r option.
     81.TP
     82\fB-T \fImax_interval\fB\fR
     83Set maximum advertisement interval in seconds.  Default is 600 secs.
     84Available only with -r option.
     85.TP
     86\fB-t\fR
     87Test mode. Do not go to background.
     88.TP
     89\fB-v\fR
     90Be verbose i.e. send lots of debugging messages to syslog.
     91.TP
     92\fB-V\fR
     93Print version and exit.
     94.SH "HISTORY"
     95.PP
     96This program was developed by Sun Microsystems (see copyright
     97notice in source file). It was ported to Linux by
     98Alexey Kuznetsov
     99<kuznet@ms2.inr.ac.ru>.
     100It is now maintained by
     101YOSHIFUJI Hideaki
     102<yoshfuji@skbuff.net>.
     103.SH "SEE ALSO"
     104.PP
     105\fBicmp\fR(7),
     106\fBinet\fR(7),
     107\fBping\fR(8).
     108.SH "REFERENCES"
     109.PP
     110Deering, S.E.,ed "ICMP Router Discovery Messages",
     111RFC1256, Network Information Center, SRI International,
     112Menlo Park, Calif., September 1991.
     113.SH "SECURITY"
     114.PP
     115\fBrdisc\fR requires CAP_NET_RAW to listen
     116and send ICMP messages and capability CAP_NET_ADMIN
     117to update routing tables.
     118.SH "AVAILABILITY"
     119.PP
     120\fBrdisc\fR is part of \fIiputils\fR package
     121and the latest versions are  available in source form at
     122http://www.skbuff.net/iputils/iputils-current.tar.bz2.
  • iputils-s20150815

    diff -Naur iputils-s20150815.orig/doc/tftpd.8 iputils-s20150815/doc/tftpd.8
    old new  
     1.\" This manpage has been automatically generated by docbook2man
     2.\" from a DocBook document.  This tool can be found at:
     3.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
     4.\" Please send any bug reports, improvements, comments, patches,
     5.\" etc. to Steve Cheng <steve@ggi-project.org>.
     6.TH "TFTPD" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
     7.SH NAME
     8tftpd \- Trivial File Transfer Protocol server
     9.SH SYNOPSIS
     10
     11\fBtftpd\fR \fB\fIdirectory\fB\fR
     12
     13.SH "DESCRIPTION"
     14.PP
     15\fBtftpd\fR is a server which supports the DARPA
     16Trivial File Transfer Protocol
     17(RFC1350).
     18The TFTP server is started
     19by \fBinetd\fR(8).
     20.PP
     21\fIdirectory\fR is required argument; if it is not given
     22\fBtftpd\fR aborts. This path is prepended to any file name requested
     23via TFTP protocol, effectively chrooting \fBtftpd\fR to this directory.
     24File names are validated not to escape out of this directory, however
     25administrator may configure such escape using symbolic links.
     26.PP
     27It is in difference of variants of \fBtftpd\fR usually distributed
     28with unix-like systems, which take a list of directories and match
     29file names to start from one of given prefixes or to some random
     30default, when no arguments were given. There are two reasons not to
     31behave in this way: first, it is inconvenient, clients are not expected
     32to know something about layout of filesystem on server host.
     33And second, TFTP protocol is not a tool for browsing of server's filesystem,
     34it is just an agent allowing to boot dumb clients.
     35.PP
     36In the case when \fBtftpd\fR is used together with
     37\fBrarpd\fR(8),
     38tftp directories in these services should coincide and it is expected
     39that each client booted via TFTP has boot image corresponding
     40its IP address with an architecture suffix following Sun Microsystems
     41conventions. See
     42\fBrarpd\fR(8)
     43for more details.
     44.SH "SECURITY"
     45.PP
     46TFTP protocol does not provide any authentication.
     47Due to this capital flaw \fBtftpd\fR is not able to restrict
     48access to files and will allow only publically readable
     49files to be accessed. Files may be written only if they already
     50exist and are publically writable.
     51.PP
     52Impact is evident, directory exported via TFTP \fBmust not\fR
     53contain sensitive information of any kind, everyone is allowed
     54to read it as soon as a client is allowed. Boot images do not contain
     55such information as rule, however you should think twice before
     56publishing f.e. Cisco IOS config files via TFTP, they contain
     57\fBunencrypted\fR passwords and may contain some information
     58about the network, which you were not going to make public.
     59.PP
     60The \fBtftpd\fR server should be executed by \fBinetd\fR
     61with dropped root privileges, namely with a user ID giving minimal
     62access to files published in tftp directory. If it is executed
     63as superuser occasionally, \fBtftpd\fR drops its UID and GID
     64to 65534, which is most likely not the thing which you expect.
     65However, this is not very essential; remember, only files accessible
     66for everyone can be read or written via TFTP.
     67.SH "SEE ALSO"
     68.PP
     69\fBrarpd\fR(8),
     70\fBtftp\fR(1),
     71\fBinetd\fR(8).
     72.SH "HISTORY"
     73.PP
     74The \fBtftpd\fR command appeared in 4.2BSD. The source in iputils
     75is cleaned up both syntactically (ANSIized) and semantically (UDP socket IO).
     76.PP
     77It is distributed with iputils mostly as good demo of an interesting feature
     78(MSG_CONFIRM) allowing to boot long images by dumb clients
     79not answering ARP requests until they are finally booted.
     80However, this is full functional and can be used in production.
     81.SH "AVAILABILITY"
     82.PP
     83\fBtftpd\fR is part of \fIiputils\fR package
     84and the latest versions are  available in source form at
     85http://www.skbuff.net/iputils/iputils-current.tar.bz2.
  • iputils-s20150815

    diff -Naur iputils-s20150815.orig/doc/tracepath.8 iputils-s20150815/doc/tracepath.8
    old new  
     1.\" This manpage has been automatically generated by docbook2man
     2.\" from a DocBook document.  This tool can be found at:
     3.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
     4.\" Please send any bug reports, improvements, comments, patches,
     5.\" etc. to Steve Cheng <steve@ggi-project.org>.
     6.TH "TRACEPATH" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
     7.SH NAME
     8tracepath, tracepath6 \- traces path to a network host discovering MTU along this path
     9.SH SYNOPSIS
     10
     11\fBtracepath\fR [\fB-n\fR] [\fB-b\fR] [\fB-l \fIpktlen\fB\fR] [\fB-m \fImax_hops\fB\fR] [\fB-p \fIport\fB\fR] \fB\fIdestination\fB\fR
     12
     13.SH "DESCRIPTION"
     14.PP
     15It traces path to \fIdestination\fR discovering MTU along this path.
     16It uses UDP port \fIport\fR or some random port.
     17It is similar to \fBtraceroute\fR, only does not require superuser
     18privileges and has no fancy options.
     19.PP
     20\fBtracepath6\fR is good replacement for \fBtraceroute6\fR
     21and classic example of application of Linux error queues.
     22The situation with IPv4 is worse, because commercial
     23IP routers do not return enough information in ICMP error messages.
     24Probably, it will change, when they will be updated.
     25For now it uses Van Jacobson's trick, sweeping a range
     26of UDP ports to maintain trace history.
     27.SH "OPTIONS"
     28.TP
     29\fB-n\fR
     30Print primarily IP addresses numerically.
     31.TP
     32\fB-b\fR
     33Print both of host names and IP addresses.
     34.TP
     35\fB-l\fR
     36Sets the initial packet length to \fIpktlen\fR instead of
     3765535 for \fBtracepath\fR or 128000 for \fBtracepath6\fR.
     38.TP
     39\fB-m\fR
     40Set maximum hops (or maximum TTLs) to \fImax_hops\fR
     41instead of 30.
     42.TP
     43\fB-p\fR
     44Sets the initial destination port to use.
     45.SH "OUTPUT"
     46.PP
     47
     48.nf
     49root@mops:~ # tracepath6 3ffe:2400:0:109::2
     50 1?: [LOCALHOST]                              pmtu 1500
     51 1:  dust.inr.ac.ru                   0.411ms
     52 2:  dust.inr.ac.ru        asymm  1   0.390ms pmtu 1480
     53 2:  3ffe:2400:0:109::2               463.514ms reached
     54     Resume: pmtu 1480 hops 2 back 2
     55.fi
     56.PP
     57The first column shows TTL of the probe, followed by colon.
     58Usually value of TTL is obtained from reply from network,
     59but sometimes reply does not contain necessary information and
     60we have to guess it. In this case the number is followed by ?.
     61.PP
     62The second column shows the network hop, which replied to the probe.
     63It is either address of router or word [LOCALHOST], if
     64the probe was not sent to the network.
     65.PP
     66The rest of line shows miscellaneous information about path to
     67the correspinding network hop. As rule it contains value of RTT.
     68Additionally, it can show Path MTU, when it changes.
     69If the path is asymmetric
     70or the probe finishes before it reach prescribed hop, difference
     71between number of hops in forward and backward direction is shown
     72following keyword async. This information is not reliable.
     73F.e. the third line shows asymmetry of 1, it is because the first probe
     74with TTL of 2 was rejected at the first hop due to Path MTU Discovery.
     75.PP
     76The last line summarizes information about all the path to the destination,
     77it shows detected Path MTU, amount of hops to the destination and our
     78guess about amount of hops from the destination to us, which can be
     79different when the path is asymmetric.
     80.SH "SEE ALSO"
     81.PP
     82\fBtraceroute\fR(8),
     83\fBtraceroute6\fR(8),
     84\fBping\fR(8).
     85.SH "AUTHOR"
     86.PP
     87\fBtracepath\fR was written by
     88Alexey Kuznetsov
     89<kuznet@ms2.inr.ac.ru>.
     90.SH "SECURITY"
     91.PP
     92No security issues.
     93.PP
     94This lapidary deserves to be elaborated.
     95\fBtracepath\fR is not a privileged program, unlike
     96\fBtraceroute\fR, \fBping\fR and other beasts of this kind.
     97\fBtracepath\fR may be executed by everyone who has some access
     98to network, enough to send UDP datagrams to investigated destination
     99using given port.
     100.SH "AVAILABILITY"
     101.PP
     102\fBtracepath\fR is part of \fIiputils\fR package
     103and the latest versions are  available in source form at
     104http://www.skbuff.net/iputils/iputils-current.tar.bz2.
  • doc/traceroute6.8

    diff -Naur iputils-s20150815.orig/doc/traceroute6.8 iputils-s20150815/doc/traceroute6.8
    old new  
     1.\" This manpage has been automatically generated by docbook2man
     2.\" from a DocBook document.  This tool can be found at:
     3.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
     4.\" Please send any bug reports, improvements, comments, patches,
     5.\" etc. to Steve Cheng <steve@ggi-project.org>.
     6.TH "TRACEROUTE6" "8" "24 August 2015" "iputils-140519" "System Manager's Manual: iputils"
     7.SH NAME
     8traceroute6 \- traces path to a network host
     9.SH SYNOPSIS
     10
     11\fBtraceroute6\fR [\fB-dnrvV\fR] [\fB-i \fIinterface\fB\fR] [\fB-m \fImax_ttl\fB\fR] [\fB-p \fIport\fB\fR] [\fB-q \fImax_probes\fB\fR] [\fB-s \fIsource\fB\fR] [\fB-w \fIwait time\fB\fR] \fB\fIdestination\fB\fR [\fB\fIsize\fB\fR]
     12
     13.SH "DESCRIPTION"
     14.PP
     15Description can be found in
     16\fBtraceroute\fR(8),
     17all the references to IP replaced to IPv6. It is needless to copy
     18the description from there.
     19.SH "SEE ALSO"
     20.PP
     21\fBtraceroute\fR(8),
     22\fBtracepath\fR(8),
     23\fBping\fR(8).
     24.SH "HISTORY"
     25.PP
     26This program has long history. Author of \fBtraceroute\fR
     27is Van Jacobson and it first appeared in 1988. This clone is
     28based on a port of \fBtraceroute\fR to IPv6 published
     29in NRL IPv6 distribution in 1996. In turn, it was ported
     30to Linux by Pedro Roque. After this it was kept in sync by   
     31Alexey Kuznetsov
     32<kuznet@ms2.inr.ac.ru>. And eventually entered
     33\fBiputils\fR package.
     34.SH "SECURITY"
     35.PP
     36\fBtracepath6\fR requires CAP_NET_RAW capability
     37to be executed. It is safe to be used as set-uid root.
     38.SH "AVAILABILITY"
     39.PP
     40\fBtraceroute6\fR is part of \fIiputils\fR package
     41and the latest versions are  available in source form at
     42http://www.skbuff.net/iputils/iputils-current.tar.bz2.
Note: See TracBrowser for help on using the repository browser.