dhcpd complaining about dynamic and static leases

I'm getting alot of these msgs on a variety of addresses that were
set up as pegged IP addresses in /etc/dhcpd.conf:

localhost dhcpd: Dynamic and static leases present for 192.168.1.139.
localhost dhcpd: Remove host declaration rockserver or remove
192.168.1.139
localhost dhcpd: from the dynamic address pool for Intranet
localhost dhcpd: DHCPREQUEST for 192.168.1.139 from 00:11:2f:94:75:fc
via eth1
localhost dhcpd: DHCPACK on 192.168.1.139 to 00:11:2f:94:75:fc via eth1

It gives out the address in the end but I don't see a conflict with any
other host so it makes me think it's a config directive issue. MAC
address
is correct. I do see some "Ping'ed before offer" msgs for that same IP
and
some of the other pegged IPs. It's almost like DHCP wants to give out
the
pegged addresses.

Here's the declaration for the host:

host rockserver {
ddns-updates on;
ddns-rev-domainname "lab";
ddns-domainname "lab";
hardware ethernet 00:11:2f:94:75:fc;
fixed-address 192.168.1.139;
}

here's the declaration of the dhcp range:

shared-network Intranet {
allow client-updates;
allow unknown-clients;
ddns-domainname "192.168.1.102";
authoritative;
ddns-updates on;
# lab computers
subnet 192.168.1.0 netmask 255.255.255.0 {
authoritative;
allow client-updates;
allow unknown-clients;
ddns-domainname "lab";
option domain-name-servers 192.168.1.102;
ddns-updates on;
range 192.168.1.51 192.168.1.254;
<snip>

System is a RHEL4 ES U1 on x86, dhcp versions are:

dhcp-3.0.1-12_EL
dhcpv6_client-0.10-8
dhcpv6-0.10-8

Everything seems ok to me in the configs. Any ideas?

Ron

(E-Mail Removed) wrote:
> I'm getting alot of these msgs on a variety of addresses that were
> set up as pegged IP addresses in /etc/dhcpd.conf:
>
> localhost dhcpd: Dynamic and static leases present for 192.168.1.139.
> localhost dhcpd: Remove host declaration rockserver or remove
> 192.168.1.139
> localhost dhcpd: from the dynamic address pool for Intranet
> localhost dhcpd: DHCPREQUEST for 192.168.1.139 from 00:11:2f:94:75:fc
> via eth1
> localhost dhcpd: DHCPACK on 192.168.1.139 to 00:11:2f:94:75:fc via eth1
>
> It gives out the address in the end but I don't see a conflict with any
> other host so it makes me think it's a config directive issue. MAC
> address
> is correct. I do see some "Ping'ed before offer" msgs for that same IP
> and
> some of the other pegged IPs. It's almost like DHCP wants to give out
> the
> pegged addresses.
>
> Here's the declaration for the host:
>
> host rockserver {
> ddns-updates on;
> ddns-rev-domainname "lab";
> ddns-domainname "lab";
> hardware ethernet 00:11:2f:94:75:fc;
> fixed-address 192.168.1.139;
> }
>
> here's the declaration of the dhcp range:
>
> shared-network Intranet {
> allow client-updates;
> allow unknown-clients;
> ddns-domainname "192.168.1.102";
> authoritative;
> ddns-updates on;
> # lab computers
> subnet 192.168.1.0 netmask 255.255.255.0 {
> authoritative;
> allow client-updates;
> allow unknown-clients;
> ddns-domainname "lab";
> option domain-name-servers 192.168.1.102;
> ddns-updates on;
> range 192.168.1.51 192.168.1.254;
> <snip>
>
> System is a RHEL4 ES U1 on x86, dhcp versions are:
>
> dhcp-3.0.1-12_EL
> dhcpv6_client-0.10-8
> dhcpv6-0.10-8
>
> Everything seems ok to me in the configs. Any ideas?

Not quite - you're double-selling the address 192.168.1.139:
it's sold separately and in the middle of the dynamic range
of 192.168.1.51 to 192.168.1.254.

Please arrange the fixed addresses out of the dynamic range
and your worries will vanish.

--

Tauno Voipio
tauno voipio (at) iki fi

> Not quite - you're double-selling the address 192.168.1.139:
> it's sold separately and in the middle of the dynamic range
> of 192.168.1.51 to 192.168.1.254.
>
> Please arrange the fixed addresses out of the dynamic range
> and your worries will vanish.

You're allowed to mix fixed and dynamic addresses in the same
range. At least that's my take on it. From the RHEL4 dhcpd.conf
man page, note the part where it says "never do a dynamic address
allocation":

There may be a host declaration matching the client's
identification.
If that host declaration contains a fixed-address declaration
that
lists an IP address that is valid for the network segment to which
the
client is connected. In this case, the DHCP server will never
do
dynamic address allocation. In this case, the client is required
to
take the address specified in the host declaration. If the
client
sends a DHCPREQUEST for some other address, the server will
respond
with a DHCPNAK.

Ron