1 .\" Copyright (c) 1988, 1989, 1991 Carnegie Mellon University
10 .Nd Internet Boot Protocol server/gateway
17 .Op Fl c Ar chdir-path
32 implements an Internet Bootstrap Protocol (BOOTP) server as defined in
33 RFC951, RFC1532, and RFC1533.
36 utility implements a simple BOOTP gateway which can be used to forward
37 requests and responses between clients on one subnet and a
40 on another subnet. While either
44 will forward BOOTREPLY packets, only
46 will forward BOOTREQUEST packets.
48 One host on each network segment is normally configured to run either
54 by including one of the following lines in the file
57 .Dl bootps dgram udp wait root /usr/libexec/bootpd bootpd /etc/bootptab
58 .Dl bootps dgram udp wait root /usr/libexec/bootpgw bootpgw server
60 This mode of operation is referred to as "inetd mode" and causes
64 to be started only when a boot request arrives. If it does not
65 receive another packet within fifteen minutes of the last one
66 it received, it will exit to conserve system resources. The
68 option controls this timeout (see OPTIONS).
70 It is also possible to run
74 in "standalone mode" (without
76 by simply invoking it from a shell like any other regular command.
77 Standalone mode is particularly useful when
79 is used with a large configuration database, where the start up
80 delay might otherwise prevent timely response to client requests.
81 (Automatic start up in standalone mode can be done by invoking
86 Standalone mode is less useful for
89 has very little start up delay because
90 it does not read a configuration file.
92 Either program automatically detects whether it was invoked from inetd
93 or from a shell and automatically selects the appropriate mode.
98 option may be used to force standalone or inetd mode respectively
101 The following options are available:
102 .Bl -tag -width indent
106 value (in minutes) that a
110 process will wait for a BOOTP packet before exiting.
111 If no packets are received for
113 minutes, then the program will exit.
114 A timeout value of zero means "run forever".
115 In standalone mode, this option is forced to zero.
116 .It Fl d Ar debug-level
119 variable that controls the amount of debugging messages generated.
124 4 will set the debugging level to 4.
125 For compatibility with older versions of
127 omitting the numeric parameter (i.e. just
129 will simply increment the debug level by one.
130 .It Fl c Ar chdir-path
131 Set the current directory used by
133 while checking the existence and size of client boot files. This is
134 useful when client boot files are specified as relative pathnames, and
136 needs to use the same current directory as the TFTP server
139 This option is not recognized by
142 Force inetd mode. This option is obsolete, but remains for
143 compatibility with older versions of
146 Force standalone mode. This option is obsolete, but remains for
147 compatibility with older versions of
150 Specify the name of the configuration file from which
152 loads its database of known clients and client options
156 Specify the name of the file that
158 will dump its internal database into when it receives a
161 only). This option is only recognized if
163 was compiled with the -DDEBUG flag.
165 Specify the name of a BOOTP server to which
167 will forward all BOOTREQUEST packets it receives
176 operate similarly in that both listen for any packets sent to the
178 port, and both simply forward any BOOTREPLY packets.
179 They differ in their handling of BOOTREQUEST packets.
183 is started, it determines the address of a BOOTP server
184 whose name is provided as a command line parameter. When
186 receives a BOOTREQUEST packet, it sets the "gateway address"
187 and "hop count" fields in the packet and forwards the packet
188 to the BOOTP server at the address determined earlier.
189 Requests are forwarded only if they indicate that
190 the client has been waiting for at least three seconds.
194 is started it reads a configuration file, (normally
196 that initializes the internal database of known clients and client
197 options. This internal database is reloaded
198 from the configuration file when
200 receives a hangup signal (SIGHUP) or when it discovers that the
201 configuration file has changed.
205 receives a BOOTREQUEST packet, it
206 .\" checks the modification time of the
207 .\" configuration file and reloads the database if necessary. Then it
208 looks for a database entry matching the client request.
209 If the client is known,
211 composes a BOOTREPLY packet using the database entry found above,
212 and sends the reply to the client (possibly using a gateway).
213 If the client is unknown, the request is discarded
214 (with a notice if debug > 0).
218 is compiled with the -DDEBUG option, receipt of a SIGUSR1 signal causes
219 it to dump its internal database to the file
221 or the dumpfile specified as a command line parameter.
223 During initialization, both programs
224 determine the UDP port numbers to be used by calling
227 .Pa /etc/services ) .
228 Two service names (and port numbers) are used:
230 .Dl bootps BOOTP Server listening port
231 .Dl bootpc BOOTP Client destination port
233 If the port numbers cannot be determined using
235 then the values default to bootps=67 and bootpc=68.
237 .Bl -tag -width /tmp/bootpd.dump -compact
239 Database file read by
241 .It Pa /tmp/bootpd.dump
242 Debugging dump file created by
245 Internet service numbers.
247 Current directory typically used by the TFTP server and
251 Individual host entries must not exceed 1024 characters.
253 This distribution is currently maintained by
254 .An Walter L. Wimer Aq walt+@cmu.edu .
256 The original BOOTP server was created by
258 at Stanford University in January 1986.
260 The current version of
262 is primarily the work of
264 .An Drew D. Perkins ,
266 .An Walter L. Wimer ,
267 at Carnegie Mellon University.
269 Enhancements and bug-fixes have been contributed by:
271 (in alphabetical order)
274 .An Danny Backx Aq db@sunbim.be
275 .An John Brezak Aq brezak@ch.hp.com
276 .An Frank da Cruz Aq fdc@cc.columbia.edu
277 .An David R. Linn Aq drl@vuse.vanderbilt.edu
278 .An Jim McKim Aq mckim@lerc.nasa.gov
279 .An Gordon W. Ross Aq gwr@mc.com
280 .An Jason Zions Aq jazz@hal.com .
286 DARPA Internet Request For Comments:
287 .Bl -tag -width RFC1533 -compact
291 Clarifications and Extensions for the Bootstrap Protocol
293 DHCP Options and BOOTP Vendor Extensions