services Reverse ARP requests on the Ethernet
connected to the specified interfaces. 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.
In normal operation, rarpd
forks a copy of itself
and runs in the background. Anomalies and errors are reported via
The options are as follows:
- Listen on all the Ethernets attached to the system. If
-a is omitted, a list of interfaces must be
- Run in debug mode, with all the output to stderr. This
option implies the -f option.
- Run in the foreground.
- Log all requests to
- Only honour a request if the server (the host that
rarpd is running on) can "boot" the
target; that is, if a file or directory called
/tftpboot/ipaddr exists, where
ipaddr is the target IP address expressed in
uppercase hexadecimal (only the first 8 characters of filenames are
- Ethernet host name database.
- Host name database.
T. Mann, J. Mogul, and
M. Theimer, A Reverse Address
Resolution Protocol, RFC 903,
and Steven McCanne
Lawrence Berkeley Laboratory, University of California, Berkeley, CA.