Ignore:
Timestamp:
Feb 18, 2009, 11:27:54 PM (15 years ago)
Author:
Jim Gifford <clfs@…>
Branches:
clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit
Children:
56c7abf
Parents:
ffe68ed
Message:

IPUtils Updates

File:
1 moved

Legend:

Unmodified
Added
Removed
  • patches/iputils-s20071127-manpages-2.patch

    rffe68ed r8d00c46  
    66Description: Provides the man pages (adding docbook2man with all its
    77             dependencies would be a major addition to the book, so I built it
    8              -once- on a completed system and saved the data). 
     8             -once- on a completed system and saved the data).
    99
    10 diff -Naur doc/arping.8 doc/arping.8
    11 --- doc/arping.8        1969-12-31 16:00:00.000000000 -0800
    12 +++ doc/arping.8        2009-02-18 20:52:34.000000000 -0800
     10diff -Naur iputils-s20071127.orig/doc/arping.8 iputils-s20071127/doc/arping.8
     11--- iputils-s20071127.orig/doc/arping.8 1969-12-31 16:00:00.000000000 -0800
     12+++ iputils-s20071127/doc/arping.8      2009-02-18 23:20:33.249183964 -0800
    1313@@ -0,0 +1,110 @@
    1414+.\" This manpage has been automatically generated by docbook2man
     
    122122+and the latest versions are  available in source form at
    123123+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
    124 diff -Naur doc/clockdiff.8 doc/clockdiff.8
    125 --- doc/clockdiff.8     1969-12-31 16:00:00.000000000 -0800
    126 +++ doc/clockdiff.8     2009-02-18 20:52:38.000000000 -0800
     124diff -Naur iputils-s20071127.orig/doc/clockdiff.8 iputils-s20071127/doc/clockdiff.8
     125--- iputils-s20071127.orig/doc/clockdiff.8      1969-12-31 16:00:00.000000000 -0800
     126+++ iputils-s20071127/doc/clockdiff.8   2009-02-18 23:20:33.249183964 -0800
    127127@@ -0,0 +1,81 @@
    128128+.\" This manpage has been automatically generated by docbook2man
     
    207207+and the latest versions are  available in source form at
    208208+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
    209 diff -Naur doc/pg3.8 doc/pg3.8
    210 --- doc/pg3.8   1969-12-31 16:00:00.000000000 -0800
    211 +++ doc/pg3.8   2009-02-18 20:52:42.000000000 -0800
    212 @@ -0,0 +1,86 @@
    213 +.\" This manpage has been automatically generated by docbook2man
    214 +.\" from a DocBook document.  This tool can be found at:
    215 +.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
    216 +.\" Please send any bug reports, improvements, comments, patches,
    217 +.\" etc. to Steve Cheng <steve@ggi-project.org>.
    218 +.TH "PG3" "8" "18 February 2009" "iputils-071127" "System Manager's Manual: iputils"
    219 +.SH NAME
    220 +pg3, ipg, pgset \- send stream of UDP packets
    221 +.SH SYNOPSIS
    222 +
    223 +\fBsource ipg\fR
    224 +
    225 +
    226 +\fBpg\fR
    227 +
    228 +
    229 +\fBpgset\fR \fB\fICOMMAND\fB\fR
    230 +
    231 +.SH "DESCRIPTION"
    232 +.PP
    233 +\fBipg\fR is not a program, it is script which should be sourced
    234 +to \fBbash\fR. When sourced it loads module \fIpg3\fR and
    235 +exports a few of functions accessible from parent shell. These macros
    236 +are \fBpg\fR to start packet injection and to get the results of run;
    237 +and \fBpgset\fR to setup packet generator.
    238 +.PP
    239 +\fBpgset\fR can send the following commands to module \fIpg3\fR:
    240 +.SH "COMMAND"
    241 +.TP
    242 +\fBodev \fIDEVICE\fB\fR
    243 +Name of Ethernet device to test. See
    244 +warning below.
    245 +.TP
    246 +\fBpkt_size \fIBYTES\fB\fR
    247 +Size of packet to generate. The size includes all the headers: UDP, IP,
    248 +MAC, but does not account for overhead internal to medium, i.e. FCS
    249 +and various paddings.
    250 +.TP
    251 +\fBfrags \fINUMBER\fB\fR
    252 +Each packet will contain \fINUMBER\fR of fragments.
    253 +Maximal amount for linux-2.4 is 6. Far not all the devices support
    254 +fragmented buffers.
    255 +.TP
    256 +\fBcount \fINUMBER\fB\fR
    257 +Send stream of \fINUMBER\fR of packets and stop after this.
    258 +.TP
    259 +\fBipg \fITIME\fB\fR
    260 +Introduce artificial delay between packets of \fITIME\fR
    261 +microseconds.
    262 +.TP
    263 +\fBdst \fIIP_ADDRESS\fB\fR
    264 +Select IP destination where the stream is sent to.
    265 +Beware, never set this address at random. \fBpg3\fR is not a toy,
    266 +it creates really tough stream. Default value is 0.0.0.0.
    267 +.TP
    268 +\fBdst \fIMAC_ADDRESS\fB\fR
    269 +Select MAC destination where the stream is sent to.
    270 +Default value is 00:00:00:00:00:00 in hope that this will not be received
    271 +by any node on LAN.
    272 +.TP
    273 +\fBstop\fR
    274 +Abort packet injection.
    275 +.SH "WARNING"
    276 +.PP
    277 +When output device is set to some random device different
    278 +of hardware Ethernet device, \fBpg3\fR will crash kernel.
    279 +.PP
    280 +Do not use it on VLAN, ethertap, VTUN and other devices,
    281 +which emulate Ethernet not being real Ethernet in fact.
    282 +.SH "AUTHOR"
    283 +.PP
    284 +\fBpg3\fR was written by Robert Olsson <robert.olsson@its.uu.se>.
    285 +.SH "SECURITY"
    286 +.PP
    287 +This can be used only by superuser.
    288 +.PP
    289 +This tool creates floods of packets which is unlikely to be handled
    290 +even by high-end machines. For example, it saturates gigabit link with
    291 +60 byte packets when used with Intel's e1000. In face of such stream
    292 +switches, routers and end hosts may deadlock, crash, explode.
    293 +Use only in test lab environment.
    294 +.SH "AVAILABILITY"
    295 +.PP
    296 +\fBpg3\fR is part of \fIiputils\fR package
    297 +and the latest versions are  available in source form at
    298 +http://www.skbuff.net/iputils/iputils-current.tar.bz2.
    299 diff -Naur doc/ping.8 doc/ping.8
    300 --- doc/ping.8  1969-12-31 16:00:00.000000000 -0800
    301 +++ doc/ping.8  2009-02-18 20:52:44.000000000 -0800
     209diff -Naur iputils-s20071127.orig/doc/ping.8 iputils-s20071127/doc/ping.8
     210--- iputils-s20071127.orig/doc/ping.8   1969-12-31 16:00:00.000000000 -0800
     211+++ iputils-s20071127/doc/ping.8        2009-02-18 23:20:33.249183964 -0800
    302212@@ -0,0 +1,332 @@
    303213+.\" This manpage has been automatically generated by docbook2man
     
    633543+and the latest versions are  available in source form at
    634544+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
    635 diff -Naur doc/rarpd.8 doc/rarpd.8
    636 --- doc/rarpd.8 1969-12-31 16:00:00.000000000 -0800
    637 +++ doc/rarpd.8 2009-02-18 20:52:48.000000000 -0800
    638 @@ -0,0 +1,84 @@
    639 +.\" This manpage has been automatically generated by docbook2man
    640 +.\" from a DocBook document.  This tool can be found at:
    641 +.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
    642 +.\" Please send any bug reports, improvements, comments, patches,
    643 +.\" etc. to Steve Cheng <steve@ggi-project.org>.
    644 +.TH "RARPD" "8" "18 February 2009" "iputils-071127" "System Manager's Manual: iputils"
    645 +.SH NAME
    646 +rarpd \- answer RARP REQUESTs
    647 +.SH SYNOPSIS
    648 +
    649 +\fBarping\fR [\fB-aAvde\fR] [\fB-b \fIbootdir\fB\fR] [\fB\fIinterface\fB\fR]
    650 +
    651 +.SH "DESCRIPTION"
    652 +.PP
    653 +Listens
    654 +RARP
    655 +requests from clients. Provided MAC address of client
    656 +is found in \fI/etc/ethers\fR database and
    657 +obtained host name is resolvable to an IP address appropriate
    658 +for attached network, \fBrarpd\fR answers to client with RARPD
    659 +reply carrying an IP address.
    660 +.PP
    661 +To allow multiple boot servers on the network \fBrarpd\fR
    662 +optionally checks for presence Sun-like bootable image in TFTP directory.
    663 +It should have form \fBHexadecimal_IP.ARCH\fR, f.e. to load
    664 +sparc 193.233.7.98 \fIC1E90762.SUN4M\fR is linked to
    665 +an image appropriate for SUM4M in directory \fI/etc/tftpboot\fR.
    666 +.SH "WARNING"
    667 +.PP
    668 +This facility is deeply obsoleted by
    669 +BOOTP
    670 +and later
    671 +DHCP protocols.
    672 +However, some clients really still need this to boot.
    673 +.SH "OPTIONS"
    674 +.TP
    675 +\fB-a\fR
    676 +Listen on all the interfaces. Currently it is an internal
    677 +option, its function is overridden with \fIinterface\fR
    678 +argument. It should not be used.
    679 +.TP
    680 +\fB-A\fR
    681 +Listen not only RARP but also ARP messages, some rare clients
    682 +use ARP by some unknown reason.
    683 +.TP
    684 +\fB-v\fR
    685 +Be verbose.
    686 +.TP
    687 +\fB-d\fR
    688 +Debug mode. Do not go to background.
    689 +.TP
    690 +\fB-e\fR
    691 +Do not check for presence of a boot image, reply if MAC address
    692 +resolves to a valid IP address using \fI/etc/ethers\fR
    693 +database and DNS.
    694 +.TP
    695 +\fB-b \fIbootdir\fB\fR
    696 +TFTP boot directory. Default is \fI/etc/tftpboot\fR
    697 +.SH "SEE ALSO"
    698 +.PP
    699 +\fBarping\fR(8),
    700 +\fBtftpd\fR(8).
    701 +.SH "AUTHOR"
    702 +.PP
    703 +\fBrarpd\fR was written by
    704 +Alexey Kuznetsov
    705 +<kuznet@ms2.inr.ac.ru>.
    706 +It is now maintained by
    707 +YOSHIFUJI Hideaki
    708 +<yoshfuji@skbuff.net>.
    709 +.SH "SECURITY"
    710 +.PP
    711 +\fBrarpd\fR requires CAP_NET_RAWIO capability
    712 +to listen and send RARP and ARP packets. It also needs CAP_NET_ADMIN
    713 +to give to kernel hint for ARP resolution; this is not strictly required,
    714 +but some (most of, to be more exact) clients are so badly broken that
    715 +are not able to answer ARP before they are finally booted. This is
    716 +not wonderful taking into account that clients using RARPD in 2002
    717 +are all unsupported relic creatures of 90's and even earlier.
    718 +.SH "AVAILABILITY"
    719 +.PP
    720 +\fBrarpd\fR is part of \fIiputils\fR package
    721 +and the latest versions are  available in source form at
    722 +http://www.skbuff.net/iputils/iputils-current.tar.bz2.
    723 diff -Naur doc/rdisc.8 doc/rdisc.8
    724 --- doc/rdisc.8 1969-12-31 16:00:00.000000000 -0800
    725 +++ doc/rdisc.8 2009-02-18 20:52:53.000000000 -0800
     545diff -Naur iputils-s20071127.orig/doc/rdisc.8 iputils-s20071127/doc/rdisc.8
     546--- iputils-s20071127.orig/doc/rdisc.8  1969-12-31 16:00:00.000000000 -0800
     547+++ iputils-s20071127/doc/rdisc.8       2009-02-18 23:20:33.249183964 -0800
    726548@@ -0,0 +1,110 @@
    727549+.\" This manpage has been automatically generated by docbook2man
     
    835657+and the latest versions are  available in source form at
    836658+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
    837 diff -Naur doc/tftpd.8 doc/tftpd.8
    838 --- doc/tftpd.8 1969-12-31 16:00:00.000000000 -0800
    839 +++ doc/tftpd.8 2009-02-18 20:52:57.000000000 -0800
    840 @@ -0,0 +1,85 @@
    841 +.\" This manpage has been automatically generated by docbook2man
    842 +.\" from a DocBook document.  This tool can be found at:
    843 +.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
    844 +.\" Please send any bug reports, improvements, comments, patches,
    845 +.\" etc. to Steve Cheng <steve@ggi-project.org>.
    846 +.TH "TFTPD" "8" "18 February 2009" "iputils-071127" "System Manager's Manual: iputils"
    847 +.SH NAME
    848 +tftpd \- Trivial File Transfer Protocol server
    849 +.SH SYNOPSIS
    850 +
    851 +\fBtftpd\fR \fB\fIdirectory\fB\fR
    852 +
    853 +.SH "DESCRIPTION"
    854 +.PP
    855 +\fBtftpd\fR is a server which supports the DARPA
    856 +Trivial File Transfer Protocol
    857 +(RFC1350).
    858 +The TFTP server is started
    859 +by \fBinetd\fR(8).
    860 +.PP
    861 +\fIdirectory\fR is required argument; if it is not given
    862 +\fBtftpd\fR aborts. This path is prepended to any file name requested
    863 +via TFTP protocol, effectively chrooting \fBtftpd\fR to this directory.
    864 +File names are validated not to escape out of this directory, however
    865 +administrator may configure such escape using symbolic links.
    866 +.PP
    867 +It is in difference of variants of \fBtftpd\fR usually distributed
    868 +with unix-like systems, which take a list of directories and match
    869 +file names to start from one of given prefixes or to some random
    870 +default, when no arguments were given. There are two reasons not to
    871 +behave in this way: first, it is inconvenient, clients are not expected
    872 +to know something about layout of filesystem on server host.
    873 +And second, TFTP protocol is not a tool for browsing of server's filesystem,
    874 +it is just an agent allowing to boot dumb clients.
    875 +.PP
    876 +In the case when \fBtftpd\fR is used together with
    877 +\fBrarpd\fR(8),
    878 +tftp directories in these services should coincide and it is expected
    879 +that each client booted via TFTP has boot image corresponding
    880 +its IP address with an architecture suffix following Sun Microsystems
    881 +conventions. See
    882 +\fBrarpd\fR(8)
    883 +for more details.
    884 +.SH "SECURITY"
    885 +.PP
    886 +TFTP protocol does not provide any authentication.
    887 +Due to this capital flaw \fBtftpd\fR is not able to restrict
    888 +access to files and will allow only publically readable
    889 +files to be accessed. Files may be written only if they already
    890 +exist and are publically writable.
    891 +.PP
    892 +Impact is evident, directory exported via TFTP \fBmust not\fR
    893 +contain sensitive information of any kind, everyone is allowed
    894 +to read it as soon as a client is allowed. Boot images do not contain
    895 +such information as rule, however you should think twice before
    896 +publishing f.e. Cisco IOS config files via TFTP, they contain
    897 +\fBunencrypted\fR passwords and may contain some information
    898 +about the network, which you were not going to make public.
    899 +.PP
    900 +The \fBtftpd\fR server should be executed by \fBinetd\fR
    901 +with dropped root privileges, namely with a user ID giving minimal
    902 +access to files published in tftp directory. If it is executed
    903 +as superuser occasionally, \fBtftpd\fR drops its UID and GID
    904 +to 65534, which is most likely not the thing which you expect.
    905 +However, this is not very essential; remember, only files accessible
    906 +for everyone can be read or written via TFTP.
    907 +.SH "SEE ALSO"
    908 +.PP
    909 +\fBrarpd\fR(8),
    910 +\fBtftp\fR(1),
    911 +\fBinetd\fR(8).
    912 +.SH "HISTORY"
    913 +.PP
    914 +The \fBtftpd\fR command appeared in 4.2BSD. The source in iputils
    915 +is cleaned up both syntactically (ANSIized) and semantically (UDP socket IO).
    916 +.PP
    917 +It is distributed with iputils mostly as good demo of an interesting feature
    918 +(MSG_CONFIRM) allowing to boot long images by dumb clients
    919 +not answering ARP requests until they are finally booted.
    920 +However, this is full functional and can be used in production.
    921 +.SH "AVAILABILITY"
    922 +.PP
    923 +\fBtftpd\fR is part of \fIiputils\fR package
    924 +and the latest versions are  available in source form at
    925 +http://www.skbuff.net/iputils/iputils-current.tar.bz2.
    926 diff -Naur doc/tracepath.8 doc/tracepath.8
    927 --- doc/tracepath.8     1969-12-31 16:00:00.000000000 -0800
    928 +++ doc/tracepath.8     2009-02-18 20:53:04.000000000 -0800
     659diff -Naur iputils-s20071127.orig/doc/tracepath.8 iputils-s20071127/doc/tracepath.8
     660--- iputils-s20071127.orig/doc/tracepath.8      1969-12-31 16:00:00.000000000 -0800
     661+++ iputils-s20071127/doc/tracepath.8   2009-02-18 23:21:37.765316105 -0800
    929662@@ -0,0 +1,94 @@
    930663+.\" This manpage has been automatically generated by docbook2man
     
    993726+with TTL of 2 was rejected at the first hop due to Path MTU Discovery.
    994727+.PP
    995 +Te last line summarizes information about all the path to the destination,
     728+The last line summarizes information about all the path to the destination,
    996729+it shows detected Path MTU, amount of hops to the destination and our
    997730+guess about amount of hops from the destination to us, which can be
     
    1022755+and the latest versions are  available in source form at
    1023756+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
    1024 diff -Naur doc/traceroute6.8 doc/traceroute6.8
    1025 --- doc/traceroute6.8   1969-12-31 16:00:00.000000000 -0800
    1026 +++ doc/traceroute6.8   2009-02-18 20:53:04.000000000 -0800
     757diff -Naur iputils-s20071127.orig/doc/traceroute6.8 iputils-s20071127/doc/traceroute6.8
     758--- iputils-s20071127.orig/doc/traceroute6.8    1969-12-31 16:00:00.000000000 -0800
     759+++ iputils-s20071127/doc/traceroute6.8 2009-02-18 23:20:33.249183964 -0800
    1027760@@ -0,0 +1,42 @@
    1028761+.\" This manpage has been automatically generated by docbook2man
     
    1068801+and the latest versions are  available in source form at
    1069802+http://www.skbuff.net/iputils/iputils-current.tar.bz2.
     803
Note: See TracChangeset for help on using the changeset viewer.