DHCPOFFER NACKed upon first REQUEST
peter at rathlev.dk
Mon Mar 17 18:34:58 UTC 2014
On Mon, 2014-03-17 at 17:33 +0100, Daniele Albrizio wrote:
> Some clients (quasi 40 out of 2000) are being NACKed just after offering
> a lease like this:
> Mar 17 14:27:48 luna dhcpd: DHCPDISCOVER from 74:f0:6d:0c:6e:6f ...
> Mar 17 14:27:48 luna dhcpd: DHCPOFFER on 126.96.36.199 to ...
> Mar 17 14:27:48 luna dhcpd: DHCPREQUEST for 188.8.131.52 ...: lease
> 184.108.40.206 unavailable.
> Mar 17 14:27:48 luna dhcpd: DHCPNAK on 220.127.116.11...
We have seen some clients using a DISCOVER for what should be a REQUEST,
since they had an already valid lease and had the address configured and
replying to ICMP echoes. But you have "ping-check" set to false in the
configuration you posted, so that shouldn't be it.
Maybe not terribly constructive, but if you're running DHCPd v3 (which I
have a feeling you do) you should seriously consider upgrading. Many
many things have been fixed the last decade-or-so.
More information about the dhcp-users