Source-Changes-HG archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

[src/netbsd-1-5]: src/usr.sbin/dhcp Pull up revision 1.10 (requested by mellon):



details:   https://anonhg.NetBSD.org/src/rev/e341fafa67f1
branches:  netbsd-1-5
changeset: 491088:e341fafa67f1
user:      he <he%NetBSD.org@localhost>
date:      Wed Apr 04 20:55:12 2001 +0000

description:
Pull up revision 1.10 (requested by mellon):
  Update DHCP software to ISC version 3, Beta 2, Patchlevel 23.

diffstat:

 usr.sbin/dhcp/README           |   55 ++-
 usr.sbin/dhcp/RELNOTES         |  309 +++++++++++++++++++-
 usr.sbin/dhcp/client/clparse.c |  477 ++++++++----------------------
 usr.sbin/dhcp/common/options.c |  646 +++++++++++++++++++++++++++-------------
 usr.sbin/dhcp/server/Makefile  |    2 +-
 5 files changed, 904 insertions(+), 585 deletions(-)

diffs (truncated from 2598 to 300 lines):

diff -r b10e2ff92d2e -r e341fafa67f1 usr.sbin/dhcp/README
--- a/usr.sbin/dhcp/README      Wed Apr 04 19:28:37 2001 +0000
+++ b/usr.sbin/dhcp/README      Wed Apr 04 20:55:12 2001 +0000
@@ -1,6 +1,6 @@
            Internet Software Consortium DHCP Distribution
-                  Version 3, Beta 2, Patchlevel 9
-                          October 15, 2000
+                  Version 3, Beta 2, Patchlevel 23
+                           March 22, 2001
 
                             README FILE
 
@@ -15,6 +15,7 @@
         3.1     UNPACKING IT
         3.2     CONFIGURING IT
          3.2.1   DYNAMIC DNS UPDATES
+         3.2.2   LOCALLY DEFINED OPTIONS
         3.3     BUILDING IT
        4       INSTALLING THE DHCP DISTRIBUTION
        5       USING THE DHCP DISTRIBUTION
@@ -141,14 +142,14 @@
 To build the DHCP Distribution, unpack the compressed tar file using
 the tar utility and the gzip command - type something like:
 
-       zcat dhcp-3.0b2pl9.tar.gz |tar xvf -
+       zcat dhcp-3.0b2pl23.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.
 
                            CONFIGURING IT
 
-Now, cd to the dhcp-3.0b2pl9 subdirectory that you've just
+Now, cd to the dhcp-3.0b2pl23 subdirectory that you've just
 created and configure the source tree by typing:
 
                ./configure
@@ -169,6 +170,16 @@
 page - see the beginning of this document for information on finding
 manual pages.
 
+                      LOCALLY DEFINED OPTIONS
+
+In previous versions of the DHCP server there was a mechanism whereby
+options that were not known by the server could be configured using
+a name made up of the option code number and an identifier:
+"option-nnn"   This is no longer supported, because it is not future-
+proof.   Instead, if you want to use an option that the server doesn't
+know about, you must explicitly define it using the method described
+in the dhcp-options man page under the DEFINING NEW OPTIONS heading.
+
                             BUILDING IT
 
 Once you've run configure, just type ``make'', and after a while
@@ -481,9 +492,13 @@
 to result in you getting help in the form of a fixed piece of
 software, you are asking for help.  Your bug report is helpful to us,
 but fundamentally you are making a support request, so please use the
-addresses described in the previous paragraphs.  If your bug report
-includes a patch, or if you don't care about getting a response to it,
-you can send it to dhcp-bugs%isc.org@localhost without subscribing.
+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@localhost 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.
 
 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,
@@ -492,7 +507,7 @@
 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 NOT RUNNING A VERSION OF THE ISC
+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
@@ -561,12 +576,12 @@
 consider contacting a commercial provider of the ISC DHCP
 Distribution.
 
-       - The specific operating system name and version of the
+      1.  The specific operating system name and version of the
           machine on which the DHCP server or client is running.
-       - The specific operating system name and version of the
+      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.
-       - If you're running Linux, the version number we care about is
+      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
@@ -575,16 +590,16 @@
           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 specific version of the DHCP distribution you're
+      4.  The specific version of the DHCP distribution you're
           running, for example "2.0b1pl19", not "2.0".
-       - Please explain the problem carefully, thinking through what
+      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.
-       - Include your dhcpd.conf and dhcpd.leases file if they're not
+      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.
-       - Include a log of your server or client running until it
+      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
@@ -592,7 +607,7 @@
           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.
-       - If the client or server is dumping core, please run the
+      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:
@@ -604,6 +619,14 @@
 
          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@localhost and NOT to
+         dhcp-server%isc.org@localhost, 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,
diff -r b10e2ff92d2e -r e341fafa67f1 usr.sbin/dhcp/RELNOTES
--- a/usr.sbin/dhcp/RELNOTES    Wed Apr 04 19:28:37 2001 +0000
+++ b/usr.sbin/dhcp/RELNOTES    Wed Apr 04 20:55:12 2001 +0000
@@ -1,6 +1,6 @@
            Internet Software Consortium DHCP Distribution
