max-lease-time not respected

David W. Hankins David_Hankins at
Mon Jul 2 16:28:49 UTC 2007

On Mon, Jul 02, 2007 at 04:59:08PM +0200, stephane.purnelle at wrote:
> These pareameter is correctly applied to special machine with 
> fixed-address, but not for other machine.

If you have host {} records with fixed-address statements that
overlap dynamic ranges, that is a configuration error (which you
should get warnings about).

fixed-address leases do not appear in dhcpd.leases.

> lease x.x.x.x {
>   starts 1 2007/07/02 14:27:43;
>   ends 1 2007/07/02 14:37:43;
>   tstp 1 2007/07/09 14:32:43;
>   cltt 1 2007/07/02 14:27:43;
>   binding state active;
>   next binding state expired;
>   hardware ethernet 00:17:9a:79:34:76;
>   uid "\001\000\027\232y4v";
> }

'tsfp' is not set here, so this lease has not been acknowledged
by the peer.

It appears that you are using an MCLT of 10 minutes.  Note that
the failover protocol stipulates that servers must not give out
lease times exeeding tsfp+MCLT (or the current time +MCLT in
the case that tsfp is not set, or is in the past).

Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil?
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins

More information about the dhcp-users mailing list