Release Notes: This release adds DHCPv6 rapid commit support. It adds explicit parser support for zero-length DHCP options. It has improved IANA compliance. Timer granularity is now 1/100s in the DHCPv6 client. DHCP now builds on AIX. Compilation bugs relating to Solaris 9 and Mac OS X Leopard (10.5) have been fixed. There are numerous other enhancements and bugfixes.
Release Notes: DHCP Failover Protocol support, addition of OMAPI (an API for accessing and modifying the DHCP server and client state), conditional behaviour, storing arbitrary information on leases, address pools with access control, client classing, address allocation restriction by class, relay agent information option support, dynamic DNS updates, and many bugfixes, performance enhancements, and minor new DHCP protocol features.
Release Notes: This release fixes a bug in update-static-leases, and a compile error on SunOS 4.
Release Notes: A fix for a bug with doing DNS updates for static leases, and a fix for a compile error on SunOS 4.
Release Notes: This release fixes a couple of failover bugs, a bug in DNS update handling for clients that don't snd a hostname option, lots of memory leaks (a fairly long run of the server doing lots of fun stuff now exits with no memory leaked), a bug that was causing the server to spin in certain cases, and a core dump in the client. The client will now do a DHCPRELEASE when shut down through OMAPI.
Release Notes: A number of fixes to the failover protocol support, some enhancements to the omshell tool (which allows the DHCP server to be controlled while it is running), and enhancements to the client to provide better apm support for laptops.
Release Notes: This is release candidate 7. No new features are being added to the server, and the final 3.0 release is imminent. The previous version listed (3.0b2pl2) is quite out of date and buggy. If you are still running it or anything up to 3.0b2pl24, upgrading is recommend.
Release Notes: This release introduces an implementation of the DHCP failover protocol, which means that you can have two DHCP servers serving the same set of clients the same set of addresses, and support for TSIG for secure signatures for doing Dynamic DNS updates, and a great deal more flexibility in terms of how Dynamic DNS updates are done. This release also allows you to query and update the DHCP server's configuration and status on the fly, using OMAPI - the Object Management API. This is a network-transportable object-oriented protocol that lets a client connect to the server, identify objects that it wants to access, and either return or change the status of these objects. Currently OMAPI can be used to manipulate host declarations, named groups, leases, failover protocol instances, and more. Access to server objects is authenticated with an MD5-based shared secret mechanism, similar to TSIG.
Release Notes: Interim Dynamic DNS Update implementation. Updated documentation. Fixed a bug in determination of client lease duration. The <em>host-name</em> and similar options are now printed as text. Support <em>always-broadcast</em> and <em>one-lease-per-client</em>. Support <em>reverse</em>, <em>leased-address</em> and <em>binary-to-ascii</em> subexpressions. Fix parser bug that prevented <em>not authoritative</em> from working.