-                  Version 3, Beta 2, Patchlevel 9
-                          October 15, 2000
+                  Version 3, Beta 2, Patchlevel 23
+                           March 22, 2001
 
                            Release Notes
 
@@ -49,6 +49,311 @@
 people here, both for working on the code and for prodding me into
 improving it.
 
+               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
+
+- This time for sure: fix the spin described in the changes for pl20.
+
+               Changes since 3.0 Beta 2 Patchlevel 20
+
+- Fix a problem with Linux detecting large numbers of interfaces (Ben)
+
+- Fix a memory smash in the quotify code, which was introduced in
+  pl19.
+
+- Actually fix the spin described in the changes for pl20.   The
+  previous fix only partially fixed the problem - enough to get it
+  past the regression test.
+
+               Changes since 3.0 Beta 2 Patchlevel 19
+
+- Fix a bug that could cause the server to abort if compiled with
+  POINTER_DEBUG enabled.
+
+- Fix a bug that could cause the server to spin when responding to a
+  DHCPREQUEST.
+
+- Apply Joost Mulders' suggested patches for DLPI on x86.
+
+- Support NUL characters in quoted strings.
+
+- Install unformatted man pages on SunOS.
+
+               Changes since 3.0 Beta 2 Patchlevel 18
+
+- Allow the server to be placed in partner-down state using OMAPI.
+  (Damien Neil)
+
+- Implement omshell, which can be used to do arbitrary things to the
+  server (in theory). (Damien Neil)
+
+- Fix a case where if a client had two different leases the server could
+  actually dereference the second one when it hadn't been referenced,
+  leading to memory corruption and a core dump. (James Brister)
+
+- Fix a case where a client could request the address of another client's
+  lease, but find_lease wouldn't detect that the other client had it, and
+  would attempt to allocate it to the client, resulting in a lease conflict
+  message.
+
+- Fix a case where a client with more than one client identifier could be
+  given a lease where the hardware address was correct but the client
+  identifier was not, resulting in a lease conflict message.
+
+- Fix a problem where the server could write out a colon-seperated
+  hex list as a value for a variable, which would then not parse.
+  The fix is to always write strings as quoted strings, with any
+  non-printable characters quoted as octal escape sequences.   So
+  a file written the old way still won't work, but new files written
+  this way will work.
+
+- Fix documentation for sending non-standard options.
+
+- Use unparsable names for unknown options.    WARNING: this will
+  break any configuration files that use the option-nnn convention.
+  If you want to continue to use this convention for some options,
+  please be sure to write a definition, like this:
+
+  option option-nnn code nnn = string;
+
+  You can use a descriptive name instead of option-nnn if you like.
+
+- Fix a problem where we would see a DHCPDISCOVER/DHCPOFFER/
+  DHCPREQUEST/DHCPACK/DHCPREQUEST/DHCPNAK sequence.   This was the
+  result of a deceptively silly bug in supersede_lease.
+
+- Fix client script exit status check, according to a fix supplied by
+  Hermann Lauer.
+
+- Fix an endianness bug in the tracefile support, regarding ICMP
+  messages.
+
+- Fix a bug in the client where the medium would not work correctly if
+  it contained quoted strings.
+
+                      ** there was no pl17 **
+
+               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
+  recorded in a file which can then be played back to reproduce the
+  behaviour of the DHCP server.   This can be used to quickly
+  reproduce bugs that cause core dumps or corruption, and also for
+  tracking down memory leaks.
+
+- Incorporate some bug fixes provided by Joost Mulders for the DLPI
+  package which should clear up problems people have been seeing on
+  Solaris.
+
+- Fix bugs in the handling of options stored as linked lists (agent
+  options, fqdn options and nwip options) that could cause memory
+  corruption and core dumps.
+
+- Fix a bug in DHCPREQUEST handling that resulted in DHCPNAK messages
+  not being send in some cases when they were needed.
+
+- Make the lease structure somewhat more compact.
+
+- Make initial failover startup *much* faster.   This was researched
+  and implemented by Damien Neil.
+
+- Add a --version flag to all executables, which prints the program
+  name and version to standard output.
+
+- Don't rewrite the lease file every thousand leases.
+
+- A bug in nit.c for older SunOS machines was fixed by a patch sent in
+  by Takeshi Hagiwara.
+
+- Fix a memory corruption bug in the DHCP client.
+
+- Lots of documentation updates.
+
+- Add a feature allowing environment variables to be passed to the
+  DHCP client script on the DHCP client command line.
+
+- Fix client medium support, which had been broken for some time.
+
+- Fix a bug in the DHCP client initial startup backoff interval, which
+  would cause two DHCPDISCOVERS to be sent back-to-back on startup.
+
+
+               Changes since 3.0 Beta 2 Patchlevel 15
+
+- Some documentation tweaks.
+
+- Maybe fix a problem in the DLPI code.
+
+- Fix some error code space inconsistencies in ddns update code.



Home | Main Index | Thread Index | Old Index