isibootd(8) [netbsd man page]

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

NAME

     isibootd -- TRFS based network boot server

SYNOPSIS

     isibootd [-d tracelevel] [-i interface] [-s directory]

DESCRIPTION

     The isibootd command is a server which supports OMRON LUNA's network boot protocol based on the Transparent Remote File System (TRFS) proto-
     col.  The TRFS protocol uses special Ethernet type packets and works within a local network.

     isibootd is a simple TRFS server that only supports client reads for booting and exports files in a specified directory.  isibootd accepts
     requests only from clients listed in the /etc/ethers and have valid hostnames.

     The options are as follows:

     -d tracelevel
		 Run isibootd in debug mode with specified tracelevel.	The tracelevel can be value 1, 2, or 3, and greater tracelevel provides
		 more detailed trace output.  The server will not fork in the debug mode.

     -i interface
		 Specify a network interface to service network boot.  If not specified isibootd searches available network interfaces (excluding
		 loopback) and use the first configured ``up'' one.

     -s directory
		 Specify a directory containing boot files to be served by isibootd.  If not specified isibootd uses /tftpboot by default.

FILES

     /etc/ethers
     /etc/hosts
     /tftpboot
     /var/run/isibootd.pid

SEE ALSO

     ethers(5), hosts(5), tftpd(8)

     http://www.NetBSD.org/ports/luna68k/install.html

HISTORY

     isibootd is based on isiboot utility which was originally written by Tohru Nishimura for NetBSD/luna68k development, and first appeared in
     NetBSD 6.0.

BSD
								 December 15, 2011							       BSD

RARP(8) 						     Linux Programmer's Manual							   RARP(8)

NAME

       rarpd - Reverse Address Resolution Protocol (RARP) daemon

SYNOPSIS

       rarpd [-aAvode] [-b bootdir] [interface]

DESCRIPTION

       Rarpd  is a daemon which responds to RARP requests.  RARP is used by some machines at boot time to discover their IP address.  They provide
       their Ethernet address and rarpd responds with their IP address if it finds it in the ethers database  (either  /etc/ethers  file  or  NIS+
       lookup)	and  using  DNS  lookup  if ethers database contains a hostname and not an IP address.	By default rarpd also checks if a bootable
       image with a name starting with the IP address in hexadecimal uppercase letters is present in the TFTP boot directory (usually /tftpboot  )
       before it decides to respond to the RARP request.

       The  optional argument interface restricts the daemon instance to access only the indicated network interface. Only a single name is possi-
       ble.

OPTIONS

       -a     Do not bind to the interface.

       -A     Respond to ARP as well as RARP requests.

       -v     Tell the user what is going on by being verbose.

       -d     Debugging mode. Do not detach from the tty. This also implies verbose mode.

       -e     Skip the check for bootable image in the TFTP boot directory. If not present, then even if the Ethernet address is  present  in  the
	      ethers database but the bootable image for the resolved IP does not exist, rarpd will not respond to the request.

       -o     Accept offlink packages on the active interfaces.

       -b bootdir
	      Access bootdir instead of the default /tftpboot as the TFTP boot directory for bootable image checks.

OBSOLETES

       This daemon rarpd obsoletes kernel rarp daemon present in Linux kernels up to 2.2 which was controlled by the rarp(8) command.

SIGNALS

       SIGHUP Renew the internal address list, which records IPv4 addresses available at each active network interface. The restriction set by the
	      command line argument interface is still in effect, if in use.

FILES

       /etc/ethers,
       /etc/nsswitch.conf,
       /tftpboot

SEE ALSO

       ethers(5)

AUTHORS

       Alexey Kuznetsov, <kuznet@ms2.inr.ac.ru>
       Jakub Jelinek, <jakub@redhat.com>

rarpd								   7 April 2000 							   RARP(8)