dhcpd.leases not getting populated..

[B. Cook]

Hello all,

I have about 8 isc-dhcpd3-server installs out there and they all do
everything they are supposed to.. all but one.

And of course it's the most complex of them all, (as compared to the rest)

I have a subnet defined with two pools inside. The top pool is set to
deny unknown clients; and the bottom pool is set to allow unknown
clients;. The problem is that the 'bottom' pool (allow unknow) is the
only pool that gets logged to /var/db/dhcpd/dhcpd.leases.

These are my startup options:

# dhcpd
#dhcpd_flags="-q" # command option(s)
dhcpd_enable="YES" # dhcpd enabled?
dhcpd_conf="/usr/local/etc/dhcpd.conf" # configuration file
dhcpd_ifaces="fxp0" # ethernet interface(s)
dhcpd_umask="022" # file creation mask
dhcpd_chuser_enable="YES" # runs w/o privileges?
dhcpd_withuser="dhcpd" # user name to run as
dhcpd_withgroup="dhcpd" # group name to run as

and my build prefs:
[/var/db/ports]# 42 > cat isc-dhcp3-server/options
# This file is auto-generated by 'make config'.
# No user-servicable parts inside!
# Options for isc-dhcp3-server-3.0.4_2
_OPTIONS_READ=isc-dhcp3-server-3.0.4_2
WITH_DHCP_PARANOIA=true
WITHOUT_DHCP_JAIL=true
WITHOUT_DHCP_SOCKETS=true
WITHOUT_DHCP_LDAP=true
WITHOUT_DHCP_LDAP_SSL=true
WITH_OPENSSL_BASE=true
WITHOUT_OPENSSL_PORT=true
WITHOUT_DHCP_LQ=true

what I am trying to do is to use dnsmasq with the "-l
/var/db/dhcpd/dhcpd.leases" option to read the leases file and assign
hostnames in dns..

Obviously if I switch the pools the functionality will not be the same..
as allow unknown will be first and everyone will go there :|

We use this range for testing new machines and setting up new machines..

Any help is appreciated.

- Brian

[Nick Withers]

On Mon, 05 Jun 2006 09:06:23 -0400
"B. Cook" <bc...@poklib.org> wrote:

> Hello all,
>
> I have about 8 isc-dhcpd3-server installs out there and they all do
> everything they are supposed to.. all but one.
>
> And of course it's the most complex of them all, (as compared to the rest)
>
> I have a subnet defined with two pools inside. The top pool is set to
> deny unknown clients; and the bottom pool is set to allow unknown
> clients;. The problem is that the 'bottom' pool (allow unknow) is the
> only pool that gets logged to /var/db/dhcpd/dhcpd.leases.

(snip)

Don't suppose you'd be able to post the configuration of the
subnet, would you?

Are you sure that leases are being handed out from the first
pool?
--
Nick Withers
email: ni...@nickwithers.com
Web: http://www.nickwithers.com
Mobile: +61 414 397 446

[B. Cook]

Nick Withers wrote:
> On Mon, 05 Jun 2006 09:06:23 -0400
> "B. Cook" <bc...@poklib.org> wrote:
>
>
> Don't suppose you'd be able to post the configuration of the
> subnet, would you?

http://www.poklib.org/~dhcpd/dhcpd.conf

>
> Are you sure that leases are being handed out from the first
> pool?

yes.

The rest of the 192.168.1.0/24 gets ips and routes as they should.

[Nick Withers]

On Mon, 05 Jun 2006 12:35:44 -0400
"B. Cook" <bc...@poklib.org> wrote:

> Nick Withers wrote:
> > On Mon, 05 Jun 2006 09:06:23 -0400
> > "B. Cook" <bc...@poklib.org> wrote:
> >
> >
> > Don't suppose you'd be able to post the configuration of the
> > subnet, would you?
>
> http://www.poklib.org/~dhcpd/dhcpd.conf

Ta for that.

Found an archived message at
"http://www.southwestern.edu/ITS/netreg/archive/0464.html" that
methinks has the answer:
________

Leases are not added to dhcpd.leases for fixed-address
clients. :-( There was a patch for a fairly recent release
candidate to log these to a separate file, but I haven't tried
it on the latest RC. The dhcpd.leases file is really there so
that state can be maintained between incarnations of dhcpd,
e.g. shutdown, restart of dhcpd, etc. The server has to keep
track of the promises it has already made. Since fixed-address
clients always get the same information, and DNS is not
updated, it's not really necessary to record these leases.
________

I looked at dhcpd.leases on my (ISC) DHCP server and indeed
leases for "fixed-address" clients were not included.

I personally use dynamic DNS with DHCP and have had no dramas
with it. Don't know if this is appropriate for your situation,
though.

> >
> > Are you sure that leases are being handed out from the first
> > pool?
>
> yes.
>
> The rest of the 192.168.1.0/24 gets ips and routes as they should.

> _______________________________________________
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questi...@freebsd.org"