- Internet Software Consortium DHCP Distribution
- Version 3, Beta 2, Patchlevel 22
- March 20, 2001
+ Internet Systems Consortium DHCP Distribution
+ Version 4.4.2
+ 22 January 2020
- README FILE
+ README FILE
You should read this file carefully before trying to install or use
the ISC DHCP Distribution.
5.2.4 BROADCAST
5.2.6 IP BOOTP AGENT
5.2.7 MULTIPLE INTERFACES
- 5.3 SCO
- 5.4 HP-UX
- 5.5 ULTRIX
- 5.6 FreeBSD
- 5.7 NeXTSTEP
- 5.8 SOLARIS
+ 5.3 ATF
6 SUPPORT
6.1 HOW TO REPORT BUGS
+ 7 HISTORY
WHERE TO FIND DOCUMENTATION
late-breaking operational and system-specific information that you
should read even if you don't want to read the manual pages, and that
you should *certainly* read if you run into trouble. Internet
-standards relating to the DHCP protocol are stored in the doc
+standards relating to the DHCP protocol are listed in the References
+document that is available in html, txt and xml formats in doc/
subdirectory. You will have the best luck reading the manual pages if
you build this software and then install it, although you can read
them directly out of the distribution if you need to.
the DHCP server lease database is in the dhcpd.leases man page.
Server configuration documentation is in the dhcpd.conf man page as
well as the dhcp-options man page. A sample DHCP server
-configuration is in the file server/dhcpd.conf. The source for the
-dhcpd, dhcpd.leases and dhcpd.conf man pages is in the server/ sub-
+configuration is in the file server/dhcpd.conf.example. The source for
+the dhcpd, dhcpd.leases and dhcpd.conf man pages is in the server/ sub-
directory in the distribution. The source for the dhcp-options.5
man page is in the common/ subdirectory.
DHCP relay agent documentation is in the dhcrelay man page, the source
for which is distributed in the relay/ subdirectory.
+KEA Migration Assistant documentation, including how to build, install
+and use it, is including in the keama directory.
+
To read installed manual pages, use the man command. Type "man page"
where page is the name of the manual page. This will only work if
you have installed the ISC DHCP distribution using the ``make install''
your current working directory is the top level directory of the ISC
DHCP Distribution.
-If you do not have the nroff command, you can type ``more catpage''
-where catpage is the filename of the catted man page. Catted man
-pages names are the name of the manual page followed by ".cat"
-followed by 5 or 8, as with unformatted manual pages.
-
-Please note that until you install the manual pages, the pathnames of
-files to which they refer will not be correct for your operating
-system.
-
- RELEASE STATUS
-
-This is the second beta release of version 3.0 of the ISC DHCP
-Distribution. Development of this release is approaching the point at
-which it will be frozen, and no significant new features will be
-added.
-
-In this release, the server and relay agent are currently fully
-functional on NetBSD, Linux systems with kernel version 2.2 or later,
-FreeBSD, OpenBSD, BSD/OS, Digital Tru64 Unix and Solaris. The
-software will also run on HP-UX, but only supports a single network
-interface. Ports also exist for QNX, SCO, NeXTStep, and MacOS X, but
-are not in wide use, with all that implies. We are not aware of an
-easy way to get this software running on HP-UX.
-
-The DHCP client currently only knows how to configure the network on
-NetBSD, FreeBSD, OpenBSD, BSD/os, Linux, Solaris and NextStep. The
-client depends on a system-dependent shell script to do network
-configuration - support for other operating systems is simply a matter
-of porting this shell script to the new platform.
-
-If you are running the DHCP distribution on a machine which is a
-firewall, or if there is a firewall between your DHCP server(s) and
-DHCP clients, please read the section on firewalls which appears later
-in this document.
-
-If you wish to run the DHCP Distribution on Linux, please see the
-Linux-specific notes later in this document. If you wish to run on an
-SCO release, please see the SCO-specific notes later in this document.
-You particularly need to read these notes if you intend to support
-Windows 95 clients. If you are running a version of FreeBSD prior to
-2.2, please read the note on FreeBSD. If you are running HP-UX or
-Ultrix, please read the notes for those operating systems below. If
-you are running NeXTSTEP, please see the notes on NeXTSTEP below.
-
-If you start dhcpd and get a message, "no free bpf", that means you
-need to configure the Berkeley Packet Filter into your operating
-system kernel. On NetBSD, FreeBSD and BSD/os, type ``man bpf'' for
-information. On Digital Unix, type ``man pfilt''.
-
+Please note that the pathnames of files to which our manpages refer
+will not be correct for your operating system until after you iterate
+'make install' (so if you're reading a manpage out of the source
+directory, it may not have up-to-date information).
BUILDING THE DHCP DISTRIBUTION
To build the DHCP Distribution, unpack the compressed tar file using
the tar utility and the gzip command - type something like:
- zcat dhcp-3.0b2pl22.tar.gz |tar xvf -
-
-On BSD/OS, you have to type gzcat, not zcat, and you may run into
-similar problems on other operating systems.
+ gunzip dhcp-4.4.2.tar.gz
+ tar xvf dhcp-4.4.2.tar
CONFIGURING IT
-Now, cd to the dhcp-3.0b2pl22 subdirectory that you've just
-created and configure the source tree by typing:
+Now, cd to the dhcp-4.4.2 subdirectory that you've just created and
+configure the source tree by typing:
- ./configure
+ ./configure
If the configure utility can figure out what sort of system you're
running on, it will create a custom Makefile for you for that
system you are using, that system is not supported - you are on
your own.
+Several options may be enabled or disabled via the configure command.
+You can get a list of these by typing:
+
+ ./configure --help
+
+If you want to use dynamic shared libraries automake, autoconf
+(aka GNU autotools) and libtool must be available. The DHCP
+distribution provides 3 configure.ac* files: the -lt version
+has no libtool support and was copied to the configure.ac
+standard file in the distribution. To enable libtool support
+you should perform these steps:
+
+ cp configure.ac+lt configure.ac
+ autoreconf -i
+
+after you can use the regenerated configure as usual
+(with libtool support (--enable-libtool) on by default):
+
+ ./configure
+
+For compatibility (and people who don't read this documentation)
+the --enable-libtool configuration file is supported even by
+the distributed configure (and off by default). The previous
+steps are performed and the regenerated configure called with
+almost the same parameters (this "almost" makes the use of
+this feature not recommended).
+
+Note you can't go back from with libtool support to without libtool
+support by restoring configure.ac and rerun autoreconf. If you
+want or need to restore the without libtool support state the
+required way is to simply restore the whole distribution.
+
DYNAMIC DNS UPDATES
A fully-featured implementation of dynamic DNS updates is included in
-this release. There are no build dependencies with any BIND version
-- this version can and should just use the resolver in your C library.
+this release. It uses libraries from BIND and, to avoid issues with
+different versions, includes the necessary BIND version. The appropriate
+BIND libraries will be compiled and installed in the bind subdirectory
+as part of the make step. In order to build the necessary libraries you
+will need to have "gmake" available on your build system.
+
There is documentation for the DDNS support in the dhcpd.conf manual
page - see the beginning of this document for information on finding
to do some programming or debugging on your own to get the DHCP
Distribution working.
+If you cross compile you have to follow the instructions from
+the BIND README, in particular you must set the BUILD_CC
+environment variable.
+
INSTALLING THE DHCP DISTRIBUTION
Once you have successfully gotten the DHCP Distribution to build, you
problems for Linux 2.1/2.2: the "SO_ATTACH_FILTER undeclared" problem
and the "protocol not configured" problem.
- LINUX: IF_TR.H NOT FOUND
-
-When you compile the distribution on Linux, you may get an error
-message indicating that the include file if_tr.h could not be found.
-If this happens, go into includes/cf/linux.h and delete the line that
-defined HAVE_TR_SUPPORT, or look into installing a new version of libc
-that includes the if_tr.h file. We will be working on removing this
-problem in the future, but for now, if you run into it, this should be
-a viable workaround.
-
- LINUX: SO_ATTACH_FILTER UNDECLARED
-
-In addition, there is a minor issue that we will mention here because
-this release is so close on the heels of the Linux 2.2 release: there
-is a symlink in /usr/include that points at the linux asm headers. It
-appears to be not uncommon that this link won't be updated correctly,
-in which case you'll get the following error when you try to build:
-
- lpf.c: In function `if_register_receive':
- lpf.c:152: `SO_ATTACH_FILTER' undeclared (first use this function)
- lpf.c:152: (Each undeclared identifier is reported only once
- lpf.c:152: for each function it appears in.)
-
-The line numbers may be different, of course. If you see this
-header, your linux asm header link is probably bad, and you should
-make sure it's pointing to correct linux source directory.
-
LINUX: PROTOCOL NOT CONFIGURED
-One additional Linux 2.1/2.2 issue: if you get the following message,
-it's because your kernel doesn't have the linux packetfilter or raw
-packet socket configured:
+If you get the following message, it's because your kernel doesn't
+have the Linux packetfilter or raw packet socket configured:
Make sure CONFIG_PACKET (Packet socket) and CONFIG_FILTER (Socket
Filtering) are enabled in your kernel configuration
If this happens, you need to configure your Linux kernel to support
-Socket Filtering and the Packet socket. You can do this by typing
-``make config'', ``make menuconfig'' or ``make xconfig'', and then
-enabling the Packet socket and Socket Filtering options that you'll
-see displayed on the menu or in the questionnaire. You can also edit
-your linux kernel .config file directly: set CONFIG_FILTER=y and
-CONFIG_PACKET=y. If you do this, make sure you run ``make oldconfig''
-afterwards, so that the changes you've made are propogated to the
-kernel header files. After you've reconfigured, you need to type
-``make'' to build a new Linux kernel, and then install it in the
-appropriate place (probably /linux). Make sure to save a copy of your
-old /linux.
-
-If the preceding paragraph made no sense to you, ask your Linux
-vendor/guru for help - please don't ask us.
-
-If you set CONFIG_PACKET=m or CONFIG_FILTER=m, then you must tell the
-kernel module loader to load the appropriate modules. If this doesn't
-make sense to you, don't use CONFIG_whatever=m - use CONFIG_whatever=y.
-Don't ask for help with this on the DHCP mailing list - it's a Linux
-kernel issue. This is probably not a problem with the most recent
-Linux 2.2.x kernels.
+Socket Filtering and the Packet socket, or to select a kernel provided
+by your Linux distribution that has these enabled (virtually all modern
+ones do by default).
LINUX: BROADCAST
DHCP clients connected to the same network as the ISC DHCP server or
ISC relay agent will not see messages from the DHCP server. It *is*
possible to run into trouble with this on Linux 2.2 and later if you
-are running a verson of the DHCP server that was compiled on a Linux
+are running a version of the DHCP server that was compiled on a Linux
2.0 system, though.
It is possible to work around this problem on some versions of Linux
broadcast address hack, but do support multiple interfaces, using the
Linux Packet Filter.
- SCO
-
-SCO has the same problem as Linux (described earlier). The thing is,
-SCO *really* doesn't want to let you add a host route to the all-ones
-broadcast address. One technique that has been successful on some
-versions of SCO is the very bizarre command:
-
- ifconfig net0 alias 10.1.1.1 netmask 8.0.0.0
-
-Apparently this works because of an interaction between SCO's support
-for network classes and the weird netmask. The 10.* network is just a
-dummy that can generally be assumed to be safe. Don't ask why this
-works. Just try it. If it works for you, great. If not, SCO is
-supposedly adding hooks to support real DHCP service in a future
-release - I have this on good authority from the people at SCO who do
-*their* DHCP server and client.
-
- HP-UX
-
-HP-UX has the same problem with the all-ones broadcast address that
-SCO and Linux have. One user reported that adding the following to
-/etc/rc.config.d/netconf helped (you may have to modify this to suit
-your local configuration):
-
-INTERFACE_NAME[0]=lan0
-IP_ADDRESS[0]=1.1.1.1
-SUBNET_MASK[0]=255.255.255.0
-BROADCAST_ADDRESS[0]="255.255.255.255"
-LANCONFIG_ARGS[0]="ether"
-DHCP_ENABLE[0]=0
-
- ULTRIX
-
-Now that we have Ultrix packet filter support, the DHCP Distribution
-on Ultrix should be pretty trouble-free. However, one thing you do
-need to be aware of is that it now requires that the pfilt device be
-configured into your kernel and present in /dev. If you type ``man
-packetfilter'', you will get some information on how to configure your
-kernel for the packet filter (if it isn't already) and how to make an
-entry for it in /dev.
-
- FreeBSD
-
-Versions of FreeBSD prior to 2.2 have a bug in BPF support in that the
-ethernet driver swaps the ethertype field in the ethernet header
-downstream from BPF, which corrupts the output packet. If you are
-running a version of FreeBSD prior to 2.2, and you find that dhcpd
-can't communicate with its clients, you should #define BROKEN_FREEBSD_BPF
-in site.h and recompile.
-
- NeXTSTEP
-
-The NeXTSTEP support uses the NeXTSTEP Berkeley Packet Filter
-extension, which is not included in the base NextStep system. You
-must install this extension in order to get dhcpd or dhclient to work.
-
- SOLARIS
-
-One problem which has been observed and is not fixed in this
-patchlevel has to do with using DLPI on Solaris machines. The symptom
-of this problem is that the DHCP server never receives any requests.
-This has been observed with Solaris 2.6 and Solaris 7 on Intel x86
-systems, although it may occur with other systems as well. If you
-encounter this symptom, and you are running the DHCP server on a
-machine with a single broadcast network interface, you may wish to
-edit the includes/site.h file and uncomment the #define USE_SOCKETS
-line. Then type ``make clean; make''.
-
-The DHCP client on Solaris will only work with DLPI. If you run it
-and it just keeps saying it's sending DHCPREQUEST packets, but never
-gets a response, you may be having DLPI trouble as described above.
-If so, we have no solution to offer at this time. Also, because
-Solaris requires you to "plumb" an interface before it can be detected
-by the DHCP client, you must either specify the name(s) of the
-interface(s) you want to configure on the command line, or must plumb
-the interfaces prior to invoking the DHCP client. This can be done
-with ``ifconfig iface plumb'', where iface is the name of the
-interface (e.g., ``ifconfig hme0 plumb'').
-
-It should be noted that Solaris versions from 2.6 onward include a
-DHCP client that you can run with ``/sbin/ifconfig iface dhcp start''
-rather than using the ISC DHCP client. The feature set of the Solaris
-client is different (not necessarily better or worse) than that of the
-ISC client, but in most cases it will be a lot easier for you to just
-use that. Please do not ask for help in using the Solaris DHCP client
-on Internet Software Consortium mailing lists - that's why you're
-paying Sun the big bucks. If you're having a problem with the
-Solaris client interoperating with the ISC dhcp server, that's another
-matter, but please check with Sun first.
+ LINUX: OpenWrt
+
+DHCP 4.1 has been tested on OpenWrt 7.09 and 8.09. In keeping with
+standard practice, client/scripts now includes a dhclient-script file
+for OpenWrt. However, this is not sufficient by itself to run dhcp on
+OpenWrt; a full OpenWrt package for DHCP is available at
+ftp://ftp.isc.org/isc/dhcp/dhcp-4.1.0-openwrt.tar.gz
+
+ LINUX: 802.1q VLAN INTERFACES
+
+If you're using 802.1q vlan interfaces on Linux, it is necessary to
+vconfig the subinterface(s) to rewrite the 802.1q information out of
+packets received by the dhcpd daemon via LPF:
+
+ vconfig set_flag eth1.523 1 1
+
+Note that this may affect the performance of your system, since the
+Linux kernel must rewrite packets received via this interface. For
+more information, consult the vconfig man pages.
+
+
+ ATF
+
+Please see the file DHCP/doc/devel/atf.dox for a description of building
+and using these tools.
+
+The optional unit tests use ATF (Automated Testing Framework) including
+the atf-run and atf-report tools. ATF deprecated these tools in
+version 0.19 and removed these tools from its sources in version 0.20,
+requiring you to get an older version, use Kyua with an ATF compatibility
+package or use the version included in the Bind sources.
SUPPORT
-The Internet Software Consortium DHCP server is not a commercial
-product, and is not supported by the ISC. However, it has attracted a
-fairly sizable following on the Internet, which means that there are a
-lot of knowledgable users who may be able to help you if you get
-stuck. These people generally read the dhcp-server@isc.org mailing
-list.
-
-If you are going to use dhcpd, you should probably subscribe to the
-dhcp-server and dhcp-announce mailing lists. If you will be using
-dhclient, you should subscribe to the dhcp-client mailing list.
-
-If you need help, you should ask on the dhcp-server or dhcp-client
-mailing list - whichever is appropriate to your application. Support
-requests for the ISC DHCP client should go to dhcp-client@isc.org.
-Support requests for the DHCP server should go to dhcp-server@isc.org.
-If you are having trouble with a combination of the client and server,
-send the request to dhcp-server@isc.org. Please do not cross-post to
-both lists under any circumstances.
+The Internet Systems Consortium DHCP server is developed and distributed
+by ISC in the public trust, thanks to the generous donations of its
+sponsors. ISC now also offers commercial quality support contracts for
+ISC DHCP, more information about ISC Support Contracts can be found at
+the following URL:
+
+ https://www.isc.org/support/
+
+Please understand that we may not respond to support inquiries unless
+you have a support contract. ISC will continue its practice of always
+responding to critical items that effect the entire community, and
+responding to all other requests for support upon ISC's mailing lists
+on a best-effort basis.
+
+However, ISC DHCP has attracted a fairly sizable following on the
+Internet, which means that there are a lot of knowledgeable users who
+may be able to help you if you get stuck. These people generally
+read the dhcp-users@isc.org mailing list. Be sure to provide as much
+detail in your query as possible.
+
+If you are going to use ISC DHCP, you should probably subscribe to
+the dhcp-users or dhcp-announce mailing lists.
+
+WHERE TO SEND FEATURE REQUESTS: We like to hear your feedback. We may
+not respond to it all the time, but we do read it. If ISC DHCP doesn't
+work well for you, or you have an idea that would improve it for your
+use, please create an issue at https://gitlab.isc.org/isc-projects/dhcp/issues.
+This is also an excellent place to send patches that add new features.
WHERE TO REPORT BUGS: If you want the act of sending in a bug report
to result in you getting help in the form of a fixed piece of
but fundamentally you are making a support request, so please use the
addresses described in the previous paragraphs. If you are _sure_ that
your problem is a bug, and not user error, or if your bug report
-includes a patch, you can send it to dhcp-bugs@isc.org without
-subscribing. This mailing list goes into a bug tracking system, so
-you don't need to check periodically to see if we still remember the
-bug - if you haven't been notified that the bug has been closed, we
-still consider it a bug, and still have it in the system.
+includes a patch, you can submit it to our ticketing system at
+https://gitlab.isc.org/isc-projects/dhcp/issues. If you have not received
+a notice that the ticket has been resolved, then we're still working on it.
PLEASE DO NOT REPORT BUGS IN OLD SOFTWARE RELEASES! Fetch the latest
release and see if the bug is still in that version of the software,
-and if it's not, _then_ report it. It's okay to report bugs in the
-latest patchlevel of a major version that's not the most recent major
-version, though - for example, if you're running 2.0, you don't have
-to upgrade to 3.0 before you can report bugs.
-
-PLEASE DO NOT REPORT BUGS IF YOU ARE RUNNING A VERSION OF THE ISC
-DHCP DISTRIBUTION THAT YOU DIDN'T GET FROM THE ISC! Free operating
-system distributions are notorious for including outdated versions of
-software, and also versions of software that were not compiled on your
-particular version of the operating system. These versions
-frequently do not work. Getting a source distribution from the ISC
-and installing it frequently *does* work. Please try this *before*
-asking for help.
-
-PLEASE READ THIS README FILE CAREFULLY BEFORE REPORTING BUGS,
-PARTICULARLY THE SECTION BELOW ON WHAT TO INCLUDE IN A BUG REPORT OR
-HELP REQUEST.
-
-PLEASE DO NOT SEND REQUESTS FOR SUPPORT DIRECTLY TO THE ENGINEERS WHO
-WORK ON THE ISC DHCP DISTRIBUTION! *PARTICULARLY*, DO NOT SEND MAIL
-TO THE ENGINEERS BECAUSE YOU AREN'T SURE TO WHOM YOU SHOULD SEND MAIL
-- if you aren't sure, *ask* on the dhcp-server@isc.org or
-dhcp-client@isc.org mailing list.
-
-The number of people using the DHCP Distribution is sufficiently large
-that if we take interrupts every time any one of those people runs
-into trouble, we will never get any more coding done. If you send a
-support request directly to any ISC or Nominum engineer, we will
-forward it to the mailing list, or possibly ignore it, depending on
-how much stress we are under at the time.
-
-Please do not Cc: us on mail you send to these lists - we read both
-mailing lists, so this just means we get two copies!
-
-If your question can only be answered by one of the engineers, send it
-to the appropriate public mailing list anyway - we will answer it
-there. When we have time.
-
-Please do not think "Oh, I don't want to bother the whole mailing list
-with this question." If you are too embarrassed to ask publically,
-get a support contract.
-
-If you are concerned about bothering everybody on the list, that's
-great, but that's what the list is there for. When you send mail to
-one of the engineers, you are taking resources away from everybody on
-the mailing list *anyway* - they just don't know it.
-
-We're not writing this because we don't respect you - we really do
-want to help you, and we appreciate your bug reports and comments.
-But please use the mechanisms we have in place to provide you with
-help, because otherwise you are almost certainly depriving someone
-else of our help.
-
-PLEASE DO NOT CALL US ON THE PHONE FOR HELP! Answering the phone
-takes a lot more of our time and attention than answering email. If
-you do call us on the phone, we will tell you to send email to the
-mailing list or buy a support contract, so please don't waste your
-time or ours. If you have a support contract, please use the support
-channel mentioned in the support contract - otherwise you probably
-won't get timely support unless you happen to ask an interesting
-question and we happen to have some time to kill, because we can't
-tell you're a support customer if you send mail to the public mailing
-lists.
+and if it is still present, _then_ report it. ISC release versions
+always have three numbers, for example: 1.2.3. The 'major release' is
+1 here, the 'minor release' is 2, and the 'maintenance release' is 3.
+ISC will accept bug reports against the most recent two major.minor
+releases: for example, 1.0.0 and 0.9.0, but not 0.8.* or prior.
+
+PLEASE take a moment to determine where the ISC DHCP distribution
+that you're using came from. ISC DHCP is sometimes heavily modified
+by integrators in various operating systems - it's not that we
+feel that our software is perfect and incapable of having bugs, but
+rather that it is very frustrating to find out after many days trying
+to help someone that the sources you're looking at aren't what they're
+running. When in doubt, please retrieve the source distribution from
+ISC's web page and install it.
HOW TO REPORT BUGS OR REQUEST HELP
When you report bugs or ask for help, please provide us complete
information. A list of information we need follows. Please read it
carefully, and put all the information you can into your initial bug
-report, so that we don't have to ask you any questions in order to
-figure out your problem. If you need handholding support, please
-consider contacting a commercial provider of the ISC DHCP
-Distribution.
+report. This will save us a great deal of time and more informative
+bug reports are more likely to get handled more quickly overall.
1. The specific operating system name and version of the
- machine on which the DHCP server or client is running.
+ machine on which the DHCP server or client is running.
2. The specific operating system name and version of the
- machine on which the client is running, if you are having
- trouble getting a client working with the server.
+ machine on which the client is running, if you are having
+ trouble getting a client working with the server.
3. If you're running Linux, the version number we care about is
- the kernel version and maybe the library version, not the
- distribution version - e.g., while we don't mind knowing
- that you're running Redhat version mumble.foo, we must know
- what kernel version you're running, and it helps if you can
- tell us what version of the C library you're running,
- although if you don't know that off the top of your head it
- may be hard for you to figure it out, so don't go crazy
- trying.
+ the kernel version and maybe the library version, not the
+ distribution version - e.g., while we don't mind knowing
+ that you're running Redhat version mumble.foo, we must know
+ what kernel version you're running, and it helps if you can
+ tell us what version of the C library you're running,
+ although if you don't know that off the top of your head it
+ may be hard for you to figure it out, so don't go crazy
+ trying.
4. The specific version of the DHCP distribution you're
- running, for example "2.0b1pl19", not "2.0".
+ running, as reported by dhcpd -t.
5. Please explain the problem carefully, thinking through what
- you're saying to ensure that you don't assume we know
- something about your situation that we don't know.
- 6. Include your dhcpd.conf and dhcpd.leases file if they're not
- huge (if they are huge, we may need them anyway, but don't
- send them until you're asked). Huge means more than 100
- kilobytes each.
+ you're saying to ensure that you don't assume we know
+ something about your situation that we don't know.
+ 6. Include your dhcpd.conf and dhcpd.leases file as MIME attachments
+ if they're not over 100 kilobytes in size each. If they are
+ this large, please make them available to us, e.g., via a hidden
+ http:// URL or FTP site. If you're not comfortable releasing
+ this information due to sensitive contents, you may encrypt
+ the file to our release signing key, available on our website.
7. Include a log of your server or client running until it
- encounters the problem - for example, if you are having
- trouble getting some client to get an address, restart the
- server with the -d flag and then restart the client, and
- send us what the server prints. Likewise, with the client,
- include the output of the client as it fails to get an
- address or otherwise does the wrong thing. Do not leave
- out parts of the output that you think aren't interesting.
+ encounters the problem - for example, if you are having
+ trouble getting some client to get an address, restart the
+ server with the -d flag and then restart the client, and
+ send us what the server prints. Likewise, with the client,
+ include the output of the client as it fails to get an
+ address or otherwise does the wrong thing. Do not leave
+ out parts of the output that you think aren't interesting.
8. If the client or server is dumping core, please run the
- debugger and get a stack trace, and include that in your
- bug report. For example, if your debugger is gdb, do the
- following:
+ debugger and get a stack trace, and include that in your
+ bug report. For example, if your debugger is gdb, do the
+ following:
gdb dhcpd dhcpd.core
(gdb) where
This assumes that it's the dhcp server you're debugging, and
that the core file is in dhcpd.core.
- 9. If you know that the problem is an actual bug, and you can
- reproduce the bug, you can skip steps 6 through 8 and instead
- capture a trace file using the -tf flag (see the man page for
- details). If you do this, and there is anything in your
- dhcp configuration that you are not willing to make public,
- please send the trace file to dhcp-bugs@isc.org and NOT to
- dhcp-server@isc.org, because the tracefile contains your entire
- dhcp configuration.
-
-PLEASE DO NOT send queries about non-isc clients to the dhcp-client
-mailing list. If you're asking about them on an ISC mailing list,
-it's probably because you're using the ISC DHCP server, so ask there.
-If you are having problems with a client whose executable is called
-dhcpcd, this is _not_ the ISC DHCP client, and we probably can't help
-you with it.
-
-Please see http://www.isc.org/services/public/lists/dhcp-lists.html
-for details on how to subscribe to the ISC DHCP mailing lists.
-
+Please see https://www.isc.org/dhcp/ for details on how to subscribe
+to the ISC DHCP mailing lists.
+
+ HISTORY
+
+ISC DHCP was originally written by Ted Lemon under a contract with
+Vixie Labs with the goal of being a complete reference implementation
+of the DHCP protocol. Funding for this project was provided by
+Internet Systems Consortium. The first release of the ISC DHCP
+distribution in December 1997 included just the DHCP server.
+Release 2 in June 1999 added a DHCP client and a BOOTP/DHCP relay
+agent. DHCP 3 was released in October 2001 and included DHCP failover
+support, OMAPI, Dynamic DNS, conditional behaviour, client classing,
+and more. Version 3 of the DHCP server was funded by Nominum, Inc.
+The 4.0 release in December 2007 introduced DHCPv6 protocol support
+for the server and client.
+
+This product includes cryptographic software written
+by Eric Young (eay@cryptsoft.com).
projects / thirdparty / dhcp.git / blobdiff