2
0
mirror of https://gitlab.isc.org/isc-projects/dhcp synced 2025-08-22 01:49:35 +00:00
isc-dhcp/RELNOTES

107 lines
4.0 KiB
Plaintext
Raw Normal View History

Internet Software Consortium DHCP Distribution
2000-09-14 12:51:38 +00:00
Version 3, Beta 2, Patchlevel 4
September 14, 2000
1996-08-29 10:48:24 +00:00
Release Notes
This is a development snapshot of Version 3 of the Internet Software
Consortium DHCP Distribution.
1996-08-29 10:48:24 +00:00
NEW FEATURES
Version 3, Beta 2 of the ISC DHCP Distribution includes the following
features that are new since version 2.0:
1997-12-11 22:35:03 +00:00
- DHCP Failover Protocol support
- 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
- Many bug fixes, performance enhancements, and minor new DHCP
protocol features.
1996-08-29 10:48:24 +00:00
2000-09-02 00:56:58 +00:00
This beta release is quite new, and is running in production at only a
few sites. We strongly recommend that you exercise caution in
installing it. The 3.0 Beta 2 lease file is not backwards compatible
with the 3.0 Beta 1 lease file, so if you have to go back, you will
have to convert your lease files back to the 3.0 Beta 1 format - if
you try to run a 3.0 Beta 1 server on a 3.0 Beta 2 lease file, it will
cheerfully delete all your leases. Having said that, of course the
way that new releases of open source software become stable is by
people using them, finding the bugs, and reporting the bugs. So
while we urge you to exercise caution, we would also appreciate any
testing or production use you can safely do.
1999-05-07 17:49:12 +00:00
For information on how to install, configure and run this software,
as well as how to find documentation and report bugs, please consult
the README file.
The Dynamic DNS Update support is a descendent of an implementation
done by Lans Carstensen and Brian Dols at Rose-Hulman Institute of
Technology, Jim Watt at Perkin-Elmer, Irina Goble at Integrated
Measurement Systems, and Brian Murrell at BC Tel Advanced
Communications. I'd like to express my thanks to all of these good
people here, both for working on the code and for prodding me into
improving it.
2000-09-04 22:49:17 +00:00
Changes since 3.0 Beta 2 Patchlevel 4
- Incorporated Peter Marschall's proposed change to array/record
parsing, which allows things like the slp-agent option to be encoded
correctly. Thanks very much to Peter for taking the initiative to
do this, and for doing such a careful job of it (e.g., updating the
comments)!
- Added an encoding for the slp-agent option. :')
2000-09-14 12:51:38 +00:00
Changes since 3.0 Beta 2 Patchlevel 3
- In the DHCP client, execute client statements prior to using the values
of options, so that the client configuration can overried, e.g., the
lease renewal time.
- Fix a reference counting error that would result in very reproducible
failures in updates, as well as occasional core dumps, if a zone was
declared without a key.
- Fix some Linux 2.0 compilation problems.
- Fix a bug in scope evaluation during execution of "on" statements that
caused values not to be recorded on leases.
- If the dhcp-max-message-size option is specified in scope, and the
client didn't send this option, use the one specified in scope to
determine the maximum size of the response.
2000-09-08 01:37:15 +00:00
Changes since 3.0 Beta 2 Patchlevel 2
2000-09-08 01:40:51 +00:00
- Fix a case where spawning subclasses were being allocated
incorrectly, resulting in a core dump.
2000-09-08 01:37:15 +00:00
- Fix a case where the DHCP server might inappropriately NAK a
RENEWING client.
- Fix a place dhcprequest() where static leases could leak.
- Include memory.h in omapip_p.h so that we don't get warnings about
using memcmp().
2000-09-04 22:49:17 +00:00
Changes since 3.0 Beta 2 Patchlevel 1
- Notice when SIOCFIGCONF returns more data than fit in the buffer -
allocate a larger buffer, and retry. Thanks to Greg Fausak for
pointing this out.
- In the server, if no interfaces were configured, report an error and
exit.
- Don't ever record a state of 'startup'.
- Don't try to evaluate the local failover binding address if none was
specified. Thanks to Joseph Breu for finding this.