1 Internet Systems Consortium DHCP Distribution
7 You should read this file carefully before trying to install or use
8 the ISC DHCP Distribution.
12 1 WHERE TO FIND DOCUMENTATION
14 3 BUILDING THE DHCP DISTRIBUTION
17 3.2.1 DYNAMIC DNS UPDATES
18 3.2.2 LOCALLY DEFINED OPTIONS
20 4 INSTALLING THE DHCP DISTRIBUTION
21 5 USING THE DHCP DISTRIBUTION
24 5.2.1 IF_TR.H NOT FOUND
25 5.2.2 SO_ATTACH_FILTER UNDECLARED
26 5.2.3 PROTOCOL NOT CONFIGURED
29 5.2.7 MULTIPLE INTERFACES
37 5.8.2 Solaris 11 and ATF
38 5.8.3 Other Solaris Items
43 6.1 HOW TO REPORT BUGS
46 WHERE TO FIND DOCUMENTATION
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.
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.
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.
78 DHCP relay agent documentation is in the dhcrelay man page, the source
79 for which is distributed in the relay/ subdirectory.
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).
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
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).
103 This is ISC DHCP 4.3.x The major theme for this release is "ipv6 uplift",
104 in which we enhance the v6 code to support many of the features found
105 in the v4 code. These include: support for v6, support for on_commit,
106 on_expiry and on_release in v6, support for accessing v6 relay options
107 and better log messages for v6 addresses. Non v6 features include:
108 support for the standard DDNS, better OMAPI class and sub-class support
109 allowing for dynamic addition and removal of sub-classes, and support for
110 DDNS without zone statements.
112 In this release, the DHCPv6 server should be fully functional on Linux,
113 Solaris, or any BSD. The DHCPv6 client should be similarly functional
116 The DHCPv4 server, relay, and client, should be fully functional
117 on Linux, Solaris, any BSD, HPUX, SCO, NextSTEP, and Irix.
119 If you are running the DHCP distribution on a machine which is a
120 firewall, or if there is a firewall between your DHCP server(s) and
121 DHCP clients, please read the section on firewalls which appears later
124 If you wish to run the DHCP Distribution on Linux, please see the
125 Linux-specific notes later in this document. If you wish to run on an
126 SCO release, please see the SCO-specific notes later in this document.
127 You particularly need to read these notes if you intend to support
128 Windows 95 clients. If you are running HP-UX or Ultrix, please read the
129 notes for those operating systems below. If you are running NeXTSTEP,
130 please see the notes on NeXTSTEP below.
132 If you start dhcpd and get a message, "no free bpf", that means you
133 need to configure the Berkeley Packet Filter into your operating
134 system kernel. On NetBSD, FreeBSD and BSD/os, type ``man bpf'' for
135 information. On Digital Unix, type ``man pfilt''.
138 BUILDING THE DHCP DISTRIBUTION
142 To build the DHCP Distribution, unpack the compressed tar file using
143 the tar utility and the gzip command - type something like:
145 gunzip dhcp-4.3.4.tar.gz
146 tar xvf dhcp-4.3.4.tar
150 Now, cd to the dhcp-4.3.4 subdirectory that you've just created and
151 configure the source tree by typing:
155 If the configure utility can figure out what sort of system you're
156 running on, it will create a custom Makefile for you for that
157 system; otherwise, it will complain. If it can't figure out what
158 system you are using, that system is not supported - you are on
161 Several options may be enabled or disabled via the configure command.
162 You can get a list of these by typing:
166 If you want to use dynamic shared libraries automake, autoconf
167 (aka GNU autotools) and libtool must be available. The DHCP
168 distribution provides 3 configure.ac* files: the -lt version
169 has no libtool support and was copied to the configure.ac
170 standard file in the distribution. To enable libtool support
171 you should perform these steps:
173 cp configure.ac+lt configure.ac
176 after you can use the regenerated configure as usual
177 (with libtool support (--enable-libtool) on by default):
181 For compatibility (and people who don't read this documentation)
182 the --enable-libtool configuration file is supported even by
183 the distributed configure (and off by default). The previous
184 steps are performed and the regenerated configure called with
185 almost the same parameters (this "almost" makes the use of
186 this feature not recommended).
190 A fully-featured implementation of dynamic DNS updates is included in
191 this release. It uses libraries from BIND and, to avoid issues with
192 different versions, includes the necessary BIND version. The appropriate
193 BIND libraries will be compiled and installed in the bind subdirectory
194 as part of the make step. In order to build the necessary libraries you
195 will need to have "gmake" available on your build system.
198 There is documentation for the DDNS support in the dhcpd.conf manual
199 page - see the beginning of this document for information on finding
202 LOCALLY DEFINED OPTIONS
204 In previous versions of the DHCP server there was a mechanism whereby
205 options that were not known by the server could be configured using
206 a name made up of the option code number and an identifier:
207 "option-nnn" This is no longer supported, because it is not future-
208 proof. Instead, if you want to use an option that the server doesn't
209 know about, you must explicitly define it using the method described
210 in the dhcp-options man page under the DEFINING NEW OPTIONS heading.
214 Once you've run configure, just type ``make'', and after a while
215 you should have a dhcp server. If you get compile errors on one
216 of the supported systems mentioned earlier, please let us know.
217 If you get warnings, it's not likely to be a problem - the DHCP
218 server compiles completely warning-free on as many architectures
219 as we can manage, but there are a few for which this is difficult.
220 If you get errors on a system not mentioned above, you will need
221 to do some programming or debugging on your own to get the DHCP
222 Distribution working.
224 If you cross compile you have to follow the instructions from
225 the BIND README, in particular you must set the BUILD_CC
226 environment variable.
228 INSTALLING THE DHCP DISTRIBUTION
230 Once you have successfully gotten the DHCP Distribution to build, you
231 can install it by typing ``make install''. If you already have an old
232 version of the DHCP Distribution installed, you may want to save it
233 before typing ``make install''.
235 USING THE DHCP DISTRIBUTION
239 If you are running the DHCP server or client on a computer that's also
240 acting as a firewall, you must be sure to allow DHCP packets through
241 the firewall. In particular, your firewall rules _must_ allow packets
242 from IP address 0.0.0.0 to IP address 255.255.255.255 from UDP port 68
243 to UDP port 67 through. They must also allow packets from your local
244 firewall's IP address and UDP port 67 through to any address your DHCP
245 server might serve on UDP port 68. Finally, packets from relay agents
246 on port 67 to the DHCP server on port 67, and vice versa, must be
249 We have noticed that on some systems where we are using a packet
250 filter, if you set up a firewall that blocks UDP port 67 and 68
251 entirely, packets sent through the packet filter will not be blocked.
252 However, unicast packets will be blocked. This can result in strange
253 behaviour, particularly on DHCP clients, where the initial packet
254 exchange is broadcast, but renewals are unicast - the client will
255 appear to be unable to renew until it starts broadcasting its
256 renewals, and then suddenly it'll work. The fix is to fix the
257 firewall rules as described above.
261 If you have a server that is connected to two networks, and you only
262 want to provide DHCP service on one of those networks (e.g., you are
263 using a cable modem and have set up a NAT router), if you don't write
264 any subnet declaration for the network you aren't supporting, the DHCP
265 server will ignore input on that network interface if it can. If it
266 can't, it will refuse to run - some operating systems do not have the
267 capability of supporting DHCP on machines with more than one
268 interface, and ironically this is the case even if you don't want to
269 provide DHCP service on one of those interfaces.
273 There are three big LINUX issues: the all-ones broadcast address,
274 Linux 2.1 ip_bootp_agent enabling, and operations with more than one
275 network interface. There are also two potential compilation/runtime
276 problems for Linux 2.1/2.2: the "SO_ATTACH_FILTER undeclared" problem
277 and the "protocol not configured" problem.
279 LINUX: PROTOCOL NOT CONFIGURED
281 If you get the following message, it's because your kernel doesn't
282 have the Linux packetfilter or raw packet socket configured:
284 Make sure CONFIG_PACKET (Packet socket) and CONFIG_FILTER (Socket
285 Filtering) are enabled in your kernel configuration
287 If this happens, you need to configure your Linux kernel to support
288 Socket Filtering and the Packet socket, or to select a kernel provided
289 by your Linux distribution that has these enabled (virtually all modern
294 If you are running a recent version of Linux, this won't be a problem,
295 but on older versions of Linux (kernel versions prior to 2.2), there
296 is a potential problem with the broadcast address being sent
299 In order for dhcpd to work correctly with picky DHCP clients (e.g.,
300 Windows 95), it must be able to send packets with an IP destination
301 address of 255.255.255.255. Unfortunately, Linux changes an IP
302 destination of 255.255.255.255 into the local subnet broadcast address
303 (here, that's 192.5.5.223).
305 This isn't generally a problem on Linux 2.2 and later kernels, since
306 we completely bypass the Linux IP stack, but on old versions of Linux
307 2.1 and all versions of Linux prior to 2.1, it is a problem - pickier
308 DHCP clients connected to the same network as the ISC DHCP server or
309 ISC relay agent will not see messages from the DHCP server. It *is*
310 possible to run into trouble with this on Linux 2.2 and later if you
311 are running a version of the DHCP server that was compiled on a Linux
314 It is possible to work around this problem on some versions of Linux
315 by creating a host route from your network interface address to
316 255.255.255.255. The command you need to use to do this on Linux
317 varies from version to version. The easiest version is:
319 route add -host 255.255.255.255 dev eth0
321 On some older Linux systems, you will get an error if you try to do
322 this. On those systems, try adding the following entry to your
325 255.255.255.255 all-ones
329 route add -host all-ones dev eth0
331 Another route that has worked for some users is:
333 route add -net 255.255.255.0 dev eth0
335 If you are not using eth0 as your network interface, you should
336 specify the network interface you *are* using in your route command.
338 LINUX: IP BOOTP AGENT
340 Some versions of the Linux 2.1 kernel apparently prevent dhcpd from
341 working unless you enable it by doing the following:
343 echo 1 >/proc/sys/net/ipv4/ip_bootp_agent
346 LINUX: MULTIPLE INTERFACES
348 Very old versions of the Linux kernel do not provide a networking API
349 that allows dhcpd to operate correctly if the system has more than one
350 broadcast network interface. However, Linux 2.0 kernels with version
351 numbers greater than or equal to 2.0.31 add an API feature: the
352 SO_BINDTODEVICE socket option. If SO_BINDTODEVICE is present, it is
353 possible for dhcpd to operate on Linux with more than one network
354 interface. In order to take advantage of this, you must be running a
355 2.0.31 or greater kernel, and you must have 2.0.31 or later system
356 headers installed *before* you build the DHCP Distribution.
358 We have heard reports that you must still add routes to 255.255.255.255
359 in order for the all-ones broadcast to work, even on 2.0.31 kernels.
360 In fact, you now need to add a route for each interface. Hopefully
361 the Linux kernel gurus will get this straight eventually.
363 Linux 2.1 and later kernels do not use SO_BINDTODEVICE or require the
364 broadcast address hack, but do support multiple interfaces, using the
369 DHCP 4.1 has been tested on OpenWrt 7.09 and 8.09. In keeping with
370 standard practice, client/scripts now includes a dhclient-script file
371 for OpenWrt. However, this is not sufficient by itself to run dhcp on
372 OpenWrt; a full OpenWrt package for DHCP is available at
373 ftp://ftp.isc.org/isc/dhcp/dhcp-4.1.0-openwrt.tar.gz
375 LINUX: 802.1q VLAN INTERFACES
377 If you're using 802.1q vlan interfaces on Linux, it is necessary to
378 vconfig the subinterface(s) to rewrite the 802.1q information out of
379 packets received by the dhcpd daemon via LPF:
381 vconfig set_flag eth1.523 1 1
383 Note that this may affect the performance of your system, since the
384 Linux kernel must rewrite packets received via this interface. For
385 more information, consult the vconfig man pages.
389 ISC DHCP will now work correctly on newer versions of SCO out of the
390 box (tested on OpenServer 5.05b, assumed to work on UnixWare 7).
392 Older versions of SCO have the same problem as Linux (described earlier).
393 The thing is, SCO *really* doesn't want to let you add a host route to
394 the all-ones broadcast address.
396 You can try the following:
398 ifconfig net0 xxx.xxx.xxx.xxx netmask 0xNNNNNNNN broadcast 255.255.255.255
400 If this doesn't work, you can also try the following strange hack:
402 ifconfig net0 alias 10.1.1.1 netmask 8.0.0.0
404 Apparently this works because of an interaction between SCO's support
405 for network classes and the weird netmask. The 10.* network is just a
406 dummy that can generally be assumed to be safe. Don't ask why this
407 works. Just try it. If it works for you, great.
411 HP-UX has the same problem with the all-ones broadcast address that
412 SCO and Linux have. One user reported that adding the following to
413 /etc/rc.config.d/netconf helped (you may have to modify this to suit
414 your local configuration):
416 INTERFACE_NAME[0]=lan0
417 IP_ADDRESS[0]=1.1.1.1
418 SUBNET_MASK[0]=255.255.255.0
419 BROADCAST_ADDRESS[0]="255.255.255.255"
420 LANCONFIG_ARGS[0]="ether"
425 Now that we have Ultrix packet filter support, the DHCP Distribution
426 on Ultrix should be pretty trouble-free. However, one thing you do
427 need to be aware of is that it now requires that the pfilt device be
428 configured into your kernel and present in /dev. If you type ``man
429 packetfilter'', you will get some information on how to configure your
430 kernel for the packet filter (if it isn't already) and how to make an
431 entry for it in /dev.
435 Versions of FreeBSD prior to 2.2 have a bug in BPF support in that the
436 ethernet driver swaps the ethertype field in the ethernet header
437 downstream from BPF, which corrupts the output packet. If you are
438 running a version of FreeBSD prior to 2.2, and you find that dhcpd
439 can't communicate with its clients, you should #define BROKEN_FREEBSD_BPF
440 in site.h and recompile.
442 Modern versions of FreeBSD include the ISC DHCP 3.0 client as part of
443 the base system, and the full distribution (for the DHCP server and
444 relay agent) is available from the Ports Collection in
445 /usr/ports/net/isc-dhcp3, or as a package on FreeBSD installation
450 The NeXTSTEP support uses the NeXTSTEP Berkeley Packet Filter
451 extension, which is not included in the base NextStep system. You
452 must install this extension in order to get dhcpd or dhclient to work.
456 There are two known issues seen when compiling using the Sun compiler.
458 The first is that older Sun compilers generate an error on some of
459 our uses of the flexible array option. Newer versions only generate
460 a warning, which can be safely ignored. If you run into this error
461 ("type of struct member "buf" can not be derived from structure with
462 flexible array member"), upgrade your tools to Oracle Solaris Studio
463 (previously Sun Studio) 12 or something newer.
465 The second is the interaction between the configure script and the
466 makefiles for the Bind libraries. Currently we don't pass all
467 environment variables between the DHCP configure and the Bind configure.
469 If you attempt to specify the compiler you wish to use like this:
471 CC=/opt/SUNWspro/bin/cc ./configure
473 "make" may not build the Bind libraries with that compiler.
475 In order to use the same compiler for Bind and DHCP we suggest the
478 CC=/opt/SUNWspro/bin/cc ./configure
479 CC=/opt/SUNWspro/bin/cc make
483 We have integrated a patch from Oracle to use sockets instead of
484 DLPI on Solaris 11. This functionality was written for use with
485 Solaris Studio 12.2 and requires the system/header package.
487 By default this code is disabled in order to minimize disruptions
488 for current users. In order to enable this code you will need to
489 enable both USE_SOCKETS and USE_V4_PKTINFO as part of the
490 configuration step. The command line would be something like:
492 ./configure --enable-use-sockets --enable-ipv4-pktinfo
496 We have reports that ATF 0.15 and 0.16 do not build on Solaris 11. The
497 following changes to the ATF source code appear to fix this issue:
499 diff -ru atf-0.15/atf-c/tp_test.c atf-0.15-patched/atf-c/tp_test.c
500 --- atf-0.15/atf-c/tp_test.c 2011-12-06 06:31:11.000000000 +0100
501 +++ atf-0.15-patched/atf-c/tp_test.c 2012-06-19 15:54:57.000000000 +0200
511 diff -ru atf-0.15/atf-run/requirements.cpp atf-0.15-patched/atf-run/requirements.cpp
512 --- atf-0.15/atf-run/requirements.cpp 2012-01-13 20:44:25.000000000 +0100
513 +++ atf-0.15-patched/atf-run/requirements.cpp 2012-06-19 15:41:51.000000000 +0200
517 #include <sys/param.h>
518 -#include <sys/sysctl.h>
519 +//#include <sys/sysctl.h>
526 One problem which has been observed and is not fixed in this
527 patchlevel has to do with using DLPI on Solaris machines. The symptom
528 of this problem is that the DHCP server never receives any requests.
529 This has been observed with Solaris 2.6 and Solaris 7 on Intel x86
530 systems, although it may occur with other systems as well. If you
531 encounter this symptom, and you are running the DHCP server on a
532 machine with a single broadcast network interface, you may wish to
533 edit the includes/site.h file and uncomment the #define USE_SOCKETS
534 line. Then type ``make clean; make''. As an alternative workaround,
535 it has been reported that running 'snoop' will cause the dhcp server
536 to start receiving packets. So the practice reported to us is to run
537 snoop at dhcpd startup time, with arguments to cause it to receive one
540 snoop -c 1 udp port 67 > /dev/null &
542 The DHCP client on Solaris will only work with DLPI. If you run it
543 and it just keeps saying it's sending DHCPREQUEST packets, but never
544 gets a response, you may be having DLPI trouble as described above.
545 If so, we have no solution to offer at this time, aside from the above
546 workaround which should also work here. Also, because Solaris requires
547 you to "plumb" an interface before it can be detected by the DHCP client,
548 you must either specify the name(s) of the interface(s) you want to
549 configure on the command line, or must plumb the interfaces prior to
550 invoking the DHCP client. This can be done with ``ifconfig iface plumb'',
551 where iface is the name of the interface (e.g., ``ifconfig hme0 plumb'').
553 It should be noted that Solaris versions from 2.6 onward include a
554 DHCP client that you can run with ``/sbin/ifconfig iface dhcp start''
555 rather than using the ISC DHCP client, including DHCPv6. Consequently,
556 we don't believe there is a need for the client to run on Solaris, and
557 have not engineered the needed DHCPv6 modifications for the dhclient-script.
558 If you feel this is in error, or have a need, please contact us.
562 The AIX support uses the BSD socket API, which cannot differentiate on
563 which network interface a broadcast packet was received; thus the DHCP
564 server and relay will work only on a single interface. (They do work
565 on multi-interface machines if configured to listen on only one of the
568 We have reports of Windows XP clients having difficulty retrieving
569 addresses from a server running on an AIX machine. This issue
570 was traced to the client requiring messages be sent to the all ones
571 broadcast address (255.255.255.255) while the AIX server was sending
574 You may be able to solve this by including a relay between the client
575 and server with the relay configured to use a broadcast of all-ones.
577 A second option that worked for AIX 5.1 but doesn't seem to work for
579 create a host file entry for all-ones (255.255.255.255)
580 and then add a route:
581 route add -host all-ones -interface <local-ip-address>
583 The ISC DHCP distribution does not include a dhclient-script for AIX--
584 AIX comes with a DHCP client. Contribution of a working dhclient-script
585 for AIX would be welcome.
590 The MacOS X system uses a TCP/IP stack derived from FreeBSD with a
591 user-friendly interface named the System Configuration Framework.
592 As it includes a builtin DHCPv4 client (you are better just using that),
593 this text is only about the DHCPv6 client (``dhclient -6 ...''). The DNS
594 configuration (domain search list and name servers' addresses) is managed
595 by a System Configuration agent, not by /etc/resolv.conf (which is a link
596 to /var/run/resolv.conf, which itself only reflects the internal state;
597 the System Configuration framework's Dynamic Store).
599 This means that modifying resolv.conf directly doesn't have the
600 intended effect, instead the macos script sample creates its own
601 resolv.conf.dhclient6 in /var/run, and inserts the contents of this
602 file into the Dynamic Store.
604 When updating the address configuration the System Configuration
605 framework expects the prefix and a default router along with the
606 configured address. As this extra information is not available via
607 the DHCPv6 protocol the System Configuration framework isn't usable
608 for address configuration, instead ifconfig is used directly.
610 Note the Dynamic Store (from which /var/run/resolv.conf is built) is
611 recomputed from scratch when the current location/set is changed.
612 Running the dhclient-script reinstalls the resolv.conf.dhclient6
618 Please see the file DHCP/doc/devel/atf.dox for a description of building
619 and using these tools.
621 The optional unit tests use ATF (Automated Testing Framework) including
622 the atf-run and atf-report tools. ATF deprecated these tools in
623 version 0.19 and removed these tools from its sources in version 0.20,
624 requiring you to get an older version, use Kyua with an ATF compatibility
625 package or use the version included in the Bind sources.
629 The Internet Systems Consortium DHCP server is developed and distributed
630 by ISC in the public trust, thanks to the generous donations of its
631 sponsors. ISC now also offers commercial quality support contracts for
632 ISC DHCP, more information about ISC Support Contracts can be found at
635 https://www.isc.org/services/support/
637 Please understand that we may not respond to support inquiries unless
638 you have a support contract. ISC will continue its practice of always
639 responding to critical items that effect the entire community, and
640 responding to all other requests for support upon ISC's mailing lists
641 on a best-effort basis.
643 However, ISC DHCP has attracted a fairly sizable following on the
644 Internet, which means that there are a lot of knowledgeable users who
645 may be able to help you if you get stuck. These people generally
646 read the dhcp-users@isc.org mailing list. Be sure to provide as much
647 detail in your query as possible.
649 If you are going to use ISC DHCP, you should probably subscribe to
650 the dhcp-users or dhcp-announce mailing lists.
652 WHERE TO SEND FEATURE REQUESTS: We like to hear your feedback. We may
653 not respond to it all the time, but we do read it. If ISC DHCP doesn't
654 work well for you, or you have an idea that would improve it for your
655 use, please send your suggestion to dhcp-suggest@isc.org. This is also
656 an excellent place to send patches that add new features.
658 WHERE TO REPORT BUGS: If you want the act of sending in a bug report
659 to result in you getting help in the form of a fixed piece of
660 software, you are asking for help. Your bug report is helpful to us,
661 but fundamentally you are making a support request, so please use the
662 addresses described in the previous paragraphs. If you are _sure_ that
663 your problem is a bug, and not user error, or if your bug report
664 includes a patch, you can send it to our ticketing system at
665 dhcp-bugs@isc.org. If you have not received a notice that the ticket
666 has been resolved, then we're still working on it.
668 PLEASE DO NOT REPORT BUGS IN OLD SOFTWARE RELEASES! Fetch the latest
669 release and see if the bug is still in that version of the software,
670 and if it is still present, _then_ report it. ISC release versions
671 always have three numbers, for example: 1.2.3. The 'major release' is
672 1 here, the 'minor release' is 2, and the 'maintenance release' is 3.
673 ISC will accept bug reports against the most recent two major.minor
674 releases: for example, 1.0.0 and 0.9.0, but not 0.8.* or prior.
676 PLEASE take a moment to determine where the ISC DHCP distribution
677 that you're using came from. ISC DHCP is sometimes heavily modified
678 by integrators in various operating systems - it's not that we
679 feel that our software is perfect and incapable of having bugs, but
680 rather that it is very frustrating to find out after many days trying
681 to help someone that the sources you're looking at aren't what they're
682 running. When in doubt, please retrieve the source distribution from
683 ISC's web page and install it.
685 HOW TO REPORT BUGS OR REQUEST HELP
687 When you report bugs or ask for help, please provide us complete
688 information. A list of information we need follows. Please read it
689 carefully, and put all the information you can into your initial bug
690 report. This will save us a great deal of time and more informative
691 bug reports are more likely to get handled more quickly overall.
693 1. The specific operating system name and version of the
694 machine on which the DHCP server or client is running.
695 2. The specific operating system name and version of the
696 machine on which the client is running, if you are having
697 trouble getting a client working with the server.
698 3. If you're running Linux, the version number we care about is
699 the kernel version and maybe the library version, not the
700 distribution version - e.g., while we don't mind knowing
701 that you're running Redhat version mumble.foo, we must know
702 what kernel version you're running, and it helps if you can
703 tell us what version of the C library you're running,
704 although if you don't know that off the top of your head it
705 may be hard for you to figure it out, so don't go crazy
707 4. The specific version of the DHCP distribution you're
708 running, as reported by dhcpd -t.
709 5. Please explain the problem carefully, thinking through what
710 you're saying to ensure that you don't assume we know
711 something about your situation that we don't know.
712 6. Include your dhcpd.conf and dhcpd.leases file as MIME attachments
713 if they're not over 100 kilobytes in size each. If they are
714 this large, please make them available to us, e.g., via a hidden
715 http:// URL or FTP site. If you're not comfortable releasing
716 this information due to sensitive contents, you may encrypt
717 the file to our release signing key, available on our website.
718 7. Include a log of your server or client running until it
719 encounters the problem - for example, if you are having
720 trouble getting some client to get an address, restart the
721 server with the -d flag and then restart the client, and
722 send us what the server prints. Likewise, with the client,
723 include the output of the client as it fails to get an
724 address or otherwise does the wrong thing. Do not leave
725 out parts of the output that you think aren't interesting.
726 8. If the client or server is dumping core, please run the
727 debugger and get a stack trace, and include that in your
728 bug report. For example, if your debugger is gdb, do the
736 This assumes that it's the dhcp server you're debugging, and
737 that the core file is in dhcpd.core.
739 Please see https://www.isc.org/software/dhcp/ for details on how to subscribe
740 to the ISC DHCP mailing lists.
744 ISC DHCP was originally written by Ted Lemon under a contract with
745 Vixie Labs with the goal of being a complete reference implementation
746 of the DHCP protocol. Funding for this project was provided by
747 Internet Systems Consortium. The first release of the ISC DHCP
748 distribution in December 1997 included just the DHCP server.
749 Release 2 in June 1999 added a DHCP client and a BOOTP/DHCP relay
750 agent. DHCP 3 was released in October 2001 and included DHCP failover
751 support, OMAPI, Dynamic DNS, conditional behaviour, client classing,
752 and more. Version 3 of the DHCP server was funded by Nominum, Inc.
753 The 4.0 release in December 2007 introduced DHCPv6 protocol support
754 for the server and client.
756 This product includes cryptographic software written
757 by Eric Young (eay@cryptsoft.com).