File:  [ELWIX - Embedded LightWeight unIX -] / embedaddon / dhcp / RELNOTES
Revision 1.1.1.1 (vendor branch): download - view: text, annotated - select for diffs - revision graph
Tue Oct 9 09:06:54 2012 UTC (11 years, 8 months ago) by misho
Branches: dhcp, MAIN
CVS tags: v4_1_R7p0, v4_1_R7, v4_1_R4, HEAD
dhcp 4.1 r7

    1: 	      Internet Systems Consortium DHCP Distribution
    2: 			    Version 4.1-ESV-R7
    3: 			     10 September 2012
    4: 
    5: 			      Release Notes
    6: 
    7: 			      NEW FEATURES
    8: 
    9: Version 4.1-ESV-R7 is a security release of an extended support version (ESV)
   10: release.  ESVs are intended for users who have longer upgrade constraints.
   11: Please see our web page http://www.isc.org/downloads/extended-support for
   12: more information on ESVs.
   13: 
   14: ISC DHCP 4.1.x includes several new DHCPv6 features that were not included
   15: in DHCP 4.0.x.  These include:
   16: 
   17: - Support for the rapid-commit option on the client side
   18: 
   19: - Prefix Delegation support
   20: 
   21: - IA_TA address support
   22: 
   23: - A basic DHCPv6 relay agent
   24: 
   25: - Basic and partial DHCPv6 leasequery support
   26: 
   27: There are a number of DHCPv6 limitations and features missing in this
   28: release, which will be addressed in the future:
   29: 
   30: - Only Solaris, Linux, FreeBSD, NetBSD, and OpenBSD are supported.
   31: 
   32: - Only a single address is supported per IA.
   33: 
   34: - DHCPv6 includes human-readable text in status code messages. These
   35:   should be configurable, and probably localized via gettext() or the
   36:   like.
   37: 
   38: - The "host-identifier" option is limited to a simple token.
   39: 
   40: - The client and server can only operate DHCPv4 or DHCPv6 at a time,
   41:   not both.  To use both protocols simultaneously, two instances of the
   42:   relevant daemon are required, one with the '-6' command line option.
   43: 
   44: For information on how to install, configure and run this software, as
   45: well as how to find documentation and report bugs, please consult the
   46: README file.
   47: 
   48: ISC DHCP uses standard GNU configure for installation. Please review the
   49: output of "./configure --help" to see what options are available.
   50: 
   51: The system has only been tested on Linux, FreeBSD, and Solaris, and may not
   52: work on other platforms. Please report any problems and suggested fixes to
   53: <dhcp-users@isc.org>.
   54: 
   55: 			Changes since 4.1-ESV-R6
   56: 
   57: - Existing legacy unit-tests have been migrated to Automated Test
   58:   Framework (ATF). Several new tests have been developed. To enable
   59:   unit-tests, please use --with-atf in configure script. A Developer's
   60:   Guide has been added. To generate it, please use make devel in
   61:   the doc directory. It is currently in early stages of development,
   62:   but is expected to grow in the near future. [ISC-Bugs 25901]
   63: 
   64: ! An issue with the use of lease times was found and fixed.  Making
   65:   certain changes to the end time of an IPv6 lease could cause the
   66:   server to abort.  Thanks to Glen Eustace of Massey University,
   67:   New Zealand for finding this issue.
   68:   [ISC-Bugs #30281]
   69:   CVE: CVE-2012-3955
   70: 
   71: 			Changes since 4.1-ESV-R5
   72: 
   73: - Correct code to calculate timing values in client to compare
   74:   rebind value to infinity instead of renew value.
   75:   Thanks to Chenda Huang from H3C Technologies Co., Limited
   76:   for reporting this issue.
   77:   [ISC-Bugs #29062]
   78: 
   79: - Fix some issues in the code for parsing and printing options.
   80:   [ISC-Bugs #22625] - properly print options that have several fields
   81:   followed by an array of something for example "fIa"
   82:   [ISC-Bugs #27289] - properly parse options in declarations that have
   83:   several fields followed by an array of something for example "fIa"
   84:   [ISC-Bugs #27296] - properly determine if we parsed a 16 or 32 bit
   85:   value in evaluate_numeric_expression (extract-int).
   86:   [ISC-Bugs #27314] - properly parse a zero length option from
   87:   a lease file.  Thanks to Marius Tomaschewski from SUSE for the report
   88:   and prototype patch for this ticket as well as ticket 27289.
   89: 
   90: ! Previously the server code was relaxed to allow packets with zero
   91:   length client ids to be processed.  Under some situations use of
   92:   zero length client ids can cause the server to go into an infinite
   93:   loop.  As such ids are not valid according to RFC 2132 section 9.14
   94:   the server no longer accepts them.  Client ids with a length of 1
   95:   are also invalid but the server still accepts them in order to
   96:   minimize disruption.  The restriction will likely be tightened in
   97:   the future to disallow ids with a length of 1.
   98:   Thanks to Markus Hietava of Codenomicon CROSS project for the
   99:   finding this issue and CERT-FI for vulnerability coordination.
  100:   [ISC-Bugs #29851]
  101:   CVE: CVE-2012-3571
  102: 
  103: ! A pair of memory leaks were found and fixed.  Thanks to
  104:   Glen Eustace of Massey University, New Zealand for finding
  105:   this issue.
  106:   [ISC-Bugs #30024]
  107:   CVE: CVE-2012-3954
  108: 
  109: 			Changes since 4.1-ESV-R5rc2
  110: 
  111: - None
  112: 
  113: 			Changes since 4.1-ESV-R5rc1
  114: 
  115: - Rotate the lease file when running in v6 mode.
  116:   Thanks to Christoph Moench-Tegeder at Astaro for the
  117:   report and the first version of the patch.
  118:   [ISC-Bugs #24887]
  119: 
  120: 			Changes since 4.1-ESV-R5b1
  121: 
  122: - None
  123: 
  124: 			Changes since 4.1-ESV-R4
  125: 
  126: - Fixed the code that checks if an address the server is planning
  127:   to hand out is in a reserved range.  This would appear as
  128:   the server being out of addresses in pools with particular ranges.
  129:   [ISC-Bugs #26498]
  130: 
  131: - Tidy up the receive calls and eliminate the need for found_pkt.
  132:   [ISC-Bugs #25066]
  133: 
  134: - Add support for Infiniband over sockets to the server and
  135:   relay code.  We've tested this on Solaris and hope to expand
  136:   support for Infiniband in the future.  This patch also corrects
  137:   some issues we found in the socket code.
  138:  [ISC-Bugs #24245]
  139: 
  140: - Add a compile time check for the presence of the noreturn attribute
  141:   and use it for log_fatal if it's available.  This will help code
  142:   checking programs to eliminate false positives.
  143:   [ISC-Bugs #27539]
  144: 
  145: - Fixed many compilation problems ("set, but not used" warnings) for
  146:   gcc 4.6 that may affect Ubuntu 11.10 users.
  147:   [ISC-Bugs #27588]
  148: 
  149: - Remove outdated note in the description of the bootp keyword about the
  150:   option not satisfying the requirement of failover peers for denying
  151:   dynamic bootp clients.
  152:   [ISC-bugs #28574]
  153: 
  154: - Multiple items to clean up IPv6 address processing.
  155:   When processing an IA that we've seen check to see if the
  156:   addresses are usable (not in use by somebody else) before
  157:   handing it out.
  158:   When reading in leases from the file discard expired addresses.
  159:   When picking an address for a client include the IA ID in
  160:   addition to the client ID to generally pick different addresses
  161:   for different IAs.
  162:   [ISC-Bugs #23138] [ISC-Bugs #27945] [ISC-Bugs #25586]
  163:   [ISC-Bugs #27684]
  164: 
  165: - Remove unnecessary checks in the lease query code and clean up
  166:   several compiler issues (some dereferences of NULL and treating
  167:   an int as a boolean).
  168:   [ISC-Bugs #26203]
  169: 
  170: - Fix the NA and PD allocation code to handle the case where a client
  171:   provides a preference and the server doesn't have any addresses or
  172:   prefixes available.  Previoulsy the server ignored the request with
  173:   this patch it replies with a NoAddrsAvail or NoPrefixAvail response.
  174:   By default the code performs according to the errata of August 2010
  175:   for RFC 3315 section 17.2.2; to enable the previous style see the
  176:   section on RFC3315_PRE_ERRATA_2010_08 in includes/site.h.  This option
  177:   may be removed in the future.
  178:   Thanks to Jiri Popelka at Red Hat for the patch.
  179:   [ISC-Bugs #22676]
  180: 
  181: - Fix up some issues found by static analysis.
  182:   A potential memory leak and NULL dereference in omapi.
  183:   The use of a boolean test instead of a bitwise test in dst.
  184:   [ISC-Bugs #28941]
  185: 
  186: 			Changes since 4.1-ESV-R3
  187: 
  188: - Add AM_MAINTAINER_MODE to configure.ac to avoid rebuilding
  189:   configuration files.  [ISC-Bugs #24107]
  190:  
  191: ! Add a check for a null pointer before calling the regexec function.
  192:   Without this check we could, under some circumstances, pass
  193:   a null pointer to the regexec function causing it to segfault.
  194:   Thanks to a report from BlueCat Networks.
  195:   [ISC-Bugs #26704].
  196:   CVE: CVE-2011-4539
  197: 
  198: 			Changes since 4.1-ESV-R3b1
  199: 
  200: - Compilation fix for gcc 4.5 or newer in server/ddns.c
  201:   [ISC-Bugs #24973]
  202: 
  203: - Strict checks for content of domain-name DHCPv4 option can now be 
  204:   configured during compilation time. Even though RFC2132 does not allow 
  205:   to store more than one domain in domain-name option, such behavior is 
  206:   now enabled by default, but this may change some time in the future.
  207:   See ACCEPT_LIST_IN_DOMAIN_NAME define in includes/site.h.
  208:   [ISC-Bugs #24167]
  209: 
  210: ! Two packets were found that cause a server to halt.  The code
  211:   has been updated to properly process or reject the packets as
  212:   appropriate.  Thanks to David Zych at University of Illinois
  213:   for reporting this issue.  [ISC-Bugs #24960]
  214:   One CVE number for each class of packet.
  215:   CVE-2011-2748
  216:   CVE-2011-2749
  217: 
  218: 			Changes since 4.1-ESV-R2
  219: 
  220: - DHCPv6 server now responds properly if client asks for a prefix that
  221:   is already assigned to a different client. [ISC-Bugs #23948]
  222: 
  223: - Fix the handling of connection requests on the failover port.
  224:   This was a security issue in 4.2.0 but is not in  4.1.x.
  225:   [ISC-Bugs #22679]
  226: 
  227: - When processing the format flags for a given option consume the
  228:   flag indicating an optional value correctly.  A symptom of this
  229:   bug was an infinite loop when trying to parse the slp-service-scope
  230:   option.  Thanks to a patch from Marius Tomaschewski.
  231:   [ISC-Bugs #22055]
  232: 
  233: - Modify the dlpi code to accept getmsg() returning a positive value.
  234:   [ISC-Bugs #22824]
  235: 
  236: - Removed the restriction on using IPv6 addresses in IPv4 mode.  This
  237:   allows IPv4 options which contain IPv6 addresses to be specified.  For
  238:   example the 6rd option can be specified and used like this:
  239:   [ISC-Bugs #23039]
  240: 
  241: 	option 6rd code 212 = { integer 8, integer 8,
  242: 				ip6-address, array of ip-address };
  243: 	option 6rd 16 10 2001:: 1.2.3.4, 5.6.7.8;
  244: 
  245: - Add the option "--no-pid" to the client, relay and server code,
  246:   to disable writing a pid file.  Add the option "-pf pidfile"
  247:   to the relay to allow the user to supply the pidfile name at
  248:   runtime.  Add the "with-relay6-pid-file" option to configure
  249:   to allow the user to supply the pidfile name for the relay
  250:   in v6 mode at configure time.
  251:   [ISC-Bugs #23351] [ISC-Bugs #17541]
  252: 
  253: - 'dhclient' no longer waits a random interval after first starting up to
  254:   begin in the INIT state.  This conforms to RFC 2131, but elects not to
  255:   implement a 'SHOULD' direction in section 4.1. [ISC-Bugs #19660]
  256:   
  257: - Added 'initial-delay' parameter that specifies maximum amount of time 
  258:   before client goes to the INIT state. The default value is 0. In previous 
  259:   versions of the code client could wait up to 5 seconds. The old behavior 
  260:   may be restored by using 'initial-delay 5;' in the client config file.
  261:   [ISC-Bugs #19660]
  262: 
  263: - ICMP ping-check should now sit closer to precisely the number of seconds
  264:   configured (or default 1), due to making use of the new microsecond
  265:   scale timer internally to dhcpd.  This corrects a bug where the server
  266:   may immediately timeout an ICMP ping-check if it was made late in the
  267:   current second. [ISC-Bugs #19660]
  268: 
  269: - The DHCP client will schedule renewal and rebinding events in
  270:   microseconds if the DHCP server provided a lease-time that would result
  271:   in sub-1-second timers.  This corrects a bug where a 2-second or lower
  272:   lease-time would cause the DHCP client to enter an infinite loop by
  273:   scheduling renewal at zero seconds. [ISC-Bugs #19660]
  274: 
  275: - Client lease records are recorded at most once every 15 seconds.  This
  276:   keeps the client from filling the lease database disk quickly on very small
  277:   lease times. [ISC-Bugs #19660]
  278: 
  279: - To defend against RFC 2131 non-compliant DHCP servers which fail to
  280:   advertise a lease-time (either mangled, or zero in value) the DHCP
  281:   client now adds the server to the reject list ACL and returns to INIT
  282:   state to hopefully find an RFC 2131 compliant server (or retry in INIT
  283:   forever). [ISC-Bugs #19660]
  284: 
  285: - Parameters configured to evaluate from user defined function calls can
  286:   now be correctly written to dhcpd.leases (as on 'on events' or dynamic
  287:   host records inserted via OMAPI).  [ISC-Bugs #22266]
  288: 
  289: - If a 'next-server' parameter is configured in a dynamic host record via
  290:   OMAPI as a domain name, the syntax written to disk is now correctly parsed
  291:   upon restart.  [ISC-Bugs #22266]
  292: 
  293: - The DHCP server now responds to DHCPLEASEQUERY messages from agents using
  294:   IP addresses not covered by a subnet in configuration.  Whether or not to
  295:   respond to such an agent is still governed by the 'allow leasequery;'
  296:   configuration parameter, in the case of an agent not covered by a configured
  297:   subnet the root configuration area is examined. Server now also returns
  298:   vendor-class-id option, if client sent it. [ISC-Bugs #21094]
  299: 
  300: - Documentation fixes
  301:   [ISC-Bugs #17959] add text to AIX section describing how to have it send
  302:   responses to the all-ones address.
  303:   [ISC-Bugs #19615] update the includes in dhcpctl/dhcpctl.3 to be more correct
  304:   [ISC-Bugs #20676] update dhcpd.conf.5 to include the RFC numbers for DDNS
  305: 
  306: - Relay no longer crashes, when DHCP packet is received over interface without
  307:   any IPv4 address assigned. [ISC-Bugs #22409]
  308: 
  309: - Linux Packet Filter interface improvement. sockaddr_pkt structure is used,
  310:   rather than sockaddr. Packet etherType is now forced to ETH_P_IP.
  311:   [ISC-Bugs #18975]
  312: 
  313: - Minor code cleanups - but note port change for #23196
  314:   [ISC-Bugs #23470] - Modify when an ignore return macro is defined to
  315:   handle unsed error return warnings for more versions of gcc.
  316:   [ISC-Bugs #23196] - Modify the reply handling in the server code to
  317:   send to a specified port rather than to the source port for the incoming
  318:   message.  Sending to the source port was test code that should have
  319:   been removed.  The previous functionality may be restored by defining
  320:   REPLY_TO_SOURCE_PORT in the includes/site.h file.  We suggest you don't
  321:   enable this except for testing purposes.
  322:   [ISC-Bugs #22695] - Close a file descriptor in an error path.
  323:   [ISC-Bugs #19368] - Tidy up variable types in validate_port.
  324: 
  325: - Code cleanup
  326:   [ISC-Bugs #13151] remove obsolete PROTO, KandR, INLINE and ANSI_DECL macros
  327: 
  328: - Compilation problem with gcc4.5 and omshell.c resolved. [ISC-Bugs #23831]
  329: 
  330: - Client Script fixes
  331:   [ISC-Bugs #23045] Typos in client/scripts/openbsd
  332:   [ISC-Bugs #23565] In the client scripts add a zone id (interface id) if
  333:   the domain search address is link local.
  334:   [ISC-Bugs #1277] In some of the client scripts add code to handle the
  335:   case of the default router information being changed without the address
  336:   being changed.
  337: 
  338: - Enlarge the buffer size used by the Omshell code and some of the
  339:   print routines to allow for greater than 60 characters or, when
  340:   printing as hex strings, 20 characters.  [ISC-Bugs #22743]
  341: 
  342: - In Solaris 11 switch to using sockets instead of DLPI, thanks
  343:   to a patch form Oracle.  [ISC-Bugs #24634].
  344: 
  345: 			Changes since 4.1-ESV-R1
  346: 
  347: ! In dhclient check the data for some string options for
  348:   reasonableness before passing it along to the script that
  349:   interfaces with the OS.
  350:   [ISC-Bugs #23722]
  351:   CVE: CVE-2011-0997
  352: 
  353: 			Changes since 4.1-ESV
  354: 
  355: ! When processing a request in the DHCPv6 server code that specifies
  356:   an address that is tagged as abandoned (meaning we received a
  357:   decline request for it previously) don't attempt to move it from
  358:   the inactive to active pool as doing so can result in the server
  359:   crshing on an assert failure.  Also retag the lease as active
  360:   and reset its timeout value.
  361:   [ISC-Bugs #21921]
  362: 
  363: 			Changes since 4.1.2
  364: 
  365: - ./configure on longer searches for -lcrypto to explicitly link against.
  366:   This fixes a bug where 'dhclient' would have shared library dependencies
  367:   on '/usr/lib'.  [ISC-Bugs #21967]
  368: 
  369: - Restore printing of values in omshell to the style pre 21585.  For
  370:   21585 we changed the print routines to always display time values
  371:   as a hex list.  This had a side effect of printing all data strings
  372:   as a hex list.  We shall investigate other ways of displaying time
  373:   values more usefully.  [ISC-Bugs #22626]
  374: 
  375: 			Changes since 4.1.2rc1
  376: 
  377: ! Handle a relay forward message with an unspecified address in the
  378:   link address field.  Previously such a message would cause the
  379:   server to crash.  Thanks to a report from John Gibbons.  [ISC-Bugs #21992]
  380:   CERT: VU#102047 CVE: CVE-2010-3611
  381: 
  382: 			Changes since 4.1.2b1
  383: 
  384: - Update the code to parse dhcpv6 lease files to accept a semi-colon at
  385:   the end of the max-life and preferred-life clauses.  In order to be
  386:   backwards compatible with older lease files not finding a semi-colon
  387:   is also accepted.  [ISC-Bugs #22303].
  388: 
  389:                         Changes since 4.1.1
  390: 
  391: - Cleaned up some compiler warnings
  392: 
  393: - Prohibit including lease time information in a response to a DHCP INFORM
  394:   Bug ticket 21092.
  395: 
  396: ! Accept a client id of length 0 while hashing.  Previously the server would
  397:   exit if it attempted to hash a zero length client id, providing attackers
  398:   with a simple denial of service attack.  Bug ticket 21253.
  399:   CERT: VU#541921 - CVE: CVE-2010-2156
  400: 
  401: - A bug was fixed that could cause the DHCPv6 server to advertise/assign a
  402:   previously allocated (active) lease to a client that has changed subnets,
  403:   despite being on different shared networks.  Dynamic prefixes specifically
  404:   allocated in shared networks also now are not offered if the client has
  405:   moved.  [ISC-Bugs #21152]
  406: 
  407: - Add declaration for variable in debug code in alloc.c.  [ISC-Bugs #21472]
  408: 
  409: - Documentation cleanup covering multiple tickets
  410:   [ISC-Bugs #20265] [ISC-Bugs #20259] [ISC-Bugs #19536] minor cleanup
  411:   [ISC-Bugs #20263] add text describing some default values
  412:   [ISC-Bugs #20193] single quotes at the start of a line indicate a control
  413:   line to nroff, escape them if we actually want a quote.
  414:   [ISC-Bugs #18916] sync the pointer to web pages amongst the different docs
  415:   [ISC-Bugs #20107] clarify description of ia-pd and ia-prefix.
  416:   [ISC-Bugs #20245] clarify editing the failover state in a lease file to put
  417:   a server into the PARTNER-DOWN state.
  418:  
  419: - 'get-host-names true;' now also works even if 'use-host-decl-names true;'
  420:   was also configured.  The nature of this repair also fixes another
  421:   error; the host-name supplied by a client is no longer overridden by a
  422:   reverse lookup of the lease address.  Thanks to a patch from Wilco Baan
  423:   Hofman supplied to us by the Debian package maintenance team.
  424:   [ISC-Bugs #21691] {Debian Bug#509445}
  425: 
  426: - The .TH tag for the dhcp-options manpage was typo repaired
  427:   thanks to a report from jidanni and the Debian package maintenance
  428:   team.  [ISC-Bugs #21676] {Debian Bug#563613}
  429:  
  430: - More documentation changes - primarily to put the options in the dhclient
  431:   and dhcpd man pages into the standard form.  Thanks in part to a patch
  432:   from David Cantrell at Red Hat.
  433:   [ISC-Bugs #20264] and parts of [ISC-Bugs #17744] dhclient.8 changes
  434: 
  435: - Minor compilation errors - type mismatches, extra semi-colons after macros
  436:   [ISC-Bugs #20884] [ISC-Bugs #20953] [ISC-Bugs #20955]
  437: 
  438: - Add code to clear the pointer to an object in an OMAPI handle when the
  439:   object is freed due to a dereference.  [ISC-Bugs #21306]
  440: 
  441: - Fixed a bug that leaks host record references onto lease structures,
  442:   causing the server to apply configuration intended for one host to any
  443:   other innocent clients that come along later.  [ISC-Bugs #22018]
  444: 
  445: - Minor code fixes
  446:   [ISC-Bugs #19566] When trying to find the zone for a name for ddns allow
  447:   the name to be at the apex of the zone.
  448:   [ISC-Bugs #19617] Restrict length of interface name read from command line
  449:   in dhcpd - based on a patch from David Cantrell at Red Hat.
  450:   [ISC-Bugs #20039] Correct some error messages in dhcpd.c
  451:   [ISC-Bugs #20070] Better range check on values when creating a DHCID.
  452:   [ISC-Bugs #20198] Avoid writing past the end of the field when adding 
  453:   overly long file or server names to a packet and add a log message
  454:   if the configuration supplied overly long names for these fields.
  455:   Thanks to Martin Pala.
  456:   [ISC-Bugs #21497] Add a little more randomness to rng seed in client
  457:   thanks to a patch from Jeremiah Jinno.
  458: 
  459: - Correct error handling in DLPI [ISC-Bugs #20378]
  460: 
  461: - Remove __sun__ and __hpux__ typedefs in osdep.h as they are now being
  462:   checked in configure.  [ISC-Bugs #20443]
  463: 
  464: - Modify how the cmsg header is allocated the v6 send and received routines
  465:   to compile on more compilers.  [ISC-Bugs #20524]
  466: 
  467: - When parsing a domain name free the memory for the name after we are
  468:   done with it.  [ISC-Bugs #20824]
  469: 
  470: - Add an elapsed time option to the release message and refactor the
  471:   code to move most of the common code to a single routine.
  472:   [ISC-Bugs #21171].
  473: 
  474: - Parse date strings more properly - the code now handles semi-colons in
  475:   date strings correctly.  Thanks to a patch from Jiri Popelka at Red Hat.
  476:   [ISC-Bugs #21501, #20598]
  477: 
  478: - Fixes to lease input and output.
  479:   [ISC-Bugs #20418] - Some systems don't support the "%s" argument to
  480:   strftime, paste together the same string using mktime instead.
  481:   [ISC-Bugs #19596] - When parsing iaid values accept printable
  482:   characters.
  483:   [ISC-Bugs #21585] - Always print time values in omshell as hex
  484:   instead of ascii if the values happen to be printable characters.
  485: 
  486: - Minor changes for scripts, configure.ac and Makefiles
  487:   [ISC-Bugs #19147] Use domain-search instead of domain-name in manual and
  488:                     example conf file.  Thanks to a patch from David Cantrell
  489:                     at Red Hat.
  490:   [ISC-Bugs #19761] Restore address when doing a rebind in DHCPv6
  491:   [ISC-Bugs #19945] Properly close the quote on some arguments.
  492:   [ISC-Bugs #20952] Add 64 bit types to configure.ac
  493:   [ISC-Bugs #21308] Add "PATH=" to CLIENT_PATH envrionment variable
  494: 
  495: ! Handle pipe failures more gracefully.  Some OSes pass a SIGPIPE
  496:   signal to a process and will kill the process if the signal isn't
  497:   caught.  This patch adds code to turn off the SIGPIPE signal via
  498:   a setsockopt() call and to ignore the SIGPIPE signal in case the
  499:   OS doesn't support the necessary setsockopt() option.  This problem
  500:   was found during internal testing when the two servers in a failover
  501:   pair were repeatedly unable to communicate for longer than the
  502:   max-response-delay value.  Eventually one of the pair attempted a
  503:   write() call at just the same time as the other server killed the
  504:   connection and caused an uncaught SIGPIPE signal which caused the
  505:   OS to kill the server.
  506:   This is a minor security issue.  It is a security issue as it can 
  507:   cause a server to stop.  It is minor as the attacker would need to
  508:   be able to interrupt traffic between the partners in a failover 
  509:   pair for max-response-delay seconds at will - in which case the 
  510:   defender has bigger problems than the DHCP server being killed.
  511:   Using the NIST CVSS security vulnerability rating system this
  512:   issue scored 1.2, meaning it is not a major risk for users.
  513:   [ISC-Bugs #22269]
  514: 
  515:                         Changes since 4.1.1rc1
  516: 
  517: - When using 'ignore client-updates;', the FQDN returned to the client
  518:   is no longer truncated to one octet.
  519: 
  520:                         Changes since 4.1.1b3
  521: 
  522: - None.
  523: 
  524: 			Changes since 4.1.1b2
  525: 
  526: - Fix test in dhcp_interface_signal_handler to check that the inner handler
  527:   has a signal_handler before calling it.
  528: 
  529: - Both host and subnet6 configuration groups are now included whether a
  530:   fixed-address6 (DHCPv6) is in use or not.  Host scoped configuration takes
  531:   precedence.  This fixes two bugs, one where host scoped configuration
  532:   would not be included from a non-fixed-address6 host record, and the equal
  533:   and opposite bug where subnet6 scoped configuration would not be used when
  534:   over-riding values were not present in a matching fixed-address6 host
  535:   configuration.
  536: 
  537: - ./configure now checks to ensure the intX_t and u_intX_t types are defined,
  538:   correcting a compilation failure when using Sun's compiler.
  539: 
  540: - Modified the handling of a connection to avoid releasing the omapi io
  541:   object for the connection while it is still in use.  One symptom from
  542:   this error was a segfault when a failover secondary attempted to connect
  543:   to the failover primary if their clocks were not synchronized.
  544: 
  545: 			Changes since 4.1.1b1
  546: 
  547: - Remove infinite loop in token_print_indent_concat().
  548: 
  549: - Memory leak in the load_balance_mine() function is fixed.  This would
  550:   leak ~20-30 octets per DHCPDISCOVER packet while failover was in use
  551:   and in normal state.
  552: 
  553: - Various compilation fixes have been included for the memory related
  554:   DEBUG #defines in includes/site.h.
  555: 
  556: - Fixed Linux client script 'unary operator expected' errors with DHCPv6.
  557: 
  558: - Fixed setting hostname in Linux hosts that require hostname argument
  559:   to be double-quoted.  Also allow server-provided hostname to
  560:   override hostnames 'localhost' and '(none)'.
  561: 
  562: - Added client support for setting interface MTU and metric, thanks to
  563:   Roy "UberLord" Marples <roy@marples.name>.
  564: 
  565: - Fixed failover reconnection retry code to continue to retry to reconnect
  566:   rather than restarting the listener.
  567: 
  568: - Compilation on Solaris with USE_SOCKETS defined in includes/site.h has
  569:   been repaired.  Other USE_ overrides should work better.
  570: 
  571: - A check for the local flavor of IFNAMSIZ had a broken 'else' condition,
  572:   that probably still resulted in the correct behaviour (but wouldn't use
  573:   a larger defined value provided by the host OS).
  574: 
  575: - Fixed a bug where an OMAPI socket disconnection message would not result
  576:   in scheduling a failover reconnection, if the link had not negotiated a
  577:   failover connect yet (e.g.: connection refused, asynch socket connect()
  578:   timeouts).
  579: 
  580: - A bug was fixed that caused the 'conflict-done' state to fail to be parsed
  581:   in failover state records.
  582: 
  583: ! A stack overflow vulnerability was fixed in dhclient that could allow
  584:   remote attackers to execute arbitrary commands as root on the system,
  585:   or simply terminate the client, by providing an over-long subnet-mask
  586:   option.  CERT VU#410676 - CVE-2009-0692
  587: 
  588: - Versions 3.0.x syntax with multiple name->code option definitions is now
  589:   supported.  Note that, similarly to 3.0.x, for by-code lookups only the
  590:   last option definition is used.
  591: 
  592: - Fixed a bug where a time difference of greater than 60 seconds between a
  593:   failover pair could cause the primary to crash on contact with the
  594:   secondary.  Thanks to a patch from Steinar Haug.
  595: 
  596: - Don't look for IPv6 interfaces on Linux when running in DHCPv4 mode.
  597:   Thanks to patches from Matthew Newton and David Cantrell.
  598: 
  599: - Secondary servers in a failover pair will now perform ddns removals if
  600:   they had performed ddns updates on a lease that is expiring, or was
  601:   released through the primary.  As part of the same fix, stale binding scopes
  602:   will now be removed if a change in identity of a lease's active client is
  603:   detected, rather than simply if a lease is noticed to have expired (which it
  604:   may have expired without a failover server noticing in some situations).
  605: 
  606: - A patch supplied by David Cantrell at RedHat was applied that detects
  607:   invalid calling parameters given to the ns_name_ntop() function.
  608:   Specifically, it detects if the caller passed a pointer and size pair
  609:   that causes the pointer to integer-wrap past zero.
  610: 
  611: ! Fixed a fenceposting bug when a client had two host records configured,
  612:   one using 'uid' and the other using 'hardware ethernet'.  CVE-2009-1892
  613: 
  614: 			Changes since 4.1.0
  615: 
  616: - Validate the argument to the -p option.
  617: 
  618: - The notorious 'option <unknown> ... larger than buffer' log line,
  619:   which is seen in some malformed DHCP client packets, was modified.
  620:   It now logs the universe name, and does not log the length values
  621:   (which are bogus corruption read from the packet anyway).  It also
  622:   carries a hopefully more useful explanation.
  623: 
  624: - A bug was fixed that caused the server not to answer some valid Solicit
  625:   and Request packets, if the dynamic range covering any requested addresses
  626:   had been deleted from configuration.
  627: 
  628: - Suppress spurious warnings from configure about --datarootdir
  629: 
  630: - Update the code to deal with GCC 4.3.  This included two sets of changes.
  631:   The first is to the configuration files to include the use of
  632:   AC_USE_SYSTEM_EXTENSIONS.  The second is to deal with return values that
  633:   were being ignored.
  634: 
  635: - The db-time-format option was documented in manpages.
  636: 
  637: - Using reserved leases no longer results in 'lease with binding state
  638:   free not on its queue' error messages, thanks to a patch from Frode
  639:   Nordahl.
  640: 
  641: - DDNS removal routines were updated so that the DHCID is not removed until
  642:   the client has been deprived of all A and AAAA records (not only the last
  643:   one of either of those).  This resolves a bug where dual stack clients
  644:   would not be able to regain their names after either expiration event.
  645: 
  646: - Fix a build error in dhcrelay, using older versions of gcc with
  647:   dhcpv6 disabled.
  648: 
  649: - Two uninitialized stack structures are now memset to zero, thanks to
  650:   patch from David Cantrell at Red Hat.
  651: 
  652: - Fixed a cosmetic bug where pretty-printing valid domain-search options would
  653:   result in an erroneous error log message ('garbage in format string').
  654: 
  655: - A bug in DLPI packet transmission (Solaris, HP/UX) that caused the server
  656:   to stop receiving packets is fixed.  The same fix also means that the MAC
  657:   address will no longer appear 'bogus' on DLPI-based systems.
  658: 
  659: - A bug in select handling was discovered where the results of one select()
  660:   call were discarded, causing the server to process the next select() call
  661:   and use more system calls than required.  This has been repaired - the
  662:   sockets will be handled after the first return from select(), resulting in
  663:   fewer system calls.
  664: 
  665: - The update-conflict-detection feature would leave an FQDN updated without
  666:   a DHCID (still currently implemented as a TXT RR).  This would cause later
  667:   expiration or release events to fail to remove the domain name.  The feature
  668:   now also inserts the client's up to date DHCID record, so records may safely
  669:   be removed at expiration or release time.  Thanks to a patch submitted by
  670:   Christof Chen.
  671: 
  672:                         Changes since 4.1.0b1
  673: 
  674: - A missing "else" in dhcrelay.c could have caused an interface not to
  675:   be recognized.
  676: 
  677: 			Changes since 4.1.0a2
  678: 
  679: - A cosmetic bug in DHCPDECLINE processing was fixed which caused all
  680:   successful DHCPDECLINEs to be logged as "not found" rather than
  681:   "abandoned".
  682: 
  683: - Added configuration file examples for DHCPv6.
  684: 
  685: - Some failover debugging #defines have been better defined and some
  686:   high frequency messages moved to a deeper debugging symbol.
  687: 
  688: - The CLTT parameter in failover is now only updated by client activity,
  689:   and not by failover binding updates (taking on the peer's CLTT).
  690: 
  691: - Failover BNDUPD messages are now discarded if they conflict with an
  692:   update that has been transmitted, but not acknowledged.
  693: 
  694: - A bug cleaning up unknown-xxx temporary option definitions was fixed.
  695: 
  696: - Delayed-ack is now a compile-time option, compiled out by default.
  697:   This feature is simply too experimental for right now, and causes
  698:   some problems to some failover installations.  We will revisit this
  699:   in future releases.
  700: 
  701: - The !inet_pton() call in res_mkupdrec was adjusted to '<= 0' as
  702:   inet_pton returns either 1, 0, or -1.
  703: 
  704: - A dhclient-script for MacOS X has been included, which enables
  705:   'dhclient -6' support.
  706: 
  707: 			Changes since 4.1.0a1
  708: 
  709: - Corrected list of failover state values in dhcpd man page.
  710: 
  711: - Fixed a bug that caused some request types to be logged incorrectly.
  712: 
  713: - Clients that sent a parameter request list containing the
  714:   routers option before the subnet mask option were receiving
  715:   only the latter.  Fixed.
  716: 
  717: - The server wasn't always sending the FQDN option when it should.
  718: 
  719: - A partner-down failover server no longer emits 'peer holds all free leases'
  720:   if it is able to newly-allocate one of the peer's leases.
  721: 
  722: - Fixed a coredump when adding a class via OMAPI.
  723: 
  724: - Check whether files are zero length before trying to parse them.
  725: 
  726: - Ari Edelkind's PARANOIA patch has been included and may be compiled in
  727:   via two ./configure parameters, --enable-paranoia and
  728:   --enable-early-chroot.
  729: 
  730: - ./configure was extended to cover many optional build features, such
  731:   as failover, server tracing, debugging, and the execute() command.
  732: 
  733: - There is now a default 1/4 of a second scheduled delay between delayed
  734:   fsync()'s, it can be configured by the max-ack-delay configuration
  735:   parameter.
  736: 
  737: - A bug was fixed where the length of a hostname was miscalculated, so that
  738:   hosts were given odd-looking domain names ("foo.bar.ba.example.com").
  739: 
  740: - Shared network selection should be done from the innermost relay
  741:   valid link-address field, rather than the outermost.
  742: 
  743: - Prefix pools are attached to shared network scopes.
  744: 
  745: - Merged IA_XX related structures.
  746: 
  747: - Add DHCPv6 files in configure.
  748: 
  749: - A memory leak when using omapi has been fixed.
  750: 
  751: - DHCPv6 vendor-class options (VSIO) are now only sent when they appear
  752:   on the DHCPv6 ORO.  This resolves a bug where VSIO options were placed
  753:   in IA_NA encapsulated options fields.
  754: 
  755: - Integrated client with stateless, temporary address and prefix delegation
  756:   support.
  757: 
  758: - A double-dereference in dhclient transmission of DHCPDECLINEs was
  759:   repaired.
  760: 
  761: - Fix handling of format code 'Z'.
  762: 
  763: - Support "-1" argument in DHCPv6.
  764: 
  765: - Merge DHCPv6-only "dhcrelay6" into general-purpose "dhcrelay" (use
  766:   "-6" option to select DHCPv6 mode).
  767: 
  768: - Fix handling of -A and -a flags in dhcrelay; it was failing to expand
  769:   packet size as needed to add relay agent options.
  770: 
  771: - A bug in subnet6 parsing where options contained in subnet6 clauses would
  772:   not be applied to clients addressed within that network was repaired.
  773: 
  774: - When configuring a "subnet {}" or "subnet6 {}" without an explicit
  775:   shared-network enclosing it, the DHCP software would synthesize a
  776:   shared-network to contain the subnet.  However, all configuration
  777:   parameters within the subnet more intuitively belong "to any client
  778:   on that interface", or rather the synthesized shared-network.  So,
  779:   when a shared-network is synthesized, it is used to contain the
  780:   configuration present inside the subnet {} clause.  This means that
  781:   the configuration will be valid for all clients on that network, not
  782:   just those addressed out of the stated subnet.  If you intended the
  783:   opposite, the workaround is to explicitly configure an empty
  784:   shared-network.
  785: 
  786: - A bug was fixed where Information-Request processing was not sourcing
  787:   configured option values.
  788: 
  789: - A warning was added since the DHCPv6 processing software does not yet
  790:   support class statements.
  791: 
  792: - Compliation warnings on GCC 4.3 relating to bootp source address
  793:   selection were repaired.
  794: 
  795: - The v6 BSD socket method was updated to use a single UDP BSD socket
  796:   no matter how many interfaces are involved, differentiating the
  797:   interfaces the packets were received on by the interface index supplied
  798:   by the OS.
  799: 
  800: - The relay agent no longer listens to the All DHCP Servers Multicast
  801:   address.
  802: 
  803: - A bug was fixed in data_string_sprintfa() where va_start was only called
  804:   once for two invocations of vsprintf() variants.
  805: 
  806: - ERO (RFC 4994) server support.
  807: 
  808: - Basic and partial DHCPv6 leasequery support.
  809: 
  810: - Reliable DHCPv6 release (previous behavior, send release and exit, is
  811:   still available with dhclient -6 -1 -r).
  812: 
  813: 			Changes since 4.0.0 (new features)
  814: 
  815: - Added DHCPv6 rapid commit support.
  816: 
  817: - Added explicit parser support for zero-length DHCP options, such as
  818:   rapid-commit, via format code 'Z'.
  819: 
  820: - It's now possible to update the "ends" field of a lease with OMAPI.
  821:   This is useful if you want not only to release a lease, but also make
  822:   it available for reuse right away.  Hat tip to Christof Chen.
  823: 
  824: - Fixed definition of the iaaddr hash functions to use the correct 
  825:   functions when referencing and dereferencing memory.
  826: 
  827: - Some definitions not in phase with the IANA registry were updated.
  828: 
  829: - Allocated interface IDs are better controlled ('u' bit set to zero,
  830:   reserved IDs avoided).
  831: 
  832: - Unicast options are taken into account only for RENEWs.
  833: 
  834: - NoAddrsAvail answers to SOLICITs are always ADVERTISEs even when a SOLICIT
  835:   carries a rapid-commit option.
  836: 
  837: - Return in place of raise an impossible condition when one tries to release
  838:   an empty active lease.
  839: 
  840: - Timer granularity is now 1/100s in the DHCPv6 client.
  841: 
  842: - The dhclient-script was updated to create a host route for the default
  843:   gateway if the supplied subnet mask for an IPv4 address was a /32.  This
  844:   allows the client to work in 'captive' network environments, where the
  845:   operator does not want clients to crosstalk directly.
  846: 
  847: - MINUS tokens should be parseable again.
  848: 
  849: - Multiple (up to "delayed-ack x;" maximum) DHCPv4 packets are now queued and
  850:   released in bursts after single fsync() events when the upper limit is
  851:   reached or if the receiving sockets go dry.  The practical upshot is
  852:   that fsync-coupled server performance is now multiplicitively increased.
  853:   The default delayed ack limit is 28.  Thanks entirely to a patch from
  854:   Christof Chen.
  855: 
  856: 			Changes since 4.0.0 (bug fixes)
  857: 
  858: - DHCP now builds on AIX.
  859: 
  860: - Exit with warning when DHCPv6-specific statements are used in the
  861:   config file but -6 is not specified.
  862: 
  863: - Fixed "--version" flag in dhcrelay
  864: 
  865: - The 'min-secs' configuration parameter's log message has been updated to
  866:   be more helpful.
  867: 
  868: - The warning logged when an address range doesn't fit in the subnets
  869:   they were declared has been updated to be more helpful and identify the
  870:   typo in configuration that created the spanning addresses.
  871: 
  872: - A bug in failover pool rebalancing that caused POOLREQ message ping-pongs
  873:   was repaired.
  874: 
  875: - A flaw in failover pool rebalancing that could cause POOLREQ messages to
  876:   be sent outside of the min-balance/max-balance scheduled intervals has
  877:   been repaired.
  878: 
  879: - A cosmetic bug during potential-conflict recovery that caused the peer's
  880:   'conflict-done' state message to be logged as 'unknown-state' has been
  881:   repaired.  It is now logged correctly.
  882: 
  883: - A bug was fixed where the 'giaddr' may be used to find the client's subnet
  884:   rather than its own 'ciaddr'.
  885: 
  886: - A log message was introduced to clarify the situation where a failover
  887:   'address' parameter (the server's local address) did not resolve to an
  888:   IPv4 address.
  889: 
  890: - The minimum site code value was set to 224 in 3.1.0 to track RFC3942.  This
  891:   broke a lot of legacy site local configurations.  The new code in place will
  892:   track site local space minimum option codes and logs a warning to encourage
  893:   updates and exploration of site local code migration problems.  Option
  894:   codes less than 128 in site local spaces remain inaccessible.
  895: 
  896: - A possible relay agent option bug was repaired where random server
  897:   initialization state may have been used to signal the relay agent
  898:   information options sub-option code for the 'END' of the option space.
  899: 
  900: - Fixes to allow code to compile and run on Solaris 9.
  901: 
  902: - Fixes to allow code to compile on Mac OS X Leopard (10.5).
  903: 
  904: - When server is configured with options that it overrides, a warning is
  905:   issued when the configuration file is read, rather than at the time the
  906:   option is overridden. This was important, because the warning was given
  907:   every time the option was overridden, which could create a lot of 
  908:   unnecessary logging.
  909: 
  910: - Fixed a compilation problems on platforms that define a value for FDDI,
  911:   which conflicts with a dhcp configuration syntax token by the same name.
  912: 
  913: - When a failover server suspects it has encountered a peer running a
  914:   version 3.0.x failover server, a warning that the failover wire protocol
  915:   is incompatible is printed.
  916: 
  917: - The failover server no longer issues a floating point error if it encounters
  918:   a previously undefined option code.
  919: 
  920: - Fix startup error messages to report a missing "subnet6 declaration", rather
  921:   than a missing "subnet declaration", when running as a DHCPv6 server.
  922: 
  923: - DHCPv6 client timestamp in DUID was based on the year 1970 rather 
  924:   than the year 2000.
  925: 
  926: - Warn when attempting to use a hardware parameter in DHCPv6.
  927: 
  928: - DHCPv6 released resources are now marked as released by the client.
  929: 
  930: - 'Soft' bindings have no more side-effects.
  931: 
  932: 			Changes since 4.0.0b3
  933: 
  934: - The reverse dns name for PTR updates on IPv6 addresses has been fixed to
  935:   use ip6.arpa. rather than default to in-addr.arpa and require user
  936:   configuration.
  937: 
  938: - dhc6_lease_destroy() and dhc6_ia_destroy() now set lease and IA pointers
  939:   to NULL after freeing, to prevent subsequent accesses to freed memory.
  940: 
  941: - The DHCPv6 server would not send the preference option unless the 
  942:   client requested it, via the ORO. This has been fixed, so the DHCPv6
  943:   server will always send the preference value if it is configured.
  944: 
  945: - When addresses were passed as hints to the server in an IA, they were 
  946:   incorrectly handled, sometimes being treated as an error. Now the 
  947:   server will treat these as hints and ignore them if it cannot supply
  948:   a requested address.
  949: 
  950: - If the client had multiple addresses, and one expired (was not renewed
  951:   by the server), the client would continue to attempt to renew the same
  952:   old address over and over.  Now, the client will omit any expired
  953:   addresses from future Confirm, Renew, or Rebind messages.
  954: 
  955: - dhclient -6 will now select renew/rebind timers based upon the longest
  956:   address expiration time rather than the shortest expiration time, in
  957:   order to avoid cascading renewals in the event a server elects not to
  958:   extend one of multiple IAADDR leases.
  959: 
  960: - The server now limits clients that request multiple addresses to one
  961:   address per IA by default, which can be adjusted through the
  962:   "limit-addrs-per-ia" configuration option.
  963: 
  964: - The DHCPv6 client now issues fresh transaction IDs on Renew and Rebind
  965:   message exchanges, rather than using the most recent ID.
  966: 
  967: - The DHCPv6 server now replies to Information-Request messages.
  968: 
  969: - A bug was fixed in the dhclient-script for BSDs to correctly carry error
  970:   codes through some conditions.
  971: 
  972: - The parsing of some options in the dhclient lease file, in particular
  973:   the success DHCPv6 status-code, was fixed.
  974: 
  975: - A bug was fixed that caused the DHCPv6 ORO option to be corrupted with
  976:   seemingly random values.
  977: 
  978: - A reference overleak in DHCPv6 shared network processing was repaired.
  979: 
  980: - ./configure now autodetects local database locations rather than trying
  981:   to put dhcpd.leases and dhclient.leases in /usr/local/var/db, which no
  982:   one ever has.
  983: 
  984: - Regression fix for bug where server advertised a IPv6 address in 
  985:   response to a SOLICIT but would not return the address in response 
  986:   to a REQUEST.
  987: 
  988: - A bug was fixed where the DHCPv6 server puts the NoAddrsAvail status
  989:   code in the IA_NA was fixed.  The status code now appears in the root
  990:   level.
  991: 
  992: 			Changes since 4.0.0b2
  993: 
  994: - Clarified error message when lease limit exceeded
  995: 
  996: - Relative time may now be used as a qualifier for 'allow' and 'deny' access
  997:   control lists.  These directives may be used to assist in re-addressing
  998:   address pools without having to constantly reconfigure the server.  Please
  999:   see 'man dhcpd.conf' for more information on allow/deny 'after time' syntax.
 1000:   Thanks to a patch from Christof Chen.
 1001: 
 1002: - The server will now include multiple IA_NA's and multiple IAADDRs within
 1003:   them, if advertised by the client.  It still only seeks to allocate one
 1004:   new address.
 1005: 
 1006: 			Changes since 4.0.0b1
 1007: 
 1008: - Use different paths for PID and lease files when running in DHCPv4
 1009:   or DHCPv6 mode, so that servers for both protcols can be run
 1010:   simultaneously on a single interface.
 1011: 
 1012: - Fixed a buffer overflow error which could have allowed a denial
 1013:   of service under unusual server configurations
 1014: 
 1015: - Eliminated a spurious error message from the client
 1016: 
 1017: - A number of bugs with the internal handling of lease state on the 
 1018:   server have been fixed. Some of these could cause server crashes.
 1019: 
 1020: - The peer_wants_leases() changes pulled up from 3.1.0 were corrected,
 1021:   'never used' leases will no longer consistently shift between servers
 1022:   on every pool rebalance run.
 1023: 
 1024: - sendmsg()/recvmsg() control buffers are now declared in such a way to
 1025:   ensure they are correctly aligned on all (esp. 64-bit) architectures.
 1026: 
 1027: - The client leasing subsystem was streamlined and corrected to account
 1028:   more closely for changes in client link attachment selection.
 1029: 
 1030: 			Changes since 4.0.0a3
 1031: 
 1032: - The DHCP server no longer requires a "ddns-update-style" statement, 
 1033:   and now defaults to "none", which means DNS updates are disabled.
 1034: 
 1035: - Log messages when failover peer names mismatch have been improved to
 1036:   point out the problem.
 1037: 
 1038: - Bug where server advertised a IPv6 address in response to a SOLICIT 
 1039:   but would not return the address in response to a REQUEST. Thanks to
 1040:   Dennis Kou for finding the bug.
 1041: 
 1042: - Fixed an error causing the server to lock up on lease expiration,
 1043:   reported independently by Jothilingam Vasu and Dennis Kou.
 1044: 
 1045: - Fixed a ./configure bug where compile tests were failing due to
 1046:   "-Werror" (unused variable) rather than the actual test failure.  Lead
 1047:   to inconsistent and unworkable auto-configurations.
 1048: 
 1049: - Compilation with DLPI and -Werror has been repaired.
 1050: 
 1051: - Error in decoding IA_NA option if multiple interfaces are present 
 1052:   fixed by Marcus Goller.
 1053: 
 1054: - DHCPv6 server Confirm message processing has been enhanced - it no
 1055:   longer replies only to clients with host {} records, it now replies
 1056:   as directed in RFC3315 section 18.2.2 - that is, to all clients
 1057:   regardless of the existence of bindings.
 1058: 
 1059: - A core dump during expired lease cleanup has been repaired.
 1060: 
 1061: - DDNS updates state information are now stored in 'binding scopes' that
 1062:   follow the leases through their lifecycles.  This enables DDNS teardowns
 1063:   on leases that are assigned and expired inbetween a server restart (the
 1064:   state is recovered from dhcpd.leases).  Arbitrary user-specified binding
 1065:   scopes ('set var = "value";') are not yet supported.
 1066: 
 1067: - Additional compilation problems on HP/UX have been repaired.
 1068: 
 1069: 			Changes since 4.0.0a2
 1070: 
 1071: - Fix for startup where there are no IPv4 addresses on an interface.
 1072:   Thanks to Marcus Goller for reporting the bug.
 1073: 
 1074: - Fixed file descriptor leak on listen failure. Thanks to Tom Clark.
 1075: 
 1076: - Bug in server configuration parser caused server to get stuck on
 1077:   startup for certain bad pool declarations. Thanks to Guillaume 
 1078:   Knispel for the bug report and fix.
 1079: 
 1080: - Code cleaned to remove warnings reported by "gcc -Wall".
 1081: 
 1082: - DHCPv6 is now the default. You can disable DHCPv6 support using the
 1083:   "--disable-dhcpv6" flag when you run the configure script.
 1084: 
 1085: - An internal database inconsistency bug was repaired where the server
 1086:   would segfault if a client attempted to renew a lease that had been
 1087:   loaded from persistent storage.
 1088: 
 1089: - 'request' and 'also request' syntaxes have been added to accommodate
 1090:   the DHCPv6 client configuration.  'send dhcp6.oro' is no longer
 1091:   necessary.
 1092: 
 1093: - Bug fixed where configuration file parsing did not work with 
 1094:   zero-length options; this made it impossible to set the 
 1095:   rapid-commit option.
 1096: 
 1097: - Bogus messages about host records with IPv4 fixed-addresses being of
 1098:   non-128-bits in length were removed.
 1099: 
 1100: 			Changes since 4.0.0a1
 1101: 
 1102: - Bug in octal parsing fixed. Thanks to Bernd Fuhrmann for the report
 1103:   and fix.
 1104: 
 1105: - Autoconf now supplies proper flags for Solaris DHCPv6 builds.
 1106: 
 1107: - Fix for parsing error on some IPv6 addresses.
 1108: 
 1109: - Invalid CIDR representation for IPv6 subnets or ranges now checked
 1110:   for when loading configuration.
 1111: 
 1112: - Compilation on HP/UX has been repaired.  The changes should generally
 1113:   apply to any architecture that supplies SIOCGLIFCONF but does not
 1114:   use 'struct lifconf' structures to pass values.
 1115: 
 1116: - Two new operators, ~= and ~~, have been integrated to implement
 1117:   boolean matches by regular expression (such as may be used in
 1118:   class matching statements).  Thanks to a patch by Alexandr S.
 1119:   Agranovsky, which underwent slight modification.
 1120: 
 1121: - Fix for icmp packets on 64-bit systems (bug introduced in 4.0).
 1122: 
 1123: - A bug was fixed in interface discovery wherein an error identifying
 1124:   a server-configured interface with no IPv4 addresses would SEGV.
 1125: 
 1126: - Fixed a bug in which write_lease() might report a failure incorrectly
 1127: 
 1128: - Added support for DHCPv6 Release messages
 1129: 
 1130: - Added -x option to dhclient, which triggers dhclient processes
 1131:   to exit gracefully without releasing leases first
 1132: 
 1133: - All binaries (client, server, relay) now change directories
 1134:   to / before going into daemon mode, so as not to hold $CWD open
 1135: 
 1136: - Fixed a bug parsing DHCPv6 client-id's in host-identifier statements
 1137: 
 1138: - Fixed a bug with the 'ddns-updates' boolean server configuration
 1139:   parameter, which caused the server to fail.
 1140: 
 1141: 			Changes since 4.0.0-20070413
 1142: 
 1143: - Old (expired) leases are now cleaned.
 1144: 
 1145: - IPv6 subnets now have support for arbitrary allocation ranges via
 1146:   a new 'range6' configuration directive.
 1147: 
 1148: - An obviated option code hash lookup to find D6O_CLIENTID was removed.
 1149: 
 1150: - Corrected some situations where variables might be used without being
 1151:   initialized.
 1152: 
 1153: - Silenced several other compiler warnings.
 1154: 
 1155: - Include the more standard sys/uio.h rather than rely upon other
 1156:   header files to include it (fixes a BSD 4.2 compile failure).
 1157: 
 1158: - Duplicate dhclient-script updates for DHCPv6 to all provided scripts.
 1159: 
 1160: - DHCPv4 I/O methods that failed to sense hardware address were corrected.
 1161: 
 1162: - DHCPv4 is now the default (as documented) rather than DHCPv6.  The default
 1163:   was set to DHCPv6 to facilitate ease early development, and forgotten.
 1164: 
 1165: - Corrected a segmentation violation in DHCPv4 socket processing.
 1166: 
 1167: - dhclient will now fork() into the background once it binds to an
 1168:   IPv6 address, or immediately if the -n flag is supplied.
 1169: 
 1170: - -q is now the default behaviour on dhclient, with -d or -v enabling
 1171:   non-quiet (stderr logging) mode.
 1172: 
 1173: - Fix documentation of the domain-search atom (quoted, with commas).
 1174: 
 1175: - Document DHCPv6 options presently in the default table.
 1176: 
 1177: - Replaced ./configure shellscripting with GNU Autoconf.
 1178: 
 1179: 		     Changes since 3.1.0 (NEW FEATURES)
 1180: 
 1181: - DHCPv6 Client and Server protocol support.  Use '-6' to run the daemons
 1182:   as v6-only.  Use '-4' to run the daemons as v4-only (default.  There is
 1183:   no support currently for both.
 1184: 
 1185: - Server support for multiple IA_NA options, containing at most one
 1186:   IAADDR option.
 1187: 
 1188: - Client support for one IA_NA option, containing any number of IAADDR
 1189:   options.
 1190: 
 1191: - Server support for the DHCPv6 Information-request message.
 1192: 
 1193: - Inappropriate unicast DHCPv6 messages sent to the server are now
 1194:   discarded, and this has rearchitected the IO system slightly.
 1195: 
 1196: - The DHCPv6 server DUID defaults to type 1, is persistently stored in
 1197:   the leases database, and can be over-ridden (either completely, or by
 1198:   specifying type 1 or type 2).
 1199: 
 1200: - The server only uses Rapid-Commit if it has been configured with the
 1201:   Rapid-Commit option and the client requests it.
 1202: 
 1203: - DDNS support. We now update AAAA records in the same place we would
 1204:   update A records, if we have an IPv6 address. We also generate IP6.ARPA
 1205:   style names for PTR records if we're dealing with an IPv6 address.  Both
 1206:   A and AAAA updates are done using the same 'fqdn.' virtual option space
 1207:   (although the DHCPv4 FQDN and DHCPv6 FQDN options are formatted
 1208:   differently, they both use the same code here).
 1209: 
 1210: - The Linux dhclient-script attempts to set and remove assigned addresses,
 1211:   and to configure /etc/resolv.conf from nameserver and domain name
 1212:   configurations.  It can be extended to configure other parameters.
 1213: 
 1214: - Initial DHCPv6 lease support.
 1215: 
 1216: - The IO system now tracks all local IP addresses, so that the DHCP
 1217:   applications (particularly the dhcrelay) can discern between what frames
 1218:   were transmitted to it, and what frames are being carried through it which
 1219:   it should not intercept.
 1220: 
 1221: 			Changes since 3.1.0 (Maintenance)
 1222: 
 1223: - A bug was repaired where MAC Address Affinity for virgin leases always
 1224:   mapped to the primary.  Virgin leases now have an interleaved preference
 1225:   between primary and secondary.
 1226: 
 1227: - A bug was repaired where MAC Address Affinity for clients with no client
 1228:   identifier was sometimes mishashed to the peer.  Load balancing during
 1229:   runtime and pool rebalancing were opposing.
 1230: 
 1231: - An assertion in lease counting relating to reserved leases was repaired.
 1232: 
 1233: - The subnet-mask option inclusion now conforms with RFC2132 section 3.3;
 1234:   it will only appear prior to the routers option if it is present on the
 1235:   Parameter-Request-List.  The subnet-mask option will also only be
 1236:   included by default (if it is not on the PRL) in response to DISCOVER
 1237:   or REQUEST messages.
 1238: 
 1239: - The FQDN option is only supplied if the client supplied an FQDN option or
 1240:   if the FQDN option was explicitly requested on the PRL.
 1241: 
 1242: - Dynamic BOOTP leases are now load balanced in failover.
 1243: 
 1244: 			Changes since 3.1.0rc1
 1245: 
 1246: - The parse warning that 'deny dyanmic bootp;' must be configured for
 1247:   failover protected subnets was removed.
 1248: 
 1249: 			Changes since 3.1.0b2
 1250: 
 1251: - Failover rebalance events no longer play ping pong with round errors
 1252:   (moving leases between free and back to backup where there are an
 1253:   odd number of leases).
 1254: 
 1255: - The 'pool' log line has been split into two messages, one before the
 1256:   rebalance run, and one after.
 1257: 
 1258: - Any queued BNDACKs are transmitted before transmitting new BNDUPDs.
 1259:   This enforces the correct sequence of events for the remote server
 1260:   processing these messages.
 1261: 
 1262: 			Changes since 3.1.0b1
 1263: 
 1264: - Fixed a bug that caused OMAPI clients to freeze when opening lease
 1265:   objects.
 1266: 
 1267: - A new server config option "fqdn-reply" specifies whether the server
 1268:   should send out option 81 (FQDN).  Defaults to "on".  If set to "off",
 1269:   the FQDN option is not sent, even if the client requested it.  This is
 1270:   needed because some clients misbehave otherwise.  Thanks to Christof Chen
 1271:   at Allianz.
 1272: 
 1273: - Allow trace output files (-tf option) to be overwritten, rather than
 1274:   crashing dhcpd if the file already exists
 1275: 
 1276: - A bug was fixed that caused dhcpd to segfault if a pool was declared
 1277:   outside the scope of a subnet in dhcpd.conf.
 1278: 
 1279: - Some uninitialized values were repaired in dhcpleasequery.c that
 1280:   caused the server to abort.
 1281: 
 1282: - A new server config option, 'do-reverse-updates', has been added
 1283:   which causes the server to abstain from performing updates on PTR
 1284:   records.  Thanks to a patch from Christof Chen at Allianz.
 1285: 
 1286: - A bug was repaired in subencapsulation support, where spaces separated
 1287:   by empty spaces would not get included.
 1288: 
 1289: - A bug in dhclient was repaired which caused it to send parameter request
 1290:   lists of 55 bytes in length no matter how long the declared PRL was.
 1291: 
 1292: - 'dhcp.c(3953): non-null pointer' has been repaired.  This fixes a flaw
 1293:   wherein the DHCPv4 server may ignore a configured server-identifier.
 1294: 
 1295: - A flaw in failover startup sequences was repaired that sometimes left
 1296:   the primary DHCP server's pool rebalance schedules unscheduled.
 1297: 
 1298: - Corrected a flaw that broke encapsulated spaces included due to presence
 1299:   on the parameter request list.
 1300: 
 1301: 			Changes since 3.1.0a3
 1302: 
 1303: - Some spelling fixes.
 1304: 
 1305: 			Changes since 3.1.0a2
 1306: 
 1307: - A bug was fixed where attempting to permit leasequeries results in a
 1308:   fatal internal error, "Unable to find server option 49".
 1309: 
 1310: - A bug was fixed in dhclient rendering the textual output form of the
 1311:   domain-search option syntax.
 1312: 
 1313: 			Changes since 3.1.0a1
 1314: 
 1315: - A bug in the FQDN universe that added FQDN codes to the NWIP universe's
 1316:   hash table was repaired.
 1317: 
 1318: - The servers now try harder to transmit pending binding updates when
 1319:   entering normal state.
 1320: 
 1321: - UPDREQ/UPDREQALL handling was optimized - it no longer dequeues and
 1322:   requeues all pending updates.  This should reduce the number of spurious
 1323:   'xid mismatch' log messages.
 1324: 
 1325: - An option definition referencing leak was fixed, which resulted in early
 1326:   termination of dhclient upon the renewal event.
 1327: 
 1328: - Some default hash table sizes were tweaked, some upwards, some downwards.
 1329:   3.1.0a1's tables resulted in a reduction in default server memory use.
 1330:   The new selected values provide more of a zero sum (increasing the size
 1331:   of tables likely to be populated, decreasing the size of tables unlikely).
 1332: 
 1333: - Lease structures appear in three separate hashes: by IP address, by UID,
 1334:   and by hardware address.  One type of table was used for all three, and
 1335:   improvements to IP address hashing were applied to all three (so UID and
 1336:   hardware addresses were treated like 4-byte integers).  There are now two
 1337:   types of tables, and the uid/hw hashes use functions more appropriate
 1338:   to their needs.
 1339: 
 1340: - The max-lease-misbalance percentage no longer causes scheduled rebalance
 1341:   runs to be skipped: it still governs the schedule, but every scheduled
 1342:   run will attempt balance.
 1343: 
 1344: - A segfault bug in recursive encapsulation support has been corrected.
 1345: 
 1346: 			Changes since 3.0 (New Features)
 1347: 
 1348: - A workaround for certain STSN servers that send a mangled domain-name
 1349:   option was introduced for dhclient.  The client will now accept corrupted
 1350:   server responses, if they contain a valid DHCP_MESSAGE_TYPE (OFFER, ACK,
 1351:   or NAK).  The server will continue to not accept corrupt client packets.
 1352: 
 1353: - Support for 'reserved' (pseudo-static) and BOOTP leases via failover
 1354:   was introduced.
 1355: 
 1356: - Support for adding, removing, and managing class and subclass statements
 1357:   via OMAPI.
 1358: 
 1359: - The failover implementation was updated to comply with revision 12 of
 1360:   the protocol draft.
 1361: 
 1362: - 'make install' now creates the initial zero-length dhcpd.leases file if
 1363:   one does not already exist on the system.
 1364: 
 1365: - RFC3942 compliance, site-local option spaces start at 224 now, not 128.
 1366: 
 1367: - The Load Balance Algorithm was misimplemented.  The current implementation
 1368:   matches RFC 3074.
 1369: 
 1370: - lcase() and ucase() configuration expressions have been added which adjust
 1371:   their arguments from upper to lower and lower to upper cases respectively.
 1372:   Thanks to a patch from Albert Herranz.
 1373: 
 1374: - The dhclient 'reject ...;' statement, which rejects leases given by named
 1375:   server-identifiers, now permits address ranges to be specified in CIDR
 1376:   notation.  Thanks to a patch from David Boyce.
 1377: 
 1378: - The subnet-mask option is now supplied by default, but at lowest
 1379:   priority.  This helps a small minority of clients that provide parameter
 1380:   request lists, but do not list the subnet-mask option because they were
 1381:   designed to interoperate with a server that behaves in this manner.
 1382: 
 1383: - The FQDN option is similarly supplied even if it does not appear on the
 1384:   parameter request list, but not to the exclusion of options that do
 1385:   appear at the parameter request list.  Up until now it had ultimate
 1386:   priority over the client's parameter request list.
 1387: 
 1388: - Varying option space code and length bit widths (8/16/32) are now
 1389:   supported.  This is a milestone in achieving RFC 3925 "VIVSO" and
 1390:   DHCPv6 support.
 1391: 
 1392: - A new common (server or client) option, 'db-time-format local;', has
 1393:   been added which prints the local time in /var/db/dhcpd.leases rather
 1394:   than UTC.  Thanks to a patch from Ken Lalonde.
 1395: 
 1396: - Some patches to improve DHCP Server startup speed from Andrew Matheson
 1397:   have been incorporated.
 1398: 
 1399: - Failover pairs now implement 'MAC Affinity' on leases moving from the
 1400:   active to free states.  Leases that belonged to the failover secondary
 1401:   are moved to BACKUP state rather than FREE upon exiting EXPIRED state.
 1402:   If lease rebalancing must move leases, it tries first to move leases
 1403:   that belong to the peer in need.
 1404: 
 1405: - The server no longer sends POOLREQ messages unless the pool is severely
 1406:   misbalanced in the peer's favor (see 'man dhcpd.conf' for more details).
 1407: 
 1408: - Pool rebalance events no longer happen upon successfully allocating a
 1409:   lease.  Instead, they happen on a schedule.  See 'man dhcpd.conf' for the
 1410:   min-balance and max-balance statements for more information.
 1411: 
 1412: - The DHCP Relay Agent Information Option / Link Selection Sub-Option
 1413:   is now supported.  (See RFC3527 for details).
 1414: 
 1415: - A new DDNS related server option, update-conflict-detection, has been
 1416:   added.  If this option is enabled, dhcpd will perform normal DHCID
 1417:   conflict resolution (the default).  If this option is disabled, it will
 1418:   instead trust the assigned name implicitly (removing any other bindings
 1419:   on that name).  This option has not been made available in dhclient.
 1420: 
 1421: - In those cases where the DHCP software manufactures an IP header (to
 1422:   transmit via bpf, lpf, etc), the IP TTL the software selects has been
 1423:   increased from 16 to 128.  This is intended to match Microsoft Windows
 1424:   DHCP Client behaviour, to increase compatibility.
 1425: 
 1426: - 'ignore client-updates;' now has behaviour that is different from
 1427:   'deny client-updates;'.  The client's request is not truly ignored,
 1428:   rather it is encouraged.  Should this value be configured, the server
 1429:   updates DNS as though client-updates were set to 'deny'.  That is, it
 1430:   enters into DNS whatever it is configured to do already, provided it is
 1431:   configured to.  Then it sends a response to the client that lets the
 1432:   client believe it is performing client updates (which it will), probably
 1433:   for a different name.  In essence, this lets the client do as it will,
 1434:   ignoring this aspect of their request.
 1435: 
 1436: - Support for compressed 'domain name list' style DHCP option contents, and
 1437:   in particular the domain search option (#119) was added.
 1438: 
 1439: - The DHCP LEASEQUERY protocol as defined in RFC4388 is now implemented.
 1440:   LEASEQUERY lets you query the DHCP server for information about a lease,
 1441:   using either an IP address, MAC address, or client identifier.  Thanks
 1442:   to a patch from Justin Haddad.
 1443: 
 1444: - DHCPD is now RFC2131 section 4.1 compliant (broadcast to all-ones ip and
 1445:   ethernet mac address) on the SCO platform specifically without any strange
 1446:   ifconfig hacks.  Many thanks go to the Kroger Co. for donating the
 1447:   hardware and funding the development.
 1448: 
 1449: - A new common configuration executable statement, execute(), has been
 1450:   added.  This permits dhcpd or dhclient to execute a named external
 1451:   program with command line arguments specified from other configuration
 1452:   language.  Thanks to a patch written by Mattias Ronnblom, gotten to us
 1453:   via Robin Breathe.
 1454: 
 1455: - A new dhcp server option 'adaptive-lease-time-threshold' has been added
 1456:   which causes the server to substantially reduce lease-times if there are
 1457:   few (configured percentage) remaining leases.  Thanks to a patch submitted
 1458:   from Christof Chen.
 1459: 
 1460: - Encapsulated option spaces within encapsulated option spaces is now
 1461:   formally supported.
 1462: 
 1463: 			Changes since 3.0.6rc1
 1464: 
 1465: - supersede_lease() now requeues leases in their respective hardware
 1466:   address hash bucket.  This mirrors client identifier behaviour.
 1467: 
 1468: 			Changes since 3.0.5
 1469: 
 1470: - Assorted fixes for broken network devices:  Packet length is now
 1471:   determined from the IP header length field to finally calculate the
 1472:   UDP payload length, because some NIC drivers return more data than
 1473:   they actually received.
 1474: 
 1475: - UDP packets are now stored in aligned data structures.
 1476: 
 1477: - A logic error in omapi interface code was repaired that might result in
 1478:   incorrectly indicating 'up' state when any flags were set, rather than
 1479:   specifically the INTERFACE_REQUESTED flag.  Thanks to a patch from
 1480:   Jochen Voss which got to us via Andrew Pollock at Debian.
 1481: 
 1482: - A reference leak on binding scopes set by ddns updates was repaired.
 1483: 
 1484: - A memory leak in the minires_nsendsigned() function call was repaired.
 1485:   Effectively, this leaked ~176 bytes per DDNS update.
 1486: 
 1487: - In the case where an "L2" DHCP Relay Agent (one that does not set giaddr)
 1488:   was directly attached to the same broadcast domain as the DHCP server,
 1489:   the RFC3046 relay agent information option was not being returned to the
 1490:   relay in the server's replies.  This was fixed; the dhcp server no longer
 1491:   requires the giaddr to reply with relay agent information.  Note that
 1492:   this also improves compatibility with L2 devices that "intercept" DHCP
 1493:   packets and expect relay agent information even in unicast (renewal)
 1494:   replies.  Thanks to a patch from Pekka Silvonen.
 1495: 
 1496: - A bug was fixed where the BOOTP header 'sname' field had a value, the
 1497:   copy written to persistent storage was actually the contents of the
 1498:   'file' field.
 1499: 
 1500: - A bug was fixed where the nwip virtual option space was referencing
 1501:   the fqdn option's virtual option space's option cache.
 1502: 
 1503: - Timestamp parsing errors that indicated missing "minutes" fields rather
 1504:   than the actually missing "seconds" fields have been repaired thanks to
 1505:   a patch from Kevin Steves.
 1506: 
 1507: - A grammar error in the dhclient.8 manpage was repaired thanks to a patch
 1508:   from Chris Wagner.
 1509: 
 1510: - Several spelling typos were repaired, and some cross-references to other
 1511:   relevant documents were included in the manpages, thanks to a patch
 1512:   by Andrew Pollock which got to us via Tomas Pospisek.
 1513: 
 1514: - Some bugs were fixed in the 'emergency relay agent options hologram'
 1515:   which is used to retain relay agent option contents from when the
 1516:   client was in INIT or REBIND states.  This should solve problems where
 1517:   relay agent options were not echoed from the server, even when giaddr
 1518:   was set.
 1519: 
 1520: - dhclient now closes its descriptor to dhclient.leases prior to executing
 1521:   dhclient-script.  Thanks to a patch from Tomas Pospisek.
 1522: 
 1523: - The server's "by client-id" and "by hardware address" hash table lists
 1524:   are now sorted according to the preference to re-allocate that lease to
 1525:   returning clients.  This should eliminate pool starvation problems
 1526:   arising when "INIT" clients were given new leases rather than presently
 1527:   active ones.
 1528: 
 1529: 			Changes since 3.0.5rc1
 1530: 
 1531: - A bug was repaired in fixes to the dhclient, which sought to run the
 1532:   dhclient-script with the 'EXPIRE' state should it receive a NAK in
 1533:   response to a REQUEST.  The client now iterates the PREINIT state
 1534:   after the EXPIRE state, so that interfaces that might be configured
 1535:   'down' can be brought back 'up' and initialized.
 1536: 
 1537: - DHCPINFORM handling for clients that properly set ciaddr and come to the
 1538:   server via a relay aget has been repaired.
 1539: 
 1540: 			Changes since 3.0.4
 1541: 
 1542: - A warning that host statements declared within subnet or shared-network
 1543:   scopes are actually global has been added.
 1544: 
 1545: - The default minimum lease time (if min-lease-time was not specified)
 1546:   was raised from 0 to 300.  0 is not thought to be sensible, and is
 1547:   known to be damaging.
 1548: 
 1549: - Added additional fatal error sanity checks surrounding lease binding
 1550:   state count calculations (free/active counts used for failover pool
 1551:   balancing).
 1552: 
 1553: - Some time value size fixes in 3.0.4 brought on from FreeBSD /usr/ports were
 1554:   misapplied to server values rather than client values.  The server no longer
 1555:   advertises 8-byte lease-time options when on 64-bit platforms.
 1556: 
 1557: - A bug where leases not in ACTIVE state would get billed to billed classes
 1558:   (classes with lease limitations) was fixed.  Non-active leases OFFERed
 1559:   to clients are no longer billed (but billing is checked before offering).
 1560: 
 1561: - The dhcpd.conf.5 manpage was updated in regard to the ddns-domainname
 1562:   configuration option - the default configuration and results should be
 1563:   more clear now.
 1564: 
 1565: - If the dhclient were to receive a DHCPNAK while it was in the RENEW
 1566:   state (and consequently, had an active, 'bound' address and related
 1567:   configuration options), it would fail to 'tear down' this information
 1568:   before proceeding into INIT state.  dhclient now iterates the dhclient-
 1569:   script with the 'EXPIRE' action to cause these teardowns prior to entering
 1570:   INIT state.  Thanks to a patch from Chris Zimmerman.
 1571: 
 1572: - The omapi.1 manpage had some formatting errors repaired thanks to a patch
 1573:   from Yoshihiko Sarumaru.
 1574: 
 1575: - A few lines of code that were failover-specific were moved within
 1576:   #if defined() clauses so that compilation without failover could be
 1577:   made possible.
 1578: 
 1579: - The log message emitted when the 'leased-address' value was not available
 1580:   in dhcpd.conf "executable statements" has been updated to be more helpful.
 1581:   Manpage information for this value has also been updated.
 1582: 
 1583: - Abandoned or dissociated (err condition) leases now remove any related
 1584:   dynamic dns bindings.  Thanks to a patch from Patrick Schoo.
 1585: 
 1586: - Attempting to write a new lease file to replace a corrupt (due to
 1587:   encountering non-retryable errors during writing) lease file should
 1588:   no longer result in an infinite recursion.
 1589: 
 1590: - Host declaration hardware addresses and client identifiers may only be
 1591:   configured once.  dhcpd will now fail to load config files that specify
 1592:   multiple identifiers (previous versions would silently over-ride the
 1593:   value with the later configured value).
 1594: 
 1595: - Several option codes that have been allocated since our last release
 1596:   have been named and documented.
 1597: 
 1598: - Option names of the form "unknown-123" have been removed from the in-
 1599:   memory hash tables.  In order to support options of these names that
 1600:   may appear in dhclient.leases or similar in previous versions, the
 1601:   parser will now find the new option code definition, or mock up a
 1602:   generic option code definition.  This should result in a smooth
 1603:   transition from one name to the other, as the new name is used to
 1604:   write new output.
 1605: 
 1606: 			Changes since 3.0.4rc1
 1607: 
 1608: - The dhcp-options.5 manpage was updated to correct indentation errors
 1609:   thanks to a patch from Jean Delvare.
 1610: 
 1611: 			Changes since 3.0.4b3
 1612: 
 1613: - Some manual pages were clarified pursuant to discussion on the dhcp-server
 1614:   mailing list.
 1615: 
 1616: 			Changes since 3.0.4b2
 1617: 
 1618: - Null-termination sensing for certain clients that unfortunately require
 1619:   it in DHCPINFORM processing was repaired.
 1620: 
 1621: - The host-name option and a few others were moved from "X" format to "t"
 1622:   format to be compatible with new NULL handling functions.
 1623: 
 1624: - DHCPINFORM processing is a little more careful about return addressing
 1625:   its responses, or if responding via a relay.  The INFORM related
 1626:   messages also log the 'effective client ip address' rather than the
 1627:   client's supplied ciaddr (since some clients produce null ciaddrs).
 1628: 
 1629: - The server was inappropriately sending leases to the RESET state in the
 1630:   event that multiple active leases were found to match a singly-identified
 1631:   client.  This was changed to RELEASED (by accepting a different, ACTIVE
 1632:   binding, the client is implicitly releasing its lease).  This repairs a
 1633:   bug wherein secondary servers in failover pairs detecting this condition
 1634:   move leases to RESET, and primaries refuse to accept that state
 1635:   transition (properly).
 1636: 
 1637: - The memset-after-dmalloc() changes made in 3.0.4b1 have been backed out.
 1638: 
 1639: 			Changes since 3.0.4b1
 1640: 
 1641: - Command line parsing in omshell was repaired - it no longer closes
 1642:   STDIN after reading one line.
 1643: 
 1644: - The resolver library no longer closes the /etc/resolv.conf file
 1645:   descriptor it opened twice.
 1646: 
 1647: - Changes to trailing NULL removal in 't' option-atoms has been rethought,
 1648:   it now includes 'd' (domain name) types, and tries hard not to rewind an
 1649:   option beyond the start of the text field it is un-terminating.
 1650: 
 1651: 			Changes since 3.0.3
 1652: 
 1653: - A DDNS update handling function was misusing the DNS error codes, rather
 1654:   than the internal generic result enumeration.  The result is a confusing
 1655:   syslog line, logging the wrong condition.
 1656: 
 1657: - The DHCP Server was not checking pool balance in the case where it brought
 1658:   a non-ACTIVE lease out of storage for a client that was returning to use
 1659:   a lease it once had long ago, and had since expired.
 1660: 
 1661: - Failover peers no longer bother to look for free leases to allocate when
 1662:   they already found the client's ACTIVE lease.  DISCOVERs are load balanced
 1663:   whether freely-allocated or not, unless the server doubts the peer has
 1664:   leases to allocate.
 1665: 
 1666: - Fixed a bug in dhcrelay agent addition code that suppressed trailing
 1667:   PAD options - it was suppressing only one trailing PAD option, rather
 1668:   than the entire block of them.
 1669: 
 1670: ! Fixed some unlikely overlapping-region memcpy() bugs in dhcrelay agent
 1671:   option addition and stripping code.  Added a few sanity checks.  Although
 1672:   highly improbable, due to requiring the reception of a DHCP datagram well
 1673:   in excess of all known to be used physical MTU limitations, it is possible
 1674:   this may have been used in a stack overflow security vulnerability.  Thanks
 1675:   to a patch from infamous42md.
 1676: 
 1677: ! Added some sanity checks to OMAPI connection/authentication code.
 1678:   Although highly improbable, due to having to deliver in excess of 2^32
 1679:   bytes of data via the OMAPI channel, not to mention requiring dhcpd to
 1680:   be able to malloc() a memory region 2^32 bytes in size, it was possible
 1681:   this might have resulted in a heap overflow security vulnerability.
 1682:   Thanks to a patch from infamous42md.
 1683: 
 1684: - dmalloc() memset()'s the non-debug (data) portion of the allocated
 1685:   memory to zero.  Code that memset()'s the result returned by dmalloc() to
 1686:   zero is redundant.  These redundancies were removed.
 1687: 
 1688: - Some type declaration corrections to u_int16_t were made in common/tr.c
 1689:   (Token Ring support) thanks to a patch from Jason Vas Dias at Red Hat.
 1690: 
 1691: - A failover bug that was allowing leases that EXPIRED or were RELEASED
 1692:   where tsfp and tstp are identical timestamps to languish in these
 1693:   transitional states has been repaired.  As a side effect, lease
 1694:   databases should be kept more consistent overall, not just for these
 1695:   transitional states.
 1696: 
 1697: - If the lease db is deleted out from under the daemon, and it moves to rewrite
 1698:   the db, it will go ahead with the operation and move the new db into place
 1699:   once it detects the old db does not exist.
 1700: 
 1701: - dhclient now ignores IRDA, SIT, and IEEE1394 network interfaces, as it
 1702:   is either nonsensical or (in the case of IEEE1394) is not known to support
 1703:   these interfaces.  Thanks to Marius Gedminas and Andrew Pollock of Debian.
 1704: 
 1705: - Some previously undocumented reasons for dhclient-script invoking has
 1706:   been documented in the dhclient-script.8 manpage.
 1707: 
 1708: - Failover potential expiry calculations (TSTP) have been corrected.  Results
 1709:   should be substantially more consistent, and proper given the constraints.
 1710: 
 1711: - Adjusted lease state validation checks in potential-conflict, to
 1712:   account for possible clock skew similarly to normal state, and several
 1713:   previously illegal transitions were made legal (ex: active->released).
 1714: 
 1715: - An impossible sanity check was removed from omapi/buffer.c, thanks to a
 1716:   patch from 'infamous42md'.
 1717: 
 1718: - An OMAPI host/network byte order problem in lease time values has been
 1719:   repaired.
 1720: 
 1721: - Several minor bugs, largely relating to treating 8-byte time values as
 1722:   4-byte entities, have been repaired after careful review of the FreeBSD
 1723:   ports collection's patch set.  Thanks to the nameless entities who have
 1724:   contributed to the FreeBSD ports.
 1725: 
 1726: - When writing a trace file, the file is now created with permissions 0600,
 1727:   to help administrators avoid accidentally publicising sensitive config
 1728:   data.
 1729: 
 1730: - The calculation of the maximum size of DHCP packets no longer includes
 1731:   Ethernet framing overhead.  The result is that the 'Maximum Message
 1732:   Size' option advertised by clients, or the default value 576, is no
 1733:   longer reduced by 14 bytes, and instead directly reflects the IP level
 1734:   MTU (and the default, minimum allowed IP MTU of 576).
 1735: 
 1736: - The special status of RELEASED/EXPIRED/RESET leases when a server
 1737:   is operating in partner-down was fixed.  It no longer requires a
 1738:   lease be twice the MCLT beyond STOS to 'reallocate', and the expiry
 1739:   event to turn these into FREE leases without peer acknowledgement
 1740:   (after STOS+MCLT) has been repaired.
 1741: 
 1742: - Compilation on older Solaris systems (lacking /usr/include/sys/int_types.h)
 1743:   has been repaired.
 1744: 
 1745: - "append"ing a string onto the end of a "t" type option (such as the
 1746:   domain-name field) that had been improperly NULL-terminated by the
 1747:   DHCP server will no longer result in a truncated string containing
 1748:   only the option from the server, and not the expected appended value.
 1749:   Thanks to a patch from Jason Vas Dias at Red Hat.
 1750: 
 1751: - File handlers on configuration state (config files and lease dbs) should
 1752:   be treated consistently, regardless of whether TRACING is defined or not.
 1753: 
 1754: - The Linux build environment has had some minor improvements - better
 1755:   sensing of 64-bit pointer sizes (only used for establishing an icmp_id),
 1756:   and corrections to #if operators regarding LINUX_MAJOR should it ever
 1757:   move to 3.[01].x.
 1758: 
 1759: - The server now tries harder to survive the condition where it is unable
 1760:   to open a new lease file to rewrite the lease state database.
 1761: 
 1762: 			Changes since 3.0.3b3
 1763: 
 1764: - dhclient.conf documentation for interface {} was updated to reflect recent
 1765:   discussion on the dhcp-hackers mailing list.
 1766: 
 1767: - In response to reports that the software does not compile on GCC 4.0.0,
 1768:   -Werror was removed from Makefile.conf for all platforms that used it.
 1769:   We will address the true problem in a future release; this is a temporary
 1770:   workaround.
 1771: 
 1772: 			Changes since 3.0.3b2
 1773: 
 1774: - An error in code changes introduced in 3.0.3b2 was corrected, which caused
 1775:   static BOOTP clients to receive random addresses.
 1776: 
 1777: 			Changes since 3.0.3b1
 1778: 
 1779: - A bug was fixed in BOOTPREQUEST handling code wherein stale references to
 1780:   host records would be left behind on leases that were not allocated to the
 1781:   client currently booting (eg in the case where the host was denied booting).
 1782: 
 1783: - The dhcpd.conf.5 manpage was updated to be more clear in regards to
 1784:   multiple host declarations (thanks to Vincent McIntyre).  'Interim' style
 1785:   dynamic updates were also retouched.
 1786: 
 1787: 			Changes since 3.0.2
 1788: 
 1789: - A bug was fixed where a server might load balance a DHCP REQUEST to its
 1790:   peer after already choosing not to load balance the preceding DISCOVER.
 1791:   The peer cannot allocate the originating server's lease.
 1792: 
 1793: - In the case where a secondary server lost its stable storage while the
 1794:   primary was still in communications-interrupted, and came back online,
 1795:   the lease databases would not be fully transferred to the secondary.
 1796:   This was due to the secondary errantly sending an extra UPDREQ message
 1797:   when the primary made its state transition to PARTNER-DOWN known.
 1798: 
 1799: - The package will now compile cleanly in gcc 3.3 and 3.4.  As a side effect,
 1800:   lease structures will be 9 bytes smaller on all platforms.  Thanks to
 1801:   Jason Vas Dias at Red Hat.
 1802: 
 1803: - Interface discovery code in DISCOVER_UNCONFIGURED mode is now
 1804:   properly restricted to only detecting broadcast interfaces.  Thanks
 1805:   to a patch from Jason Vas Dias at Red Hat.
 1806: 
 1807: - decode_udp_ip_header was changed so that the IP address was copied out
 1808:   to a variable, rather than referenced by a pointer.  This enforces 4-byte
 1809:   alignment of the 32-bit IP address value.  Thanks to a patch from Dr.
 1810:   Peter Poeml.
 1811: 
 1812: - An incorrect log message was corrected thanks to a patch from
 1813:   Dr. Peter Poeml.
 1814: 
 1815: - A bug in DDNS was repaired, where if the server's first DDNS action was
 1816:   a DDNS removal rather than a DDNS update, the resolver library's
 1817:   retransmit timer and retry timer was set to the default, implying a
 1818:   15 second timeout interval.  Which is a little excessive in a synchronous,
 1819:   single-threaded system.  In all cases, ISC DHCP should now hold fast to
 1820:   a 1-second timeout, trying only once.
 1821: 
 1822: - The siaddr field was being improperly set to the server-identifier when
 1823:   responding to DHCP messages.  RFC2131 clarified the siaddr field as
 1824:   meaning the 'next server in the bootstrap process', eg a tftp server.
 1825:   The siaddr field is now left zeroed unless next-server is configured.
 1826: 
 1827: - mockup_lease() could have returned in an error condition (or in the
 1828:   condition where no fixed-address was found matching the shared
 1829:   network) with stale references to a host record.  This is probably not
 1830:   a memory leak since host records generally never die anyway.
 1831: 
 1832: - A bug was repaired where failover servers would let stale client identifiers
 1833:   persist on leases that were reallocated to new clients not sending an id.
 1834: 
 1835: - Binding scopes ("set var = value;") are now removed from leases allocated
 1836:   by failover peers if the lease had expired.  This should help reduce the
 1837:   number of stale binding scopes on leases.
 1838: 
 1839: - A small memory leak was closed involving client identifiers larger than
 1840:   7 bytes, and failover.
 1841: 
 1842: - Configuring a subnet in dhcpd.conf with a subnet mask of 32 bits might
 1843:   cause an internal function to overflow heap.  Thanks to Jason Vas Dias
 1844:   at Red Hat.
 1845: 
 1846: - Some inconsistencies in treating numbers that the lexer parsed as 'NUMBER'
 1847:   or 'NUMBER_OR_NAME' was repaired.  Hexadecimal parsing is affected, and
 1848:   should work better.
 1849: 
 1850: - In several cases, parse warnings were being issued before the lexical
 1851:   token had been advanced to the token whose value was causing an error...
 1852:   causing parse warnings to claim the problem is on the wrong token.
 1853: 
 1854: - Host declarations matching on client identifier for dynamic leases will
 1855:   no longer match fixed-address host declarations (this is now identical
 1856:   to behaviour for host records matching on hardware address).
 1857: 
 1858: 			Changes since 3.0.2rc3
 1859: 
 1860: - A previously undocumented configuration directive, 'local-address',
 1861:   was documented in the dhcpd.conf manpage.
 1862: 
 1863: 			Changes since 3.0.2rc2
 1864: 
 1865: - Two variables introduced in 3.0.2b1 were used without being initialized
 1866:   in the case where neither the FILE nor SNAME fields were available for
 1867:   overloading.  This was repaired.
 1868: 
 1869: - A heretofore believed to be impossible corner case of the option
 1870:   overloading implementation turned out to be possible ("Unable to sort
 1871:   overloaded options after 10 tries.").  The implementation was reworked
 1872:   to consider the case of an option so large it would require more than
 1873:   three chunks to fit.
 1874: 
 1875: - Many other instances of variables being used without being initialized
 1876:   were repaired.
 1877: 
 1878: - An uninitialized variable in omapi_io_destroy() led to the discovery
 1879:   that this function may result in orphaned pointers (and hence, a memory
 1880:   leak).
 1881: 
 1882: 			Changes since 3.0.2rc1
 1883: 
 1884: - allocate_lease() was rewritten to repair a bug in which the server would
 1885:   try to allocate an ABANDONED lease when FREE leases were available.
 1886: 
 1887: 			Changes since 3.0.2b1
 1888: 
 1889: - Some dhcp-eval.5 manpage formatting was repaired.
 1890: 
 1891: 			Changes since 3.0.1
 1892: 
 1893: - A bug was fixed in the server's 'option overloading' implementation,
 1894:   where options loaded into the 'file' and 'sname' packet fields were
 1895:   not aligned precisely as rfc2131 dictates.
 1896: 
 1897: - The FreeBSD client script was changed to support the case where a domain
 1898:   name was not provided by the server.
 1899: 
 1900: - A memory leak in 'omshell' per each command line parsed was
 1901:   repaired, thanks to a patch from Jarkko Torppa.
 1902: 
 1903: - Log functions writing to stderr were adjusted to use the STDERR_FILENO
 1904:   system definition rather than '2'.  This is a no-op for 90% of platforms.
 1905: 
 1906: - One call to trace_write_packet_iov() counted the number of io vectors
 1907:   incorrectly, causing inconsistent tracefiles.  This was fixed.
 1908: 
 1909: - Some expression parse failure memory leaks were closed.
 1910: 
 1911: - A host byte order problem in tracefiles was repaired.
 1912: 
 1913: - Pools configured in DHCPD for failover possessing permission lists that
 1914:   previously were assumed to not include dyanmic bootp clients are now
 1915:   a little more pessimistic.  The result is, dhcpd will nag you about just
 1916:   about most pools that possess a 'allow' statement with no 'deny' that
 1917:   would definitely match a dynamic bootp client.
 1918: 
 1919: - The 'ddns-update-style' configuration warning bit now insists that
 1920:   the configuration be globally scoped.
 1921: 
 1922: - Two memory leaks in dhclient were closed thanks to a patch from Felix
 1923:   Farkas.
 1924: 
 1925: - Some minor but excellently pedantic documentation errors were fixed
 1926:   thanks to a patch from Thomas Klausner.
 1927: 
 1928: - Bugs in operator precedence in executable statements have been repaired
 1929:   once again.  More legal syntaxes should be parsed legally.
 1930: 
 1931: - Failing to initialize a tracefile for any reason if a tracefile was
 1932:   specified is now a fatal error.  Thanks to a patch from Albert Herranz.
 1933: 
 1934: - Corrected a bug in which the number of leases transferred as calculated
 1935:   by the failover primary and sent to peers in POOLRESP responses may be
 1936:   incorrect.  This value is not believed to be used by other failover
 1937:   implementations, excepting perhaps as logged information.
 1938: 
 1939: - Corrected a bug in which 'dhcp_failover_send_poolresp()' was in fact
 1940:   sending POOLREQ messages instead of POOLRESP mesasges.  This message
 1941:   was essentially ignored since failover secondaries effectively do not
 1942:   respond to POOLREQ messages.
 1943: 
 1944: - Type definitions for various bitwidths of integers in the sunos5-5
 1945:   build of ISC DHCP have been fixed.  It should compile and run more
 1946:   easily when built in 64-bit for this platform.
 1947: 
 1948: - "allow known-clients;" is now a legal syntax, to avoid confusion.
 1949: 
 1950: - If one dhcp server chooses to 'load balance' a request to its failover
 1951:   peer, it first checks to see if it believes said peer has a free
 1952:   lease to allocate before ignoring the DISCOVER.
 1953: 
 1954: - log() was logging a work buffer, rather than the value returned by
 1955:   executing the statements configured by the user.  In some cases,
 1956:   the work buffer and the intended results were the same.  In some other
 1957:   cases, they were not.  This was fixed thanks to a patch from Gunnar
 1958:   Fjone and directconnect.no.
 1959: 
 1960: - Compiler warnings for some string type conversions was fixed, thanks
 1961:   to Andreas Gustafsson.
 1962: 
 1963: - The netbsd build environments were simplified to one, in which
 1964:   -Wconversion is not used, thanks to Andreas Gustafsson.
 1965: 
 1966: - How randomness in the backoff-cutoff dhclient configuration variable
 1967:   is implemented was better documented in the manpage, and the behaviour
 1968:   of dhclient in REQUEST timeout handling was changed to match that of
 1969:   DISCOVER timeout handling.
 1970: 
 1971: - Omapi was hardened against clients that pass in null values, thanks
 1972:   to a patch from Mark Jason Dominus.
 1973: 
 1974: - A bug was fixed in dhclient that kept it from doing client-side
 1975:   ddns updates.  Thanks to a patch from Andreas Gustafsson, which
 1976:   underwent some modification after review by Jason Vas Dias.
 1977: 
 1978: - Failover implementations disconnected due to the network between
 1979:   them (rather than one of the two shutting down) will now try to
 1980:   re-establish the failover connection every 5 seconds, rather than
 1981:   to simply try once and give up until one of them is restarted.
 1982:   Thanks to a patch from Ulf Ekberg from Infoblox, and field testing
 1983:   by Greger V. Teigre which led to an enhancement to it.
 1984: 
 1985: - A problem that kept DHCP Failover secondaries from tearing down
 1986:   ddns records was repaired.  Thanks to a patch from Ulf Ekberg from
 1987:   Infoblox.
 1988: 
 1989: - 64bit pointer sizes are detected properly on FreeBSD now.
 1990: 
 1991: - A bug was repaired where the DHCP server would leave stale references
 1992:   to host records on leases it once thought about offering to certain
 1993:   clients.  The result would be to apply host and 'known' scopes to the
 1994:   wrong clients (possibly denying booting).  NOTE:  The 'mis-host' patch
 1995:   that was being circulated as a workaround is not the way this bug was
 1996:   fixed.  If you were a victim of this bug in 3.0.1, you are cautioned
 1997:   to proceed carefully and see if it fixes your problem.
 1998: 
 1999: - A bug was repaired in the server's DHCPINFORM handling, where it
 2000:   tried to divine the client's address from the source packet and
 2001:   would get it wrong.  Thanks to Anshuman Singh Rawat.
 2002: 
 2003: - A log message was introduced to help illuminate the case where the
 2004:   server was unable to find a lease to assign to any BOOTP client.
 2005:   Thanks to Daniel Baker.
 2006: 
 2007: - A minor dhcpd.conf.5 manpage error was fixed.
 2008: 
 2009: 			Changes since 3.0.1rc14
 2010: 
 2011: - The global variable 'cur_time' was centralized and is now uniformly of a
 2012:   type #defined in system-dependent headers.  It had previously been defined
 2013:   in one of many places as a 32-bit value, and this causes mayhem on 64-bit
 2014:   big endian systems.  It probably wasn't too healthy on little endian
 2015:   systems either.
 2016: 
 2017: - A printf format string error introduced in rc14 was repaired.
 2018: 
 2019: - AIX system-dependent header file was altered to only define NO_SNPRINTF
 2020:   if the condition used to #ifdef in vsnprintf in AIX' header files
 2021:   is false.
 2022: 
 2023: - The Alpha/OSF system-dependent header file was altered to define
 2024:   NO_SNPRINTF on OS revisions older than 4.0G.
 2025: 
 2026: - omapip/test.c had string.h added to its includes.
 2027: 
 2028: 			Changes since 3.0.1rc13
 2029: 
 2030: ! CAN-2004-0460 - CERT VU#317350: Five stack overflow exploits were closed
 2031:   in logging messages with excessively long hostnames provided by the
 2032:   clients.  It is highly probable that these could have been used by
 2033:   attackers to gain arbitrary root access on systems using ISC DHCP 3.0.1
 2034:   release candidates 12 or 13.  Special thanks to Gregory Duchemin for
 2035:   both finding and solving the problem.
 2036: 
 2037: ! CAN-2004-0461 - CERT VU#654390: Once the above was closed, an opening
 2038:   in log_*() functions was evidenced, on some specific platforms where
 2039:   vsnprintf() was not believed to be available and calls were wrapped to
 2040:   sprintf() instead.  Again, credit goes to Gregory Duchemin for finding
 2041:   the problem.  Calls to snprintf() are now linked to a distribution-local
 2042:   snprintf implementation, only in those cases where the architecture is
 2043:   not known to provide one (see includes/cf/[arch].h).  If you experience
 2044:   linking problems with snprintf/vsnprintf or 'isc_print_' functions, this
 2045:   is where to look.  This vulnerability did not exist in any previously
 2046:   published version of ISC DHCP.
 2047: 
 2048: - Compilation on hpux 11.11 was repaired.
 2049: 
 2050: - 'The cross-compile bug fix' was backed out.
 2051: 
 2052: 			Changes since 3.0.1rc12
 2053: 
 2054: - Fixed a bug in omapi lease lookup function, to form the hardware
 2055:   address for the hash lookup correctly, thanks to a patch from
 2056:   Richard Hirst.
 2057: 
 2058: - Fixed a bug where dhcrelay was sending relayed responses back to the
 2059:   broadcast address, but with the source's unicast mac address.  Should
 2060:   now conform to rfc2131 section 4.1.
 2061: 
 2062: - Cross-compile bug fix; use $(AR) instead of ar.  Thanks to Morten Brorup.
 2063: 
 2064: - Fixed a crash bug in dhclient where dhcpd servers that do not provide
 2065:   renewal times results in an FPE.  As a side effect, dhclient can now
 2066:   properly handle 0xFFFFFFFF (-1) expiry times supplied by servers.  Thanks
 2067:   to a patch from Burt Silverman.
 2068: 
 2069: - The 'ping timeout' debugs from rc12 were removed to -DDEBUG only,
 2070:   and reformatted to correct a compilation error on Solaris platforms.
 2071: 
 2072: - A patch was applied which fixes a case where leases read from the
 2073:   leases database do not properly over-ride previously read leases.
 2074: 
 2075: - dhcpctl.3 manpage was tweaked.
 2076: 
 2077: 			Changes since 3.0.1rc11
 2078: 
 2079: - A patch from Steve Campbell was applied with minor modifications to
 2080:   permit reverse dns PTR record updates with values containing spaces.
 2081: 
 2082: - A patch from Florian Lohoff was applied with some modifications to
 2083:   dhcrelay.  It now discards packets whose hop count exceeds 10 by default,
 2084:   and a command-line option (-c) can be used to set this threshold.
 2085: 
 2086: - A failover bug relating to identifying peers by name length instead of
 2087:   by name was fixed.
 2088: 
 2089: - Declaring failover configs within shared-network statements should no
 2090:   longer result in error.
 2091: 
 2092: - The -nw command line option to dhclient now works.
 2093: 
 2094: - Thanks to a patch from Michael Richardson:
 2095: 	- Some problems with long option processing have been fixed.
 2096: 	- Some fixes to minires so that updates of KEY records will work.
 2097: 
 2098: - contrib/ms2isc was updated by Shu-Min Chang of the Intel Corporation.
 2099:   see contrib/ms2isc/readme.txt for revision notes.
 2100: 
 2101: - Dhclient no longer uses shell commands to kill another instance of
 2102:   itself, it sends the signal directly.  Thanks to a patch from Martin
 2103:   Blapp.
 2104: 
 2105: - The FreeBSD dhclient-script was changed so that a failure to write to
 2106:   /etc/resolv.conf does not prematurely end the script.  This keeps dhclient
 2107:   from looping infinitely when this is the case.  Thanks to a patch from
 2108:   Martin Blapp.
 2109: 
 2110: - A patch from Bill Stephens was applied which resolves a problem with lease
 2111:   expiry times in failover configurations.
 2112: 
 2113: - A memory leak in configuration parsing was closed thanks to a patch from
 2114:   Steve G.
 2115: 
 2116: - The function which discovers interfaces will now skip non-broadcast or
 2117:   point-to-point interfaces, thanks to a patch from David Brownlee.
 2118: 
 2119: - Options not yet known by the dhcpd or dhclient have had their names
 2120:   changed such that they do not contain # symbols, in case they should ever
 2121:   appear in a lease file.  An option that might have been named "#144" is
 2122:   now "unknown-144".
 2123: 
 2124: - Another patch from Bill Stephens which allows the ping-check timeout to
 2125:   be configured as 'ping-timeout'.  Defaults to 1.
 2126: 
 2127: 			Changes since 3.0.1rc10
 2128: 
 2129: - Potential buffer overflows in minires repaired.
 2130: 
 2131: - A change to the linux client script to use /bin/bash, since /bin/sh may
 2132:   not be bash.
 2133: 
 2134: - Some missing va_end cleanups thanks to a patch from Thomas Klausner.
 2135: 
 2136: - A correction of boolean parsing syntax validation - some illegal syntaxes
 2137:   that worked before are now detected and produce errs, some legal syntaxes
 2138:   that errored before will now work properly.
 2139: 
 2140: - Some search-and-replace errors that caused some options to change their
 2141:   names was repaired.
 2142: 
 2143: - Shu-min Chang of the Intel corporation has contributed a perl script and
 2144:   module that converts the MS NT4 DHCP configuration to a ISC DHCP3
 2145:   configuration file.
 2146: 
 2147: - Applied the remainder of the dhcpctl memory leak patch provided by Bill
 2148:   Squier at ReefEdge, Inc.  (groo@reefedge.com).
 2149: 
 2150: - Missing non-optional failover peer configurations will now result in a soft
 2151:   error rather than a null dereference.
 2152: 
 2153: 			Changes since 3.0.1rc9
 2154: 
 2155: - A format string was corrected to fix compiler warnings.
 2156: 
 2157: - A number of spelling corrections were made in the man pages.
 2158: 
 2159: - The dhclient.conf.5 man page was changed to refer to do-forward-updates
 2160:   rather than a configuration option that doesn't exist.
 2161: 
 2162: - A FreeBSD-specific bug in the interface removal handling was fixed.
 2163: 
 2164: - A Linux-specific Token Ring detection problem was fixed.
 2165: 
 2166: - Hashes removed from as-yet-unknown agent options, having those options
 2167:   appear in reality before we know about them will no longer produce
 2168:   self-corrupting lease databases.
 2169: 
 2170: - dhclient will use the proper port numbers now when using the -g option.
 2171: 
 2172: - A order-of-operations bug with 2 match clauses in 1 class statement is
 2173:   fixed thanks to a patch from Andrew Matheson.
 2174: 
 2175: - Compilation problems on Solaris were fixed.
 2176: 
 2177: - Compilation problems when built with DEBUG or DEBUG_PACKET were repaired.
 2178: 
 2179: - A fix to the dhcp ack process which makes certain group options will be
 2180:   included in the first DHCPOFFER message was made thanks to a patch from
 2181:   Ling Gou.
 2182: 
 2183: - A few memory leaks were repaired thanks to patches from Bill Squier at
 2184:   ReefEdge, Inc.  (groo@reefedge.com).
 2185: 
 2186: - A fix for shared-networks that sometimes give clients options for the
 2187:   wrong subnets (in particular, 'option routers') was applied, thanks to
 2188:   Ted Lemon for the patch.
 2189: 
 2190: - Omshell's handling of dotted octets as values was changed such that dots
 2191:   one after the other produce zero values in the integer string.
 2192: 
 2193: 			Changes since 3.0.1rc8
 2194: 
 2195: - Fix a format string vulnerability in the server that could lead to a
 2196:   remote root compromise (discovered by NGSEC Research Team, www.ngsec.com).
 2197: 
 2198: - Add additional support for NetBSD/sparc64.
 2199: 
 2200: - Fix a bug in the command-line parsing of the client.  Also, resolve
 2201:   a memory leak.
 2202: 
 2203: - Add better support for shells other than bash in the Linux client
 2204:   script.
 2205: 
 2206: - Various build fixes for modern versions of FreeBSD and Linux.
 2207: 
 2208: - Fix a bad bounds check when printing binding state names.
 2209: 
 2210: - Clarify documentation about fixed-address and multiple addresses.
 2211: 
 2212: - Fix a typo in the authoritative error message.
 2213: 
 2214: - Make a log entry when we can't write a billing class.
 2215: 
 2216: - Use conversion targets that are the right size on all architectures.
 2217: 
 2218: - Increment the hop count when relaying.
 2219: 
 2220: - Log a message when lease state is changed through OMAPI.
 2221: 
 2222: - Don't rerun the shared_network when evaluating the pool.
 2223: 
 2224: - Fix a reversed test in the parser.
 2225: 
 2226: - Change the type of rbuf_max.
 2227: 
 2228: - Make FTS_LAST a manifest constant to quiet warnings.
 2229: 
 2230: 			Changes since 3.0.1rc7
 2231: 
 2232: - Fix two compiler warnings that are generated when compiling on Solaris
 2233:   with gcc.   These stop the build, even though they weren't actually
 2234:   errors, because we prefer that our builds generate no warnings.
 2235: 
 2236: 			Changes since 3.0.1rc6
 2237: 
 2238: - Don't allow a lease that's in the EXPIRED, RELEASED or RESET state
 2239:   to be renewed.
 2240: 
 2241: - Implement lease stealing for cases where the primary has fewer leases
 2242:   than the secondary, as called for by the standard.
 2243: 
 2244: - Add a fudge factor to the lease expiry acceptance code, (suggested
 2245:   by Kevin Miller of CMU).
 2246: 
 2247: - Fix a bug in permit_list_match that made it much too willing to say
 2248:   that two permit lists matched.
 2249: 
 2250: - Unless DEBUG_DNS_UPDATES is defined, print more user-friendly (and
 2251:   also more compact) messages about DNS updates.
 2252: 
 2253: - Fix a bug in generating wire-format domain names for the FQDN option.
 2254: 
 2255: - Fix a bug where the FQDN option would not be returned if the client
 2256:   requested it, contrary to the standard.
 2257: 
 2258: - On Darwin, use the FreeBSD DHCP client script.
 2259: 
 2260: - On NetBSD/sparc, don't check for casting warnings.
 2261: 
 2262: - Add a flag in the DHCP client to disable updating the client's A
 2263:   record when sending an FQDN option indicating that the client is
 2264:   going to update its A record.
 2265: 
 2266: - In the client, don't attempt a DNS update until one second after
 2267:   configuring the new IP address, and if the update times out, keep
 2268:   trying until a response, positive or negative, is received from the
 2269:   DNS server.
 2270: 
 2271: - Fix an uninitialized memory bug in the DHCP client.
 2272: 
 2273: - Apply some FreeBSD-specific bug fixes suggested by Murray Stokely.
 2274: 
 2275: - Fix a bug in ns_parserr(), where it was returning the wrong sort
 2276:   of result code in some cases (suggested by Ben Harris of the
 2277:   NetBSD project).
 2278: 
 2279: - Fix a bug in is_identifier(), where it was checking against EOF
 2280:   instead of the END_OF_FILE token (also suggested by Ben Harris).
 2281: 
 2282: - Fix a bug where if an option universe contained no options, the
 2283:   DHCP server could dump core (Walter Steiner).
 2284: 
 2285: - Fix a bug in the handling of encapsulated options.
 2286: 
 2287: - Fix a bug that prevented NWIP suboptions from being processed.
 2288: 
 2289: - Delete the FTS_BOOTP and FTS_RESERVED states and implement them
 2290:   as modifier flags to the FTS_ACTIVE state, as called for in the
 2291:   failover protocol standard.
 2292: 
 2293: - Fix bugs in the pool merging code that resulted in references and
 2294:   dereferences of null pointers.   This bug had no impact unless the
 2295:   POINTER_DEBUG flag was defined.
 2296: 
 2297: - In the server, added a do-forward-updates flag that can be used to
 2298:   disable forward updates in all cases, so that sites that want the
 2299:   clients to take sole responsibility for updating their A record can
 2300:   do so.
 2301: 
 2302: - Make it possible to disable optimization of PTR record updates.
 2303: 
 2304: 			Changes since 3.0.1rc5
 2305: 
 2306: - Include some new documentation and changes provided by Karl Auer.
 2307: 
 2308: - Add a workaround for some Lexmark printers that send a double-NUL-
 2309:   terminated host-name option, which would break DNS updates.
 2310: 
 2311: - Fix an off-by-one error in the MAC-address checking code for
 2312:   DHCPRELEASE that was added in 3.0.1rc5.
 2313: 
 2314: - Fix a bug where client-specific information was not being discarded
 2315:   from the lease when it expired or was released, resulting in
 2316:   problems if the lease was reallocated to a different client.
 2317: 
 2318: - If more than one allocation pool is specified that has the same set
 2319:   of constraints as another allocation pool on the same shared
 2320:   network, merge the two pools.
 2321: 
 2322: - Don't print an error in fallback_discard, since this just causes
 2323:   confusion and does not appear to be helping to encourage anyone to
 2324:   fix this bug.
 2325: 
 2326: 			Changes since 3.0.1rc4
 2327: 
 2328: - Fix a bug that would cause the DHCP server to spin if asked to parse
 2329:   a certain kind of incorrect statement.
 2330: 
 2331: - Fix a related bug that would prevent an error from being reported in
 2332:   the same case.
 2333: 
 2334: - Additional documentation.
 2335: 
 2336: - Make sure that the hardware address matches the lease when
 2337:   processing a DHCPRELEASE message.
 2338: 
 2339: 			Changes since 3.0.1rc3
 2340: 
 2341: - A minor bug fix in the arguments to a logging function call.
 2342: - Documentation update for dhcpd.conf.
 2343: 
 2344: 		        Changes since 3.0.1rc2
 2345: 
 2346: - Allow the primary to send a POOLREQ message.   This isn't what the current
 2347:   failover draft says to do, so we may have to back it out if I can't get the
 2348:   authors to relent, but the scheme for balancing that's specified in the
 2349:   current draft seems needlessly hairy, so I'm floating a trial balloon.
 2350:   The rc1 code did not implement the method described in the draft either.
 2351: 
 2352: 		        Changes since 3.0.1rc1
 2353: 
 2354: - Treat NXDOMAIN and NXRRSET as success when we are trying to delete a
 2355:   domain or RRSET.   This allows the DHCP server to forget about a name
 2356:   it added to the DNS once it's been removed, even if the DHCP server
 2357:   wasn't the one that removed it.
 2358: 
 2359: - Install defaults for failover maximum outstanding updates and maximum
 2360:   silent time.   This prevents problems that might occur if these values
 2361:   were not configured.
 2362: 
 2363: - Don't do DDNS deletes if ddns-update-style is none.
 2364: 
 2365: - Return relay agent information options in DHCPNAK.   This prevents DHCPNAK
 2366:   messages from being dropped when the relay agent information option contains
 2367:   routing information.
 2368: 
 2369: - Fix a problem where coming up in recover wouldn't result in an update
 2370:   request being sent.
 2371: 
 2372: - Add some more chatty messages when we start a recovery update and when it's
 2373:   done.
 2374: 
 2375: - Fix a possible problem where some state might have been left around
 2376:   after the peer lost contact and regained contact about how many updates
 2377:   were pending.
 2378: 
 2379: - Don't nix a lease update because of a lease conflict.   This test has
 2380:   never (as far as I know) prevented a mistake, and it appears to cause
 2381:   problems with failover.
 2382: 
 2383: - Add support in rc history code for keeping a selective history, rather
 2384:   than a history of all references and dereferences.   This code is only used
 2385:   when extensive additional debugging is enabled.
 2386: 
 2387: 		           Changes since 3.0
 2388: 
 2389: - Make allocators for hash tables.   As a side effect, this fixes a memory
 2390:   smash in the subclass allocation code.
 2391: 
 2392: - Fix a small bug in omshell where if you try to close an object when
 2393:   no object is open, it dumps core.
 2394: 
 2395: - Fix an obscure coredump that could occur on shutdown.
 2396: 
 2397: - Fix a bug in the recording of host declaration rubouts in the lease file.
 2398: 
 2399: - Fix two potential spins in the host deletion code.
 2400: 
 2401: - Fix a core dump that would happen if an application tried to update
 2402:   a host object attribute with a null value.
 2403: 
 2404: 		Changes since 3.0 Release Candidate 12
 2405: 
 2406: - Fix a memory leak in the evaluation code.
 2407: 
 2408: - Fix an obscure core dump.
 2409: 
 2410: - Print a couple of new warnings when parsing the configuration file
 2411:   when crucial information is left out.
 2412: 
 2413: - Log "no free leases" as an error.
 2414: 
 2415: - Documentation updates.
 2416: 
 2417: 		Changes since 3.0 Release Candidate 11
 2418: 
 2419: - Always return a subnet selection option if one is sent.
 2420: 
 2421: - Fix a warning that was being printed because an automatic data
 2422:   structure wasn't zeroed.
 2423: 
 2424: - Fix some failover state transitions that were being handled
 2425:   incorrectly.
 2426: 
 2427: - When supersede_lease is called on a lease whose end time has already
 2428:   expired, but for which a state transition has not yet been done, do
 2429:   a state transition.   This fixes the case where if the secondary
 2430:   allocated a lease to a client and the lease "expired" while the
 2431:   secondary was in partner-down, no expiry event would actually
 2432:   happen, so the lease would remain active until the primary was
 2433:   restarted.
 2434: 
 2435: 		Changes since 3.0 Release Candidate 10
 2436: 
 2437: - Fix a bug that was preventing released leases from changing state
 2438:   in failover-enabled pools.
 2439: 
 2440: - Fix a core dump in the client identifier finder code (for host
 2441:   declarations).
 2442: 
 2443: - Finish fixing a bug where bogus data would sometimes get logged to
 2444:   the dhclient.leases file because it was opened as descriptor 2.
 2445: 
 2446: - Fix the Linux dhclient-script according to suggestions made by
 2447:   several people on the dhcp-client mailing list.
 2448: 
 2449: - Log successful DNS updates at LOG_INFO, not LOG_ERROR.
 2450: 
 2451: - Print an error message and refuse to run if a failover peer is
 2452:   defined but not referenced by any pools.
 2453: 
 2454: - Correct a confusing error message in failover.
 2455: 
 2456: 		Changes since 3.0 Release Candidate 9
 2457: 
 2458: - Fix a bug in lease allocation for Dynamic BOOTP clients.
 2459: 
 2460: 	  Changes since 3.0 Release Candidate 8 Patchlevel 2
 2461: 
 2462: - Fix a bug that prevented update-static-leases from working.
 2463: 
 2464: - Document failover-state OMAPI object.
 2465: 
 2466: - Fix a compilation error on SunOS 4.
 2467: 
 2468: 	  Changes since 3.0 Release Candidate 8 Patchlevel 1
 2469: 
 2470: - Fix a parsing bug that broke dns updates (both interim and ad-hoc).
 2471:   This was introduced in rc8pl1 as an unintended result of the memory
 2472:   leakage fixes that were in pl1.
 2473: 
 2474: - Fix a long-standing bug where the server would record that an update
 2475:   had been done for a client with no name, even though no update had
 2476:   been done, and then when the client's lease expired the deletion of
 2477:   that nonexistant record would time out because the name was the null
 2478:   string. 
 2479: 
 2480: - Clean up the omshell, dhcpctl and omapi man pages a bit.
 2481: 
 2482: 		Changes since 3.0 Release Candidate 8
 2483: 
 2484: - Fix a bug that could cause the DHCP server to spin if
 2485:   one-lease-per-client was enabled.
 2486: 
 2487: - Fix a bug that was causing core dumps on BSD/os in the presence of
 2488:   malformed packets.
 2489: 
 2490: - In partner-down state, don't restrict lease lengths to MCLT.
 2491: 
 2492: - On the failover secondary, record the MCLT received from the primary
 2493:   so that if we come up without a connection to the primary we don't
 2494:   wind up giving out zero-length leases.
 2495: 
 2496: - Fix some compilation problems on BSD/os.
 2497: 
 2498: - Fix a bunch of memory leaks.
 2499: 
 2500: - Fix a couple of bugs in the option printer.
 2501: 
 2502: - Fix an obscure error reporting bug in the dns update code, and also
 2503:   make the message clearer when a key algorithm isn't supported.
 2504: 
 2505: - Fix a bug in the tracing code that prevented trace runs that used
 2506:   tcp connections from being played back.
 2507: 
 2508: - Add some additional debugging capability for catching memory leaks
 2509:   on exit.
 2510: 
 2511: - Make the client release the lease correctly on shutdown.
 2512: 
 2513: - Add some configurability to the build system.
 2514: 
 2515: - Install omshell manual page in man1, not man8.
 2516: 
 2517: - Craig Gwydir sent in a patch that fixes a long-standing bug in the
 2518:   DHCP client that could cause core dumps, but that for some reason
 2519:   hadn't been noticed until now.
 2520: 
 2521: 		Changes since 3.0 Release Candidate 7
 2522: 
 2523: - Fix a bug in failover where we weren't sending updates after a
 2524:   transition from communications-interrupted to normal.
 2525: 
 2526: - Handle expired/released/reset -> free transition according to the
 2527:   protocol specification (this works - the other way not only wasn't
 2528:   conformant, but also didn't work).
 2529: 
 2530: - Add a control object in both client and server that allows either
 2531:   daemon to be shut down cleanly.
 2532: 
 2533: - When writing a lease, if we run out of disk space, shut down the
 2534:   output file and insist on writing a new one before proceeding.
 2535: 
 2536: - In the server, if the OMAPI listener port is occupied, keep trying
 2537:   to get it, rather than simply giving up and exiting.
 2538: 
 2539: - Support fetching variables from leases and also updating and adding
 2540:   variables to leases via OMAPI.
 2541: 
 2542: - If two failover peers have wildly different clocks, refuse to start
 2543:   doing failover.
 2544: 
 2545: - Fix a bug in the DNS update code that could cause core dumps when
 2546:   running on alpha processors.
 2547: 
 2548: - Fixed a bug in ddns updates for static lease entries, thanks to a
 2549:   patch from Andrey M Linkevitch.
 2550: 
 2551: - Add support for Darwin/MacOS X
 2552: 
 2553: - Install omshell (including new documentation).
 2554: 
 2555: - Support DNS updates in the client (this is a very obscure feature
 2556:   that most DHCP client users probably will not be able to use).
 2557: 
 2558: - Somewhat cleaner status logging in the client.
 2559: 
 2560: - Make OMAPI key naming syntax compatible with the way keys are
 2561:   actually named (key names are domain names).
 2562: 
 2563: - Fix a bug in the lease file writer.
 2564: 
 2565: - Install DHCP ISC headers in a different place than BIND 9 ISC
 2566:   headers, to avoid causing trouble in BIND 9 builds.
 2567: 
 2568: - Don't send updates for attributes on an object when the attributes
 2569:   haven't changed.   Support deleting attributes on remote objects.
 2570: 
 2571: - Fix a number of bugs in omshell, and add the unset and refresh
 2572:   statements.
 2573: 
 2574: - Handle disconnects in OMAPI a little bit more intelligently (so that
 2575:   the caller gets ECONNRESET instead of EINVAL).
 2576: 
 2577: - Fix a bunch of bugs in the handling of clients that have existing
 2578:   leases when the try to renew their leases while failover is
 2579:   operating.
 2580: 
 2581: 		Changes since 3.0 Release Candidate 6
 2582: 
 2583: - Fix a core dump that could happen when processing a DHCPREQUEST from
 2584:   a client that had a host declaration that contained both a
 2585:   fixed-address declaration and a dhcp-client-identifier option
 2586:   declaration, if the client identifier was longer than nine bytes.
 2587: 
 2588: - Fix a memory leak that could happen in certain obscure cases when
 2589:   using omapi to manipulate leases.
 2590: 
 2591: - Fix some bugs and omissions in omshell.
 2592: 
 2593: 		Changes since 3.0 Release Candidate 5
 2594: 
 2595: - Fix a bug in omapi_object_dereference that prevented objects in
 2596:   chains from having their reference counts decreased on dereference.
 2597: 
 2598: - Fix a bug in omapi_object_dereference that would prevent object
 2599:   chains from being freed upon removal of the last reference external
 2600:   to the chain.
 2601: 
 2602: - Fix a number of other memory leaks in the OMAPI protocol subsystem.
 2603: 
 2604: - Add code in the OMAPI protocol handler to trace memory leakage.
 2605: 
 2606: - Clean up the memory allocation/reference history printer.
 2607: 
 2608: - Support input of dotted quads and colon-separated hex lists as
 2609:   attribute values in omshell.
 2610: 
 2611: - Fix a typo in the Linux interface discovery code.
 2612: 
 2613: - Conditionalize a piece of trace code that wasn't conditional.
 2614: 
 2615: 		Changes since 3.0 Release Candidate 4
 2616: 
 2617: - Fix a bug that would prevent leases from being abandoned properly on
 2618:   DHCPDECLINE.
 2619: 
 2620: - Fix failover peer OMAPI support.
 2621: 
 2622: - In failover, correctly handle expiration of leases.   Previously,
 2623:   leases would never be reclaimed because they couldn't make the
 2624:   transition from EXPIRED to FREE.
 2625: 
 2626: - Fix some broken failover state transitions.
 2627: 
 2628: - Documentation fixes.
 2629: 
 2630: - Take out an unnecessary check in DHCP relay agent information option
 2631:   stashing code that was preventing REBINDING clients from rebinding.
 2632: 
 2633: - Prevent failover peers from allocating leases in DHCPREQUEST
 2634:   processing if the lease belongs to the other server.
 2635: 
 2636: - Record server version in lease file introductory comment.
 2637: 
 2638: - Correctly report connection errors in OMAPI and failover.
 2639: 
 2640: - Make authentication signature algorithm name comparisons in OMAPI
 2641:   case-insensitive.
 2642: 
 2643: - Fix compile problem on SunOS 4.x
 2644: 
 2645: - If a signature algorithm is not terminated with '.', terminate it so
 2646:   that comparisons between fully-qualified names will work
 2647:   consistently.
 2648: 
 2649: - Different SIOCGIFCONF probe code, may "fix" problem on some Linux
 2650:   systems with the probe not working correctly.
 2651: 
 2652: - Don't allow user to type omapi key on command line of omshell.
 2653: 
 2654: 		Changes since 3.0 Release Candidate 3
 2655: 
 2656: - Do lease billing on startup in a way that I *think* will finally do
 2657:   the billing correctly - the previous method could overbill as a
 2658:   result of duplicate leases.
 2659: 
 2660: - Document OMAPI server objects.
 2661: 
 2662: 	  Changes since 3.0 Release Candidate 2 Patchlevel 1
 2663: 
 2664: - Fix some problems in the DDNS update code.   Thanks to Albert
 2665:   Herranz for figuring out the main problem.
 2666: 
 2667: - Fix some reference counting errors on host entries that were causing
 2668:   core dumps.
 2669: 
 2670: - Fix a byte-swap bug in the token ring code, thanks to Jochen
 2671:   Friedrich.
 2672: 
 2673: - Fix a bug in lease billing, thanks to Jonas Bulow.
 2674: 
 2675: 		Changes since 3.0 Release Candidate 2
 2676: 
 2677: - Change the conditions under which a DHCPRELEASE is actually
 2678:   committed to be consistent with lease binding states rather than
 2679:   using the lease end time.   This may fix some problems with the
 2680:   billing class code.
 2681: 
 2682: - Fix a bug where lease updates would fail on Digital Unix (and maybe
 2683:   others) because malloc was called with a size of zero.
 2684: 
 2685: - Fix a core dump that happens when the DHCP server can't create its
 2686:   trace file.
 2687: 
 2688: 	  Changes since 3.0 Release Candidate 1 Patchlevel 1
 2689: 
 2690: - Fix the dhcp_failover_put_message to not attempt to allocate a
 2691:   zero-length buffer.   Some versions of malloc() fail if you try to
 2692:   allocate a zero-length buffer, and this was causing problems on,
 2693:   e.g., Digital Unix.
 2694: 
 2695: - Fix a case where the failover code was printing an error message
 2696:   when no error had occurred.
 2697: 
 2698: - Fix a problem where when a server went down and back up again, the
 2699:   peer would not see a state transition and so would stay in the
 2700:   non-communicating state.
 2701: 
 2702: - Be smart about going into recover_wait.
 2703: 
 2704: - Fix a problem in the failover implementation where peers would fail
 2705:   to come into sync if interrupted in the RECOVER state.   This could
 2706:   have been the cause of some problems people have reported recently.
 2707: 
 2708: - Fix a problem with billing classes where they would not be unbilled
 2709:   when the client lease expired.
 2710: 
 2711: - If select fails, figure out which descriptor is bad, and cut it out
 2712:   of the I/O loop.   This prevents a potentially nasty spin.  I
 2713:   haven't heard any report it in a while, but it came up consistently
 2714:   in testing.
 2715: 
 2716: - Fix a bug in the relay agent where if you specified interfaces on
 2717:   the command line, it would fail.
 2718: 
 2719: - Fix a couple of small bugs in the omapi connection object (no known
 2720:   user impact).
 2721: 
 2722: - Add the missing 3.0 Beta 1 lease conversion script.
 2723: 
 2724: - Read dhcp client script hooks if they exist, rather than only if
 2725:   they're executable.
 2726: 
 2727: 		Changes since 3.0 Release Candidate 1
 2728: 
 2729: - Fix a memory smash that happens when fixed-address leases are used.
 2730:   ANY SITE AT WHICH FIXED-ADDRESS STATEMENTS ARE BEING USED SHOULD
 2731:   UPGRADE IMMEDIATELY.   This has been a long-standing bug - thanks to
 2732:   Alvise Nobile for discovering it and helping me to find it!
 2733: 
 2734: - Fix a small bug in binary-to-ascii, thanks to H. Peter Anvin of
 2735:   Transmeta.
 2736: 
 2737: - There is a known problem with the DHCP server doing failover on
 2738:   Compaq Alpha systems.   This patchlevel is not a release candidate
 2739:   because of this bug.   The bug should be straightforward to fix, so
 2740:   a new release candidate is expected shortly.
 2741: 
 2742: - There is a known problem in the DDNS update code that is probably a
 2743:   bug, and is not, as far as we know, fixed in this patchlevel.
 2744: 
 2745: 		Changes since 3.0 Beta 2 Patchlevel 24
 2746: 
 2747: - Went over problematic failover state transitions and made them all
 2748:   work, so that failover should now much less fragile.
 2749: 
 2750: - Add some dhcpctl and omapi documentation
 2751: 
 2752: - Fix compile errors when compiling with unusual predefines.
 2753: 
 2754: - Make Token Ring work on Linux 2.4
 2755: 
 2756: - Fix the Digital Unix BPF_WORDALIGN bug.
 2757: 
 2758: - Fix some dhcp client documentation errors.
 2759: 
 2760: - Update some parts of the README file.
 2761: 
 2762: - Support GCC on SCO.
 2763: 
 2764: 	        Changes since 3.0 Beta 2 Patchlevel 23
 2765: 
 2766: - Fix a bug in the DNS update code where a status code was not being
 2767:   checked.   This may have been causing core dumps.
 2768: 
 2769: - When parsing the lease file, if a lease declaration includes a
 2770:   billing class statement, and the lease already has a billing class,
 2771:   unbill the old class.
 2772: 
 2773: - When processing failover transactions, where acks will be deferred,
 2774:   process the state transition immediately.
 2775: 
 2776: -  Don't try to use the new SIOCGIFCONF buffer size detection code on
 2777:    Linux 2.0, which doesn't provide this functionality.
 2778: 
 2779: - Apply a patch suggested by Tuan Uong for a problem in dlpi.c.
 2780: 
 2781: - Fix a problem in using the which command in the configure script.
 2782: 
 2783: - Fix a parse error in the client when setting up an omapi listener.
 2784: 
 2785: - Document the -n and -g flags to the client.
 2786: 
 2787: - Make sure there is always a stdin and stdout on startup.   This
 2788:   prevents shell scripts from accidentally writing error messages into
 2789:   configuration files that happen to be opened as stderr.
 2790: 
 2791: - If an interface is removed, the client will now notice that it is
 2792:   gone rather than spinning.   This has only been tested on NetBSD.
 2793: 
 2794: - The client will attempt to get an address even if it can't create a
 2795:   lease file.
 2796: 
 2797: - Don't overwrite tracefiles.
 2798: 
 2799: - Fix some memory allocation bugs in failover.
 2800: 
 2801: 	        Changes since 3.0 Beta 2 Patchlevel 22
 2802: 
 2803: - Apply some patches suggested by Cyrille Lefevre, who is maintaining
 2804:   the FreeBSD ISC DHCP Distribution port.
 2805: 
 2806: - Fix a core dump in DHCPRELEASE.
 2807: 
 2808: 	        Changes since 3.0 Beta 2 Patchlevel 21
 2809: 
 2810: - This time for sure: fix the spin described in the changes for pl20.
 2811: 
 2812: 	        Changes since 3.0 Beta 2 Patchlevel 20
 2813: 
 2814: - Fix a problem with Linux detecting large numbers of interfaces (Ben)
 2815: 
 2816: - Fix a memory smash in the quotify code, which was introduced in
 2817:   pl19.
 2818: 
 2819: - Actually fix the spin described in the changes for pl20.   The
 2820:   previous fix only partially fixed the problem - enough to get it
 2821:   past the regression test.
 2822: 
 2823: 	        Changes since 3.0 Beta 2 Patchlevel 19
 2824: 
 2825: - Fix a bug that could cause the server to abort if compiled with
 2826:   POINTER_DEBUG enabled.
 2827: 
 2828: - Fix a bug that could cause the server to spin when responding to a
 2829:   DHCPREQUEST.
 2830: 
 2831: - Apply Joost Mulders' suggested patches for DLPI on x86.
 2832: 
 2833: - Support NUL characters in quoted strings.
 2834: 
 2835: - Install unformatted man pages on SunOS.
 2836: 
 2837: 	        Changes since 3.0 Beta 2 Patchlevel 18
 2838: 
 2839: - Allow the server to be placed in partner-down state using OMAPI.
 2840:   (Damien Neil)
 2841: 
 2842: - Implement omshell, which can be used to do arbitrary things to the
 2843:   server (in theory). (Damien Neil)
 2844: 
 2845: - Fix a case where if a client had two different leases the server could
 2846:   actually dereference the second one when it hadn't been referenced,
 2847:   leading to memory corruption and a core dump. (James Brister)
 2848: 
 2849: - Fix a case where a client could request the address of another client's
 2850:   lease, but find_lease wouldn't detect that the other client had it, and
 2851:   would attempt to allocate it to the client, resulting in a lease conflict
 2852:   message.
 2853: 
 2854: - Fix a case where a client with more than one client identifier could be
 2855:   given a lease where the hardware address was correct but the client
 2856:   identifier was not, resulting in a lease conflict message.
 2857: 
 2858: - Fix a problem where the server could write out a colon-separated
 2859:   hex list as a value for a variable, which would then not parse.
 2860:   The fix is to always write strings as quoted strings, with any
 2861:   non-printable characters quoted as octal escape sequences.   So
 2862:   a file written the old way still won't work, but new files written
 2863:   this way will work.
 2864: 
 2865: - Fix documentation for sending non-standard options.
 2866: 
 2867: - Use unparsable names for unknown options.    WARNING: this will
 2868:   break any configuration files that use the option-nnn convention.
 2869:   If you want to continue to use this convention for some options,
 2870:   please be sure to write a definition, like this:
 2871: 
 2872:   option option-nnn code nnn = string;
 2873: 
 2874:   You can use a descriptive name instead of option-nnn if you like.
 2875: 
 2876: - Fix a problem where we would see a DHCPDISCOVER/DHCPOFFER/
 2877:   DHCPREQUEST/DHCPACK/DHCPREQUEST/DHCPNAK sequence.   This was the
 2878:   result of a deceptively silly bug in supersede_lease.
 2879: 
 2880: - Fix client script exit status check, according to a fix supplied by
 2881:   Hermann Lauer.
 2882: 
 2883: - Fix an endianness bug in the tracefile support, regarding ICMP
 2884:   messages.
 2885: 
 2886: - Fix a bug in the client where the medium would not work correctly if
 2887:   it contained quoted strings.
 2888: 
 2889: 		       ** there was no pl17 **
 2890: 
 2891: 	        Changes since 3.0 Beta 2 Patchlevel 16
 2892: 
 2893: - Add support for transaction tracing.   This allows the state of the
 2894:   DHCP server on startup, and all the subsequent transactions, to be
 2895:   recorded in a file which can then be played back to reproduce the
 2896:   behaviour of the DHCP server.   This can be used to quickly
 2897:   reproduce bugs that cause core dumps or corruption, and also for
 2898:   tracking down memory leaks.
 2899: 
 2900: - Incorporate some bug fixes provided by Joost Mulders for the DLPI
 2901:   package which should clear up problems people have been seeing on
 2902:   Solaris.
 2903: 
 2904: - Fix bugs in the handling of options stored as linked lists (agent
 2905:   options, fqdn options and nwip options) that could cause memory
 2906:   corruption and core dumps.
 2907: 
 2908: - Fix a bug in DHCPREQUEST handling that resulted in DHCPNAK messages
 2909:   not being send in some cases when they were needed.
 2910: 
 2911: - Make the lease structure somewhat more compact.
 2912: 
 2913: - Make initial failover startup *much* faster.   This was researched
 2914:   and implemented by Damien Neil.
 2915: 
 2916: - Add a --version flag to all executables, which prints the program
 2917:   name and version to standard output.
 2918: 
 2919: - Don't rewrite the lease file every thousand leases.
 2920: 
 2921: - A bug in nit.c for older SunOS machines was fixed by a patch sent in
 2922:   by Takeshi Hagiwara.
 2923: 
 2924: - Fix a memory corruption bug in the DHCP client.
 2925: 
 2926: - Lots of documentation updates.
 2927: 
 2928: - Add a feature allowing environment variables to be passed to the
 2929:   DHCP client script on the DHCP client command line.
 2930: 
 2931: - Fix client medium support, which had been broken for some time.
 2932: 
 2933: - Fix a bug in the DHCP client initial startup backoff interval, which
 2934:   would cause two DHCPDISCOVERS to be sent back-to-back on startup.
 2935: 
 2936: 	        Changes since 3.0 Beta 2 Patchlevel 15
 2937: 
 2938: - Some documentation tweaks.
 2939: 
 2940: - Maybe fix a problem in the DLPI code.
 2941: 
 2942: - Fix some error code space inconsistencies in ddns update code.
 2943: 
 2944: - Support relay agents that intercept unicast DHCP messages to stuff
 2945:   agent options into them.
 2946: 
 2947: - Fix a small memory leak in the relay agent option support code.
 2948: 
 2949: - Fix a core dump that would occur if a packet was sent with no
 2950:   options.
 2951: 
 2952: 	        Changes since 3.0 Beta 2 Patchlevel 14
 2953: 
 2954: - Finish fixing a long-standing bug in the agent options code.   This
 2955:   was causing core dumps and failing to operate correctly - in
 2956:   particular, agent option stashing wasn't working.   Agent option
 2957:   stashing should now be working, meaning that agent options can be
 2958:   used in class statements to control address allocation.
 2959: 
 2960: - Fix up documentation.
 2961: 
 2962: - Fix a couple of small memory leaks that would have added up
 2963:   significantly in a high-demand situation.
 2964: 
 2965: - Add a log-facility configuration parameter.
 2966: 
 2967: - Fix a compile error on some older operating systems.
 2968: 
 2969: - Add the ability in the client to execute certain statements before
 2970:   transmitting packets to the server.   Handy for debugging; not much
 2971:   practical use otherwise.
 2972: 
 2973: - Don't send faked-out giaddr when renewing or bound - again, useful
 2974:   for debugging.
 2975: 
 2976: 	        Changes since 3.0 Beta 2 Patchlevel 13
 2977: 
 2978: - Fixed a problem where the fqdn decoder would sometimes try to store
 2979:   an option with an (unsigned) negative length, resulting in a core
 2980:   dump on some systems.
 2981: 
 2982: - Work around the Win98 DHCP client, which NUL-terminates the FQDN
 2983:   option.
 2984: 
 2985: - Work around Win98 and Win2k clients that will claim they want to do
 2986:   the update even when they don't have any way to do it.
 2987: 
 2988: - Fix some log messages that can be printed when failover is operating
 2989:   that were not printing enough information.
 2990: 
 2991: - It was possible for a DHCPDISCOVER to get an allocation even when
 2992:   the state machine said the server shouldn't be responding.
 2993: 
 2994: - Don't load balance DHCPREQUESTs from clients in RENEWING and
 2995:   REBINDING, since in RENEWING, if we heard it, it's for us, and in
 2996:   REBINDING, the client wouldn't have got to REBINDING if its primary
 2997:   were answering.
 2998: 
 2999: - When we get a bogus state lease binding state transition, don't do
 3000:   the transition.
 3001:   
 3002: 
 3003: 	        Changes since 3.0 Beta 2 Patchlevel 12
 3004: 
 3005: - Fixed a couple of silly compile errors.
 3006: 
 3007: 		Changes since 3.0 Beta 2 Patchlevel 11
 3008: 
 3009: - Albert Herranz tracked down and fixed a subtle bug in the base64
 3010:   decoder that would prevent any key with an 'x' in its base64
 3011:   representation from working correctly.
 3012: 
 3013: - Thanks to Chris Cheney and Michael Sanders, we have a fix for the
 3014:   hang that they both spotted in the DHCP server - when
 3015:   one-lease-per-client was set, the code to release the "other" lease
 3016:   could spin.
 3017: 
 3018: - Fix a problem with alignment of the input buffer in bpf in cases
 3019:   where two packets arrive in the same bpf read.
 3020: 
 3021: - Fix a problem where the relay agent would crash if you specified an
 3022:   interface name on the command line.
 3023: 
 3024: - Add the ability to conditionalize client behaviour based on the
 3025:   client state.
 3026: 
 3027: - Add support for the FQDN option, and added support for a new way of
 3028:   doing ddns updates (ddns update style interim) that allows more than
 3029:   one DHCP server to update the DNS for the same network(s).   This
 3030:   was implemented by Damien Neil with some additional functionality
 3031:   added by Ted Lemon.
 3032: 
 3033: - Damien added a "log" statement, so that the configuration file can
 3034:   be made to log debugging information and other information.
 3035: 
 3036: - Fixed a bug that caused option buffers not to be terminated with an
 3037:   end option.
 3038: 
 3039: - Fixed a long-standing bug in the support for option spaces where the
 3040:   options are stored as an ordered list rather than in a hash table,
 3041:   which could theoretically result in memory pool corruption.
 3042: 
 3043: - Prevent hardware declarations with no actual hardware address from
 3044:   being written as something unparsable, and behave correctly in the
 3045:   face of a null hardware address on input.
 3046: 
 3047: - Allow key names to be FQDNs, and qualify the algorithm name if it is
 3048:   specified unqualified.
 3049: 
 3050: - Modify the DDNS update code so that it never prints the "resolver
 3051:   failed" message, but instead says *why* the resolver failed.
 3052: 
 3053: - Officially support the subnet selection option, which now has an
 3054:   RFC.
 3055: 
 3056: - Fix a build bug on MacOS X.
 3057: 
 3058: - Allow administrator to disable ping checking.
 3059: 
 3060: - Clean up dhcpd.conf documentation and add more information about how
 3061:   it works.
 3062: 
 3063: 		Changes since 3.0 Beta 2 Patchlevel 10
 3064: 
 3065: - Fix a bug introduced during debugging (!) and accidentally committed
 3066:   to CVS.
 3067: 
 3068: 		Changes since 3.0 Beta 2 Patchlevel 9
 3069: 
 3070: - Fix DHCP client handling of vendor encapsulated options.
 3071: 
 3072: - Fix a bug in the handling of relay agent information options introduced
 3073:   in patchlevel 9.
 3074: 
 3075: - Stash agent options on client leases by default, and use the stashed
 3076:   options at renewal time.
 3077: 
 3078: - Add the ability to test the client's binding state in the client
 3079:   configuration language.
 3080: 
 3081: - Fix a core dump in the DNS update code.
 3082: 
 3083: - Fix some expression evaluation bugs that were causing updates to be
 3084:   done when no client hostname was received.
 3085: 
 3086: - Fix expression evaluation debugging printfs.
 3087: 
 3088: - Teach pretty_print_option to print options in option spaces other than
 3089:   the DHCP option space.
 3090: 
 3091: - Add a warning message if the RHS of a not is not boolean.
 3092: 
 3093: - Never select for more than a day, because some implementations of
 3094:   select will just fail if the timeout is too long (!).
 3095: 
 3096: - Fix a case where a DHCPDISCOVER from an unknown network would be
 3097:   silently dropped.
 3098: 
 3099: - Fix a bug where if a client requested an IP address for which a different
 3100:   client had the lease, the DHCP server would reallocate it anyway.
 3101: 
 3102: - Fix the DNS update code so that if the client changes its name, the DNS
 3103:   will be correctly updated.
 3104: 
 3105: 		Changes since 3.0 Beta 2 Patchlevel 8
 3106: 
 3107: - Oops, there was another subtle math error in the header-length
 3108:   bounds-checking.
 3109: 
 3110: 		Changes since 3.0 Beta 2 Patchlevel 7
 3111: 
 3112: - Oops, forgot to byte-swap udp header length before bounds-checking it.
 3113: 
 3114: 		Changes since 3.0 Beta 2 Patchlevel 6
 3115: 
 3116: - Fix a possible DoS attack where a client could cause the checksummer
 3117:   to dump core.   This was a read, not a write, so it shouldn't be
 3118:   possible to exploit it any further than that.
 3119: 
 3120: - Implement client- and server-side support for using the Client FQDN
 3121:   option.
 3122: 
 3123: - Support for other option spaces in the client has been added.   This
 3124:   means that it is now possible to define a vendor option space on the
 3125:   client, request options in that space from the server (which must
 3126:   define the same option space), and then use those options in the
 3127:   client.   This also allows NWIP and Client FQDN options to be used
 3128:   meaningfully.
 3129: 
 3130: - Add object initializer support.   This means that objects can now be
 3131:   initialized to something other than all-zeros when allocated, which
 3132:   makes, e.g., the interface object support code a little more robust.
 3133: 
 3134: - Fix an off-by-one bug in the host stuffer.   This was causing host
 3135:   deletes not the work, and may also have been causing OMAPI
 3136:   connections to get dropped.   Thanks to James Brister for tracking
 3137:   this one down!
 3138: 
 3139: - Fixed a core dump in the interface discovery code that is triggered
 3140:   when there is no subnet declaration for an interface, but the server
 3141:   decides to continue running.   Thanks to Shane Kerr for tracking
 3142:   down and fixing this problem.
 3143: 
 3144: 		Changes since 3.0 Beta 2 Patchlevel 5
 3145: 
 3146: - Fix a bug in the recent enhancement to the interface discovery code
 3147:   to support arbitrary-length interface lists.
 3148: 
 3149: - Support NUL-terminated DHCP options when initializing client-script
 3150:   environment.
 3151: 
 3152: - Fix suffix operator.
 3153: 
 3154: - Fix NetWare/IP option parsing.
 3155: 
 3156: - Better error/status checking in dhcpctl initialization and omapi
 3157:   connection code.
 3158: 
 3159: - Fix a potential memory smash in dhcpctl code.
 3160: 
 3161: - Fix SunOS4 and (maybe) Ultrix builds.
 3162: 
 3163: - Fix a bug where a certain sort of incoming packet could cause a core
 3164:   dump on Solaris (and probably elsewhere).
 3165: 
 3166: - Add some more safety checks in error logging code.
 3167: 
 3168: - Add support for ISC_R_INCOMPLETE in OMAPI protocol connection code.
 3169: 
 3170: - Fix relay agent so that if an interface is specified on the command
 3171:   line, the relay agent does not dump core.
 3172: 
 3173: - Fix class matching so that match if can be combined with match or
 3174:   spawn with.
 3175: 
 3176: - Do not allow spurious leases in the lease database to introduce
 3177:   potentially bogus leases into the in-memory database.
 3178: 
 3179: - Fix a byte-order problem in the client hardware address type code
 3180:   for OMAPI.
 3181: 
 3182: - Be slightly less picky about what sort of hardware addresses OMAPI
 3183:   can install in host declarations.
 3184: 
 3185: 		Changes since 3.0 Beta 2 Patchlevel 4
 3186: 
 3187: - Incorporated Peter Marschall's proposed change to array/record
 3188:   parsing, which allows things like the slp-agent option to be encoded
 3189:   correctly.   Thanks very much to Peter for taking the initiative to
 3190:   do this, and for doing such a careful job of it (e.g., updating the
 3191:   comments)!
 3192: 
 3193: - Added an encoding for the slp-agent option.   :')
 3194: 
 3195: - Fixed SunOS 4 build.  Thanks to Robert Elz for responding to my
 3196:   request for help on this with patches!
 3197: 
 3198: - Incorporated a change that should fix a problem reported by Philippe
 3199:   Jumelle where when the network connection between two servers is
 3200:   lost, they never reconnect.
 3201: 
 3202: - Fix client script files other than that for NetBSD to actually use
 3203:   make_resolv_conf as documented in the manual page.
 3204: 
 3205: - Fix a bug in the packet handling code that could result in a core
 3206:   dump.
 3207: 
 3208: - Fix a bug in the bootp code where responses on the local net would
 3209:   be sent to the wrong MAC address.   Thanks to Jerry Schave for
 3210:   catching this one.
 3211: 
 3212: 		Changes since 3.0 Beta 2 Patchlevel 3
 3213: 
 3214: - In the DHCP client, execute client statements prior to using the values
 3215:   of options, so that the client configuration can overridden, e.g., the
 3216:   lease renewal time.
 3217: 
 3218: - Fix a reference counting error that would result in very reproducible
 3219:   failures in updates, as well as occasional core dumps, if a zone was
 3220:   declared without a key.
 3221: 
 3222: - Fix some Linux 2.0 compilation problems.
 3223: 
 3224: - Fix a bug in scope evaluation during execution of "on" statements that
 3225:   caused values not to be recorded on leases.
 3226: 
 3227: - If the dhcp-max-message-size option is specified in scope, and the
 3228:   client didn't send this option, use the one specified in scope to
 3229:   determine the maximum size of the response.
 3230: 
 3231: 		Changes since 3.0 Beta 2 Patchlevel 2
 3232: 
 3233: - Fix a case where spawning subclasses were being allocated
 3234:   incorrectly, resulting in a core dump.
 3235: 
 3236: - Fix a case where the DHCP server might inappropriately NAK a
 3237:   RENEWING client.
 3238: 
 3239: - Fix a place dhcprequest() where static leases could leak.
 3240: 
 3241: - Include memory.h in omapip_p.h so that we don't get warnings about
 3242:   using memcmp().
 3243: 
 3244: 		Changes since 3.0 Beta 2 Patchlevel 1
 3245: 
 3246: - Notice when SIOCFIGCONF returns more data than fit in the buffer -
 3247:   allocate a larger buffer, and retry.   Thanks to Greg Fausak for
 3248:   pointing this out.
 3249: 
 3250: - In the server, if no interfaces were configured, report an error and
 3251:   exit.
 3252: 
 3253: - Don't ever record a state of 'startup'.
 3254: 
 3255: - Don't try to evaluate the local failover binding address if none was
 3256:   specified.   Thanks to Joseph Breu for finding this.

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>