dhcpcd-discuss

OK, I tried 'lastlease' in my 'dhcpcd.conf' file and see the following:

20160531 15:57:47.103 info daemon(dhcpcd):eth1: carrier lost
20160531 15:57:47.109 info daemon(dhcpcd):eth1: 60-custom: received reason=NOCARRIER, ip=, sn=, gw=, dns=, options=, hn=
20160531 15:57:47.109 info daemon(dhcpcd):eth1: deleting route to 205.159.216.128/25
20160531 15:57:47.109 info daemon(dhcpcd):eth1: deleting default route via 205.159.216.130
20160531 15:57:47.115 info daemon(dhcpcd):eth1: 60-custom: received reason=EXPIRE, ip=, sn=, gw=, dns=, options=, hn=
20160531 15:57:50.313 info daemon(dhcpcd):eth1: carrier acquired
20160531 15:57:50.319 info daemon(dhcpcd):eth1: 60-custom: received reason=CARRIER, ip=, sn=, gw=, dns=, options=, hn=
20160531 15:57:50.319 info daemon(dhcpcd):eth1: IAID e0:53:f3:9f
20160531 15:57:50.434 info daemon(dhcpcd):eth1: rebinding lease of 205.159.216.184
20160531 15:57:55.435 info daemon(dhcpcd):eth1: leased 205.159.216.184 for 28800 seconds
20160531 15:57:55.435 info daemon(dhcpcd):eth1: adding route to 205.159.216.128/25
20160531 15:57:55.435 info daemon(dhcpcd):eth1: adding default route via 205.159.216.130
20160531 15:57:55.442 info daemon(dhcpcd):eth1: 60-custom: received reason=REBOOT, ip=205.159.216.184, sn=255.255.255.128, gw=205.159.216.130, dns=205.159.216.147 172.20.0.6 205.159.216.73, options=, hn=
20160531 15:57:55.455 info daemon(dhcpcd):eth1: soliciting a DHCP lease

I never see a transition occur beyond the line above? This looks the same as when I don't have 'lastlease' specified. Should I be seeing something else (note: I also don't see any TIMEOUT transition)?

Thx, 
-David

On Tuesday, May 31, 2016 3:47 PM, David Hauck wrote:
> Hi Roy,
> 
> On Tuesday, May 31, 2016 12:12 PM, Roy Marples wrote:
>> Hi David
>> 
>> On 2016-05-31 17:13, David Hauck wrote:
>>>> You need to enable the --lastlease option for this to work.
>>> 
>>> Is there an equivalent parameter in dhcpcd.conf (I didn't see one)?
>> 
>> lastlease also works :)
> 
> ;) K, I'll give it a try.
> 
>>> Also, what REASON string will the hook functions see when the
>>> TIMEOUT expires and the last lease is used/obtained?
>> 
>> Yes.
> 
> By "Yes" do you mean "Yes, TIMEOUT should be seen"?
> 
>>> In both cases I mentioned I never see a TIMEOUT reason code appear
>>> in the hook functions. Is this expected? It would be nice to give
>>> the hook functions the ability to react to this state (in my case
>>> to perform other cleanup associated with a failed attempt to bring
>>> up the interface)>
>> 
>> TIMEOUT should appear as the reason when the lastlease is used and
>> when a DHCP server cannot be reached.
> 
> I'll look for this.
> 
> Are you saying TIMEOUT will only be seen in this case and not the
> other cases I'm wondering about (i.e., when 'lastlease' isn't used)?
> 
> Thanks,
> -David
> 
>> Although I've not tested this for a while, will do so tomorrow.
>> 
>> Roy