Re: dhcp-lease

[Bart Vanbrabant <bart vanbrabant zoeloelip be>]

Dan Williams wrote:

> On Tue, 2005-01-18 at 14:33 -0500, Lance A. Brown wrote:
>  
>
> > Standard operation for a dhcp client is to request a DHCP renewal at 1/2
> > lease-time, or at the time specified by the dhcp-renewal-time DHCP
> > option.  If you're waiting until lease-time to renew the lease, then you
> > have a significant chance of loosing the lease before you can renew it.
> >
> > Section 4.4.5 of the DHCP RFC (http://www.faqs.org/rfcs/rfc2131.html)
> > describes this all in detail.
> >    
>
> Correct, as the code currently does it (dhcpcd/client.c:270):
>
> T1 (renew): 0.5 * lease time
> T2 (rebind): 0.875 * lease time
>
> The timeouts for T1 and T2 are set up with these values by default.  If
> the DHCP server passes us explicit T1 and T2 values, we'll use those
> instead.
>
> Its entirely possible that NetworkManager isn't actually doing the
> renew/rebind stuff correctly or at the correct time, I'll check that
> out.
>
> Dan
>  
This could be correct if I look at my log, but I only does this once. NM 
send two times a dhcp request after it's initial request. These are 
probably the T1 and T2 request but the timer isn't reset.

Bart

--
Bart Vanbrabant <bart vanbrabant zoeloelip be>
PGP fingerprint: 093C BB84 17F6 3AA6 6D5E  FC4F 84E1 FED1 E426 64D1