]>
Commit | Line | Data |
---|---|---|
1 | Internet Systems Consortium DHCP Distribution | |
2 | Version 4.4.1 | |
3 | 28 February 2018 | |
4 | ||
5 | README FILE | |
6 | ||
7 | You should read this file carefully before trying to install or use | |
8 | the ISC DHCP Distribution. | |
9 | ||
10 | TABLE OF CONTENTS | |
11 | ||
12 | 1 WHERE TO FIND DOCUMENTATION | |
13 | 2 RELEASE STATUS | |
14 | 3 BUILDING THE DHCP DISTRIBUTION | |
15 | 3.1 UNPACKING IT | |
16 | 3.2 CONFIGURING IT | |
17 | 3.2.1 DYNAMIC DNS UPDATES | |
18 | 3.2.2 LOCALLY DEFINED OPTIONS | |
19 | 3.3 BUILDING IT | |
20 | 4 INSTALLING THE DHCP DISTRIBUTION | |
21 | 5 USING THE DHCP DISTRIBUTION | |
22 | 5.1 FIREWALL RULES | |
23 | 5.2 LINUX | |
24 | 5.2.1 IF_TR.H NOT FOUND | |
25 | 5.2.2 SO_ATTACH_FILTER UNDECLARED | |
26 | 5.2.3 PROTOCOL NOT CONFIGURED | |
27 | 5.2.4 BROADCAST | |
28 | 5.2.6 IP BOOTP AGENT | |
29 | 5.2.7 MULTIPLE INTERFACES | |
30 | 5.3 SCO | |
31 | 5.4 HP-UX | |
32 | 5.5 ULTRIX | |
33 | 5.6 FreeBSD | |
34 | 5.7 NeXTSTEP | |
35 | 5.8 SOLARIS | |
36 | 5.8.1 Solaris 11 | |
37 | 5.8.2 Solaris 11 and ATF | |
38 | 5.8.3 Other Solaris Items | |
39 | 5.9 AIX | |
40 | 5.10 MacOS X | |
41 | 5.11 ATF | |
42 | 6 SUPPORT | |
43 | 6.1 HOW TO REPORT BUGS | |
44 | 7 HISTORY | |
45 | ||
46 | WHERE TO FIND DOCUMENTATION | |
47 | ||
48 | Documentation for this software includes this README file, the | |
49 | RELNOTES file, and the manual pages, which are in the server, common, | |
50 | client and relay subdirectories. The README file (this file) includes | |
51 | late-breaking operational and system-specific information that you | |
52 | should read even if you don't want to read the manual pages, and that | |
53 | you should *certainly* read if you run into trouble. Internet | |
54 | standards relating to the DHCP protocol are listed in the References | |
55 | document that is available in html, txt and xml formats in doc/ | |
56 | subdirectory. You will have the best luck reading the manual pages if | |
57 | you build this software and then install it, although you can read | |
58 | them directly out of the distribution if you need to. | |
59 | ||
60 | DHCP server documentation is in the dhcpd man page. Information about | |
61 | the DHCP server lease database is in the dhcpd.leases man page. | |
62 | Server configuration documentation is in the dhcpd.conf man page as | |
63 | well as the dhcp-options man page. A sample DHCP server | |
64 | configuration is in the file server/dhcpd.conf.example. The source for | |
65 | the dhcpd, dhcpd.leases and dhcpd.conf man pages is in the server/ sub- | |
66 | directory in the distribution. The source for the dhcp-options.5 | |
67 | man page is in the common/ subdirectory. | |
68 | ||
69 | DHCP Client documentation is in the dhclient man page. DHCP client | |
70 | configuration documentation is in the dhclient.conf man page and the | |
71 | dhcp-options man page. The DHCP client configuration script is | |
72 | documented in the dhclient-script man page. The format of the DHCP | |
73 | client lease database is documented in the dhclient.leases man page. | |
74 | The source for all these man pages is in the client/ subdirectory in | |
75 | the distribution. In addition, the dhcp-options man page should be | |
76 | referred to for information about DHCP options. | |
77 | ||
78 | DHCP relay agent documentation is in the dhcrelay man page, the source | |
79 | for which is distributed in the relay/ subdirectory. | |
80 | ||
81 | To read installed manual pages, use the man command. Type "man page" | |
82 | where page is the name of the manual page. This will only work if | |
83 | you have installed the ISC DHCP distribution using the ``make install'' | |
84 | command (described later). | |
85 | ||
86 | If you want to read manual pages that aren't installed, you can type | |
87 | ``nroff -man page |more'' where page is the filename of the | |
88 | unformatted manual page. The filename of an unformatted manual page | |
89 | is the name of the manual page, followed by '.', followed by some | |
90 | number - 5 for documentation about files, and 8 for documentation | |
91 | about programs. For example, to read the dhcp-options man page, | |
92 | you would type ``nroff -man common/dhcp-options.5 |more'', assuming | |
93 | your current working directory is the top level directory of the ISC | |
94 | DHCP Distribution. | |
95 | ||
96 | Please note that the pathnames of files to which our manpages refer | |
97 | will not be correct for your operating system until after you iterate | |
98 | 'make install' (so if you're reading a manpage out of the source | |
99 | directory, it may not have up-to-date information). | |
100 | ||
101 | BUILDING THE DHCP DISTRIBUTION | |
102 | ||
103 | UNPACKING IT | |
104 | ||
105 | To build the DHCP Distribution, unpack the compressed tar file using | |
106 | the tar utility and the gzip command - type something like: | |
107 | ||
108 | gunzip dhcp-4.4.1.tar.gz | |
109 | tar xvf dhcp-4.4.1.tar | |
110 | ||
111 | CONFIGURING IT | |
112 | ||
113 | Now, cd to the dhcp-4.4.1 subdirectory that you've just created and | |
114 | configure the source tree by typing: | |
115 | ||
116 | ./configure | |
117 | ||
118 | If the configure utility can figure out what sort of system you're | |
119 | running on, it will create a custom Makefile for you for that | |
120 | system; otherwise, it will complain. If it can't figure out what | |
121 | system you are using, that system is not supported - you are on | |
122 | your own. | |
123 | ||
124 | Several options may be enabled or disabled via the configure command. | |
125 | You can get a list of these by typing: | |
126 | ||
127 | ./configure --help | |
128 | ||
129 | If you want to use dynamic shared libraries automake, autoconf | |
130 | (aka GNU autotools) and libtool must be available. The DHCP | |
131 | distribution provides 3 configure.ac* files: the -lt version | |
132 | has no libtool support and was copied to the configure.ac | |
133 | standard file in the distribution. To enable libtool support | |
134 | you should perform these steps: | |
135 | ||
136 | cp configure.ac+lt configure.ac | |
137 | autoreconf -i | |
138 | ||
139 | after you can use the regenerated configure as usual | |
140 | (with libtool support (--enable-libtool) on by default): | |
141 | ||
142 | ./configure | |
143 | ||
144 | For compatibility (and people who don't read this documentation) | |
145 | the --enable-libtool configuration file is supported even by | |
146 | the distributed configure (and off by default). The previous | |
147 | steps are performed and the regenerated configure called with | |
148 | almost the same parameters (this "almost" makes the use of | |
149 | this feature not recommended). | |
150 | ||
151 | Note you can't go back from with libtool support to without libtool | |
152 | support by restoring configure.ac and rerun autoreconf. If you | |
153 | want or need to restore the without libtool support state the | |
154 | required way is to simply restore the whole distribution. | |
155 | ||
156 | DYNAMIC DNS UPDATES | |
157 | ||
158 | A fully-featured implementation of dynamic DNS updates is included in | |
159 | this release. It uses libraries from BIND and, to avoid issues with | |
160 | different versions, includes the necessary BIND version. The appropriate | |
161 | BIND libraries will be compiled and installed in the bind subdirectory | |
162 | as part of the make step. In order to build the necessary libraries you | |
163 | will need to have "gmake" available on your build system. | |
164 | ||
165 | ||
166 | There is documentation for the DDNS support in the dhcpd.conf manual | |
167 | page - see the beginning of this document for information on finding | |
168 | manual pages. | |
169 | ||
170 | LOCALLY DEFINED OPTIONS | |
171 | ||
172 | In previous versions of the DHCP server there was a mechanism whereby | |
173 | options that were not known by the server could be configured using | |
174 | a name made up of the option code number and an identifier: | |
175 | "option-nnn" This is no longer supported, because it is not future- | |
176 | proof. Instead, if you want to use an option that the server doesn't | |
177 | know about, you must explicitly define it using the method described | |
178 | in the dhcp-options man page under the DEFINING NEW OPTIONS heading. | |
179 | ||
180 | BUILDING IT | |
181 | ||
182 | Once you've run configure, just type ``make'', and after a while | |
183 | you should have a dhcp server. If you get compile errors on one | |
184 | of the supported systems mentioned earlier, please let us know. | |
185 | If you get warnings, it's not likely to be a problem - the DHCP | |
186 | server compiles completely warning-free on as many architectures | |
187 | as we can manage, but there are a few for which this is difficult. | |
188 | If you get errors on a system not mentioned above, you will need | |
189 | to do some programming or debugging on your own to get the DHCP | |
190 | Distribution working. | |
191 | ||
192 | If you cross compile you have to follow the instructions from | |
193 | the BIND README, in particular you must set the BUILD_CC | |
194 | environment variable. | |
195 | ||
196 | INSTALLING THE DHCP DISTRIBUTION | |
197 | ||
198 | Once you have successfully gotten the DHCP Distribution to build, you | |
199 | can install it by typing ``make install''. If you already have an old | |
200 | version of the DHCP Distribution installed, you may want to save it | |
201 | before typing ``make install''. | |
202 | ||
203 | USING THE DHCP DISTRIBUTION | |
204 | ||
205 | FIREWALL RULES | |
206 | ||
207 | If you are running the DHCP server or client on a computer that's also | |
208 | acting as a firewall, you must be sure to allow DHCP packets through | |
209 | the firewall. In particular, your firewall rules _must_ allow packets | |
210 | from IP address 0.0.0.0 to IP address 255.255.255.255 from UDP port 68 | |
211 | to UDP port 67 through. They must also allow packets from your local | |
212 | firewall's IP address and UDP port 67 through to any address your DHCP | |
213 | server might serve on UDP port 68. Finally, packets from relay agents | |
214 | on port 67 to the DHCP server on port 67, and vice versa, must be | |
215 | permitted. | |
216 | ||
217 | We have noticed that on some systems where we are using a packet | |
218 | filter, if you set up a firewall that blocks UDP port 67 and 68 | |
219 | entirely, packets sent through the packet filter will not be blocked. | |
220 | However, unicast packets will be blocked. This can result in strange | |
221 | behaviour, particularly on DHCP clients, where the initial packet | |
222 | exchange is broadcast, but renewals are unicast - the client will | |
223 | appear to be unable to renew until it starts broadcasting its | |
224 | renewals, and then suddenly it'll work. The fix is to fix the | |
225 | firewall rules as described above. | |
226 | ||
227 | PARTIAL SERVERS | |
228 | ||
229 | If you have a server that is connected to two networks, and you only | |
230 | want to provide DHCP service on one of those networks (e.g., you are | |
231 | using a cable modem and have set up a NAT router), if you don't write | |
232 | any subnet declaration for the network you aren't supporting, the DHCP | |
233 | server will ignore input on that network interface if it can. If it | |
234 | can't, it will refuse to run - some operating systems do not have the | |
235 | capability of supporting DHCP on machines with more than one | |
236 | interface, and ironically this is the case even if you don't want to | |
237 | provide DHCP service on one of those interfaces. | |
238 | ||
239 | LINUX | |
240 | ||
241 | There are three big LINUX issues: the all-ones broadcast address, | |
242 | Linux 2.1 ip_bootp_agent enabling, and operations with more than one | |
243 | network interface. There are also two potential compilation/runtime | |
244 | problems for Linux 2.1/2.2: the "SO_ATTACH_FILTER undeclared" problem | |
245 | and the "protocol not configured" problem. | |
246 | ||
247 | LINUX: PROTOCOL NOT CONFIGURED | |
248 | ||
249 | If you get the following message, it's because your kernel doesn't | |
250 | have the Linux packetfilter or raw packet socket configured: | |
251 | ||
252 | Make sure CONFIG_PACKET (Packet socket) and CONFIG_FILTER (Socket | |
253 | Filtering) are enabled in your kernel configuration | |
254 | ||
255 | If this happens, you need to configure your Linux kernel to support | |
256 | Socket Filtering and the Packet socket, or to select a kernel provided | |
257 | by your Linux distribution that has these enabled (virtually all modern | |
258 | ones do by default). | |
259 | ||
260 | LINUX: BROADCAST | |
261 | ||
262 | If you are running a recent version of Linux, this won't be a problem, | |
263 | but on older versions of Linux (kernel versions prior to 2.2), there | |
264 | is a potential problem with the broadcast address being sent | |
265 | incorrectly. | |
266 | ||
267 | In order for dhcpd to work correctly with picky DHCP clients (e.g., | |
268 | Windows 95), it must be able to send packets with an IP destination | |
269 | address of 255.255.255.255. Unfortunately, Linux changes an IP | |
270 | destination of 255.255.255.255 into the local subnet broadcast address | |
271 | (here, that's 192.5.5.223). | |
272 | ||
273 | This isn't generally a problem on Linux 2.2 and later kernels, since | |
274 | we completely bypass the Linux IP stack, but on old versions of Linux | |
275 | 2.1 and all versions of Linux prior to 2.1, it is a problem - pickier | |
276 | DHCP clients connected to the same network as the ISC DHCP server or | |
277 | ISC relay agent will not see messages from the DHCP server. It *is* | |
278 | possible to run into trouble with this on Linux 2.2 and later if you | |
279 | are running a version of the DHCP server that was compiled on a Linux | |
280 | 2.0 system, though. | |
281 | ||
282 | It is possible to work around this problem on some versions of Linux | |
283 | by creating a host route from your network interface address to | |
284 | 255.255.255.255. The command you need to use to do this on Linux | |
285 | varies from version to version. The easiest version is: | |
286 | ||
287 | route add -host 255.255.255.255 dev eth0 | |
288 | ||
289 | On some older Linux systems, you will get an error if you try to do | |
290 | this. On those systems, try adding the following entry to your | |
291 | /etc/hosts file: | |
292 | ||
293 | 255.255.255.255 all-ones | |
294 | ||
295 | Then, try: | |
296 | ||
297 | route add -host all-ones dev eth0 | |
298 | ||
299 | Another route that has worked for some users is: | |
300 | ||
301 | route add -net 255.255.255.0 dev eth0 | |
302 | ||
303 | If you are not using eth0 as your network interface, you should | |
304 | specify the network interface you *are* using in your route command. | |
305 | ||
306 | LINUX: IP BOOTP AGENT | |
307 | ||
308 | Some versions of the Linux 2.1 kernel apparently prevent dhcpd from | |
309 | working unless you enable it by doing the following: | |
310 | ||
311 | echo 1 >/proc/sys/net/ipv4/ip_bootp_agent | |
312 | ||
313 | ||
314 | LINUX: MULTIPLE INTERFACES | |
315 | ||
316 | Very old versions of the Linux kernel do not provide a networking API | |
317 | that allows dhcpd to operate correctly if the system has more than one | |
318 | broadcast network interface. However, Linux 2.0 kernels with version | |
319 | numbers greater than or equal to 2.0.31 add an API feature: the | |
320 | SO_BINDTODEVICE socket option. If SO_BINDTODEVICE is present, it is | |
321 | possible for dhcpd to operate on Linux with more than one network | |
322 | interface. In order to take advantage of this, you must be running a | |
323 | 2.0.31 or greater kernel, and you must have 2.0.31 or later system | |
324 | headers installed *before* you build the DHCP Distribution. | |
325 | ||
326 | We have heard reports that you must still add routes to 255.255.255.255 | |
327 | in order for the all-ones broadcast to work, even on 2.0.31 kernels. | |
328 | In fact, you now need to add a route for each interface. Hopefully | |
329 | the Linux kernel gurus will get this straight eventually. | |
330 | ||
331 | Linux 2.1 and later kernels do not use SO_BINDTODEVICE or require the | |
332 | broadcast address hack, but do support multiple interfaces, using the | |
333 | Linux Packet Filter. | |
334 | ||
335 | LINUX: OpenWrt | |
336 | ||
337 | DHCP 4.1 has been tested on OpenWrt 7.09 and 8.09. In keeping with | |
338 | standard practice, client/scripts now includes a dhclient-script file | |
339 | for OpenWrt. However, this is not sufficient by itself to run dhcp on | |
340 | OpenWrt; a full OpenWrt package for DHCP is available at | |
341 | ftp://ftp.isc.org/isc/dhcp/dhcp-4.1.0-openwrt.tar.gz | |
342 | ||
343 | LINUX: 802.1q VLAN INTERFACES | |
344 | ||
345 | If you're using 802.1q vlan interfaces on Linux, it is necessary to | |
346 | vconfig the subinterface(s) to rewrite the 802.1q information out of | |
347 | packets received by the dhcpd daemon via LPF: | |
348 | ||
349 | vconfig set_flag eth1.523 1 1 | |
350 | ||
351 | Note that this may affect the performance of your system, since the | |
352 | Linux kernel must rewrite packets received via this interface. For | |
353 | more information, consult the vconfig man pages. | |
354 | ||
355 | SCO | |
356 | ||
357 | ISC DHCP will now work correctly on newer versions of SCO out of the | |
358 | box (tested on OpenServer 5.05b, assumed to work on UnixWare 7). | |
359 | ||
360 | Older versions of SCO have the same problem as Linux (described earlier). | |
361 | The thing is, SCO *really* doesn't want to let you add a host route to | |
362 | the all-ones broadcast address. | |
363 | ||
364 | You can try the following: | |
365 | ||
366 | ifconfig net0 xxx.xxx.xxx.xxx netmask 0xNNNNNNNN broadcast 255.255.255.255 | |
367 | ||
368 | If this doesn't work, you can also try the following strange hack: | |
369 | ||
370 | ifconfig net0 alias 10.1.1.1 netmask 8.0.0.0 | |
371 | ||
372 | Apparently this works because of an interaction between SCO's support | |
373 | for network classes and the weird netmask. The 10.* network is just a | |
374 | dummy that can generally be assumed to be safe. Don't ask why this | |
375 | works. Just try it. If it works for you, great. | |
376 | ||
377 | HP-UX | |
378 | ||
379 | HP-UX has the same problem with the all-ones broadcast address that | |
380 | SCO and Linux have. One user reported that adding the following to | |
381 | /etc/rc.config.d/netconf helped (you may have to modify this to suit | |
382 | your local configuration): | |
383 | ||
384 | INTERFACE_NAME[0]=lan0 | |
385 | IP_ADDRESS[0]=1.1.1.1 | |
386 | SUBNET_MASK[0]=255.255.255.0 | |
387 | BROADCAST_ADDRESS[0]="255.255.255.255" | |
388 | LANCONFIG_ARGS[0]="ether" | |
389 | DHCP_ENABLE[0]=0 | |
390 | ||
391 | ULTRIX | |
392 | ||
393 | Now that we have Ultrix packet filter support, the DHCP Distribution | |
394 | on Ultrix should be pretty trouble-free. However, one thing you do | |
395 | need to be aware of is that it now requires that the pfilt device be | |
396 | configured into your kernel and present in /dev. If you type ``man | |
397 | packetfilter'', you will get some information on how to configure your | |
398 | kernel for the packet filter (if it isn't already) and how to make an | |
399 | entry for it in /dev. | |
400 | ||
401 | FreeBSD | |
402 | ||
403 | Versions of FreeBSD prior to 2.2 have a bug in BPF support in that the | |
404 | ethernet driver swaps the ethertype field in the ethernet header | |
405 | downstream from BPF, which corrupts the output packet. If you are | |
406 | running a version of FreeBSD prior to 2.2, and you find that dhcpd | |
407 | can't communicate with its clients, you should #define BROKEN_FREEBSD_BPF | |
408 | in site.h and recompile. | |
409 | ||
410 | Modern versions of FreeBSD include the ISC DHCP 3.0 client as part of | |
411 | the base system, and the full distribution (for the DHCP server and | |
412 | relay agent) is available from the Ports Collection in | |
413 | /usr/ports/net/isc-dhcp3, or as a package on FreeBSD installation | |
414 | CDROMs. | |
415 | ||
416 | NeXTSTEP | |
417 | ||
418 | The NeXTSTEP support uses the NeXTSTEP Berkeley Packet Filter | |
419 | extension, which is not included in the base NextStep system. You | |
420 | must install this extension in order to get dhcpd or dhclient to work. | |
421 | ||
422 | SOLARIS | |
423 | ||
424 | There are two known issues seen when compiling using the Sun compiler. | |
425 | ||
426 | The first is that older Sun compilers generate an error on some of | |
427 | our uses of the flexible array option. Newer versions only generate | |
428 | a warning, which can be safely ignored. If you run into this error | |
429 | ("type of struct member "buf" can not be derived from structure with | |
430 | flexible array member"), upgrade your tools to Oracle Solaris Studio | |
431 | (previously Sun Studio) 12 or something newer. | |
432 | ||
433 | The second is the interaction between the configure script and the | |
434 | makefiles for the Bind libraries. Currently we don't pass all | |
435 | environment variables between the DHCP configure and the Bind configure. | |
436 | ||
437 | If you attempt to specify the compiler you wish to use like this: | |
438 | ||
439 | CC=/opt/SUNWspro/bin/cc ./configure | |
440 | ||
441 | "make" may not build the Bind libraries with that compiler. | |
442 | ||
443 | In order to use the same compiler for Bind and DHCP we suggest the | |
444 | following commands: | |
445 | ||
446 | CC=/opt/SUNWspro/bin/cc ./configure | |
447 | CC=/opt/SUNWspro/bin/cc make | |
448 | ||
449 | Solaris 11 | |
450 | ||
451 | We have integrated a patch from Oracle to use sockets instead of | |
452 | DLPI on Solaris 11. This functionality was written for use with | |
453 | Solaris Studio 12.2 and requires the system/header package. | |
454 | ||
455 | By default this code is disabled in order to minimize disruptions | |
456 | for current users. In order to enable this code you will need to | |
457 | enable both USE_SOCKETS and USE_V4_PKTINFO as part of the | |
458 | configuration step. The command line would be something like: | |
459 | ||
460 | ./configure --enable-use-sockets --enable-ipv4-pktinfo | |
461 | ||
462 | Solaris 11 and ATF | |
463 | ||
464 | We have reports that ATF 0.15 and 0.16 do not build on Solaris 11. The | |
465 | following changes to the ATF source code appear to fix this issue: | |
466 | ||
467 | diff -ru atf-0.15/atf-c/tp_test.c atf-0.15-patched/atf-c/tp_test.c | |
468 | --- atf-0.15/atf-c/tp_test.c 2011-12-06 06:31:11.000000000 +0100 | |
469 | +++ atf-0.15-patched/atf-c/tp_test.c 2012-06-19 15:54:57.000000000 +0200 | |
470 | @@ -28,6 +28,7 @@ | |
471 | */ | |
472 | ||
473 | #include <string.h> | |
474 | +#include <stdio.h> | |
475 | #include <unistd.h> | |
476 | ||
477 | #include <atf-c.h> | |
478 | ||
479 | diff -ru atf-0.15/atf-run/requirements.cpp atf-0.15-patched/atf-run/requirements.cpp | |
480 | --- atf-0.15/atf-run/requirements.cpp 2012-01-13 20:44:25.000000000 +0100 | |
481 | +++ atf-0.15-patched/atf-run/requirements.cpp 2012-06-19 15:41:51.000000000 +0200 | |
482 | @@ -29,7 +29,7 @@ | |
483 | ||
484 | extern "C" { | |
485 | #include <sys/param.h> | |
486 | -#include <sys/sysctl.h> | |
487 | +//#include <sys/sysctl.h> | |
488 | } | |
489 | ||
490 | #include <cerrno> | |
491 | ||
492 | Other Solaris Items | |
493 | ||
494 | One problem which has been observed and is not fixed in this | |
495 | patchlevel has to do with using DLPI on Solaris machines. The symptom | |
496 | of this problem is that the DHCP server never receives any requests. | |
497 | This has been observed with Solaris 2.6 and Solaris 7 on Intel x86 | |
498 | systems, although it may occur with other systems as well. If you | |
499 | encounter this symptom, and you are running the DHCP server on a | |
500 | machine with a single broadcast network interface, you may wish to | |
501 | edit the includes/site.h file and uncomment the #define USE_SOCKETS | |
502 | line. Then type ``make clean; make''. As an alternative workaround, | |
503 | it has been reported that running 'snoop' will cause the dhcp server | |
504 | to start receiving packets. So the practice reported to us is to run | |
505 | snoop at dhcpd startup time, with arguments to cause it to receive one | |
506 | packet and exit. | |
507 | ||
508 | snoop -c 1 udp port 67 > /dev/null & | |
509 | ||
510 | The DHCP client on Solaris will only work with DLPI. If you run it | |
511 | and it just keeps saying it's sending DHCPREQUEST packets, but never | |
512 | gets a response, you may be having DLPI trouble as described above. | |
513 | If so, we have no solution to offer at this time, aside from the above | |
514 | workaround which should also work here. Also, because Solaris requires | |
515 | you to "plumb" an interface before it can be detected by the DHCP client, | |
516 | you must either specify the name(s) of the interface(s) you want to | |
517 | configure on the command line, or must plumb the interfaces prior to | |
518 | invoking the DHCP client. This can be done with ``ifconfig iface plumb'', | |
519 | where iface is the name of the interface (e.g., ``ifconfig hme0 plumb''). | |
520 | ||
521 | It should be noted that Solaris versions from 2.6 onward include a | |
522 | DHCP client that you can run with ``/sbin/ifconfig iface dhcp start'' | |
523 | rather than using the ISC DHCP client, including DHCPv6. Consequently, | |
524 | we don't believe there is a need for the client to run on Solaris, and | |
525 | have not engineered the needed DHCPv6 modifications for the dhclient-script. | |
526 | If you feel this is in error, or have a need, please contact us. | |
527 | ||
528 | AIX | |
529 | ||
530 | The AIX support uses the BSD socket API, which cannot differentiate on | |
531 | which network interface a broadcast packet was received; thus the DHCP | |
532 | server and relay will work only on a single interface. (They do work | |
533 | on multi-interface machines if configured to listen on only one of the | |
534 | interfaces.) | |
535 | ||
536 | We have reports of Windows XP clients having difficulty retrieving | |
537 | addresses from a server running on an AIX machine. This issue | |
538 | was traced to the client requiring messages be sent to the all ones | |
539 | broadcast address (255.255.255.255) while the AIX server was sending | |
540 | to 192.168.0.255. | |
541 | ||
542 | You may be able to solve this by including a relay between the client | |
543 | and server with the relay configured to use a broadcast of all-ones. | |
544 | ||
545 | A second option that worked for AIX 5.1 but doesn't seem to work for | |
546 | AIX 5.3 was to: | |
547 | create a host file entry for all-ones (255.255.255.255) | |
548 | and then add a route: | |
549 | route add -host all-ones -interface <local-ip-address> | |
550 | ||
551 | The ISC DHCP distribution does not include a dhclient-script for AIX-- | |
552 | AIX comes with a DHCP client. Contribution of a working dhclient-script | |
553 | for AIX would be welcome. | |
554 | ||
555 | ||
556 | MacOS X | |
557 | ||
558 | The MacOS X system uses a TCP/IP stack derived from FreeBSD with a | |
559 | user-friendly interface named the System Configuration Framework. | |
560 | As it includes a builtin DHCPv4 client (you are better just using that), | |
561 | this text is only about the DHCPv6 client (``dhclient -6 ...''). The DNS | |
562 | configuration (domain search list and name servers' addresses) is managed | |
563 | by a System Configuration agent, not by /etc/resolv.conf (which is a link | |
564 | to /var/run/resolv.conf, which itself only reflects the internal state; | |
565 | the System Configuration framework's Dynamic Store). | |
566 | ||
567 | This means that modifying resolv.conf directly doesn't have the | |
568 | intended effect, instead the macos script sample creates its own | |
569 | resolv.conf.dhclient6 in /var/run, and inserts the contents of this | |
570 | file into the Dynamic Store. | |
571 | ||
572 | When updating the address configuration the System Configuration | |
573 | framework expects the prefix and a default router along with the | |
574 | configured address. As this extra information is not available via | |
575 | the DHCPv6 protocol the System Configuration framework isn't usable | |
576 | for address configuration, instead ifconfig is used directly. | |
577 | ||
578 | Note the Dynamic Store (from which /var/run/resolv.conf is built) is | |
579 | recomputed from scratch when the current location/set is changed. | |
580 | Running the dhclient-script reinstalls the resolv.conf.dhclient6 | |
581 | configuration. | |
582 | ||
583 | ||
584 | ATF | |
585 | ||
586 | Please see the file DHCP/doc/devel/atf.dox for a description of building | |
587 | and using these tools. | |
588 | ||
589 | The optional unit tests use ATF (Automated Testing Framework) including | |
590 | the atf-run and atf-report tools. ATF deprecated these tools in | |
591 | version 0.19 and removed these tools from its sources in version 0.20, | |
592 | requiring you to get an older version, use Kyua with an ATF compatibility | |
593 | package or use the version included in the Bind sources. | |
594 | ||
595 | SUPPORT | |
596 | ||
597 | The Internet Systems Consortium DHCP server is developed and distributed | |
598 | by ISC in the public trust, thanks to the generous donations of its | |
599 | sponsors. ISC now also offers commercial quality support contracts for | |
600 | ISC DHCP, more information about ISC Support Contracts can be found at | |
601 | the following URL: | |
602 | ||
603 | https://www.isc.org/services/support/ | |
604 | ||
605 | Please understand that we may not respond to support inquiries unless | |
606 | you have a support contract. ISC will continue its practice of always | |
607 | responding to critical items that effect the entire community, and | |
608 | responding to all other requests for support upon ISC's mailing lists | |
609 | on a best-effort basis. | |
610 | ||
611 | However, ISC DHCP has attracted a fairly sizable following on the | |
612 | Internet, which means that there are a lot of knowledgeable users who | |
613 | may be able to help you if you get stuck. These people generally | |
614 | read the dhcp-users@isc.org mailing list. Be sure to provide as much | |
615 | detail in your query as possible. | |
616 | ||
617 | If you are going to use ISC DHCP, you should probably subscribe to | |
618 | the dhcp-users or dhcp-announce mailing lists. | |
619 | ||
620 | WHERE TO SEND FEATURE REQUESTS: We like to hear your feedback. We may | |
621 | not respond to it all the time, but we do read it. If ISC DHCP doesn't | |
622 | work well for you, or you have an idea that would improve it for your | |
623 | use, please send your suggestion to dhcp-suggest@isc.org. This is also | |
624 | an excellent place to send patches that add new features. | |
625 | ||
626 | WHERE TO REPORT BUGS: If you want the act of sending in a bug report | |
627 | to result in you getting help in the form of a fixed piece of | |
628 | software, you are asking for help. Your bug report is helpful to us, | |
629 | but fundamentally you are making a support request, so please use the | |
630 | addresses described in the previous paragraphs. If you are _sure_ that | |
631 | your problem is a bug, and not user error, or if your bug report | |
632 | includes a patch, you can send it to our ticketing system at | |
633 | dhcp-bugs@isc.org. If you have not received a notice that the ticket | |
634 | has been resolved, then we're still working on it. | |
635 | ||
636 | PLEASE DO NOT REPORT BUGS IN OLD SOFTWARE RELEASES! Fetch the latest | |
637 | release and see if the bug is still in that version of the software, | |
638 | and if it is still present, _then_ report it. ISC release versions | |
639 | always have three numbers, for example: 1.2.3. The 'major release' is | |
640 | 1 here, the 'minor release' is 2, and the 'maintenance release' is 3. | |
641 | ISC will accept bug reports against the most recent two major.minor | |
642 | releases: for example, 1.0.0 and 0.9.0, but not 0.8.* or prior. | |
643 | ||
644 | PLEASE take a moment to determine where the ISC DHCP distribution | |
645 | that you're using came from. ISC DHCP is sometimes heavily modified | |
646 | by integrators in various operating systems - it's not that we | |
647 | feel that our software is perfect and incapable of having bugs, but | |
648 | rather that it is very frustrating to find out after many days trying | |
649 | to help someone that the sources you're looking at aren't what they're | |
650 | running. When in doubt, please retrieve the source distribution from | |
651 | ISC's web page and install it. | |
652 | ||
653 | HOW TO REPORT BUGS OR REQUEST HELP | |
654 | ||
655 | When you report bugs or ask for help, please provide us complete | |
656 | information. A list of information we need follows. Please read it | |
657 | carefully, and put all the information you can into your initial bug | |
658 | report. This will save us a great deal of time and more informative | |
659 | bug reports are more likely to get handled more quickly overall. | |
660 | ||
661 | 1. The specific operating system name and version of the | |
662 | machine on which the DHCP server or client is running. | |
663 | 2. The specific operating system name and version of the | |
664 | machine on which the client is running, if you are having | |
665 | trouble getting a client working with the server. | |
666 | 3. If you're running Linux, the version number we care about is | |
667 | the kernel version and maybe the library version, not the | |
668 | distribution version - e.g., while we don't mind knowing | |
669 | that you're running Redhat version mumble.foo, we must know | |
670 | what kernel version you're running, and it helps if you can | |
671 | tell us what version of the C library you're running, | |
672 | although if you don't know that off the top of your head it | |
673 | may be hard for you to figure it out, so don't go crazy | |
674 | trying. | |
675 | 4. The specific version of the DHCP distribution you're | |
676 | running, as reported by dhcpd -t. | |
677 | 5. Please explain the problem carefully, thinking through what | |
678 | you're saying to ensure that you don't assume we know | |
679 | something about your situation that we don't know. | |
680 | 6. Include your dhcpd.conf and dhcpd.leases file as MIME attachments | |
681 | if they're not over 100 kilobytes in size each. If they are | |
682 | this large, please make them available to us, e.g., via a hidden | |
683 | http:// URL or FTP site. If you're not comfortable releasing | |
684 | this information due to sensitive contents, you may encrypt | |
685 | the file to our release signing key, available on our website. | |
686 | 7. Include a log of your server or client running until it | |
687 | encounters the problem - for example, if you are having | |
688 | trouble getting some client to get an address, restart the | |
689 | server with the -d flag and then restart the client, and | |
690 | send us what the server prints. Likewise, with the client, | |
691 | include the output of the client as it fails to get an | |
692 | address or otherwise does the wrong thing. Do not leave | |
693 | out parts of the output that you think aren't interesting. | |
694 | 8. If the client or server is dumping core, please run the | |
695 | debugger and get a stack trace, and include that in your | |
696 | bug report. For example, if your debugger is gdb, do the | |
697 | following: | |
698 | ||
699 | gdb dhcpd dhcpd.core | |
700 | (gdb) where | |
701 | [...] | |
702 | (gdb) quit | |
703 | ||
704 | This assumes that it's the dhcp server you're debugging, and | |
705 | that the core file is in dhcpd.core. | |
706 | ||
707 | Please see https://www.isc.org/software/dhcp/ for details on how to subscribe | |
708 | to the ISC DHCP mailing lists. | |
709 | ||
710 | HISTORY | |
711 | ||
712 | ISC DHCP was originally written by Ted Lemon under a contract with | |
713 | Vixie Labs with the goal of being a complete reference implementation | |
714 | of the DHCP protocol. Funding for this project was provided by | |
715 | Internet Systems Consortium. The first release of the ISC DHCP | |
716 | distribution in December 1997 included just the DHCP server. | |
717 | Release 2 in June 1999 added a DHCP client and a BOOTP/DHCP relay | |
718 | agent. DHCP 3 was released in October 2001 and included DHCP failover | |
719 | support, OMAPI, Dynamic DNS, conditional behaviour, client classing, | |
720 | and more. Version 3 of the DHCP server was funded by Nominum, Inc. | |
721 | The 4.0 release in December 2007 introduced DHCPv6 protocol support | |
722 | for the server and client. | |
723 | ||
724 | This product includes cryptographic software written | |
725 | by Eric Young (eay@cryptsoft.com). |