From: David Hankins Date: Wed, 7 Jan 2009 20:03:16 +0000 (+0000) Subject: Pave the way for 4.2.0 feature listings, s/eight-spaces/tab/g. X-Git-Tag: v4_2_0a1~113 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=adbef1193138bc1fbf629649828d91316a82e5ab;p=thirdparty%2Fdhcp.git Pave the way for 4.2.0 feature listings, s/eight-spaces/tab/g. --- diff --git a/README b/README index 98021ab06..22ff6a1e2 100644 --- a/README +++ b/README @@ -1,6 +1,6 @@ Internet Systems Consortium DHCP Distribution - Version 4.1.0 - 5 December 2008 + Version 4.2.0 + 21 December 2012 README FILE @@ -399,7 +399,7 @@ relay agent) is available from the Ports Collection in /usr/ports/net/isc-dhcp3, or as a package on FreeBSD installation CDROMs. - NeXTSTEP + NeXTSTEP The NeXTSTEP support uses the NeXTSTEP Berkeley Packet Filter extension, which is not included in the base NextStep system. You @@ -544,24 +544,24 @@ 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, as reported by dhcpd -t. + 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. + 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 eg via a hidden @@ -569,17 +569,17 @@ bug reports are more likely to get handled more quickly overall. 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 diff --git a/RELNOTES b/RELNOTES index 1fb078ae6..dd118d5e4 100644 --- a/RELNOTES +++ b/RELNOTES @@ -1,34 +1,22 @@ Internet Systems Consortium DHCP Distribution - Version 4.1.0 - 5 December 2008 + Version 4.2.0 + 21 December 2012 Release Notes NEW FEATURES -ISC DHCP 4.1.x includes several new DHCPv6 features that were not included -in DHCP 4.0.x. These include: - -- Support for the rapid-commit option on the client side - -- Prefix Delegation support - -- IA_TA address support - -- A basic DHCPv6 relay agent - -- Basic and partial DHCPv6 leasequery support +ISC DHCP 4.2.x includes features that were not included in DHCP 4.1.x. +These include: There are a number of DHCPv6 limitations and features missing in this release, which will be addressed in the future: - Only Solaris, Linux, FreeBSD, NetBSD, and OpenBSD are supported. -- Only a single address is supported per IA. - -- DHCPv6 includes human-readable text in status code messages. These - should be configurable, and probably localized via gettext() or the - like. +- DHCPv6 includes human-readable text in status code messages, in + English. A method to reconfigure or support other languages would + be preferrable. - The "host-identifier" option is limited to a simple token. @@ -47,6 +35,11 @@ The system has only been tested on Linux, FreeBSD, and Solaris, and may not work on other platforms. Please report any problems and suggested fixes to . + + Changes since 4.1.0 (new features) + + + Changes since 4.1.0 (bug fixes) - Validate the argument to the -p option. @@ -57,7 +50,7 @@ work on other platforms. Please report any problems and suggested fixes to (which are bogus corruption read from the packet anyway). It also carries a hopefully more useful explanation. - Changes since 4.1.0b1 + Changes since 4.1.0b1 - A missing "else" in dhcrelay.c could have caused an interface not to be recognized. @@ -1729,7 +1722,7 @@ work on other platforms. Please report any problems and suggested fixes to - A minor bug fix in the arguments to a logging function call. - Documentation update for dhcpd.conf. - Changes since 3.0.1rc2 + Changes since 3.0.1rc2 - Allow the primary to send a POOLREQ message. This isn't what the current failover draft says to do, so we may have to back it out if I can't get the @@ -1737,7 +1730,7 @@ work on other platforms. Please report any problems and suggested fixes to current draft seems needlessly hairy, so I'm floating a trial balloon. The rc1 code did not implement the method described in the draft either. - Changes since 3.0.1rc1 + Changes since 3.0.1rc1 - Treat NXDOMAIN and NXRRSET as success when we are trying to delete a domain or RRSET. This allows the DHCP server to forget about a name @@ -1772,7 +1765,7 @@ work on other platforms. Please report any problems and suggested fixes to than a history of all references and dereferences. This code is only used when extensive additional debugging is enabled. - Changes since 3.0 + Changes since 3.0 - Make allocators for hash tables. As a side effect, this fixes a memory smash in the subclass allocation code. @@ -2150,7 +2143,7 @@ work on other platforms. Please report any problems and suggested fixes to - Support GCC on SCO. - Changes since 3.0 Beta 2 Patchlevel 23 + Changes since 3.0 Beta 2 Patchlevel 23 - Fix a bug in the DNS update code where a status code was not being checked. This may have been causing core dumps. @@ -2187,18 +2180,18 @@ work on other platforms. Please report any problems and suggested fixes to - Fix some memory allocation bugs in failover. - Changes since 3.0 Beta 2 Patchlevel 22 + Changes since 3.0 Beta 2 Patchlevel 22 - Apply some patches suggested by Cyrille Lefevre, who is maintaining the FreeBSD ISC DHCP Distribution port. - Fix a core dump in DHCPRELEASE. - Changes since 3.0 Beta 2 Patchlevel 21 + Changes since 3.0 Beta 2 Patchlevel 21 - This time for sure: fix the spin described in the changes for pl20. - Changes since 3.0 Beta 2 Patchlevel 20 + Changes since 3.0 Beta 2 Patchlevel 20 - Fix a problem with Linux detecting large numbers of interfaces (Ben) @@ -2209,7 +2202,7 @@ work on other platforms. Please report any problems and suggested fixes to previous fix only partially fixed the problem - enough to get it past the regression test. - Changes since 3.0 Beta 2 Patchlevel 19 + Changes since 3.0 Beta 2 Patchlevel 19 - Fix a bug that could cause the server to abort if compiled with POINTER_DEBUG enabled. @@ -2223,7 +2216,7 @@ work on other platforms. Please report any problems and suggested fixes to - Install unformatted man pages on SunOS. - Changes since 3.0 Beta 2 Patchlevel 18 + Changes since 3.0 Beta 2 Patchlevel 18 - Allow the server to be placed in partner-down state using OMAPI. (Damien Neil) @@ -2277,7 +2270,7 @@ work on other platforms. Please report any problems and suggested fixes to ** there was no pl17 ** - Changes since 3.0 Beta 2 Patchlevel 16 + Changes since 3.0 Beta 2 Patchlevel 16 - Add support for transaction tracing. This allows the state of the DHCP server on startup, and all the subsequent transactions, to be @@ -2323,7 +2316,7 @@ work on other platforms. Please report any problems and suggested fixes to would cause two DHCPDISCOVERS to be sent back-to-back on startup. - Changes since 3.0 Beta 2 Patchlevel 15 + Changes since 3.0 Beta 2 Patchlevel 15 - Some documentation tweaks. @@ -2339,7 +2332,7 @@ work on other platforms. Please report any problems and suggested fixes to - Fix a core dump that would occur if a packet was sent with no options. - Changes since 3.0 Beta 2 Patchlevel 14 + Changes since 3.0 Beta 2 Patchlevel 14 - Finish fixing a long-standing bug in the agent options code. This was causing core dumps and failing to operate correctly - in @@ -2363,7 +2356,7 @@ work on other platforms. Please report any problems and suggested fixes to - Don't send faked-out giaddr when renewing or bound - again, useful for debugging. - Changes since 3.0 Beta 2 Patchlevel 13 + Changes since 3.0 Beta 2 Patchlevel 13 - Fixed a problem where the fqdn decoder would sometimes try to store an option with an (unsigned) negative length, resulting in a core @@ -2390,7 +2383,7 @@ work on other platforms. Please report any problems and suggested fixes to the transition. - Changes since 3.0 Beta 2 Patchlevel 12 + Changes since 3.0 Beta 2 Patchlevel 12 - Fixed a couple of silly compile errors.