wicd disconnects on ipv6 enabled networks due to early dhcpcd fork
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| wicd |
New
|
Undecided
|
Unassigned | ||
Bug Description
I have discovered that when using dhcpcd as the dhcp client, the dhcpcd daemon will fork as soon as it has received an ip address, which causes problems if the first ip it receives is ipv6.
As wicd checks for a valid ipv4 ip immediately after dhcpcd has forked, it detects the dhcp request as being failed, and kills the dhcpcd daemon.
It looks like the -w (--waitip) option to dhcpcd helps to have it only fork after receiving valid ip(s).
I have not been able to find where exactly in the source code I could add this option when dhcpcd is being called, so I haven't been able to try it out.
Perhaps an alternative would be to have wicd check for a valid ipv4 address again a couple of seconds later.
I don't have this problem after switching to dhclient.
Running wicd-1.7.2.1-1 on Arch.
| Wim Lewis (wiml) wrote | #1 |
From AopicieR's comment in bug #861860, I think this may be the same bug or situation as that one.