Subject: Re: is dhcpd broken
To: None <M.Drochner@fz-juelich.de>
From: Greg A. Woods <woods@weird.com>
List: current-users
Date: 03/11/2003 14:02:06
[ On Tuesday, March 11, 2003 at 14:22:42 (+0100), Matthias Drochner wrote: ]
> Subject: Re: is dhcpd broken 
>
> 
> woods@weird.com said:
> > BTW, even with this "bug" it would be very nice if 3.0.1rc11 could be
> > pulled up onto the netbsd-1-6 branch. 
> 
> This would set up people (like Martin) who use the ad-hoc
> mode on a 1.6 system.

True enough -- However I'm hoping there's some simple work-around made
available from ISC in the very near future.  Ultimately the same problem
applies to anyone using -current or who upgrades to the ISC release.

The stock answers in ISC circles seem to be the likes of:

  Ad hoc DNS updates don't work in rc8 - it's a bug.   You shouldn't use         
  ad-hoc anyway.                                                                 

and:

  I urge folks to move away from ad-hoc to interim as a) interim is a bit        
  closer to the way things will work in the fugure b) ad-hoc is deprecated,      
  c) ad-hoc does not work with failover and interim does                         

(quoted anonymously from the dhcp-server mailing list archives)

I personally don't care either way because I'm not likely going to use
dynamic DNS with DHCP any time soon and I'm just _very_ peeved that they
now require this bogus "ddns-update-style none;" statement and that the
server can't provide its own default setting that doesn't break
perfectly valid non-DDNS configurations out-of-the-box!


Arguably maybe 1.6.x should use the 3.0p2 release, not a release
candidate, but that won't solve everyone's problems either.


> I'm not sure the bugfixes between rc9 and rc11 outweight the
> newly introduced bug(s)...

There are other major fixes in 3.0.1rc11, such as the ability to prevent
creation of corrupt leases entries (e.g. with a valid option-82
sub-option 4 request, but also of course malicious use of any other
undefined sub-option causes the same problems).  Of course it's not very
hard to patch those fixes into the existing code, and even the rc11
release still seems to have the potential to be abused into creating
corrupt lease entries.

-- 
								Greg A. Woods

+1 416 218-0098;            <g.a.woods@ieee.org>;           <woods@robohack.ca>
Planix, Inc. <woods@planix.com>; VE3TCP; Secrets of the Weird <woods@weird.com>