NameDateSize

..16-Mar-201612 KiB

client/10-Sep-20154 KiB

common/10-Sep-20154 KiB

configure.ac10-Sep-201525.4 KiB

contrib/26-May-20144 KiB

debian/12-Oct-20154 KiB

dhcpctl/12-May-20154 KiB

doc/26-May-20144 KiB

includes/10-Sep-20154 KiB

LICENSE12-May-20151 KiB

Makefile.am10-Sep-20151.4 KiB

omapip/12-May-20154 KiB

README10-Sep-201530.8 KiB

relay/12-May-20154 KiB

RELNOTES10-Sep-2015169 KiB

server/10-Sep-20154 KiB

tests/12-May-20154 KiB

util/10-Sep-20154 KiB

README

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