Gilles Espinasse wrote:
----- Original Message -----
From: "Simon Kelley" <si...@thekelleys.org.uk>
To: "Jeb Campbell" <j...@c4solutions.net>
Cc: "dnsmasq discussion list" <dnsmasq-discuss@lists.thekelleys.org.uk>
Sent: Friday, October 20, 2006 5:23 PM
Subject: Re: [Dnsmasq-discuss] v2.34 on Openbsd 4.0 (fix)
...
One last thing -- as a temp fix last night, I recompiled dnsmasq to read
ISC lease files and it works great, but the source says that this will
go away soon -- is it just not maintainable?
The main motivation for getting rid of it is that it's a hack which
depends on the ISC leasefile format not changing, and is rather
race-condition prone. Very few people use it, and it's quite likely that
it will get inadvertently broken. My plan is to remove it in the first
release after Debian "etch", which might well be 2.35.
Please don't remove it now and not so fast after.
We need it on IPCop actually.
We have planned to test other solutions on the next major IPCop version but
development is actually not so fast.
Gilles Espinasse maintainer of IPcop v1.4
It can be left in place whilst you are still using it.
Have you condidered using the dnsmasq built-in DHCP server instead of
the ISC one? I took a look at your documentation, and the only thing I
can see which would not work out of the box is enable/disable BOOTP.
Dnsmasq will always honour BOOTP requests from hosts with
fixed-addresses, it has to be enabled with a flag for dynamic address
allocation. It would be trivial to add another flag to disable it
completely.
The dnsmasq DHCP server is pretty mature now: most of the *wrt distros
are using it, for instance, which is a similar application to IPcop.
Cheers,
Simon.
