1
<!-- retain these comments for translator revision tracking -->
2
<!-- $Id: bootp.xml 28997 2005-07-07 21:09:22Z fjp $ -->
5
<sect2 condition="supports-bootp" id="tftp-bootp">
6
<title>Setting up BOOTP server</title>
9
There are two BOOTP servers available for GNU/Linux, the CMU
10
<command>bootpd</command> and the other is actually a DHCP server, ISC
11
<command>dhcpd</command>, which are contained in the
12
<classname>bootp</classname> and <classname>dhcp</classname> packages
17
To use CMU <command>bootpd</command>, you must first uncomment (or
18
add) the relevant line in <filename>/etc/inetd.conf</filename>. On
19
&debian;, you can run <userinput>update-inetd --enable
20
bootps</userinput>, then <userinput>/etc/init.d/inetd
21
reload</userinput> to do so. Elsewhere, the line in question should
24
<informalexample><screen>
25
bootps dgram udp wait root /usr/sbin/bootpd bootpd -i -t 120
26
</screen></informalexample>
28
Now, you must create an <filename>/etc/bootptab</filename> file. This
29
has the same sort of familiar and cryptic format as the good old BSD
30
<filename>printcap</filename>, <filename>termcap</filename>, and
31
<filename>disktab</filename> files. See the
32
<filename>bootptab</filename> manual page for more information. For
33
CMU <command>bootpd</command>, you will need to know the hardware
34
(MAC) address of the client. Here is an example
35
<filename>/etc/bootptab</filename>:
37
<informalexample><screen>
45
</screen></informalexample>
47
You will need to change at least the <quote>ha</quote> option, which
48
specifies the hardware address of the client. The <quote>bf</quote>
49
option specifies the file a client should retrieve via TFTP; see
50
<xref linkend="tftp-images"/> for more details.
53
On SGI Indys you can just enter the command monitor and type
54
<userinput>printenv</userinput>. The value of the
55
<userinput>eaddr</userinput> variable is the machine's MAC address.
60
By contrast, setting up BOOTP with ISC <command>dhcpd</command> is
61
really easy, because it treats BOOTP clients as a moderately special
62
case of DHCP clients. Some architectures require a complex
63
configuration for booting clients via BOOTP. If yours is one of
64
those, read the section <xref linkend="dhcpd"/>. Otherwise, you
65
will probably be able to get away with simply adding the
66
<userinput>allow bootp</userinput> directive to the configuration
67
block for the subnet containing the client, and restart
68
<command>dhcpd</command> with <userinput>/etc/init.d/dhcpd