Installing and Administering LAN/9000 Software

Chapter 7 175
LAN Device and Interface Terminology
RARP Configuration
appropriate entry can be added to the server database.
Setting Up a RARP Server
A system is set up to be a RARP server when the RARPD variable in
/etc/rc.config.d/netconf is set to 1. Usually, this variable is set to 0
so that a RARP server is not started.
This can be done with a text editor such as vi. This will cause
/usr/sbin/rarpd to be started at boot time.
Another file which must be modified is /etc/rarpd.conf. This is the
RARP server database file. It contains a list of entries that map
hardware address to IP address for each client interface.
The /etc/rarpd.conf file has the following format:
• A comment line is indicated by a pound sign (#) in the first column.
Other than comment lines and blank lines, all lines are considered
client entries. A client entry is of the form:
— <hardware_address> <ip_address>
where <hardware_address> consists of colon-separated (:)
hexadecimal bytes, and <ip_address> consists of dot-separated (.)
decimal bytes.
Example:
— 08:00:09:22:e4:a9 15.13.106.69
There must be exactly 6 hardware address bytes.
There must be exactly 4 protocol address bytes.
Once the rarpd server is started, it will receive RARP requests over all
configured network interfaces, and it will respond to clients that have
entries in the RARP database.
If the /etc/rarpd.conf file is modified while a rarpd is already
running, the changes will not be reflected in the rarpd application until
it is restarted or is sent the SIGHUP signal. To see what information is
in the currently running rarpd, sending it a SIGINT signal causes it to
dump its database into /usr/tmp/rarpd.db.
See the rarpd(1M) and rarpc(1M) man pages for more information.