3 dhcpd, dhcp6d, dhcpleases, rarpd, tftpd \- Internet booting
44 These programs support booting over the Internet.
45 They should all be run on the same server to
46 allow other systems to be booted.
51 are used to boot everything;
53 is an extra piece just for Suns.
61 Clients use these protocols to obtain configuration information.
62 This information comes from attribute/value pairs in the network database
67 DHCP requests are honored both for static addresses found in
68 the NDB and for dynamic addresses listed in the command line.
69 DHCP requests are honored if either:
71 \- there exists an NDB entry
72 containing both the ethernet address of the requester and
73 an IP address on the originating network or subnetwork.
75 \- a free dynamic address exists on the originating network or subnetwork.
77 A BOOTP request is honored if all of the following are true:
79 \- there exists an NDB entry
80 containing both the ethernet address of the requester and
81 an IP address on the originating network or subnetwork.
83 \- the entry contains a
89 attribute is readable.
91 Dynamic addresses are specified on the command line as a list
92 of addresses and number pairs.
95 ip/dhcpd 10.1.1.12 10 10.2.1.70 12
99 to return dynamic addresses 10.1.1.12 through 10.1.1.21 inclusive
100 and 10.2.1.70 through 10.2.1.81 inclusive.
103 maintains a record of all dynamic addresses in the directory
105 one file per address.
106 If multiple servers have access to this common directory,
107 they will correctly coordinate their actions.
109 Attributes come from either the NDB entry for the system, the entry for its
110 subnet, or the entry for its network. The system entry has precedence,
111 then the subnet, then the network.
112 The NDB attributes used are:
122 the default IP gateway
125 the domain name of the system
128 the default Plan 9 file server
131 the default Plan 9 authentication server
137 a network time protocol server
148 a World Wide Web proxy
157 the default boot file;
165 requests only if it has been specifically targeted or if it
166 has read access to the boot file for the requester. That means that the requester
167 must specify a boot file in the request or one has to exist in NDB for
173 requests for which it can associate an IP address with the
178 Print debugging to standard output.
181 Specify a file other than
183 as the network database.
186 Mute: don't reply to requests, just log them and what
193 as the minimum lease time for dynamic addresses.
208 Mute static addresses: don't reply to requests for static addresses,
209 just log them and what
214 Sleep 2 seconds before answering requests for static addresses.
215 This is used to make a server be a backup only.
218 Sleep 2 seconds before answering requests for dynamic addresses.
221 The IP stack to use is mounted at
229 as the minimum lease time for static addresses.
233 provides DHCPv6 service for IPv6 clients. Only network boot and
234 DNS parameters are supported.
237 prints out the currently valid DHCP leases found in the
242 performs the Reverse Address Resolution Protocol, translating
243 Ethernet addresses into IP addresses.
247 Print debugging to standard output.
250 Use the Ethernet mounted at
251 .BI /net/ etherdev\f1.
254 The IP stack to use is mounted at
261 transfers files to systems that are booting.
264 and can only access files with global read permission.
268 Print debugging to standard output.
271 The IP stack to use is mounted at
281 All requests for files with non-rooted file names are served starting at this
284 supports only octet mode.
287 Restricts access to only those files rooted in the
291 .BR /lib/ndb/dhcp " directory of dynamic address files