Sometimes server / client doesn't honor leasing time

[perl-list]

The client can, and sometimes does, request a different lease time than what the server specifies. The server honors this request. This is normal behavior. For example, some versions of windows will initially request only an hour lease, then at renew time will take the full length lease. 

> From: "Roberto De Oliveira" <rcdeoliveira at gmail.com>
> To: dhcp-users at lists.isc.org
> Sent: Friday, February 17, 2017 10:18:03 AM
> Subject: Sometimes server / client doesn't honor leasing time

> Hello everyone!,

> I am writing you because I have a DHCP cluster and sometimes I have a weird
> behavior between server / clients, they don't agree on the lease time, I have
> this configuration on both servers:
> default-lease-time 129600;
> max-lease-time 129600;
> min-lease-time 129600;

> And sometimes I have this on dhcpd.leases:
> lease X.X.X.X {
> starts 2 2016/12/27 13:16:56;
> ends 2 2016/12/27 14:16:56;
> tstp 4 2016/12/29 01:46:56;
> tsfp 2 2016/12/27 10:29:38;
> cltt 2 2016/12/27 13:16:56;
> binding state active;
> next binding state expired;
> hardware ethernet f4:09:d8:7a:fd:a5;
> uid "\001\364\011\330z\375\245";
> client-hostname "android-2003cbf0e82ff81d";
> }

> The lease ends an hour later despite of tsfp is equal to *-lease-time. What is
> happening in this cases?.

> Thanks in advanced.

> --
> Saludos,
> Roberto De Oliveira

> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20170217/660360b0/attachment.html>