dhcpcd-discuss

On Friday, October 17, 2014 6:56 AM, Roy Marples wrote:
> On 17/10/2014 14:25, David Hauck wrote:
>>> I don't see this problem with dhcpcd-6.5.0 (well, the latest trunk).
>>> There was a problem, although unrelated, which resulted in this
>>> patch
>>> 
>>> http://roy.marples.name/projects/dhcpcd/ci/4c1f2f8a298ad244f8c739710b
>>> a e46088ea7efd6?sbs=0 But that patch means nothing for 6.1.0.
>>> 
>>> So, can you test 6.5.0 with that patch please?
>> 
>> Sure, I'll test either 6.5.0 of 6.1.0 with the patch, but may not
>> get to this
> before the end of the day.

I did a quick test of this (essentially just a rebuild of 'dhcpcd' v6.5.0 and deploy to the target - I didn't deploy the hooks and this seems OK since the changes there seem to be irrelevant to my configuration) and I'm seeing the same issue. 

Here's my configuration:
hostname
option rapid_commit
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
option ntp_servers
require dhcp_server_identifier
nohook lookup-hostname
timeout 20
ipv4only
vendor 01,"0"

Any ideas for what else to try?

Thanks,
-David

> Don't waste your time with that patch and 6.1.0, it's not relevant as
> the eloop code didn't have different queues.
> These days we have timeout queues for dhcpcd control, DHCP + IPv4LL,
> IPv6RS and DHCPv6.
> 
> That patch moved the IPv4LL queue from dhcpcd control into the DHCP
> queue as they can cancel each others timeouts.
> 
> Roy
> 
> 
> ---
> This email is free from viruses and malware because avast! Antivirus
> protection is active.
> http://www.avast.com