dhcpcd-discuss

On 05/17/2018 10:27 PM, Roy Marples wrote:
> 
> On 17/05/2018 20:33, Moritz Warning wrote:
>> On 05/17/2018 09:18 PM, Roy Marples wrote:
>>>
>>>
>>> On 17/05/2018 19:00, Moritz Warning wrote:
>>>> The patch revealed some interesting info:
>>>> May 17 19:53:19 brick dhcpcd[12604]: LISTENING TO fdbc:652b:8f56:0:75f0:740c:fdf8:84e4/64
>>>> May 17 19:53:19 brick dhcpcd[12598]: LISTENING TO fdbc:652b:8f56:0:75f0:740c:fdf8:84e4/64
>>>> May 17 19:53:19 brick dhcpcd[12598]: dhcp6_listen: Address already in use
>>>
>>> Can I get the full log plz?
>> See attachment.
>> Fun fact, I had to rename my computer name to get it past the spamhaus.org filter.
> 
> The filter I run on mail.marples.name?
> 
>>
>>>
>>>>
>>>> Anyway, "waitip 4" in /etc/dhcpcd.conf also make the problem disappear.
>>>>
>>>> Does dhcpcd signal wicd as soon an IP address (IPv6 in this case), has been received/set?
>>>>
>>>
>>> No, dhcpcd just exits 0
>>> I think wicd checks for an ipv4 address at this point and when none found says it's an error and kills dhcpcd
>>
>> Does it mean that dhcpcd exits as soon as an ipv6 address has been set and no ipv4 address yet?
> 
> By default yes, if the IPv6 provides DNS.
> I'm pretty sure wicd doesn't like that.
I think waitip 3 should be added by wicd.
Or is there a nicer approach? 

> 
> 
> Anyway, new patch to try and stop the listen error from happening.
> This is a little more invasive and should create a core dump on error so we can see how it's being called.
> 
> Roy

I think you forgot to append the patch.