[Solved] Wicd won't kill dhcpcd on disconnect

quantumphaze · 2009-05-31 12:04:59

Wicd is having problems when I need to reconnect to my home network (crappy router). It seems that it doesn't stop the dhcpcd process when I make it reconnect and consequently fails at the "Obtaining IP Address" stage. I have to manually stop it with dhcpcd -k wlan0

Current versions are:
wicd 1.5.9-1
dhcpcd 5.0.4-1

My pkg cache has versions 4.0.12-1 5.0.1-1 5.0.2-1 and 5.0.4-1 of dhcpcd. Wicd has not ever been upgraded on this laptop.

The only dhcpcd version that works correctly is 4.0.12-1 and it is killed upon disconnect of the network. It's still running after disconnect with any of the 5.0.* versions.

It seems that dhcpcd has changed it's behaviour in however it is interfaced with wicd and the current version of wicd doesn't like it.

Has anyone else had this problem?

Last edited by quantumphaze (2009-06-10 05:12:47)

quantumphaze · 2009-06-10 05:12:14

Fixed in Wicd version 1.6.0

uwinkelvos · 2009-06-13 14:04:50

this is weired... it has not been an issue for me before upgradeing to 1.6.0, but now it hangs on "Obtaining IP Address" on the first connect. When i setup wicd to use dhclient, everything works like charm.

quantumphaze · 2009-06-14 10:43:43

That seems to be a slightly different bug than what I had. For me it was that dhcpcd was still running and wicd never even got to the "Obtaining IP Address" part, failing just after it authenticated.

drandre · 2009-06-21 04:56:24

For about the same period of time I've had trouble reconnecting to my wireless network after waking from sleep mode. The log indicates that the problem for me might be with restarting dhcpcd:

2009-06-21 14:03:54    akoya    dhcpcd    dhcpcd not running
2009-06-21 14:03:54    akoya    dhcpcd    dhcpcd not running
2009-06-21 14:04:03    akoya    dhcpcd    version 5.0.4 starting
2009-06-21 14:04:03    akoya    dhcpcd    ra0: rebinding lease of 192.168.0.188
2009-06-21 14:04:04    akoya    dhcpcd    ra0: acknowledged 192.168.0.188 from 192.168.0.1
2009-06-21 14:04:04    akoya    dhcpcd    ra0: checking for 192.168.0.188
2009-06-21 14:04:08    akoya    dhcpcd    ra0: leased 192.168.0.188 for 86400 seconds
2009-06-21 14:04:08    akoya    dhcpcd    forking to background
2009-06-21 14:05:10    akoya    dhcpcd    ra0: carrier lost
2009-06-21 14:05:15    akoya    dhcpcd    ra0: carrier acquired
2009-06-21 14:05:15    akoya    dhcpcd    ra0: rebinding lease of 192.168.0.188
2009-06-21 14:05:15    akoya    dhcpcd    ra0: acknowledged 192.168.0.188 from 192.168.0.1
2009-06-21 14:05:15    akoya    dhcpcd    ra0: checking for 192.168.0.188
2009-06-21 14:05:17    akoya    dhcpcd    dhcpcd not running
2009-06-21 14:05:17    akoya    dhcpcd    ra0: carrier lost
2009-06-21 14:05:17    akoya    dhcpcd    sending signal 1 to pid 3805
2009-06-21 14:05:17    akoya    dhcpcd    waiting for pid 3805 to exit
2009-06-21 14:05:17    akoya    dhcpcd    received SIGHUP, releasing lease
2009-06-21 14:05:17    akoya    dhcpcd    ra0: removing interface
2009-06-21 14:05:55    akoya    dhcpcd    dhcpcd not running
2009-06-21 14:05:56    akoya    dhcpcd    dhcpcd not running
2009-06-21 14:06:33    akoya    dhcpcd    dhcpcd not running
2009-06-21 14:06:34    akoya    dhcpcd    dhcpcd not running
2009-06-21 14:07:10    akoya    dhcpcd    dhcpcd not running
2009-06-21 14:07:10    akoya    dhcpcd    dhcpcd not running
2009-06-21 14:09:25    akoya    dhcpcd    dhcpcd not running
2009-06-21 14:09:28    akoya    dhcpcd    dhcpcd not running
2009-06-21 14:09:28    akoya    dhcpcd    dhcpcd not running
2009-06-21 14:11:28    akoya    dhcpcd    dhcpcd not running
2009-06-21 14:11:29    akoya    dhcpcd    dhcpcd not running
2009-06-21 14:11:30    akoya    dhcpcd    dhcpcd not running
2009-06-21 14:11:39    akoya    dhcpcd    version 5.0.4 starting
2009-06-21 14:11:39    akoya    dhcpcd    ra0: rebinding lease of 192.168.0.188
2009-06-21 14:11:39    akoya    dhcpcd    ra0: acknowledged 192.168.0.188 from 192.168.0.1
2009-06-21 14:11:39    akoya    dhcpcd    ra0: checking for 192.168.0.188
2009-06-21 14:11:43    akoya    dhcpcd    ra0: leased 192.168.0.188 for 86400 seconds
2009-06-21 14:11:44    akoya    dhcpcd    forking to background

