reverse ARP daemon
utility services Reverse ARP
requests on the Ethernet connected to
. Upon receiving a request,
maps the target hardware address to
an IP address via its name, which must be present in both the
databases. If a host does not exist in both databases, the translation cannot
proceed and a reply will not be sent.
By default, a request is honored only if the server (i.e., the host that
is running on) can "boot"
the target; that is, a file or directory matching the glob
is the target IP address in hex. For
example, the IP address 188.8.131.52 will be replied to if any of
requirement can be overridden with the
flag (see below).
In normal operation,
forks a copy of
itself and runs in the background. Anomalies and errors are reported via
The following options are available:
- Listen on all the Ethernets attached to the system. If
-a is omitted, an interface must be
-f is also specified,
rarpd logs messages to
stderr instead of via
- Run in the foreground.
- Specify the pathname of the PID file. If not specified,
/var/run/rarpd.ifname.pid will be used
depending on the
-a flag or the
specified interface name.
- Supply a response to any RARP request for which an ethernet to IP address
mapping exists; do not depend on the existence of
- Supply an alternate tftp root directory to
/tftpboot, similar to the
-s option of
rarpd to selectively
respond to RARP requests, but use an alternate directory for IP
- Enable verbose syslogging.
Mann, T., Mogul, J.C., and
Theimer, M., RFC 903: Reverse
Address Resolution Protocol, June 1984,
and Steven McCanne
Lawrence Berkeley Laboratory, University of California, Berkeley, CA.
utility can depend on the DNS to
resolve the name discovered from
. If this name is not in the DNS
but is in /etc/hosts
, the DNS lookup can
cause a delayed RARP response, so in this situation it is recommended to
to read /etc/hosts