Home | History | Annotate | Line # | Download | only in dist
README revision 1.1.1.2
      1      1.1  christos 	      Internet Systems Consortium DHCP Distribution
      2  1.1.1.2  christos 			     Version 4.4.2
      3  1.1.1.2  christos 			    22 January 2020
      4      1.1  christos 
      5      1.1  christos 			      README FILE
      6      1.1  christos 
      7      1.1  christos You should read this file carefully before trying to install or use
      8      1.1  christos the ISC DHCP Distribution.
      9      1.1  christos 
     10      1.1  christos 			  TABLE OF CONTENTS
     11      1.1  christos 
     12      1.1  christos 	1	WHERE TO FIND DOCUMENTATION
     13      1.1  christos 	2	RELEASE STATUS
     14      1.1  christos 	3	BUILDING THE DHCP DISTRIBUTION
     15      1.1  christos 	 3.1	 UNPACKING IT
     16      1.1  christos 	 3.2	 CONFIGURING IT
     17      1.1  christos 	  3.2.1	  DYNAMIC DNS UPDATES
     18      1.1  christos 	  3.2.2   LOCALLY DEFINED OPTIONS
     19      1.1  christos 	 3.3	 BUILDING IT
     20      1.1  christos 	4	INSTALLING THE DHCP DISTRIBUTION
     21      1.1  christos 	5	USING THE DHCP DISTRIBUTION
     22      1.1  christos 	 5.1	  FIREWALL RULES
     23      1.1  christos 	 5.2	 LINUX
     24      1.1  christos 	  5.2.1	  IF_TR.H NOT FOUND
     25      1.1  christos 	  5.2.2	  SO_ATTACH_FILTER UNDECLARED
     26      1.1  christos 	  5.2.3	  PROTOCOL NOT CONFIGURED
     27      1.1  christos 	  5.2.4	  BROADCAST
     28      1.1  christos 	  5.2.6	  IP BOOTP AGENT
     29      1.1  christos 	  5.2.7	  MULTIPLE INTERFACES
     30  1.1.1.2  christos      5.3    ATF
     31      1.1  christos 	6	SUPPORT
     32      1.1  christos 	 6.1	 HOW TO REPORT BUGS
     33      1.1  christos 	7	HISTORY
     34      1.1  christos 
     35      1.1  christos 		      WHERE TO FIND DOCUMENTATION
     36      1.1  christos 
     37      1.1  christos Documentation for this software includes this README file, the
     38      1.1  christos RELNOTES file, and the manual pages, which are in the server, common,
     39      1.1  christos client and relay subdirectories.  The README file (this file) includes
     40      1.1  christos late-breaking operational and system-specific information that you
     41      1.1  christos should read even if you don't want to read the manual pages, and that
     42      1.1  christos you should *certainly* read if you run into trouble.  Internet
     43      1.1  christos standards relating to the DHCP protocol are listed in the References
     44      1.1  christos document that is available in html, txt and xml formats in doc/
     45      1.1  christos subdirectory.  You will have the best luck reading the manual pages if
     46      1.1  christos you build this software and then install it, although you can read
     47      1.1  christos them directly out of the distribution if you need to.
     48      1.1  christos 
     49      1.1  christos DHCP server documentation is in the dhcpd man page.  Information about
     50      1.1  christos the DHCP server lease database is in the dhcpd.leases man page.
     51      1.1  christos Server configuration documentation is in the dhcpd.conf man page as
     52      1.1  christos well as the dhcp-options man page.   A sample DHCP server
     53      1.1  christos configuration is in the file server/dhcpd.conf.example.   The source for
     54      1.1  christos the dhcpd, dhcpd.leases and dhcpd.conf man pages is in the server/ sub-
     55      1.1  christos directory in the distribution.   The source for the dhcp-options.5
     56      1.1  christos man page is in the common/ subdirectory.
     57      1.1  christos 
     58      1.1  christos DHCP Client documentation is in the dhclient man page.  DHCP client
     59      1.1  christos configuration documentation is in the dhclient.conf man page and the
     60      1.1  christos dhcp-options man page.  The DHCP client configuration script is
     61      1.1  christos documented in the dhclient-script man page.   The format of the DHCP
     62      1.1  christos client lease database is documented in the dhclient.leases man page.
     63      1.1  christos The source for all these man pages is in the client/ subdirectory in
     64      1.1  christos the distribution.   In addition, the dhcp-options man page should be
     65      1.1  christos referred to for information about DHCP options.
     66      1.1  christos 
     67      1.1  christos DHCP relay agent documentation is in the dhcrelay man page, the source
     68      1.1  christos for which is distributed in the relay/ subdirectory.
     69      1.1  christos 
     70  1.1.1.2  christos KEA Migration Assistant documentation, including how to build, install
     71  1.1.1.2  christos and use it, is including in the keama directory.
     72  1.1.1.2  christos 
     73      1.1  christos To read installed manual pages, use the man command.  Type "man page"
     74      1.1  christos where page is the name of the manual page.   This will only work if
     75      1.1  christos you have installed the ISC DHCP distribution using the ``make install''
     76      1.1  christos command (described later).
     77      1.1  christos 
     78      1.1  christos If you want to read manual pages that aren't installed, you can type
     79      1.1  christos ``nroff -man page |more'' where page is the filename of the
     80      1.1  christos unformatted manual page.  The filename of an unformatted manual page
     81      1.1  christos is the name of the manual page, followed by '.', followed by some
     82      1.1  christos number - 5 for documentation about files, and 8 for documentation
     83      1.1  christos about programs.   For example, to read the dhcp-options man page,
     84      1.1  christos you would type ``nroff -man common/dhcp-options.5 |more'', assuming
     85      1.1  christos your current working directory is the top level directory of the ISC
     86      1.1  christos DHCP Distribution.
     87      1.1  christos 
     88      1.1  christos Please note that the pathnames of files to which our manpages refer
     89      1.1  christos will not be correct for your operating system until after you iterate
     90      1.1  christos 'make install' (so if you're reading a manpage out of the source
     91      1.1  christos directory, it may not have up-to-date information).
     92      1.1  christos 
     93      1.1  christos 		    BUILDING THE DHCP DISTRIBUTION
     94      1.1  christos 
     95      1.1  christos 			     UNPACKING IT
     96      1.1  christos 
     97      1.1  christos To build the DHCP Distribution, unpack the compressed tar file using
     98      1.1  christos the tar utility and the gzip command - type something like:
     99      1.1  christos 
    100  1.1.1.2  christos 	gunzip dhcp-4.4.2.tar.gz
    101  1.1.1.2  christos 	tar xvf dhcp-4.4.2.tar
    102      1.1  christos 
    103      1.1  christos 			    CONFIGURING IT
    104      1.1  christos 
    105  1.1.1.2  christos Now, cd to the dhcp-4.4.2 subdirectory that you've just created and
    106      1.1  christos configure the source tree by typing:
    107      1.1  christos 
    108      1.1  christos 	./configure
    109      1.1  christos 
    110      1.1  christos If the configure utility can figure out what sort of system you're
    111      1.1  christos running on, it will create a custom Makefile for you for that
    112      1.1  christos system; otherwise, it will complain.  If it can't figure out what
    113      1.1  christos system you are using, that system is not supported - you are on
    114      1.1  christos your own.
    115      1.1  christos 
    116      1.1  christos Several options may be enabled or disabled via the configure command.
    117      1.1  christos You can get a list of these by typing:
    118      1.1  christos 
    119      1.1  christos 	./configure --help
    120      1.1  christos 
    121      1.1  christos If you want to use dynamic shared libraries automake, autoconf
    122      1.1  christos (aka GNU autotools) and libtool must be available. The DHCP
    123      1.1  christos distribution provides 3 configure.ac* files: the -lt version
    124      1.1  christos has no libtool support and was copied to the configure.ac
    125      1.1  christos standard file in the distribution. To enable libtool support
    126      1.1  christos you should perform these steps:
    127      1.1  christos 
    128      1.1  christos 	cp configure.ac+lt configure.ac
    129      1.1  christos 	autoreconf -i
    130      1.1  christos 
    131      1.1  christos after you can use the regenerated configure as usual
    132      1.1  christos (with libtool support (--enable-libtool) on by default):
    133      1.1  christos 
    134      1.1  christos 	./configure
    135      1.1  christos 
    136      1.1  christos For compatibility (and people who don't read this documentation)
    137      1.1  christos the --enable-libtool configuration file is supported even by
    138      1.1  christos the distributed configure (and off by default). The previous
    139      1.1  christos steps are performed and the regenerated configure called with
    140      1.1  christos almost the same parameters (this "almost" makes the use of
    141      1.1  christos this feature not recommended).
    142      1.1  christos 
    143      1.1  christos Note you can't go back from with libtool support to without libtool
    144      1.1  christos support by restoring configure.ac and rerun autoreconf. If you
    145      1.1  christos want or need to restore the without libtool support state the
    146      1.1  christos required way is to simply restore the whole distribution.
    147      1.1  christos 
    148      1.1  christos 			 DYNAMIC DNS UPDATES
    149      1.1  christos 
    150      1.1  christos A fully-featured implementation of dynamic DNS updates is included in
    151      1.1  christos this release.  It uses libraries from BIND and, to avoid issues with
    152      1.1  christos different versions, includes the necessary BIND version.  The appropriate
    153      1.1  christos BIND libraries will be compiled and installed in the bind subdirectory
    154      1.1  christos as part of the make step.  In order to build the necessary libraries you
    155      1.1  christos will need to have "gmake" available on your build system.
    156      1.1  christos 
    157      1.1  christos 
    158      1.1  christos There is documentation for the DDNS support in the dhcpd.conf manual
    159      1.1  christos page - see the beginning of this document for information on finding
    160      1.1  christos manual pages.
    161      1.1  christos 
    162      1.1  christos 		       LOCALLY DEFINED OPTIONS
    163      1.1  christos 
    164      1.1  christos In previous versions of the DHCP server there was a mechanism whereby
    165      1.1  christos options that were not known by the server could be configured using
    166      1.1  christos a name made up of the option code number and an identifier:
    167      1.1  christos "option-nnn"   This is no longer supported, because it is not future-
    168      1.1  christos proof.   Instead, if you want to use an option that the server doesn't
    169      1.1  christos know about, you must explicitly define it using the method described
    170      1.1  christos in the dhcp-options man page under the DEFINING NEW OPTIONS heading.
    171      1.1  christos 
    172      1.1  christos 			     BUILDING IT
    173      1.1  christos 
    174      1.1  christos Once you've run configure, just type ``make'', and after a while
    175      1.1  christos you should have a dhcp server.  If you get compile errors on one
    176      1.1  christos of the supported systems mentioned earlier, please let us know.
    177      1.1  christos If you get warnings, it's not likely to be a problem - the DHCP
    178      1.1  christos server compiles completely warning-free on as many architectures
    179      1.1  christos as we can manage, but there are a few for which this is difficult.
    180      1.1  christos If you get errors on a system not mentioned above, you will need
    181      1.1  christos to do some programming or debugging on your own to get the DHCP
    182      1.1  christos Distribution working.
    183      1.1  christos 
    184      1.1  christos If you cross compile you have to follow the instructions from
    185      1.1  christos the BIND README, in particular you must set the BUILD_CC
    186      1.1  christos environment variable.
    187      1.1  christos 
    188      1.1  christos 		   INSTALLING THE DHCP DISTRIBUTION
    189      1.1  christos 
    190      1.1  christos Once you have successfully gotten the DHCP Distribution to build, you
    191      1.1  christos can install it by typing ``make install''.   If you already have an old
    192      1.1  christos version of the DHCP Distribution installed, you may want to save it
    193      1.1  christos before typing ``make install''.
    194      1.1  christos 
    195      1.1  christos 		     USING THE DHCP DISTRIBUTION
    196      1.1  christos 
    197      1.1  christos 			    FIREWALL RULES
    198      1.1  christos 
    199      1.1  christos If you are running the DHCP server or client on a computer that's also
    200      1.1  christos acting as a firewall, you must be sure to allow DHCP packets through
    201      1.1  christos the firewall.  In particular, your firewall rules _must_ allow packets
    202      1.1  christos from IP address 0.0.0.0 to IP address 255.255.255.255 from UDP port 68
    203      1.1  christos to UDP port 67 through.  They must also allow packets from your local
    204      1.1  christos firewall's IP address and UDP port 67 through to any address your DHCP
    205      1.1  christos server might serve on UDP port 68.  Finally, packets from relay agents
    206      1.1  christos on port 67 to the DHCP server on port 67, and vice versa, must be
    207      1.1  christos permitted.
    208      1.1  christos 
    209      1.1  christos We have noticed that on some systems where we are using a packet
    210      1.1  christos filter, if you set up a firewall that blocks UDP port 67 and 68
    211      1.1  christos entirely, packets sent through the packet filter will not be blocked.
    212      1.1  christos However, unicast packets will be blocked.   This can result in strange
    213      1.1  christos behaviour, particularly on DHCP clients, where the initial packet
    214      1.1  christos exchange is broadcast, but renewals are unicast - the client will
    215      1.1  christos appear to be unable to renew until it starts broadcasting its
    216      1.1  christos renewals, and then suddenly it'll work.   The fix is to fix the
    217      1.1  christos firewall rules as described above.
    218      1.1  christos 
    219      1.1  christos 			   PARTIAL SERVERS
    220      1.1  christos 
    221      1.1  christos If you have a server that is connected to two networks, and you only
    222      1.1  christos want to provide DHCP service on one of those networks (e.g., you are
    223      1.1  christos using a cable modem and have set up a NAT router), if you don't write
    224      1.1  christos any subnet declaration for the network you aren't supporting, the DHCP
    225      1.1  christos server will ignore input on that network interface if it can.  If it
    226      1.1  christos can't, it will refuse to run - some operating systems do not have the
    227      1.1  christos capability of supporting DHCP on machines with more than one
    228      1.1  christos interface, and ironically this is the case even if you don't want to
    229      1.1  christos provide DHCP service on one of those interfaces.
    230      1.1  christos 
    231      1.1  christos 				LINUX
    232      1.1  christos 
    233      1.1  christos There are three big LINUX issues: the all-ones broadcast address,
    234      1.1  christos Linux 2.1 ip_bootp_agent enabling, and operations with more than one
    235      1.1  christos network interface.   There are also two potential compilation/runtime
    236      1.1  christos problems for Linux 2.1/2.2: the "SO_ATTACH_FILTER undeclared" problem
    237      1.1  christos and the "protocol not configured" problem.
    238      1.1  christos 
    239      1.1  christos 		    LINUX: PROTOCOL NOT CONFIGURED
    240      1.1  christos 
    241      1.1  christos If you get the following message, it's because your kernel doesn't
    242      1.1  christos have the Linux packetfilter or raw packet socket configured:
    243      1.1  christos 
    244      1.1  christos  Make sure CONFIG_PACKET (Packet socket) and CONFIG_FILTER (Socket
    245      1.1  christos  Filtering) are enabled in your kernel configuration
    246      1.1  christos 
    247      1.1  christos If this happens, you need to configure your Linux kernel to support
    248      1.1  christos Socket Filtering and the Packet socket, or to select a kernel provided
    249      1.1  christos by your Linux distribution that has these enabled (virtually all modern
    250      1.1  christos ones do by default).
    251      1.1  christos 
    252      1.1  christos 			   LINUX: BROADCAST
    253      1.1  christos 
    254      1.1  christos If you are running a recent version of Linux, this won't be a problem,
    255      1.1  christos but on older versions of Linux (kernel versions prior to 2.2), there
    256      1.1  christos is a potential problem with the broadcast address being sent
    257      1.1  christos incorrectly.
    258      1.1  christos 
    259      1.1  christos In order for dhcpd to work correctly with picky DHCP clients (e.g.,
    260      1.1  christos Windows 95), it must be able to send packets with an IP destination
    261      1.1  christos address of 255.255.255.255.  Unfortunately, Linux changes an IP
    262      1.1  christos destination of 255.255.255.255 into the local subnet broadcast address
    263      1.1  christos (here, that's 192.5.5.223).
    264      1.1  christos 
    265      1.1  christos This isn't generally a problem on Linux 2.2 and later kernels, since
    266      1.1  christos we completely bypass the Linux IP stack, but on old versions of Linux
    267      1.1  christos 2.1 and all versions of Linux prior to 2.1, it is a problem - pickier
    268      1.1  christos DHCP clients connected to the same network as the ISC DHCP server or
    269      1.1  christos ISC relay agent will not see messages from the DHCP server.   It *is*
    270      1.1  christos possible to run into trouble with this on Linux 2.2 and later if you
    271      1.1  christos are running a version of the DHCP server that was compiled on a Linux
    272      1.1  christos 2.0 system, though.
    273      1.1  christos 
    274      1.1  christos It is possible to work around this problem on some versions of Linux
    275      1.1  christos by creating a host route from your network interface address to
    276      1.1  christos 255.255.255.255.   The command you need to use to do this on Linux
    277      1.1  christos varies from version to version.   The easiest version is:
    278      1.1  christos 
    279      1.1  christos 	route add -host 255.255.255.255 dev eth0
    280      1.1  christos 
    281      1.1  christos On some older Linux systems, you will get an error if you try to do
    282      1.1  christos this.   On those systems, try adding the following entry to your
    283      1.1  christos /etc/hosts file:
    284      1.1  christos 
    285      1.1  christos 255.255.255.255	all-ones
    286      1.1  christos 
    287      1.1  christos Then, try:
    288      1.1  christos 
    289      1.1  christos 	route add -host all-ones dev eth0
    290      1.1  christos 
    291      1.1  christos Another route that has worked for some users is:
    292      1.1  christos 
    293      1.1  christos 	route add -net 255.255.255.0 dev eth0
    294      1.1  christos 
    295      1.1  christos If you are not using eth0 as your network interface, you should
    296      1.1  christos specify the network interface you *are* using in your route command.
    297      1.1  christos 
    298      1.1  christos 			LINUX: IP BOOTP AGENT
    299      1.1  christos 
    300      1.1  christos Some versions of the Linux 2.1 kernel apparently prevent dhcpd from
    301      1.1  christos working unless you enable it by doing the following:
    302      1.1  christos 
    303      1.1  christos 	      echo 1 >/proc/sys/net/ipv4/ip_bootp_agent
    304      1.1  christos 
    305      1.1  christos 
    306      1.1  christos 		      LINUX: MULTIPLE INTERFACES
    307      1.1  christos 
    308      1.1  christos Very old versions of the Linux kernel do not provide a networking API
    309      1.1  christos that allows dhcpd to operate correctly if the system has more than one
    310      1.1  christos broadcast network interface.  However, Linux 2.0 kernels with version
    311      1.1  christos numbers greater than or equal to 2.0.31 add an API feature: the
    312      1.1  christos SO_BINDTODEVICE socket option.  If SO_BINDTODEVICE is present, it is
    313      1.1  christos possible for dhcpd to operate on Linux with more than one network
    314      1.1  christos interface.  In order to take advantage of this, you must be running a
    315      1.1  christos 2.0.31 or greater kernel, and you must have 2.0.31 or later system
    316      1.1  christos headers installed *before* you build the DHCP Distribution.
    317      1.1  christos 
    318      1.1  christos We have heard reports that you must still add routes to 255.255.255.255
    319      1.1  christos in order for the all-ones broadcast to work, even on 2.0.31 kernels.
    320      1.1  christos In fact, you now need to add a route for each interface.   Hopefully
    321      1.1  christos the Linux kernel gurus will get this straight eventually.
    322      1.1  christos 
    323      1.1  christos Linux 2.1 and later kernels do not use SO_BINDTODEVICE or require the
    324      1.1  christos broadcast address hack, but do support multiple interfaces, using the
    325      1.1  christos Linux Packet Filter.
    326      1.1  christos 
    327      1.1  christos 			     LINUX: OpenWrt
    328      1.1  christos 
    329      1.1  christos DHCP 4.1 has been tested on OpenWrt 7.09 and 8.09.  In keeping with
    330      1.1  christos standard practice, client/scripts now includes a dhclient-script file
    331      1.1  christos for OpenWrt.  However, this is not sufficient by itself to run dhcp on
    332      1.1  christos OpenWrt; a full OpenWrt package for DHCP is available at
    333      1.1  christos ftp://ftp.isc.org/isc/dhcp/dhcp-4.1.0-openwrt.tar.gz
    334      1.1  christos 
    335      1.1  christos 		    LINUX: 802.1q VLAN INTERFACES
    336      1.1  christos 
    337      1.1  christos If you're using 802.1q vlan interfaces on Linux, it is necessary to
    338      1.1  christos vconfig the subinterface(s) to rewrite the 802.1q information out of
    339      1.1  christos packets received by the dhcpd daemon via LPF:
    340      1.1  christos 
    341      1.1  christos 	vconfig set_flag eth1.523 1 1
    342      1.1  christos 
    343      1.1  christos Note that this may affect the performance of your system, since the
    344      1.1  christos Linux kernel must rewrite packets received via this interface.  For
    345      1.1  christos more information, consult the vconfig man pages.
    346      1.1  christos 
    347      1.1  christos 
    348      1.1  christos 			       ATF
    349      1.1  christos 
    350      1.1  christos Please see the file DHCP/doc/devel/atf.dox for a description of building
    351      1.1  christos and using these tools.  
    352      1.1  christos 
    353      1.1  christos The optional unit tests use ATF (Automated Testing Framework) including
    354      1.1  christos the atf-run and atf-report tools. ATF deprecated these tools in
    355      1.1  christos version 0.19 and removed these tools from its sources in version 0.20,
    356      1.1  christos requiring you to get an older version, use Kyua with an ATF compatibility
    357      1.1  christos package or use the version included in the Bind sources.
    358      1.1  christos 
    359      1.1  christos 			       SUPPORT
    360      1.1  christos 
    361      1.1  christos The Internet Systems Consortium DHCP server is developed and distributed
    362      1.1  christos by ISC in the public trust, thanks to the generous donations of its
    363      1.1  christos sponsors.  ISC now also offers commercial quality support contracts for
    364      1.1  christos ISC DHCP, more information about ISC Support Contracts can be found at
    365      1.1  christos the following URL:
    366      1.1  christos 
    367  1.1.1.2  christos 	https://www.isc.org/support/
    368      1.1  christos 
    369      1.1  christos Please understand that we may not respond to support inquiries unless
    370      1.1  christos you have a support contract.  ISC will continue its practice of always
    371      1.1  christos responding to critical items that effect the entire community, and
    372      1.1  christos responding to all other requests for support upon ISC's mailing lists
    373      1.1  christos on a best-effort basis.
    374      1.1  christos 
    375      1.1  christos However, ISC DHCP has attracted a fairly sizable following on the
    376      1.1  christos Internet, which means that there are a lot of knowledgeable users who
    377      1.1  christos may be able to help you if you get stuck.  These people generally
    378      1.1  christos read the dhcp-users (a] isc.org mailing list.  Be sure to provide as much
    379      1.1  christos detail in your query as possible.
    380      1.1  christos 
    381      1.1  christos If you are going to use ISC DHCP, you should probably subscribe to
    382      1.1  christos the dhcp-users or dhcp-announce mailing lists.
    383      1.1  christos 
    384      1.1  christos WHERE TO SEND FEATURE REQUESTS: We like to hear your feedback.  We may
    385      1.1  christos not respond to it all the time, but we do read it.  If ISC DHCP doesn't
    386      1.1  christos work well for you, or you have an idea that would improve it for your
    387  1.1.1.2  christos use, please create an issue at https://gitlab.isc.org/isc-projects/dhcp/issues.  
    388  1.1.1.2  christos This is also an excellent place to send patches that add new features.
    389      1.1  christos 
    390      1.1  christos WHERE TO REPORT BUGS: If you want the act of sending in a bug report
    391      1.1  christos to result in you getting help in the form of a fixed piece of
    392      1.1  christos software, you are asking for help.  Your bug report is helpful to us,
    393      1.1  christos but fundamentally you are making a support request, so please use the
    394      1.1  christos addresses described in the previous paragraphs.  If you are _sure_ that
    395      1.1  christos your problem is a bug, and not user error, or if your bug report
    396  1.1.1.2  christos includes a patch, you can submit it to our ticketing system at 
    397  1.1.1.2  christos https://gitlab.isc.org/isc-projects/dhcp/issues.  If you have not received 
    398  1.1.1.2  christos a notice that the ticket has been resolved, then we're still working on it.
    399      1.1  christos 
    400      1.1  christos PLEASE DO NOT REPORT BUGS IN OLD SOFTWARE RELEASES!  Fetch the latest
    401      1.1  christos release and see if the bug is still in that version of the software,
    402      1.1  christos and if it is still present, _then_ report it.  ISC release versions 
    403      1.1  christos always have three numbers, for example: 1.2.3.  The 'major release' is 
    404      1.1  christos 1 here, the 'minor release' is 2, and the 'maintenance release' is 3.  
    405      1.1  christos ISC will accept bug reports against the most recent two major.minor
    406      1.1  christos releases: for example, 1.0.0 and 0.9.0, but not 0.8.* or prior.
    407      1.1  christos 
    408      1.1  christos PLEASE take a moment to determine where the ISC DHCP distribution
    409      1.1  christos that you're using came from.  ISC DHCP is sometimes heavily modified
    410      1.1  christos by integrators in various operating systems - it's not that we
    411      1.1  christos feel that our software is perfect and incapable of having bugs, but
    412      1.1  christos rather that it is very frustrating to find out after many days trying
    413      1.1  christos to help someone that the sources you're looking at aren't what they're
    414      1.1  christos running.  When in doubt, please retrieve the source distribution from
    415      1.1  christos ISC's web page and install it.
    416      1.1  christos 
    417      1.1  christos 		HOW TO REPORT BUGS OR REQUEST HELP
    418      1.1  christos 
    419      1.1  christos When you report bugs or ask for help, please provide us complete
    420      1.1  christos information.  A list of information we need follows.  Please read it
    421      1.1  christos carefully, and put all the information you can into your initial bug
    422      1.1  christos report.  This will save us a great deal of time and more informative
    423      1.1  christos bug reports are more likely to get handled more quickly overall.
    424      1.1  christos 
    425      1.1  christos       1.  The specific operating system name and version of the
    426      1.1  christos 	  machine on which the DHCP server or client is running.
    427      1.1  christos       2.  The specific operating system name and version of the
    428      1.1  christos 	  machine on which the client is running, if you are having
    429      1.1  christos 	  trouble getting a client working with the server.
    430      1.1  christos       3.  If you're running Linux, the version number we care about is
    431      1.1  christos 	  the kernel version and maybe the library version, not the
    432      1.1  christos 	  distribution version - e.g., while we don't mind knowing
    433      1.1  christos 	  that you're running Redhat version mumble.foo, we must know
    434      1.1  christos 	  what kernel version you're running, and it helps if you can
    435      1.1  christos 	  tell us what version of the C library you're running,
    436      1.1  christos 	  although if you don't know that off the top of your head it
    437      1.1  christos 	  may be hard for you to figure it out, so don't go crazy
    438      1.1  christos 	  trying.
    439      1.1  christos       4.  The specific version of the DHCP distribution you're
    440      1.1  christos 	  running, as reported by dhcpd -t.
    441      1.1  christos       5.  Please explain the problem carefully, thinking through what
    442      1.1  christos 	  you're saying to ensure that you don't assume we know
    443      1.1  christos 	  something about your situation that we don't know.
    444      1.1  christos       6.  Include your dhcpd.conf and dhcpd.leases file as MIME attachments
    445      1.1  christos 	  if they're not over 100 kilobytes in size each.  If they are
    446      1.1  christos 	  this large, please make them available to us, e.g., via a hidden
    447      1.1  christos 	  http:// URL or FTP site.  If you're not comfortable releasing
    448      1.1  christos 	  this information due to sensitive contents, you may encrypt
    449      1.1  christos 	  the file to our release signing key, available on our website.
    450      1.1  christos       7.  Include a log of your server or client running until it
    451      1.1  christos 	  encounters the problem - for example, if you are having
    452      1.1  christos 	  trouble getting some client to get an address, restart the
    453      1.1  christos 	  server with the -d flag and then restart the client, and
    454      1.1  christos 	  send us what the server prints.   Likewise, with the client,
    455      1.1  christos 	  include the output of the client as it fails to get an
    456      1.1  christos 	  address or otherwise does the wrong thing.   Do not leave
    457      1.1  christos 	  out parts of the output that you think aren't interesting.
    458      1.1  christos       8.  If the client or server is dumping core, please run the
    459      1.1  christos 	  debugger and get a stack trace, and include that in your
    460      1.1  christos 	  bug report.   For example, if your debugger is gdb, do the
    461      1.1  christos 	  following:
    462      1.1  christos 
    463      1.1  christos 		gdb dhcpd dhcpd.core
    464      1.1  christos 		(gdb) where
    465      1.1  christos 		      [...]
    466      1.1  christos 		(gdb) quit
    467      1.1  christos 
    468      1.1  christos 	  This assumes that it's the dhcp server you're debugging, and
    469      1.1  christos 	  that the core file is in dhcpd.core.
    470      1.1  christos 
    471  1.1.1.2  christos Please see https://www.isc.org/dhcp/ for details on how to subscribe
    472      1.1  christos to the ISC DHCP mailing lists.
    473      1.1  christos 
    474      1.1  christos 			       HISTORY
    475      1.1  christos 
    476      1.1  christos ISC DHCP was originally written by Ted Lemon under a contract with
    477      1.1  christos Vixie Labs with the goal of being a complete reference implementation
    478      1.1  christos of the DHCP protocol.  Funding for this project was provided by
    479      1.1  christos Internet Systems Consortium. The first release of the ISC DHCP
    480      1.1  christos distribution in December 1997 included just the DHCP server.
    481      1.1  christos Release 2 in June 1999 added a DHCP client and a BOOTP/DHCP relay
    482      1.1  christos agent. DHCP 3 was released in October 2001 and included DHCP failover
    483      1.1  christos support, OMAPI, Dynamic DNS, conditional behaviour, client classing,
    484      1.1  christos and more. Version 3 of the DHCP server was funded by Nominum, Inc.
    485      1.1  christos The 4.0 release in December 2007 introduced DHCPv6 protocol support
    486      1.1  christos for the server and client.
    487      1.1  christos 
    488      1.1  christos This product includes cryptographic software written
    489      1.1  christos by Eric Young (eay (a] cryptsoft.com).
    490