1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
|
<refentry xmlns="http://docbook.org/ns/docbook" version="5.0"
xml:id="man.rarpd">
<refentryinfo>
<title>rarpd</title>
<productname>iputils</productname>
</refentryinfo>
<refmeta>
<refentrytitle>
<application>rarpd</application>
</refentrytitle>
<manvolnum>8</manvolnum>
<refmiscinfo class='manual'>iputils</refmiscinfo>
</refmeta>
<refnamediv>
<refname>rarpd</refname>
<refpurpose>answer RARP REQUESTs</refpurpose>
</refnamediv>
<refsynopsisdiv>
<cmdsynopsis sepchar=" ">
<command>rarpd</command>
<arg choice="opt" rep="norepeat">
<option>-AadevV</option>
</arg>
<arg choice="opt" rep="norepeat">
<option>-b
<replaceable>bootdir</replaceable></option>
</arg>
<arg choice="req" rep="norepeat">interface</arg>
</cmdsynopsis>
</refsynopsisdiv>
<refsection xml:id="description">
<info>
<title>DESCRIPTION</title>
</info>
<para>Listens for RARP requests broadcasted by clients. If the MAC address
of the client is found in <filename>/etc/ethers</filename> and the obtained
hostname is resolvable to a valid IP address from the attached network,
<command>rarpd</command> answers to the client with a RARPD reply
and provides an IP address.</para>
<para>To allow multiple boot servers on the network
<command>rarpd</command> optionally checks if a Sun-like
bootable image in the TFTP directory is present. It should be formatted like
<emphasis remap="B">Hexadecimal_IP.ARCH</emphasis>. For example: To
load sparc 193.233.7.98,
<emphasis remap="I">C1E90762.SUN4M</emphasis> is linked to an
image appropriate for SUN4M in the directory
<filename>/etc/tftpboot</filename>.</para>
</refsection>
<refsection xml:id="warning">
<info>
<title>WARNING</title>
</info>
<para>This facility is deeply obsoleted by BOOTP and later DHCP
protocols. However, some clients actually still need this to
boot.</para>
</refsection>
<refsection xml:id="options">
<info>
<title>OPTIONS</title>
</info>
<variablelist remap="TP">
<varlistentry>
<term>
<option>-a</option>
</term>
<listitem>
<para>Listen on all available interfaces. Currently it is an
internal option, its function is overwritten with the
<emphasis remap="I">interface</emphasis> argument. It
should not be used.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>-A</option>
</term>
<listitem>
<para>Listen not only to RARP but also ARP messages. Some
rare clients use ARP for some unknown reason.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>-v</option>
</term>
<listitem>
<para>Be verbose.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>-d</option>
</term>
<listitem>
<para>Debug mode. Do not go to background.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>-e</option>
</term>
<listitem>
<para>Do not check for the presence of a boot image. Reply if
MAC address resolves to a valid IP address using
<filename>/etc/ethers</filename> database and DNS.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>-b</option>
<emphasis remap="I">bootdir</emphasis>
</term>
<listitem>
<para>TFTP boot directory. Default is
<filename>/etc/tftpboot</filename></para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>-V</option>
</term>
<listitem>
<para>Print version and exit.</para>
</listitem>
</varlistentry>
</variablelist>
</refsection>
<refsection xml:id="see_also">
<info>
<title>SEE ALSO</title>
</info>
<para>
<citerefentry>
<refentrytitle>arping</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry>,
<citerefentry>
<refentrytitle>tftpd</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry>.</para>
</refsection>
<refsection xml:id="author">
<info>
<title>AUTHOR</title>
</info>
<para>
<command>rarpd</command> was written by Alexey Kuznetsov
<kuznet@ms2.inr.ac.ru>.</para>
</refsection>
<refsection xml:id="security">
<info>
<title>SECURITY</title>
</info>
<para>
<command>rarpd</command> requires CAP_NET_RAW capability to
listen and send RARP and ARP packets. It also needs
CAP_NET_ADMIN to assist the kernel with ARP resolution; this
is not strictly required, but some (to be more exact: most) of
the clients are so badly broken that they are not able to answer
to ARP before they are fully booted. This is no surprise, taking
into account that clients using RARPD in 2002 are all
unsupported relic creatures of the 90's and even earlier.</para>
</refsection>
<refsection xml:id="availability">
<info>
<title>AVAILABILITY</title>
</info>
<para>
<emphasis remap="B">rarpd</emphasis> is part of the
<emphasis remap="I">iputils</emphasis> package.</para>
</refsection>
</refentry>
|
