1 <refentry xmlns="http://docbook.org/ns/docbook" version="5.0"
6 <productname>iputils</productname>
11 <application>rarpd</application>
13 <manvolnum>8</manvolnum>
14 <refmiscinfo class='manual'>iputils</refmiscinfo>
18 <refname>rarpd</refname>
19 <refpurpose>answer RARP REQUESTs</refpurpose>
23 <cmdsynopsis sepchar=" ">
24 <command>rarpd</command>
25 <arg choice="opt" rep="norepeat">
26 <option>-AadevV</option>
28 <arg choice="opt" rep="norepeat">
30 <replaceable>bootdir</replaceable></option>
32 <arg choice="req" rep="norepeat">interface</arg>
36 <refsection xml:id="description">
38 <title>DESCRIPTION</title>
40 <para>Listens for RARP requests broadcasted by clients. If the MAC address
41 of the client is found in <filename>/etc/ethers</filename> and the obtained
42 hostname is resolvable to a valid IP address from the attached network,
43 <command>rarpd</command> answers to the client with a RARPD reply
44 and provides an IP address.</para>
46 <para>To allow multiple boot servers on the network
47 <command>rarpd</command> optionally checks if a Sun-like
48 bootable image in the TFTP directory is present. It should be formatted like
49 <emphasis remap="B">Hexadecimal_IP.ARCH</emphasis>. For example: To
50 load sparc 193.233.7.98,
51 <emphasis remap="I">C1E90762.SUN4M</emphasis> is linked to an
52 image appropriate for SUN4M in the directory
53 <filename>/etc/tftpboot</filename>.</para>
56 <refsection xml:id="warning">
58 <title>WARNING</title>
60 <para>This facility is deeply obsoleted by BOOTP and later DHCP
61 protocols. However, some clients actually still need this to
65 <refsection xml:id="options">
67 <title>OPTIONS</title>
69 <variablelist remap="TP">
75 <para>Listen on all available interfaces. Currently it is an
76 internal option, its function is overwritten with the
77 <emphasis remap="I">interface</emphasis> argument. It
78 should not be used.</para>
86 <para>Listen not only to RARP but also ARP messages. Some
87 rare clients use ARP for some unknown reason.</para>
95 <para>Be verbose.</para>
103 <para>Debug mode. Do not go to background.</para>
111 <para>Do not check for the presence of a boot image. Reply if
112 MAC address resolves to a valid IP address using
113 <filename>/etc/ethers</filename> database and DNS.</para>
119 <emphasis remap="I">bootdir</emphasis>
122 <para>TFTP boot directory. Default is
123 <filename>/etc/tftpboot</filename></para>
131 <para>Print version and exit.</para>
137 <refsection xml:id="see_also">
139 <title>SEE ALSO</title>
143 <refentrytitle>arping</refentrytitle>
144 <manvolnum>8</manvolnum>
147 <refentrytitle>tftpd</refentrytitle>
148 <manvolnum>8</manvolnum>
149 </citerefentry>.</para>
152 <refsection xml:id="author">
154 <title>AUTHOR</title>
157 <command>rarpd</command> was written by Alexey Kuznetsov
158 <kuznet@ms2.inr.ac.ru>.</para>
161 <refsection xml:id="security">
163 <title>SECURITY</title>
166 <command>rarpd</command> requires CAP_NET_RAW capability to
167 listen and send RARP and ARP packets. It also needs
168 CAP_NET_ADMIN to assist the kernel with ARP resolution; this
169 is not strictly required, but some (to be more exact: most) of
170 the clients are so badly broken that they are not able to answer
171 to ARP before they are fully booted. This is no surprise, taking
172 into account that clients using RARPD in 2002 are all
173 unsupported relic creatures of the 90's and even earlier.</para>
176 <refsection xml:id="availability">
178 <title>AVAILABILITY</title>
181 <emphasis remap="B">rarpd</emphasis> is part of the
182 <emphasis remap="I">iputils</emphasis> package.</para>