3 dhcpd, dhcp6d, dhcpleases, rarpd, tftpd \- Internet booting
46 These programs support booting over the Internet.
47 They should all be run on the same server to
48 allow other systems to be booted.
53 are used to boot everything;
55 is an extra piece just for Suns.
63 Clients use these protocols to obtain configuration information.
64 This information comes from attribute/value pairs in the network database
69 DHCP requests are honored both for static addresses found in
70 the NDB and for dynamic addresses listed in the command line.
71 DHCP requests are honored if either:
73 \- there exists an NDB entry
74 containing both the ethernet address of the requester and
75 an IP address on the originating network or subnetwork.
77 \- a free dynamic address exists on the originating network or subnetwork.
79 A BOOTP request is honored if all of the following are true:
81 \- there exists an NDB entry
82 containing both the ethernet address of the requester and
83 an IP address on the originating network or subnetwork.
85 \- the entry contains a
91 attribute is readable.
93 Dynamic addresses are specified on the command line as a list
94 of addresses and number pairs.
97 ip/dhcpd 10.1.1.12 10 10.2.1.70 12
101 to return dynamic addresses 10.1.1.12 through 10.1.1.21 inclusive
102 and 10.2.1.70 through 10.2.1.81 inclusive.
105 maintains a record of all dynamic addresses in the directory
107 one file per address.
108 If multiple servers have access to this common directory,
109 they will correctly coordinate their actions.
111 Attributes come from either the NDB entry for the system, the entry for its
112 subnet, or the entry for its network. The system entry has precedence,
113 then the subnet, then the network.
114 The NDB attributes used are:
124 the default IP gateway
127 the domain name of the system
130 the default Plan 9 file server
133 the default Plan 9 authentication server
139 a network time protocol server
150 a World Wide Web proxy
159 the default boot file;
164 the TFTP server to fetch
169 the NFS root for unix machines
172 the NFS server used with
176 Specific vendor attribute for dhcp and bootp
182 requests only if it has been specifically targeted or if it
183 has read access to the boot file for the requester. That means that the requester
184 must specify a boot file in the request or one has to exist in NDB for
190 requests for which it can associate an IP address with the
195 Print debugging to standard output.
202 This should match the
206 so that the existence check of non-rooted file names
210 Specify a file other than
212 as the network database.
215 Mute: don't reply to requests, just log them and what
222 as the minimum lease time for dynamic addresses.
237 Mute static addresses: don't reply to requests for static addresses,
238 just log them and what
243 Sleep 2 seconds before answering requests for static addresses.
244 This is used to make a server be a backup only.
247 Sleep 2 seconds before answering requests for dynamic addresses.
250 The IP stack to use is mounted at
258 as the minimum lease time for static addresses.
262 provides DHCPv6 service for IPv6 clients. Only network boot and
263 DNS parameters are supported.
266 prints out the currently valid DHCP leases found in the
271 performs the Reverse Address Resolution Protocol, translating
272 Ethernet addresses into IP addresses.
276 Print debugging to standard output.
279 Use the Ethernet mounted at
280 .BI /net/ etherdev\f1.
283 The IP stack to use is mounted at
290 transfers files to systems that are booting.
293 and can only access files with global read permission.
297 Print debugging to standard output.
300 The IP stack to use is mounted at
310 All requests for files with non-rooted file names are served starting at this
311 directory. This needs to be consistent with the
316 supports only octet mode.
319 Restricts access to only those files rooted in the
323 .BR /lib/ndb/dhcp " directory of dynamic address files