either way there seems to be an issue with dhcpcd. would love to hear more

quantumphaze · 2009-06-21 05:38:35

Try using Wicd with dhclient instead. Also try it with dhcpcd manually with wpa_supplicant and stuff.

drandre · 2009-06-21 06:45:56

dhclient has similar issues... long time to connect. On balance it seems a little worse. In fact the problem is worst if I use the special function button on the lappie to turn the wireless off and on. I subsequently get "bad password" messages.

from the commandline I get this kind of problem

dhcpcd: version 5.0.4 starting
dhcpcd: ra0: rebinding lease of 192.168.0.188
dhcpcd: ra0: broadcasting for a lease
dhcpcd: ra0: carrier lost
dhcpcd: ra0: carrier acquired
dhcpcd: ra0: rebinding lease of 192.168.0.188
dhcpcd: ra0: broadcasting for a lease
dhcpcd: ra0: offered 192.168.0.188 from 192.168.0.1
dhcpcd: ra0: acknowledged 192.168.0.188 from 192.168.0.1
dhcpcd: ra0: checking for 192.168.0.188
dhcpcd: timed out

second time (not always the second time but in this case I'm lucky) it connects correctly.

[root@akoya ~]# dhcpcd ra0
dhcpcd: version 5.0.4 starting
dhcpcd: ra0: rebinding lease of 192.168.0.188
dhcpcd: ra0: acknowledged 192.168.0.188 from 192.168.0.1
dhcpcd: ra0: checking for 192.168.0.188
dhcpcd: ra0: leased 192.168.0.188 for 86400 seconds
dhcpcd: forking to background

i.e. not much new - only the timeout message. Perhaps I can tweak this but it doesn't seem like the root cause.
not much fun trying to work this one out

Last edited by drandre (2009-06-21 06:50:59)

quantumphaze · 2009-06-21 09:14:24

This really should be in it's own thread since I have marked my original problem as [Solved], but anyway.

It looks like there are problems with the connection's stability. When you do get an IP after a suspend, send continuous pings to your router. (ping 192.168.x.x would send one per second).
Observe any pings that are missed (icmp_seq=#) or no route to host errors.

Try to reload the driver module for whatever card you have. (ra0 means RaLink??)
If this solves the problem you can add the module to a config for pm-utils that will unload it automatically.

Arch Linux

#1 2009-05-31 12:04:59

[Solved] Wicd won't kill dhcpcd on disconnect

#2 2009-06-10 05:12:14

Re: [Solved] Wicd won't kill dhcpcd on disconnect

#3 2009-06-13 14:04:50

Re: [Solved] Wicd won't kill dhcpcd on disconnect

#4 2009-06-14 10:43:43

Re: [Solved] Wicd won't kill dhcpcd on disconnect

#5 2009-06-21 04:56:24

Re: [Solved] Wicd won't kill dhcpcd on disconnect

#6 2009-06-21 05:38:35

Re: [Solved] Wicd won't kill dhcpcd on disconnect

#7 2009-06-21 06:45:56

Re: [Solved] Wicd won't kill dhcpcd on disconnect

#8 2009-06-21 09:14:24

Re: [Solved] Wicd won't kill dhcpcd on disconnect

Board footer