Passphrase issue ends with "Unable to obtain IP"

[Snakefinger]

Original forum post was http://wicd.net/punbb/viewtopic.php?id=699 by alexiy

The end resolution of his problem is as follows:

Then I have edited the template: /etc/wicd/encryption/templates/passphrase removing quotation marks around $_PASSPHRASE variable

name = WEP (Passphrase)
author = Adam Blackburn
version = 1
require passphrase *Passphrase
-----
ctrl_interface=/var/run/wpa_supplicant
network={
       ssid="$_ESSID"
       scan_ssid=$_SCAN
       key_mgmt=NONE
       wep_key0=$_PASSPHRASE
       wep_tx_keyidx=0
       priority=5
}

I experienced a similar issue which was made more confusing by the fact that the error message in the GUI showed that I was connected but unable to obtain an IP address, when in fact I had apparently never successfully authenticated. The fix above took care of the issue.

My WICD version = Wicd 1.6.2.2
Linux distro = SuSE 11.2
Wicd log file
First section is failure:
2009/12/18 17:33:27 :: setting use global dns to 0
2009/12/18 17:33:27 :: setting global dns
2009/12/18 17:33:27 :: global dns servers are
2009/12/18 17:33:27 :: domain is
2009/12/18 17:33:27 :: search domain is
2009/12/18 17:33:27 :: setting wireless interface wlan0
2009/12/18 17:33:27 :: setting wired interface eth0
2009/12/18 17:33:27 :: setting wpa driver wext
2009/12/18 17:33:27 :: setting automatically reconnect when connection drops 1
2009/12/18 17:33:27 :: setting backend to external
2009/12/18 17:33:27 :: Setting dhcp client to 0
2009/12/18 17:33:29 :: Connecting to wireless network 2WIRE250
2009/12/18 17:33:29 :: Putting interface down
2009/12/18 17:33:30 :: Releasing DHCP leases...
2009/12/18 17:33:30 :: Setting false IP...
2009/12/18 17:33:30 :: Stopping wpa_supplicant
2009/12/18 17:33:30 :: Flushing the routing table...
2009/12/18 17:33:30 :: Putting interface up...
2009/12/18 17:33:30 :: Attempting to authenticate...
2009/12/18 17:33:32 :: Running DHCP
2009/12/18 17:33:52 :: err, wlan0: timed out
2009/12/18 17:33:52 ::
2009/12/18 17:33:52 :: DHCP connection failed
2009/12/18 17:33:52 :: exiting connection thread
2009/12/18 17:33:52 :: Sending connection attempt result dhcp_failed

Second section is success:
2009/12/18 18:07:29 :: wicd initializing...
2009/12/18 18:07:29 :: ---------------------------
2009/12/18 18:07:29 :: wicd is version 1.6.2.2 463
2009/12/18 18:07:29 :: setting backend to external
2009/12/18 18:07:29 :: trying to load backend external
2009/12/18 18:07:29 :: successfully loaded backend external
2009/12/18 18:07:29 :: trying to load backend external
2009/12/18 18:07:29 :: successfully loaded backend external
2009/12/18 18:07:29 :: Automatically detected wireless interface wlan0
2009/12/18 18:07:29 :: setting wireless interface wlan0
2009/12/18 18:07:29 :: automatically detected wired interface eth0
2009/12/18 18:07:29 :: setting wired interface eth0
2009/12/18 18:07:29 :: setting wpa driver wext
2009/12/18 18:07:29 :: setting use global dns to False
2009/12/18 18:07:29 :: setting global dns
2009/12/18 18:07:29 :: global dns servers are None None None
2009/12/18 18:07:29 :: domain is None
2009/12/18 18:07:29 :: search domain is None
2009/12/18 18:07:29 :: setting automatically reconnect when connection drops True
2009/12/18 18:07:29 :: Setting dhcp client to 0
2009/12/18 18:07:29 :: Wireless configuration file found...
2009/12/18 18:07:29 :: Wired configuration file found...
2009/12/18 18:07:29 :: chmoding configuration files 0600...
2009/12/18 18:07:29 :: chowning configuration files root:root...
2009/12/18 18:07:29 :: Using wireless interface...wlan0
2009/12/18 18:07:29 :: Using wired interface...eth0
2009/12/18 18:07:36 :: Autoconnecting...
2009/12/18 18:07:38 :: No wired connection present, attempting to autoconnect to wireless network
2009/12/18 18:07:39 :: trying to automatically connect to...2WIRE250
2009/12/18 18:07:39 :: Connecting to wireless network 2WIRE250
2009/12/18 18:07:39 :: Putting interface down
2009/12/18 18:07:39 :: Releasing DHCP leases...
2009/12/18 18:07:39 :: Setting false IP...
2009/12/18 18:07:39 :: Stopping wpa_supplicant
2009/12/18 18:07:39 :: Flushing the routing table...
2009/12/18 18:07:39 :: Putting interface up...
2009/12/18 18:07:39 :: Attempting to authenticate...
2009/12/18 18:07:41 :: Running DHCP
2009/12/18 18:07:44 ::
2009/12/18 18:07:44 :: DHCP connection successful
2009/12/18 18:07:44 :: Connecting thread exiting.
2009/12/18 18:07:46 :: Sending connection attempt result Success

