1 .\" Copyright (c) 1988, 1989, 1991 Carnegie Mellon University
10 .Nd Internet Boot Protocol server/gateway
14 .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
45 will forward BOOTREPLY packets, only
47 will forward BOOTREQUEST packets.
49 One host on each network segment is normally configured to run either
55 by including one of the following lines in the file
58 .Dl bootps dgram udp wait root /usr/libexec/bootpd bootpd /etc/bootptab
59 .Dl bootps dgram udp wait root /usr/libexec/bootpgw bootpgw server
61 This mode of operation is referred to as "inetd mode" and causes
65 to be started only when a boot request arrives.
67 receive another packet within fifteen minutes of the last one
68 it received, it will exit to conserve system resources.
71 option controls this timeout (see OPTIONS).
73 It is also possible to run
77 in "standalone mode" (without
79 by simply invoking it from a shell like any other regular command.
80 Standalone mode is particularly useful when
82 is used with a large configuration database, where the start up
83 delay might otherwise prevent timely response to client requests.
84 (Automatic start up in standalone mode can be done by invoking
89 Standalone mode is less useful for
92 has very little start up delay because
93 it does not read a configuration file.
95 Either program automatically detects whether it was invoked from inetd
96 or from a shell and automatically selects the appropriate mode.
101 option may be used to force standalone or inetd mode respectively
104 The following options are available:
105 .Bl -tag -width indent
109 value (in minutes) that a
113 process will wait for a BOOTP packet before exiting.
114 If no packets are received for
116 minutes, then the program will exit.
117 A timeout value of zero means "run forever".
118 In standalone mode, this option is forced to zero.
119 .It Fl d Ar debug-level
122 variable that controls the amount of debugging messages generated.
127 4 will set the debugging level to 4.
128 For compatibility with older versions of
130 omitting the numeric parameter (i.e., just
132 will simply increment the debug level by one.
133 .It Fl c Ar chdir-path
134 Set the current directory used by
136 while checking the existence and size of client boot files.
138 useful when client boot files are specified as relative pathnames, and
140 needs to use the same current directory as the TFTP server
143 This option is not recognized by
146 Specify the hostname corresponding to the IP address to listen on.
149 listens on the IP address corresponding to the machine's hostname, as
154 This option is obsolete, but remains for
155 compatibility with older versions of
158 Force standalone mode.
159 This option is obsolete, but remains for
160 compatibility with older versions of
163 Specify the name of the configuration file from which
165 loads its database of known clients and client options
169 Specify the name of the file that
171 will dump its internal database into when it receives a
175 This option is only recognized if
177 was compiled with the -DDEBUG flag.
179 Specify the name of a BOOTP server to which
181 will forward all BOOTREQUEST packets it receives
190 operate similarly in that both listen for any packets sent to the
192 port, and both simply forward any BOOTREPLY packets.
193 They differ in their handling of BOOTREQUEST packets.
197 is started, it determines the address of a BOOTP server
198 whose name is provided as a command line parameter.
201 receives a BOOTREQUEST packet, it sets the "gateway address"
202 and "hop count" fields in the packet and forwards the packet
203 to the BOOTP server at the address determined earlier.
204 Requests are forwarded only if they indicate that
205 the client has been waiting for at least three seconds.
209 is started it reads a configuration file, (normally
211 that initializes the internal database of known clients and client
213 This internal database is reloaded
214 from the configuration file when
216 receives a hangup signal (SIGHUP) or when it discovers that the
217 configuration file has changed.
221 receives a BOOTREQUEST packet, it
222 .\" checks the modification time of the
223 .\" configuration file and reloads the database if necessary. Then it
224 looks for a database entry matching the client request.
225 If the client is known,
227 composes a BOOTREPLY packet using the database entry found above,
228 and sends the reply to the client (possibly using a gateway).
229 If the client is unknown, the request is discarded
230 (with a notice if debug > 0).
234 is compiled with the -DDEBUG option, receipt of a SIGUSR1 signal causes
235 it to dump its internal database to the file
237 or the dumpfile specified as a command line parameter.
239 During initialization, both programs
240 determine the UDP port numbers to be used by calling
243 .Pa /etc/services ) .
244 Two service names (and port numbers) are used:
246 .Dl bootps BOOTP Server listening port
247 .Dl bootpc BOOTP Client destination port
249 If the port numbers cannot be determined using
251 then the values default to bootps=67 and bootpc=68.
253 .Bl -tag -width /tmp/bootpd.dump -compact
255 Database file read by
257 .It Pa /tmp/bootpd.dump
258 Debugging dump file created by
261 Internet service numbers.
263 Current directory typically used by the TFTP server and
267 Individual host entries must not exceed 1024 characters.
269 This distribution is currently maintained by
270 .An Walter L. Wimer Aq walt+@cmu.edu .
272 The original BOOTP server was created by
274 at Stanford University in January 1986.
276 The current version of
278 is primarily the work of
280 .An Drew D. Perkins ,
282 .An Walter L. Wimer ,
283 at Carnegie Mellon University.
285 Enhancements and bug-fixes have been contributed by:
287 (in alphabetical order)
290 .An Danny Backx Aq db@sunbim.be
291 .An John Brezak Aq brezak@ch.hp.com
292 .An Frank da Cruz Aq fdc@cc.columbia.edu
293 .An David R. Linn Aq drl@vuse.vanderbilt.edu
294 .An Jim McKim Aq mckim@lerc.nasa.gov
295 .An Gordon W. Ross Aq gwr@mc.com
296 .An Jason Zions Aq jazz@hal.com .
302 DARPA Internet Request For Comments:
303 .Bl -tag -width RFC1533 -compact
307 Clarifications and Extensions for the Bootstrap Protocol
309 DHCP Options and BOOTP Vendor Extensions