dhcpcd-discuss

Re: dhcpcd not recognising link detection + hang

Nico Schottelius

Tue Nov 05 17:42:21 2019

Hey Roy,

wow, did not expect an answer that fast and with that good content.

I just cloned the repo && built it and I am running dhcpcd now from the
checkout (dhcpcd-8.1.1-36-g81dd5cc5). I'll monitor the behaviour and
give some feedback the next days, if it happened again or whether it's
fixed.

Best,

Nico


Roy Marples <roy@xxxxxxxxxxxx> writes:

> Hi NicoOn 04/11/2019 19:52, Nico Schottelius wrote:
>> when running dhcpcd 8.1.1 on 5.3.8-arch1-1 the link detection seems to
>> be unreliable and dhcpcd seems to hang (needs SIGKILL) when the link is
>> lost.
>>
>> The log of such a session is attached below. I have also reported this
>> bug in Arch Linux [0], because I assume that this might be more a kernel
>> than dhcpcd bug, however as I am not sure I wanted to ask in here what
>> you think.
>>
>> According to wpa_supplicant, the connection is (re-)established and the
>> hanging is not related to suspend/resume, but more disconnects.
>>
>> Best regards,
>>
>> Nico
>>
>>
>> [0]
>> https://bugs.archlinux.org/task/64366?project=1&opened=7436
>>
>>
>> [root@diamond ~]# dhcpcd -B wlp0s20f3
>> main: control_open: Connection refused
>> DUID 00:04:4c:4c:45:44:00:32:4c:10:80:56:b4:c0:4f:30:5a:32
>> wlp0s20f3: IAID 9a:54:c3:bf
>> wlp0s20f3: adding address fe80::3b98:cb58:ed02:c25
>> wlp0s20f3: soliciting a DHCP lease
>> wlp0s20f3: soliciting an IPv6 router
>> wlp0s20f3: Router Advertisement from fe80::20d:b9ff:fe46:3bd4
>> wlp0s20f3: adding address 2a0a:e5c1:111:111:6aa6:5bc:535a:8e21/64
>> wlp0s20f3: adding route to 2a0a:e5c1:111:111::/64
>> wlp0s20f3: adding default route via fe80::20d:b9ff:fe46:3bd4
>> wlp0s20f3: offered 192.168.4.22 from 192.168.4.188
>> wlp0s20f3: probing address 192.168.4.22/24
>> wlp0s20f3: Router Advertisement from fe80::20d:b9ff:fe46:3bd4
>> wlp0s20f3: leased 192.168.4.22 for 600 seconds
>> wlp0s20f3: adding route to 192.168.4.0/24
>> wlp0s20f3: adding default route via 192.168.4.188
>> wlp0s20f3: fe80::20d:b9ff:fe46:3bd4 is unreachable
>> wlp0s20f3: carrier lost
>> wlp0s20f3: deleting address 2a0a:e5c1:111:111:6aa6:5bc:535a:8e21/64
>> wlp0s20f3: deleting route to 2a0a:e5c1:111:111::/64
>> wlp0s20f3: deleting default route via fe80::20d:b9ff:fe46:3bd4
>> wlp0s20f3: deleting address fe80::3b98:cb58:ed02:c25
>> Killed
>
> This should be fixed here:
> https://roy.marples.name/cgit/dhcpcd.git/commit/src?id=73ac184333f77b38a8b4c4202c2928278e2237ca
>
> Roy


--
Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch

Follow-Ups:
Re: dhcpcd not recognising link detection + hangRoy Marples
References:
dhcpcd not recognising link detection + hangNico Schottelius
Re: dhcpcd not recognising link detection + hangRoy Marples
Archive administrator: postmaster@marples.name