dhcp-agent-0.41 errata
----------------------

None yet :-)

dhcp-agent-0.40 errata
---------------------

The sysconf dns configuration has a bug in it. The
/etc/resolv.conf is not truncated when written to. This will be
fixed in the next release. Here's a patch to dhcp-agent-0.40.tar.gz

cd conf/dhcp-client
patch < /path/to/patch file

Index: default.sysconf
===================================================================
RCS file: /cvsroot/dhcp-agent/dhcp-agent/conf/dhcp-client/default.sysconf,v
retrieving revision 1.1
diff -C3 -r1.1 default.sysconf
*** default.sysconf     5 Jul 2003 19:30:51 -0000       1.1
--- default.sysconf     8 Jul 2003 17:23:43 -0000
***************
*** 69,75 ****
  
          (lambda ()
            (if (do-configure)
!               (let ((resolv-conf-file-port (open "/etc/resolv.conf" O_WRONLY 0644)))
                  (client-info-message "configuring resolver")
                  (map-in-order
                   (lambda (dns-server)
--- 69,75 ----
  
          (lambda ()
            (if (do-configure)
!               (let ((resolv-conf-file-port (open "/etc/resolv.conf" (logior O_WRONLY O_TRUNC) 0644)))
                  (client-info-message "configuring resolver")
                  (map-in-order
                   (lambda (dns-server)


dhcp-agent-0.39 errata
----------------------

-- Under FreeBSD and possibly other *BSDs, if dhcp-client is run on
   an interface without the broadcast clear the client will not
   function properly. To work around this do the following:

   ifconfig <interface> inet 0.0.0.0 netmask 0

   To clear the broadcast bits. A fix is planned for the next
   release. (Thanks Jon Nistor)

   (Update: this only happened on a release candidate version of FreeBSD 4.7
    and thus is considered to probably be a bug of that release candidate)

-- Interface MTU settings are being ignored by the interface
   manipulation code. This will be fixed in the next release.

dhcp-agent-0.38 errata
----------------------

This is a list of errata for the dhcp-agent-0.38 release. If you
have problems this may help solve them.

-- dhcp-sniff's "-p" option mysteriously disappeared. It will come 
   back in the next release. (Thanks Jon Nistor)

-- If you're in Toronto and using Rogers cable you may find that
   the default configuration file is a bit too
   strict. Unfortunately no "novice" settings exist which cause the
   client to try to behave as well as it can. Currently in cvs
   under the "contrib" directory is a default.conf.rogers-toronto
   file which can be used in the place of a default.conf (Thanks Jon Nistor)

-- enable-icmp-latency-discovery isn't working as
   advertised. it's being ignored and icmp latency is checked
   against routers anyway.