Copyright (c) 2001, Sun Microsystems, Inc.
The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
You use the RARP protocol to map dynamically between the Internet Protocol (IP) and network interface MAC addresses. RARP is often used to boot a Solaris client. RARP clients include the SPARC boot PROM, x86 boot floppy, SunOS kernel, and ifconfig(1M). in.rarpd(1M) provides the server-side implementation.
RARP request timeout behavior in application-layer clients is governed by the /etc/inet/rarp default file. To tune the number of retries an application attempts before giving up, set the RARP_RETRIES variable in /etc/inet/rarp. If the file is not present or RARP_RETRIES is not initialized within it, applications retry a maximum of five times with a eight second wait between retries.
See attributes(5) for descriptions of the following attributes:
| ATTRIBUTE TYPE ATTRIBUTE VALUE |
| Interface Stability (protocol) Standard |
| Interface Stability (defaults file) Unstable |
| Interface Stability (RARP_RETRIES) Unstable |
ifconfig(1M), in.rarpd(1M), arp(7P)
Reverse Address Resolution Protocol RFC 903. June, 1984 R. Finlayson, T. Mann, J.C. Mogul, M. Theimer