[mitch (mitchelly)]

I am having similar problems (using WPA2), though removing the quotes in my WPA/WPA-PSK template did not correct the issue. :-/ I can switch over to using the networkmanager daemon to connect to the same network without a hitch, but when I try to use wicd, no dice... Just fails at obtaining an IP address.

[Ponchietto (ponchio)]

The original submitter already said it but i want to stress that this is in-fact a double bug: i just inserted the wrong password and the error message (Unable to obtain IP) was quite unhelpful. Spent quite a few hours looking
for what was wrong...

The error message should be changed to "Wrong password.".

[FAJALOU (fajalou)]

I am on WICD 1.7.0, and I am having this issue with a WEP 64 HEX encryption. After working on this for hours, coming up with logs that look exactly like the OP's, I tried connecting by hand following:
http://mediakey.dk/~cc/howto-use-wep-encryption-with-ubuntu-linux/
and the DHClient worked out of the Box.
I was always able to pass authentication, and used the same password to manually connect as I have to auto-connect on WICD.
I know this is old, but still not complete, any help would be appreciated. Thanks!

[Snakefinger (snakefinger69)]

Don't know that I can be of much help since I experienced this issue quite a while back. I now use LXDE desktop on my wireless workstation, it has been easier to setup than anything else I've tried.

> Date: Fri, 24 Jun 2011 00:58:40 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 498424] Re: Passphrase issue ends with "Unable to obtain IP"
>
> I am on WICD 1.7.0, and I am having this issue with a WEP 64 HEX encryption. After working on this for hours, coming up with logs that look exactly like the OP's, I tried connecting by hand following:
> http://mediakey.dk/~cc/howto-use-wep-encryption-with-ubuntu-linux/
> and the DHClient worked out of the Box.
> I was always able to pass authentication, and used the same password to manually connect as I have to auto-connect on WICD.
> I know this is old, but still not complete, any help would be appreciated. Thanks!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/498424
>
> Title:
> Passphrase issue ends with "Unable to obtain IP"
>
> Status in wicd:
> New
>
> Bug description:
> Original forum post was http://wicd.net/punbb/viewtopic.php?id=699 by
> alexiy
>
> The end resolution of his problem is as follows:
>
> Then I have edited the template:
> /etc/wicd/encryption/templates/passphrase removing quotation marks
> around $_PASSPHRASE variable
>
> name = WEP (Passphrase)
> author = Adam Blackburn
> version = 1
> require passphrase *Passphrase
> -----
> ctrl_interface=/var/run/wpa_supplicant
> network={
> ssid="$_ESSID"
> scan_ssid=$_SCAN
> key_mgmt=NONE
> wep_key0=$_PASSPHRASE
> wep_tx_keyidx=0
> priority=5
> }
>
> I experienced a similar issue which was made more confusing by the
> fact that the error message in the GUI showed that I was connected but
> unable to obtain an IP address, when in fact I had apparently never
> successfully authenticated. The fix above took care of the issue.
>
> My WICD version = Wicd 1.6.2.2
> Linux distro = SuSE 11.2
> Wicd log file
> First section is failure:
> 2009/12/18 17:33:27 :: setting use global dns to 0
> 2009/12/18 17:33:27 :: setting global dns
> 2009/12/18 17:33:27 :: global dns servers are
> 2009/12/18 17:33:27 :: domain is
> 2009/12/18 17:33:27 :: search domain is
> 2009/12/18 17:33:27 :: setting wireless interface wlan0
> 2009/12/18 17:33:27 :: setting wired interface eth0
> 2009/12/18 17:33:27 :: setting wpa driver wext
> 2009/12/18 17:33:27 :: setting automatically reconnect when connection drops 1
> 2009/12/18 17:33:27 :: setting backend to external
> 2009/12/18 17:33:27 :: Setting dhcp client to 0
> 2009/12/18 17:33:29 :: Connecting to wireless network 2WIRE250
> 2009/12/18 17:33:29 :: Putting interface down
> 2009/12/18 17:33:30 :: Releasing DHCP leases...
> 2009/12/18 17:33:30 :: Setting false IP...
> 2009/12/18 17:33:30 :: Stopping wpa_supplicant
> 2009/12/18 17:33:30 :: Flushing the routing table...
> 2009/12/18 17:33:30 :: Putting interface up...
> 2009/12/18 17:33:30 :: Attemptin...