[Dnsmasq-discuss] Wrong dhcp-renewal-time

Andrija Panic andrija.panic at gmail.com
Thu Feb 20 10:49:17 GMT 2020


Hi all,

first time posting to this ML.

We are using dnsmasq with CloudStack to provide DNS/DHCP services.

Recently we've changed the lease duration to 36250 days (98y, i.e. closer
to infinity) to make sure that the clients will not renew its lease for a
loooong time (for reasons known to us).

Now, the lease time is sent fine to the client, but the dhcp-renewal-time
and dhcp-rebinding-time are NOT set to 50% (87.5%) of the lease time, but
instead to "only" ~650 days, which beats the purpose of us increasing it to
36250 days.

Can anyone advise what is happening and if this might be a known issue?

Here's an example from the log (dnsmasq version 2.76 on Debian 9)

root at r-3199-VM:~# cat /var/log/dnsmasq.log

:
Feb 20 02:21:17 dnsmasq-dhcp[26752]: 3440196161 sent size: 4 option: 51
lease-time 36250d
Feb 20 02:21:17 dnsmasq-dhcp[26752]: 3440196161 sent size: 4 option: 58 T1
649d19h57m19s
Feb 20 02:21:17 dnsmasq-dhcp[26752]: 3440196161 sent size: 4 option: 59 T2
649d19h57m20s


Thanks,

-- 

Andrija Panić
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20200220/1b0b47b3/attachment.html>


More information about the Dnsmasq-discuss mailing list