dhcpcd-discuss

Hi Roy,
 
On Monday, June 06, 2016 2:56 AM, Roy Marples wrote:
> On 01/06/2016 22:43, David Hauck wrote:
>> Notwithstanding what you say above, why does the last line say
>> "soliciting a DHCP lease"?
>> 
>> Also, when I try this again now, I see the following:
>> 
>> 20160601 14:36:19.169 info daemon(dhcpcd):eth1: carrier lost
>> 20160601 14:36:19.175 info daemon(dhcpcd):eth1: 60-netacquire:
>> received reason=NOCARRIER, beeppid=0, ip=, sn=, gw=, dns=, options=,
>> hn=
>> 20160601 14:36:19.186 info daemon(dhcpcd):eth1: deleting route to
>> 205.159.216.128/25
>> 20160601 14:36:19.186 info daemon(dhcpcd):eth1: deleting default
>> route via 205.159.216.130
>> 20160601 14:36:19.192 info daemon(dhcpcd):eth1: 60-netacquire:
>> received reason=EXPIRE, beeppid=0, ip=, sn=, gw=, dns=, options=,
>> hn=
>> 20160601 14:36:26.690 info daemon(dhcpcd):eth1: carrier acquired
>> 20160601 14:36:26.696 info daemon(dhcpcd):eth1: 60-netacquire:
>> received reason=CARRIER, beeppid=0, ip=, sn=, gw=, dns=, options=,
>> hn=
>> 20160601 14:36:26.696 info daemon(dhcpcd):eth1: IAID e0:53:f3:9f
>> 20160601 14:36:27.466 info daemon(dhcpcd):eth1: soliciting a DHCP
>> lease
>> 
>> This doesn't have the intervening messages as the first trace
>> regarding
> "rebinding" but it does end the same way: with "soliciting a DHCP
> lease". In both traces I never see a TIMEOUT reason code in the hook
> scripts (both traces are with 'lastlease' present in dhcpcd.conf).
>> 
>> What's going on here?
> 
> When it says "soliciting a DHCP lease" dhcpcd tries to solicit a lease
> for $reboot seconds.

I don't have reboot configured for a specific value and my understanding is that this defaults to 5s in this case.

> If this fails, dhcpcd will use the last lease if it's not expired and
> the lastlease option is enabled. At this point you should see the TIMEOUT reason.

Right, OK, I definitely don't see this reason code show up. Any more ideas why?

Thanks,
-David

> Roy