NAME | SYNOPSIS | DESCRIPTION | WARNING | OPTIONS | SEE ALSO | AUTHOR | SECURITY | AVAILABILITY | COLOPHON

RARPD(8)              System Manager's Manual: iputils              RARPD(8)

NAME         top

       rarpd - answer RARP REQUESTs

SYNOPSIS         top

       arping [-aAvde] [-b bootdir] [interface]

DESCRIPTION         top

       Listens RARP requests from clients. Provided MAC address of client is
       found in /etc/ethers database and obtained host name is resolvable to
       an IP address appropriate for attached network, rarpd answers to
       client with RARPD reply carrying an IP address.

       To allow multiple boot servers on the network rarpd optionally checks
       for presence Sun-like bootable image in TFTP directory.  It should
       have form Hexadecimal_IP.ARCH, f.e. to load sparc 193.233.7.98
       C1E90762.SUN4M is linked to an image appropriate for SUM4M in
       directory /etc/tftpboot.

WARNING         top

       This facility is deeply obsoleted by BOOTP and later DHCP protocols.
       However, some clients really still need this to boot.

OPTIONS         top

       -a     Listen on all the interfaces. Currently it is an internal
              option, its function is overridden with interface argument. It
              should not be used.

       -A     Listen not only RARP but also ARP messages, some rare clients
              use ARP by some unknown reason.

       -v     Be verbose.

       -d     Debug mode. Do not go to background.

       -e     Do not check for presence of a boot image, reply if MAC
              address resolves to a valid IP address using /etc/ethers
              database and DNS.

       -b bootdir
              TFTP boot directory. Default is /etc/tftpboot

SEE ALSO         top

       arping(8), tftpd(8).

AUTHOR         top

       rarpd was written by Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>.  It is
       now maintained by YOSHIFUJI Hideaki <yoshfuji@skbuff.net>.

SECURITY         top

       rarpd requires CAP_NET_RAW capability to listen and send RARP and ARP
       packets. It also needs CAP_NET_ADMIN to give to kernel hint for ARP
       resolution; this is not strictly required, but some (most of, to be
       more exact) clients are so badly broken that are not able to answer
       ARP before they are finally booted. This is not wonderful taking into
       account that clients using RARPD in 2002 are all unsupported relic
       creatures of 90's and even earlier.

AVAILABILITY         top

       rarpd is part of iputils package and the latest versions are
       available in source form at
       http://www.skbuff.net/iputils/iputils-current.tar.bz2.

COLOPHON         top

       This page is part of the iputils (IP utilities) project.  Information
       about the project can be found at ⟨http://www.skbuff.net/iputils/⟩.
       If you have a bug report for this manual page, send it to
       yoshfuji@skbuff.net, netdev@vger.kernel.org.  This page was obtained
       from the project's upstream Git repository 
       ⟨git://git.linux-ipv6.org/gitroot/iputils.git⟩ on 2017-05-03.  If you
       discover any rendering problems in this HTML version of the page, or
       you believe there is a better or more up-to-date source for the page,
       or you have corrections or improvements to the information in this
       COLOPHON (which is not part of the original manual page), send a mail
       to man-pages@man7.org

iputils-151218                   03 May 2017                        RARPD(8)

Pages that refer to this page: tftpd(8)