Re: 1.280 dhcp renewal/rebinding time

[Bill Moss <bmoss CLEMSON EDU>]

Please disregard my last message. I spoke too soon. My wired dhcp server 
is providing a lease time of 14400 and my wireless of 1800. These show 
up in the syslog created by NM as

Feb 15 10:09:24 localhost NetworkManager:       Address Time (51):      
14400
Feb 15 10:13:28 localhost NetworkManager:       Address Time (51):      1800

Neither of my dhcp servers is configured to provide T1 and T2 values as 
you can see from the dhcpcd debug message.

Feb 15 10:22:15 localhost dhcpcd[19508]: dhcpIPaddrLeaseTime=14400 in 
DHCP server response.
Feb 15 10:22:15 localhost dhcpcd[19508]: dhcpT1value is missing in DHCP 
server response. Assuming 7200 sec
Feb 15 10:22:15 localhost dhcpcd[19508]: dhcpT2value is missing in DHCP 
server response. Assuming 12600 sec

The dhcpcd debug messages are a bit more informative than the current NM 
message:

Feb 15 10:09:24 localhost NetworkManager:       Renewal Time (58):      0
Feb 15 10:09:24 localhost NetworkManager:       Rebinding Time (59):    0

I assume that in this scenario NM is computing T1 = lease_time/2 and T2 
= 0.875*lease_time or something like that.

--
Bill Moss
Professor, Mathematical Sciences
Clemson University