DHCPOFFER NACKed upon first REQUEST
albrizio at univ.trieste.it
Tue Mar 18 12:43:54 UTC 2014
On 17/03/2014 17:33, 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 18.104.22.168 to ...
> Mar 17 14:27:48 luna dhcpd: DHCPREQUEST for 22.214.171.124 ...: lease
> 126.96.36.199 unavailable.
> Mar 17 14:27:48 luna dhcpd: DHCPNAK on 188.8.131.52...
> This happens not always for the same client.
> The shared network segment needs to give out more than 2k leases during
> rush hours.
> Syslog and packet dumps are available here:
> Note that the same client after a while (18 mins) successfulli gets the
> lease and uses it for 10 minutes.140.105.104.
> Meaningful server configuration on both servers (failover configuration)
> is here:
Today I tried commenting out the 140.105.108. and 140.105.104. pools.
All begun working flawlessly.
As soon as I re-enabled the 140.105.104. pool, suddenly the problem
Uhm... is there a maximum number of pools or leases per shared network?
Daniele ALBRIZIO - albrizio at univ.trieste.it
UNIVERSITY OF TRIESTE - Network Services
Divisione V - Infrastrutture e Servizi Informativi
via Alfonso Valerio, 12 I-34127 Trieste, Italy
Sezione Infrastrutture Informatiche e Telematiche
More information about the dhcp-users