dhcpcd-discuss

Hi Roy,
 
On Friday, June 23, 2017 7:37 AM, Roy Marples wrote:
> On 22/06/2017 17:31, David Hauck wrote:
>> On Thursday, June 22, 2017 9:24 AM, Roy Marples wrote:
>>> On 22/06/2017 17:20, David Hauck wrote:
>>>> Hi Roy,
>>>> 
>>>> On Thursday, June 22, 2017 7:38 AM, Roy Marples wrote:
>>>>> On 22/06/2017 09:05, Roy Marples wrote:
>>>>>> Saying that, there is an issue where the lease will be discarded
>>>>>> if it has expired when dhcpcd starts up. If this is your issue,
>>>>>> subscribe to the below task and we'll see about fixing it.
>>>>>> https://dev.marples.name/T124
>>>>> 
>>>>> I forgot that the lastleaseextend directive allows this.
>>>>> You might need that option as well.
>>>> 
>>>> Just so I'm clear here: without lastleaseextend the lease *should*
>>>> be deleted on expiration,
>>> regardless of lastlease, right?  That is, lastlease only refers to
>>> using the lease iff REBIND/REBOOT fails
>>> *and* the least hasn't expired. Once the lease has expired it
>>> rightfully should be discarded and the interface brought down.
>>> 
>>> The interface is never brought down, just de-configured if persistent is not set.
> 
> No, the leasefile isn't deleted as such.
> dhcpcd just discards it (ie mentions it, but doesn't delete it).
> When it get a new lease it will overwrite the old one.

OK. See below, but I *still* see no difference between persistent and non-persistent: I never see the last lease take effect when 'lastlease' is specified - both cases result in dhcpcd exiting on the timeout (and no TIMEOUT reason code passed to the hooks).
 
> Does this help?

Perhaps, but please see my other response re: different behaviour between debug and non-debug. 

As of right now neither of these things (TIMEOUT reasons code to hook and 'lastlease') are working for me.

Regards,
-David

> Roy