rarpd(8)rarpd(8)NAMErarpd - answer RARP REQUESTs
SYNOPSIS
arping [-aAvde] [-b bootdir] [interface]
DESCRIPTION
Listens RARP ⟨http://tools.ietf.org/rfc/rfc903.txt⟩ requests from
clients. Provided MAC address of client is found in /etc/ethers data‐
base 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
This facility is deeply obsoleted by BOOTP ⟨http://tools.ietf.org/rfc/
rfc951.txt⟩ and later DHCP ⟨http://tools.ietf.org/rfc/rfc2131.txt⟩ pro‐
tocols. However, some clients really still need this to boot.
OPTIONS-a Listen on all the interfaces. Currently it is an internal op‐
tion, 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 ALSOarping(8)[Cross reference to non-existant ID “arping”], tftpd(8)[Cross
reference to non-existant ID “tftpd”].
AUTHORrarpd was written by Alexey Kuznetsov kuznet@ms2.inr.ac.ru
⟨mailto:kuznet@ms2.inr.ac.ru⟩ . It is now maintained by YOSHIFUJI
Hideaki yoshfuji@skbuff.net ⟨mailto:yoshfuji@skbuff.net⟩ .
SECURITYrarpd 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 ac‐
count that clients using RARPD in 2002 are all unsupported relic crea‐
tures of 90's and even earlier.
AVAILABILITYrarpd is part of iputils package and the latest versions are available
in source form at ⟨http://www.skbuff.net/iputils/iputils-cur‐
rent.tar.bz2⟩.
iputils- 13 August 2013 rarpd(8)