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