wicd gets stuck on "obtaining IP"

Barbarax · 03-31-2011, 03:19 PM

It is a WEP connection. I am able to connect fine from the terminal (iwconfig/dhclient), but when i try to connect using wicd it hangs on "obtaining IP" until finally giving up.

Also, i noticed if i disconnect after already connecting via command line, Wicd will then connect properly.

frankbell · 03-31-2011, 07:19 PM

I just experienced this on a wireless network with WEP encryption.

I had "Use encryption" checked, but, to get it to connect, I also had to check "Use these settings for all networks sharing this essid." Once I checked that, I connected flawlessly.

Hope this helps.

Barbarax · 04-01-2011, 02:15 PM

Quote:

Originally Posted by frankbell

I just experienced this on a wireless network with WEP encryption.

I had "Use encryption" checked, but, to get it to connect, I also had to check "Use these settings for all networks sharing this essid." Once I checked that, I connected flawlessly.

Hope this helps.

Thanks. I tried that but it doesn't fix it.

Barbarax · 04-01-2011, 02:16 PM

Now i have spent a hour @#%#ing with the preferences which has created a new problem....

I have set the preferences back but this still persists.

Wicd will say "Generating WPA configuration file" and subsequently fail and say "not connected".

Now it will not connect, even after connecting via iwconfig/dhclient from command line.

The terminal output when this occurs:

Code:

 setting encryption info...
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 214, in maybe_handle_message
    self._handler(*args, **kwargs)
  File "/usr/share/wicd/gtk/gui.py", line 243, in handle_connection_results
    error(self.window, language[results], block=False)
KeyError: dbus.String(u'Failed')

frankbell · 04-01-2011, 08:45 PM

A couple of things I've noticed (and I'm not a wireless expert, just another veteran of the Linux wireless wars):

If you connect via the command line and subsequently start wicd and wicd shows "connected," wicd is reflecting the already-connected state of the computer.

I strikes me as curious that wicd would report, "Generating WPA configuration file," for a WEP connection.

When I was struggling with getting connected Wednesday evening, I cycled through the WEP configuration settings one-by-one until I hit on the combination that worked. If I selected WPA, the connection would just hang.

Hopefully, someone will come along and parse that error message.

hf2046 · 04-02-2011, 02:15 PM

Quote:

Originally Posted by Barbarax

Wicd will say "Generating WPA configuration file" and subsequently fail and say "not connected".

Now it will not connect, even after connecting via iwconfig/dhclient from command line.

It looks like you're stuck on WPA authentication instead of WEP. Most likely you'll have to look at your inet startup scripts to fix this problem - they should be in /etc/rc.d. What Linux distribution are you using?

snmcdonald · 01-07-2012, 12:38 PM

Sorry for resurrecting this thread. I believe this answer is still relevant.

I had a lot of trouble with WICD. It would occasionally say that I had a "bad password" or just hang when "obtaining IP address". I often had to restart WICD several times to connect. Although, I was always able to connect, it often took several minutes. This could happen several times in a row. The connection problem always seemed sporadic.

I checked out linksys page and upgraded my firmware to the latest version. WICD has not given me a problem since.