ISC DHCP 4.0.0b1 is now available!

[David W. Hankins]

  *** From dhcp-announce -- To unsubscribe, see the end of this message. ***

ISC DHCP 4.0.0b1 is now available for download.  ISC DHCP 4.0.0 is a
development track engineered primarily for the purpose of developing
DHCPv6 features.

This is the first BETA release of 4.0.0, marking the approximate
moment at which features are frozen, and only fixes to bugs are
sought.  The main focus of this beta release is to update Confirm
message processing to more closely and generally match RFC3315 section
18.2.2 guidance.  A full list of changes in this release is included
below.

A couple imperfections were discovered during release engineering, a
list has been included below along with a full list of all changes
since relevant recent releases.  We will endeavor to correct these
issues in a forthcoming beta release.

For a complete list of changes from any previous release, please
consult the RELNOTES file within the source distribution, or on our
website:

    http://www.isc.org/sw/dhcp/dhcp4_0.php

This release, and its OpenPGP-signatures are available now from:

    ftp://ftp.isc.org/isc/dhcp/dhcp-4.0.0b1.tar.gz
    ftp://ftp.isc.org/isc/dhcp/dhcp-4.0.0b1.tar.gz.sha512.asc
    ftp://ftp.isc.org/isc/dhcp/dhcp-4.0.0b1.tar.gz.sha256.asc
    ftp://ftp.isc.org/isc/dhcp/dhcp-4.0.0b1.tar.gz.sha1.asc

ISC's Release Signing Key can be obtained at:

    http://www.isc.org/about/openpgp/



			    KNOWN DEFECTS

	o A problem has been reported in DHCPv6 appropriate address
	  detection.  When a client is moved between networks, it is
	  possible that it will receive its old address rather than
	  an address that is appropriate for the link to which it
	  is attached.  This was reported during release engineering
	  and has not been confirmed or reproduced yet.

	o There may still be a condition in which the DHCPv6 server
	  may enter into an infinite loop, subsequently failing but
	  consuming all CPU.


                        Changes since 4.0.0a3

- The DHCP server no longer requires a "ddns-update-style" statement,
  and now defaults to "none", which means DNS updates are disabled.

- Log messages when failover peer names mismatch have been improved to
  point out the problem.

- Bug where server advertised a IPv6 address in response to a SOLICIT
  but would not return the address in response to a REQUEST. Thanks to
  Dennis Kou for finding the bug.

- Fixed an error causing the server to lock up on lease expiration,
  reported independently by Jothilingam Vasu and Dennis Kou.

- Fixed a ./configure bug where compile tests were failing due to
  "-Werror" (unused variable) rather than the actual test failure.  Lead
  to inconsistent and unworkable auto-configurations.

- Compilation with DLPI and -Werror has been repaired.

- Error in decoding IA_NA option if multiple interfaces are present
  fixed by Marcus Goller.

- DHCPv6 server Confirm message processing has been enhanced - it no
  longer replies only to clients with host {} records, it now replies
  as directed in RFC3315 section 18.2.2 - that is, to all clients
  regardless of the existence of bindings.

- A core dump during expired lease cleanup has been repaired.

- DDNS updates state information are now stored in 'binding scopes' that
  follow the leases through their lifecycles.  This enables DDNS teardowns
  on leases that are assigned and expired inbetween a server restart (the
  state is recovered from dhcpd.leases).  Arbitrary user-specified binding
  scopes ('set var = "value";') are not yet supported.

                        Changes since 3.1.0 (Maintenance)

- A bug was repaired where MAC Address Affinity for virgin leases always
  mapped to the primary.  Virgin leases now have an interleaved preference
  between primary and secondary.

- A bug was repaired where MAC Address Affinity for clients with no client
  identifier was sometimes mishashed to the peer.  Load balancing during
  runtime and pool rebalancing were opposing.

- An assertion in lease counting relating to reserved leases was repaired.

- The subnet-mask option inclusion now conforms with RFC2132 section 3.3;
  it will only appear prior to the routers option if it is present on the
  Parameter-Request-List.  The subnet-mask option will also only be
  included by default (if it is not on the PRL) in response to DISCOVER
  or REQUEST messages.

- The FQDN option is only supplied if the client supplied an FQDN option or
  if the FQDN option was explicitly requested on the PRL.

- Dynamic BOOTP leases are now load balanced in failover.

-- 
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil?	 https://secure.isc.org/store/t-shirt/
-- 
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins
-----------------------------------------------------------------------
To unsubscribe from this list, visit http://www.isc.org/dhcp-lists.html
or send mail to dhcp-announce-request at isc.org with the subject line of
'unsubscribe'.
-----------------------------------------------------------------------