Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

rarpd(8) [freebsd man page]

RARPD(8)						    BSD System Manager's Manual 						  RARPD(8)

NAME
rarpd -- reverse ARP daemon SYNOPSIS
rarpd -a [-dfsv] [-t directory] [-P pidfile] rarpd [-dfsv] [-t directory] [-P pidfile] interface DESCRIPTION
The rarpd utility services Reverse ARP requests on the Ethernet connected to interface. Upon receiving a request, rarpd maps the target hardware address to an IP address via its name, which must be present in both the ethers(5) and hosts(5) 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 rarpd is running on) can "boot" the target; that is, a file or directory matching the glob /tftpboot/ipaddr* exists, where ipaddr is the target IP address in hex. For example, the IP address 204.216.27.18 will be replied to if any of /tftpboot/CCD81B12, /tftpboot/CCD81B12.SUN3, or /tftpboot/CCD81B12-boot exist. This requirement can be overridden with the -s flag (see below). In normal operation, rarpd forks a copy of itself and runs in the background. Anomalies and errors are reported via syslog(3). The following options are available: -a Listen on all the Ethernets attached to the system. If -a is omitted, an interface must be specified. -d If -f is also specified, rarpd logs messages to stdout and stderr instead of via syslog(3). -f Run in the foreground. -P Specify the pathname of the PID file. If not specified, /var/run/rarpd.pid or /var/run/rarpd.ifname.pid will be used depending on the -a flag or the specified interface name. -s Supply a response to any RARP request for which an ethernet to IP address mapping exists; do not depend on the existence of /tftpboot/ipaddr*. -t Supply an alternate tftp root directory to /tftpboot, similar to the -s option of tftpd(8). This permits rarpd to selectively respond to RARP requests, but use an alternate directory for IP checking. -v Enable verbose syslogging. FILES
/etc/ethers /etc/hosts /tftpboot /var/run/rarpd.pid SEE ALSO
bpf(4) Finlayson, R., Mann, T., Mogul, J.C., and Theimer, M., RFC 903: Reverse Address Resolution Protocol, June 1984, 4 p. AUTHORS
Craig Leres <leres@ee.lbl.gov> and Steven McCanne <mccanne@ee.lbl.gov>. Lawrence Berkeley Laboratory, University of California, Berkeley, CA. BUGS
The rarpd utility can depend on the DNS to resolve the name discovered from /etc/ethers. 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 configure nsswitch.conf(5) to read /etc/hosts first. BSD
July 9, 2012 BSD

Check Out this Related Man Page

in.rarpd(1M)						  System Administration Commands					      in.rarpd(1M)

NAME
in.rarpd, rarpd - DARPA Reverse Address Resolution Protocol server SYNOPSIS
/usr/sbin/in.rarpd [-d] -a /usr/sbin/in.rarpd [-d] device unit DESCRIPTION
in.rarpd starts a daemon that responds to Reverse Address Resolution Protocol (RARP) requests. The daemon forks a copy of itself that runs in background. It must be run as root. RARP is used by machines at boot time to discover their Internet Protocol (IP) address. The booting machine provides its Ethernet address in a RARP request message. Using the ethers and hosts databases, in.rarpd maps this Ethernet address into the corresponding IP address which it returns to the booting machine in an RARP reply message. The booting machine must be listed in both databases for in.rarpd to locate its IP address. in.rarpd issues no reply when it fails to locate an IP address. in.rarpd uses the STREAMS-based Data Link Provider Interface (DLPI) message set to communicate directly with the datalink device driver. OPTIONS
The following options are supported: -a Get the list of available network interfaces from IP using the SIOCGIFADDR ioctl and start a RARP daemon process on each interface returned. -d Print assorted debugging messages while executing. EXAMPLES
Example 1: Starting An in.rarpd Daemon For Each Network Interface Name Returned From /dev/ip: The following command starts an in.rarpd for each network interface name returned from /dev/ip: example# /usr/sbin/in.rarpd -a Example 2: Starting An in.rarpd Daemon On The Device /dev/le With The Device Instance Number 0 The following command starts one in.rarpd on the device /dev/le with the device instance number 0. example# /usr/sbin/in.rarpd le 0 FILES
/etc/ethers File or other source, as specified by nsswitch.conf(4). /etc/hosts File or other source, as specified by nsswitch.conf(4). /tftpboot /dev/ip /dev/arp ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWbsu | +-----------------------------+-----------------------------+ SEE ALSO
svcs(1), boot(1M), ifconfig(1M), svcadm(1M), ethers(4), hosts(4), netconfig(4), nsswitch.conf(4),attributes(5), smf(5), dlpi(7P) Finlayson, R., Mann, T., Mogul, J., and Theimer, M., RFC 903, A Reverse Address Resolution Protocol, Network Information Center, SRI Inter- national, June 1984. NOTES
The in.rarpd service is managed by the service management facility, smf(5), under the service identifier: svc:/network/rarp Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. SunOS 5.10 20 Aug 2004 in.rarpd(1M)
Man Page