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.4b1.tar.gz
146 tar xvf dhcp-4.3.4b1.tar
150 Now, cd to the dhcp-4.3.4b1 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:
168 A fully-featured implementation of dynamic DNS updates is included in
169 this release. It uses libraries from BIND and, to avoid issues with
170 different versions, includes the necessary BIND version. The appropriate
171 BIND libraries will be compiled and installed in the bind subdirectory
172 as part of the make step. In order to build the necessary libraries you
173 will need to have "gmake" available on your build system.
176 There is documentation for the DDNS support in the dhcpd.conf manual
177 page - see the beginning of this document for information on finding
180 LOCALLY DEFINED OPTIONS
182 In previous versions of the DHCP server there was a mechanism whereby
183 options that were not known by the server could be configured using
184 a name made up of the option code number and an identifier:
185 "option-nnn" This is no longer supported, because it is not future-
186 proof. Instead, if you want to use an option that the server doesn't
187 know about, you must explicitly define it using the method described
188 in the dhcp-options man page under the DEFINING NEW OPTIONS heading.
192 Once you've run configure, just type ``make'', and after a while
193 you should have a dhcp server. If you get compile errors on one
194 of the supported systems mentioned earlier, please let us know.
195 If you get warnings, it's not likely to be a problem - the DHCP
196 server compiles completely warning-free on as many architectures
197 as we can manage, but there are a few for which this is difficult.
198 If you get errors on a system not mentioned above, you will need
199 to do some programming or debugging on your own to get the DHCP
200 Distribution working.
202 If you cross compile you have to follow the instructions from
203 the BIND README, in particular you must set the BUILD_CC
204 environment variable.
206 INSTALLING THE DHCP DISTRIBUTION
208 Once you have successfully gotten the DHCP Distribution to build, you
209 can install it by typing ``make install''. If you already have an old
210 version of the DHCP Distribution installed, you may want to save it
211 before typing ``make install''.
213 USING THE DHCP DISTRIBUTION
217 If you are running the DHCP server or client on a computer that's also
218 acting as a firewall, you must be sure to allow DHCP packets through
219 the firewall. In particular, your firewall rules _must_ allow packets
220 from IP address 0.0.0.0 to IP address 255.255.255.255 from UDP port 68
221 to UDP port 67 through. They must also allow packets from your local
222 firewall's IP address and UDP port 67 through to any address your DHCP
223 server might serve on UDP port 68. Finally, packets from relay agents
224 on port 67 to the DHCP server on port 67, and vice versa, must be
227 We have noticed that on some systems where we are using a packet
228 filter, if you set up a firewall that blocks UDP port 67 and 68
229 entirely, packets sent through the packet filter will not be blocked.
230 However, unicast packets will be blocked. This can result in strange
231 behaviour, particularly on DHCP clients, where the initial packet
232 exchange is broadcast, but renewals are unicast - the client will
233 appear to be unable to renew until it starts broadcasting its
234 renewals, and then suddenly it'll work. The fix is to fix the
235 firewall rules as described above.
239 If you have a server that is connected to two networks, and you only
240 want to provide DHCP service on one of those networks (e.g., you are
241 using a cable modem and have set up a NAT router), if you don't write
242 any subnet declaration for the network you aren't supporting, the DHCP
243 server will ignore input on that network interface if it can. If it
244 can't, it will refuse to run - some operating systems do not have the
245 capability of supporting DHCP on machines with more than one
246 interface, and ironically this is the case even if you don't want to
247 provide DHCP service on one of those interfaces.
251 There are three big LINUX issues: the all-ones broadcast address,
252 Linux 2.1 ip_bootp_agent enabling, and operations with more than one
253 network interface. There are also two potential compilation/runtime
254 problems for Linux 2.1/2.2: the "SO_ATTACH_FILTER undeclared" problem
255 and the "protocol not configured" problem.
257 LINUX: PROTOCOL NOT CONFIGURED
259 If you get the following message, it's because your kernel doesn't
260 have the linux packetfilter or raw packet socket configured:
262 Make sure CONFIG_PACKET (Packet socket) and CONFIG_FILTER (Socket
263 Filtering) are enabled in your kernel configuration
265 If this happens, you need to configure your Linux kernel to support
266 Socket Filtering and the Packet socket, or to select a kernel provided
267 by your Linux distribution that has these enabled (virtually all modern
272 If you are running a recent version of Linux, this won't be a problem,
273 but on older versions of Linux (kernel versions prior to 2.2), there
274 is a potential problem with the broadcast address being sent
277 In order for dhcpd to work correctly with picky DHCP clients (e.g.,
278 Windows 95), it must be able to send packets with an IP destination
279 address of 255.255.255.255. Unfortunately, Linux changes an IP
280 destination of 255.255.255.255 into the local subnet broadcast address
281 (here, that's 192.5.5.223).
283 This isn't generally a problem on Linux 2.2 and later kernels, since
284 we completely bypass the Linux IP stack, but on old versions of Linux
285 2.1 and all versions of Linux prior to 2.1, it is a problem - pickier
286 DHCP clients connected to the same network as the ISC DHCP server or
287 ISC relay agent will not see messages from the DHCP server. It *is*
288 possible to run into trouble with this on Linux 2.2 and later if you
289 are running a version of the DHCP server that was compiled on a Linux
292 It is possible to work around this problem on some versions of Linux
293 by creating a host route from your network interface address to
294 255.255.255.255. The command you need to use to do this on Linux
295 varies from version to version. The easiest version is:
297 route add -host 255.255.255.255 dev eth0
299 On some older Linux systems, you will get an error if you try to do
300 this. On those systems, try adding the following entry to your
303 255.255.255.255 all-ones
307 route add -host all-ones dev eth0
309 Another route that has worked for some users is:
311 route add -net 255.255.255.0 dev eth0
313 If you are not using eth0 as your network interface, you should
314 specify the network interface you *are* using in your route command.
316 LINUX: IP BOOTP AGENT
318 Some versions of the Linux 2.1 kernel apparently prevent dhcpd from
319 working unless you enable it by doing the following:
321 echo 1 >/proc/sys/net/ipv4/ip_bootp_agent
324 LINUX: MULTIPLE INTERFACES
326 Very old versions of the Linux kernel do not provide a networking API
327 that allows dhcpd to operate correctly if the system has more than one
328 broadcast network interface. However, Linux 2.0 kernels with version
329 numbers greater than or equal to 2.0.31 add an API feature: the
330 SO_BINDTODEVICE socket option. If SO_BINDTODEVICE is present, it is
331 possible for dhcpd to operate on Linux with more than one network
332 interface. In order to take advantage of this, you must be running a
333 2.0.31 or greater kernel, and you must have 2.0.31 or later system
334 headers installed *before* you build the DHCP Distribution.
336 We have heard reports that you must still add routes to 255.255.255.255
337 in order for the all-ones broadcast to work, even on 2.0.31 kernels.
338 In fact, you now need to add a route for each interface. Hopefully
339 the Linux kernel gurus will get this straight eventually.
341 Linux 2.1 and later kernels do not use SO_BINDTODEVICE or require the
342 broadcast address hack, but do support multiple interfaces, using the
347 DHCP 4.1 has been tested on OpenWrt 7.09 and 8.09. In keeping with
348 standard practice, client/scripts now includes a dhclient-script file
349 for OpenWrt. However, this is not sufficient by itself to run dhcp on
350 OpenWrt; a full OpenWrt package for DHCP is available at
351 ftp://ftp.isc.org/isc/dhcp/dhcp-4.1.0-openwrt.tar.gz
353 LINUX: 802.1q VLAN INTERFACES
355 If you're using 802.1q vlan interfaces on Linux, it is necessary to
356 vconfig the subinterface(s) to rewrite the 802.1q information out of
357 packets received by the dhcpd daemon via LPF:
359 vconfig set_flag eth1.523 1 1
361 Note that this may affect the performance of your system, since the
362 Linux kernel must rewrite packets received via this interface. For
363 more information, consult the vconfig man pages.
367 ISC DHCP will now work correctly on newer versions of SCO out of the
368 box (tested on OpenServer 5.05b, assumed to work on UnixWare 7).
370 Older versions of SCO have the same problem as Linux (described earlier).
371 The thing is, SCO *really* doesn't want to let you add a host route to
372 the all-ones broadcast address.
374 You can try the following:
376 ifconfig net0 xxx.xxx.xxx.xxx netmask 0xNNNNNNNN broadcast 255.255.255.255
378 If this doesn't work, you can also try the following strange hack:
380 ifconfig net0 alias 10.1.1.1 netmask 8.0.0.0
382 Apparently this works because of an interaction between SCO's support
383 for network classes and the weird netmask. The 10.* network is just a
384 dummy that can generally be assumed to be safe. Don't ask why this
385 works. Just try it. If it works for you, great.
389 HP-UX has the same problem with the all-ones broadcast address that
390 SCO and Linux have. One user reported that adding the following to
391 /etc/rc.config.d/netconf helped (you may have to modify this to suit
392 your local configuration):
394 INTERFACE_NAME[0]=lan0
395 IP_ADDRESS[0]=1.1.1.1
396 SUBNET_MASK[0]=255.255.255.0
397 BROADCAST_ADDRESS[0]="255.255.255.255"
398 LANCONFIG_ARGS[0]="ether"
403 Now that we have Ultrix packet filter support, the DHCP Distribution
404 on Ultrix should be pretty trouble-free. However, one thing you do
405 need to be aware of is that it now requires that the pfilt device be
406 configured into your kernel and present in /dev. If you type ``man
407 packetfilter'', you will get some information on how to configure your
408 kernel for the packet filter (if it isn't already) and how to make an
409 entry for it in /dev.
413 Versions of FreeBSD prior to 2.2 have a bug in BPF support in that the
414 ethernet driver swaps the ethertype field in the ethernet header
415 downstream from BPF, which corrupts the output packet. If you are
416 running a version of FreeBSD prior to 2.2, and you find that dhcpd
417 can't communicate with its clients, you should #define BROKEN_FREEBSD_BPF
418 in site.h and recompile.
420 Modern versions of FreeBSD include the ISC DHCP 3.0 client as part of
421 the base system, and the full distribution (for the DHCP server and
422 relay agent) is available from the Ports Collection in
423 /usr/ports/net/isc-dhcp3, or as a package on FreeBSD installation
428 The NeXTSTEP support uses the NeXTSTEP Berkeley Packet Filter
429 extension, which is not included in the base NextStep system. You
430 must install this extension in order to get dhcpd or dhclient to work.
434 There are two known issues seen when compiling using the Sun compiler.
436 The first is that older Sun compilers generate an error on some of
437 our uses of the flexible array option. Newer versions only generate
438 a warning, which can be safely ignored. If you run into this error
439 ("type of struct member "buf" can not be derived from structure with
440 flexible array member"), upgrade your tools to Oracle Solaris Studio
441 (previously Sun Studio) 12 or something newer.
443 The second is the interaction between the configure script and the
444 makefiles for the Bind libraries. Currently we don't pass all
445 environment variables between the DHCP configure and the Bind configure.
447 If you attempt to specify the compiler you wish to use like this:
449 CC=/opt/SUNWspro/bin/cc ./configure
451 "make" may not build the Bind libraries with that compiler.
453 In order to use the same compiler for Bind and DHCP we suggest the
456 CC=/opt/SUNWspro/bin/cc ./configure
457 CC=/opt/SUNWspro/bin/cc make
461 We have integrated a patch from Oracle to use sockets instead of
462 DLPI on Solaris 11. This functionality was written for use with
463 Solaris Studio 12.2 and requires the system/header package.
465 By default this code is disabled in order to minimize disruptions
466 for current users. In order to enable this code you will need to
467 enable both USE_SOCKETS and USE_V4_PKTINFO as part of the
468 configuration step. The command line would be something like:
470 ./configure --enable-use-sockets --enable-ipv4-pktinfo
474 We have reports that ATF 0.15 and 0.16 do not build on Solaris 11. The
475 following changes to the ATF source code appear to fix this issue:
477 diff -ru atf-0.15/atf-c/tp_test.c atf-0.15-patched/atf-c/tp_test.c
478 --- atf-0.15/atf-c/tp_test.c 2011-12-06 06:31:11.000000000 +0100
479 +++ atf-0.15-patched/atf-c/tp_test.c 2012-06-19 15:54:57.000000000 +0200
489 diff -ru atf-0.15/atf-run/requirements.cpp atf-0.15-patched/atf-run/requirements.cpp
490 --- atf-0.15/atf-run/requirements.cpp 2012-01-13 20:44:25.000000000 +0100
491 +++ atf-0.15-patched/atf-run/requirements.cpp 2012-06-19 15:41:51.000000000 +0200
495 #include <sys/param.h>
496 -#include <sys/sysctl.h>
497 +//#include <sys/sysctl.h>
504 One problem which has been observed and is not fixed in this
505 patchlevel has to do with using DLPI on Solaris machines. The symptom
506 of this problem is that the DHCP server never receives any requests.
507 This has been observed with Solaris 2.6 and Solaris 7 on Intel x86
508 systems, although it may occur with other systems as well. If you
509 encounter this symptom, and you are running the DHCP server on a
510 machine with a single broadcast network interface, you may wish to
511 edit the includes/site.h file and uncomment the #define USE_SOCKETS
512 line. Then type ``make clean; make''. As an alternative workaround,
513 it has been reported that running 'snoop' will cause the dhcp server
514 to start receiving packets. So the practice reported to us is to run
515 snoop at dhcpd startup time, with arguments to cause it to receive one
518 snoop -c 1 udp port 67 > /dev/null &
520 The DHCP client on Solaris will only work with DLPI. If you run it
521 and it just keeps saying it's sending DHCPREQUEST packets, but never
522 gets a response, you may be having DLPI trouble as described above.
523 If so, we have no solution to offer at this time, aside from the above
524 workaround which should also work here. Also, because Solaris requires
525 you to "plumb" an interface before it can be detected by the DHCP client,
526 you must either specify the name(s) of the interface(s) you want to
527 configure on the command line, or must plumb the interfaces prior to
528 invoking the DHCP client. This can be done with ``ifconfig iface plumb'',
529 where iface is the name of the interface (e.g., ``ifconfig hme0 plumb'').
531 It should be noted that Solaris versions from 2.6 onward include a
532 DHCP client that you can run with ``/sbin/ifconfig iface dhcp start''
533 rather than using the ISC DHCP client, including DHCPv6. Consequently,
534 we don't believe there is a need for the client to run on Solaris, and
535 have not engineered the needed DHCPv6 modifications for the dhclient-script.
536 If you feel this is in error, or have a need, please contact us.
540 The AIX support uses the BSD socket API, which cannot differentiate on
541 which network interface a broadcast packet was received; thus the DHCP
542 server and relay will work only on a single interface. (They do work
543 on multi-interface machines if configured to listen on only one of the
546 We have reports of Windows XP clients having difficulty retrieving
547 addresses from a server running on an AIX machine. This issue
548 was traced to the client requiring messages be sent to the all ones
549 broadcast address (255.255.255.255) while the AIX server was sending
552 You may be able to solve this by including a relay between the client
553 and server with the relay configured to use a broadcast of all-ones.
555 A second option that worked for AIX 5.1 but doesn't seem to work for
557 create a host file entry for all-ones (255.255.255.255)
558 and then add a route:
559 route add -host all-ones -interface <local-ip-address>
561 The ISC DHCP distribution does not include a dhclient-script for AIX--
562 AIX comes with a DHCP client. Contribution of a working dhclient-script
563 for AIX would be welcome.
568 The MacOS X system uses a TCP/IP stack derived from FreeBSD with a
569 user-friendly interface named the System Configuration Framework.
570 As it includes a builtin DHCPv4 client (you are better just using that),
571 this text is only about the DHCPv6 client (``dhclient -6 ...''). The DNS
572 configuration (domain search list and name servers' addresses) is managed
573 by a System Configuration agent, not by /etc/resolv.conf (which is a link
574 to /var/run/resolv.conf, which itself only reflects the internal state;
575 the System Configuration framework's Dynamic Store).
577 This means that modifying resolv.conf directly doesn't have the
578 intended effect, instead the macos script sample creates its own
579 resolv.conf.dhclient6 in /var/run, and inserts the contents of this
580 file into the Dynamic Store.
582 When updating the address configuration the System Configuration
583 framework expects the prefix and a default router along with the
584 configured address. As this extra information is not available via
585 the DHCPv6 protocol the System Configuration framework isn't usable
586 for address configuration, instead ifconfig is used directly.
588 Note the Dynamic Store (from which /var/run/resolv.conf is built) is
589 recomputed from scratch when the current location/set is changed.
590 Running the dhclient-script reinstalls the resolv.conf.dhclient6
596 Please see the file DHCP/doc/devel/atf.dox for a description of building
597 and using these tools.
599 The optional unit tests use ATF (Automated Testing Framework) including
600 the atf-run and atf-report tools. ATF deprecated these tools in
601 version 0.19 and removed these tools from its sources in version 0.20,
602 requiring you to get an older version, use Kyua with an ATF compatibility
603 package or use the version included in the Bind sources.
607 The Internet Systems Consortium DHCP server is developed and distributed
608 by ISC in the public trust, thanks to the generous donations of its
609 sponsors. ISC now also offers commercial quality support contracts for
610 ISC DHCP, more information about ISC Support Contracts can be found at
613 https://www.isc.org/services/support/
615 Please understand that we may not respond to support inquiries unless
616 you have a support contract. ISC will continue its practice of always
617 responding to critical items that effect the entire community, and
618 responding to all other requests for support upon ISC's mailing lists
619 on a best-effort basis.
621 However, ISC DHCP has attracted a fairly sizable following on the
622 Internet, which means that there are a lot of knowledgeable users who
623 may be able to help you if you get stuck. These people generally
624 read the dhcp-users@isc.org mailing list. Be sure to provide as much
625 detail in your query as possible.
627 If you are going to use ISC DHCP, you should probably subscribe to
628 the dhcp-users or dhcp-announce mailing lists.
630 WHERE TO SEND FEATURE REQUESTS: We like to hear your feedback. We may
631 not respond to it all the time, but we do read it. If ISC DHCP doesn't
632 work well for you, or you have an idea that would improve it for your
633 use, please send your suggestion to dhcp-suggest@isc.org. This is also
634 an excellent place to send patches that add new features.
636 WHERE TO REPORT BUGS: If you want the act of sending in a bug report
637 to result in you getting help in the form of a fixed piece of
638 software, you are asking for help. Your bug report is helpful to us,
639 but fundamentally you are making a support request, so please use the
640 addresses described in the previous paragraphs. If you are _sure_ that
641 your problem is a bug, and not user error, or if your bug report
642 includes a patch, you can send it to our ticketing system at
643 dhcp-bugs@isc.org. If you have not received a notice that the ticket
644 has been resolved, then we're still working on it.
646 PLEASE DO NOT REPORT BUGS IN OLD SOFTWARE RELEASES! Fetch the latest
647 release and see if the bug is still in that version of the software,
648 and if it is still present, _then_ report it. ISC release versions
649 always have three numbers, for example: 1.2.3. The 'major release' is
650 1 here, the 'minor release' is 2, and the 'maintenance release' is 3.
651 ISC will accept bug reports against the most recent two major.minor
652 releases: for example, 1.0.0 and 0.9.0, but not 0.8.* or prior.
654 PLEASE take a moment to determine where the ISC DHCP distribution
655 that you're using came from. ISC DHCP is sometimes heavily modified
656 by integrators in various operating systems - it's not that we
657 feel that our software is perfect and incapable of having bugs, but
658 rather that it is very frustrating to find out after many days trying
659 to help someone that the sources you're looking at aren't what they're
660 running. When in doubt, please retrieve the source distribution from
661 ISC's web page and install it.
663 HOW TO REPORT BUGS OR REQUEST HELP
665 When you report bugs or ask for help, please provide us complete
666 information. A list of information we need follows. Please read it
667 carefully, and put all the information you can into your initial bug
668 report. This will save us a great deal of time and more informative
669 bug reports are more likely to get handled more quickly overall.
671 1. The specific operating system name and version of the
672 machine on which the DHCP server or client is running.
673 2. The specific operating system name and version of the
674 machine on which the client is running, if you are having
675 trouble getting a client working with the server.
676 3. If you're running Linux, the version number we care about is
677 the kernel version and maybe the library version, not the
678 distribution version - e.g., while we don't mind knowing
679 that you're running Redhat version mumble.foo, we must know
680 what kernel version you're running, and it helps if you can
681 tell us what version of the C library you're running,
682 although if you don't know that off the top of your head it
683 may be hard for you to figure it out, so don't go crazy
685 4. The specific version of the DHCP distribution you're
686 running, as reported by dhcpd -t.
687 5. Please explain the problem carefully, thinking through what
688 you're saying to ensure that you don't assume we know
689 something about your situation that we don't know.
690 6. Include your dhcpd.conf and dhcpd.leases file as MIME attachments
691 if they're not over 100 kilobytes in size each. If they are
692 this large, please make them available to us eg via a hidden
693 http:// URL or FTP site. If you're not comfortable releasing
694 this information due to sensitive contents, you may encrypt
695 the file to our release signing key, available on our website.
696 7. Include a log of your server or client running until it
697 encounters the problem - for example, if you are having
698 trouble getting some client to get an address, restart the
699 server with the -d flag and then restart the client, and
700 send us what the server prints. Likewise, with the client,
701 include the output of the client as it fails to get an
702 address or otherwise does the wrong thing. Do not leave
703 out parts of the output that you think aren't interesting.
704 8. If the client or server is dumping core, please run the
705 debugger and get a stack trace, and include that in your
706 bug report. For example, if your debugger is gdb, do the
714 This assumes that it's the dhcp server you're debugging, and
715 that the core file is in dhcpd.core.
717 Please see https://www.isc.org/software/dhcp/ for details on how to subscribe
718 to the ISC DHCP mailing lists.
722 ISC DHCP was originally written by Ted Lemon under a contract with
723 Vixie Labs with the goal of being a complete reference implementation
724 of the DHCP protocol. Funding for this project was provided by
725 Internet Systems Consortium. The first release of the ISC DHCP
726 distribution in December 1997 included just the DHCP server.
727 Release 2 in June 1999 added a DHCP client and a BOOTP/DHCP relay
728 agent. DHCP 3 was released in October 2001 and included DHCP failover
729 support, OMAPI, Dynamic DNS, conditional behaviour, client classing,
730 and more. Version 3 of the DHCP server was funded by Nominum, Inc.
731 The 4.0 release in December 2007 introduced DHCPv6 protocol support
732 for the server and client.
734 This product includes cryptographic software written
735 by Eric Young (eay@cryptsoft.com).