xref: /titanic_41/usr/src/man/man1m/in.rarpd.1m (revision ed22c7109fc5dd9e1b7a5d0333bdc7ad2718e2ab)
te
Copyright 1989 AT&T Copyright (c) 2004 Sun Microsystems, Inc. All Rights Reserved.
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]
IN.RARPD 1M "Aug 20, 2004"
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

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 International, 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 service's status can be queried using the svcs(1) command.