Arch Linux

silversnakeeyes

Member

From: Seattle, WA

Registered: 2009-11-14

Posts: 31

Website

Wicd | "Connection Failed: Unable to get IP address"

Using wicd was fine up until recently, for some reason, every network except the one I am connected to now are giving me the error "Connection Failed: Unable to get IP address". In external programs, I have tried all options, and in advanced settings, I have tried ralink_legacy (I am using a rt2570 linksys wireless adapter) and wext, none of which work.

(Hope this might help somewhat, results are slimmed down to the wlan parts)
ifconfig:

wlan0     Link encap:Ethernet  HWaddr 00:0C:41:69:D1:EC  
          inet addr:192.168.1.106  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:41ff:fe69:d1ec/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8621 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7871 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:5915753 (5.6 Mb)  TX bytes:1970689 (1.8 Mb)

dmesg:

wlan0: authenticate with AP 00:18:01:f1:ba:b0
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
eth0: link down
wlan0: authenticate with AP 00:18:01:f1:ba:b0
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
eth0: link down
wlan0: authenticate with AP 00:18:01:f1:ba:b0
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
eth0: link down
wlan0: authenticate with AP 00:1c:10:13:07:a2
wlan0: authenticated
wlan0: associate with AP 00:1c:10:13:07:a2
wlan0: RX AssocResp from 00:1c:10:13:07:a2 (capab=0x401 status=0 aid=4)
wlan0: associated
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth0: link is not ready
wlan0: no IPv6 routers present
eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
wlan0: deauthenticating by local choice (reason=3)
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: authenticate with AP 00:1f:90:c9:8b:34
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: authenticate with AP 00:1c:10:13:07:a2
wlan0: authenticated
wlan0: associate with AP 00:1c:10:13:07:a2
wlan0: RX AssocResp from 00:1c:10:13:07:a2 (capab=0x401 status=0 aid=4)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present

lynucs

Member

Registered: 2008-05-05

Posts: 67

Website

Re: Wicd | "Connection Failed: Unable to get IP address"

same here,
Atheros AR5212 802.11abg NIC (rev 01).

rolling back to kernel, kernel-firmware and kernel-headers 2.6.31 didn't help.

wicd often also just founds nothing, then hangs for 3-5 mins and finds some access points with failing on connect either with "bad password" or "could not obtain IP".

EDIT: firware upgrade of router _and_ resetting router solved the problem for me, so not a wicd fault in my case.

Last edited by lynucs (2010-01-07 23:58:23)

---

Pinky, are you pondering what I'm pondering?

cathexis

Member

Registered: 2010-01-07

Posts: 1

Re: Wicd | "Connection Failed: Unable to get IP address"

I'm getting the same problem.  It appears that iwconfig is unhappy associating with an access point if it's already been associated with an access point this boot (even if you do the association manually) and then dhcpcd times out because it can't find a dhcp server.  When I go home I'll grab the dmesg output and see what I can grab from my syslog to try and narrow this down (assuming it hasn't already been done elsewhere on the forum).

Roline

Member

From: Netherlands

Registered: 2009-12-05

Posts: 207

Website

Re: Wicd | "Connection Failed: Unable to get IP address"

I've had the same problem, but if i try connecting again it all works flawless.

---

Bitbucket - DeviantART - Userstyles
*Currently Not Using Arch

mcsaba77

Member

From: Ho Chi Minh City, Vietnam

Registered: 2009-09-30

Posts: 52

Re: Wicd | "Connection Failed: Unable to get IP address"

I have the same problem, 100% reproducible. Wicd connects on startup, if I disconnect and then try to connect again, I get the Connection Failed error. What I noticed in dmesg output is that it tries to get an ipv6 address, and fails with wlan0: no IPv6 routers present:

ADDRCONF(NETDEV_UP): wlan0: link is not ready
tg3 0000:09:00.0: irq 31 for MSI/MSI-X
ADDRCONF(NETDEV_UP): eth0: link is not ready
Registered led device: iwl-phy0::radio
Registered led device: iwl-phy0::assoc
Registered led device: iwl-phy0::RX
Registered led device: iwl-phy0::TX
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: direct probe to AP 00:1a:2b:15:e9:d4 (try 1)
wlan0: direct probe responded
wlan0: authenticate with AP 00:1a:2b:15:e9:d4 (try 1)
wlan0: deauthenticating from 00:1a:2b:15:e9:d4 by local choice (reason=3)
wlan0: direct probe to AP 00:1a:2b:15:e9:d4 (try 1)
wlan0: direct probe responded
wlan0: authenticate with AP 00:1a:2b:15:e9:d4 (try 1)
wlan0: authenticated
wlan0: associate with AP 00:1a:2b:15:e9:d4 (try 1)
wlan0: RX AssocResp from 00:1a:2b:15:e9:d4 (capab=0x411 status=0 aid=1)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present

Any ideas how to solve this? I think this is a serious issue, since I can no longer use suspend/hybernate for example... I have an Intel Pro Wireless (using iwl3945 driver), up to date system... The problem started about a week ago? (I'm not sure).

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: Wicd | "Connection Failed: Unable to get IP address"

You could try this workaround:

# iwconfig wlan0 power off

It has worked for others with similar issues (and a range of wireless cards...)
http://bbs.archlinux.org/viewtopic.php?id=87220

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

mcsaba77

Member

From: Ho Chi Minh City, Vietnam

Registered: 2009-09-30

Posts: 52

Re: Wicd | "Connection Failed: Unable to get IP address"

You could try this workaround:

# iwconfig wlan0 power off

It has worked for others with similar issues (and a range of wireless cards...)
http://bbs.archlinux.org/viewtopic.php?id=87220

Thanks!! Had to unload the kernel module too to make it work:

[root@Helios molinari]# iwconfig wlan0 power off
[root@Helios molinari]# rmmod iwl3945
[root@Helios molinari]# modprobe iwl3945
[root@Helios molinari]# iwconfig wlan0 power on
[root@Helios molinari]# ifconfig wlan0 up

Then Wicd Manager could connect correctly again. Good workaround, thanks again. Hope this gets fixed soon though...

Last edited by mcsaba77 (2010-01-09 03:50:47)

mcsaba77

Member

From: Ho Chi Minh City, Vietnam

Registered: 2009-09-30

Posts: 52

Re: Wicd | "Connection Failed: Unable to get IP address"

After latest kernel upgrade the above method stopped working.

[root@Helios molinari]# iwconfig wlan0 power off
Error for wireless request "Set Power Management" (8B2C) :
    SET failed on device wlan0 ; Operation not supported.

I changed nothing, just did the upgrade.

rant

Kernel 2.6.32 is probably the worst release of the year For example, starting virtualbox without rebuilding the kernel module hardlocks my laptop. I know I SHOULD rebuild virtualbox modules with each kernel update, but they never hardlocked my laptop (just failed gracefully with an error message).

/rant

Anyway, any ideas about the wireless issues?

silversnakeeyes

Member

From: Seattle, WA

Registered: 2009-11-14

Posts: 31

Website

Re: Wicd | "Connection Failed: Unable to get IP address"

I solved my problem, just reverted back to the default NetworkManager, I miss wicd already though.

MONVMENTVM

Member

Registered: 2007-10-06

Posts: 50

Re: Wicd | "Connection Failed: Unable to get IP address"

I have the same Unable to get IP address for months now. A week ago I uninstalled wicd and wpa_supplicant and removed some config files and it suddenly worked again. Just then I upgraded my system and after the first reboot afterwards it's not working again and I don't get it to work no matter what I do.

Tried using dhclient, reinstalling wicd and wpa_supplicant, removing configs.. but nothing.

brianhanna

Member

Registered: 2009-10-30

Posts: 157

Re: Wicd | "Connection Failed: Unable to get IP address"

You may try disabling the IPv6 module.  It helped me.  See the last few posts in this thread for more info.  http://bbs.archlinux.org/viewtopic.php?id=87802&p=2

palbo

Member

From: norway

Registered: 2008-03-22

Posts: 4

Re: Wicd | "Connection Failed: Unable to get IP address"

Been having similar issues, upgraded to 2.6.32 and the wifi was b0rked, downgraded back to 2.6.31 and i got unsecured wifis to work, but when trying to connect with WPA2 encrypted ones it doesn't work.

wpa_supplicant debug output:

Initializing interface 'wlan0' conf '001e526bd1eb' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '001e526bd1eb' -> '/home/palbo/001e526bd1eb'
Reading configuration file '/home/palbo/001e526bd1eb'
ap_scan=1
ctrl_interface='/var/run/wpa_supplicant'
Priority group 0
   id=0 ssid='Daedalus'
Initializing interface (2) 'wlan0'
Interface wlan0 set UP - waiting a second for the driver to complete iniWireless event: new AP: 00:00:00:00:00:00
Added BSSID 00:1e:52:6b:d1:eb into blacklist
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keystialization
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0xf flags 0x0
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1b:77:9c:c5:5f
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
WPS: UUID based on MAC address - hexdump(len=16): d4 95 d3 0b 75 ee 5f 53 b2 28 32 b2 b8 84 40 c8
WPS: Build Beacon and Probe Response IEs
WPS:  * Version
WPS:  * Wi-Fi Protected Setup State (0)
WPS:  * Version
WPS:  * Wi-Fi Protected Setup State (0)
WPS:  * Response Type (2)
WPS:  * UUID-E
WPS:  * Manufacturer
WPS:  * Model Name
WPS:  * Model Number
WPS:  * Serial Number
WPS:  * Primary Device Type
WPS:  * Device Name
WPS:  * Config Methods (0)
WPS:  * RF Bands (3)
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Ignore event for foreign ifindex 7
Ignore event for foreign ifindex 7
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=8
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 3664 bytes of scan results (10 BSSes)
CTRL-EVENT-SCAN-RESULTS 
WPS-AP-AVAILABLE 
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1e:52:78:94:40 ssid='Prometheus' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
   skip - SSID mismatch
1: 00:1e:52:6b:d1:eb ssid='Daedalus' wpa_ie_len=24 rsn_ie_len=24 caps=0x11
   selected based on RSN IE
   selected WPA AP 00:1e:52:6b:d1:eb ssid='Daedalus'
Trying to associate with 00:1e:52:6b:d1:eb (SSID='Daedalus' freq=2447 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
RSN: using IEEE 802.11i/D9.0
WPA: Selected cipher suites: group 8 pairwise 24 key_mgmt 2 proto 2
WPA: set AP WPA IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: set AP RSN IE - hexdump(len=26): 30 18 01 00 00 0f ac 02 02 00 00 0f ac 04 00 0f ac 02 01 00 00 0f ac 02 00 00
WPA: using GTK TKIP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RSN: Ignored PMKID candidate without preauth flag
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b04 len=12
EAPOL: disable timer tick
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Added BSSID 00:1e:52:6b:d1:eb into blacklist
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:00:00:00:00:00 into blacklist
No keys have been configured - skip key clearing
State: DISCONNECTED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=8
Scan results did not fit - trying larger buffer (8192 bytes)
Received 4453 bytes of scan results (12 BSSes)
CTRL-EVENT-SCAN-RESULTS 
WPS-AP-AVAILABLE 
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:1e:52:78:94:40 ssid='Prometheus' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
   skip - SSID mismatch
1: 00:1e:52:6b:d1:eb ssid='Daedalus' wpa_ie_len=24 rsn_ie_len=24 caps=0x11
   selected based on RSN IE
   selected WPA AP 00:1e:52:6b:d1:eb ssid='Daedalus'
Trying to associate with 00:1e:52:6b:d1:eb (SSID='Daedalus' freq=2447 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
RSN: using IEEE 802.11i/D9.0
WPA: Selected cipher suites: group 8 pairwise 24 key_mgmt 2 proto 2
WPA: set AP WPA IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: set AP RSN IE - hexdump(len=26): 30 18 01 00 00 0f ac 02 02 00 00 0f ac 04 00 0f ac 02 01 00 00 0f ac 02 00 00
WPA: using GTK TKIP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RSN: Ignored PMKID candidate without preauth flag
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
BSSID 00:1e:52:6b:d1:eb blacklist count incremented to 2
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_

Any ideas? It's baffling that downgrading everything from the upgrade didn't solve the issues.

---

/end

cactus.ed

Member

From: The lonesome crowded west

Registered: 2007-08-11

Posts: 32

Re: Wicd | "Connection Failed: Unable to get IP address"

Kernel 2.6.32 is probably the worst release of the year For example, starting virtualbox without rebuilding the kernel module hardlocks my laptop. I know I SHOULD rebuild virtualbox modules with each kernel update, but they never hardlocked my laptop (just failed gracefully with an error message).

Same here... 2.6.32 has sucked. Virtualbox hard-locked my desktop after upgrading from 2.6.32.1 -> 2.6.32.2, Nvidia hard-locked my desktop (vgaarb Nvidia multi-gpu problem, for patch see http://www.nvnews.net/vbulletin/showthr … ?t=142656), wireless problems, IRQ issues that were not present in 2.6.31... Things were so stable for such a long time, what happened with 2.6.32?

JackH79

Member

From: Australia

Registered: 2009-06-18

Posts: 663

Website

Re: Wicd | "Connection Failed: Unable to get IP address"

I would recommend to upgrade to wicd 1.7 from testing if you haven't already. Resolved ALL my problems I had with 1.6. Release 1.7 had a number of fixes.

ise

Developer

From: Karlsruhe / Germany

Registered: 2005-10-06

Posts: 404

Website

Re: Wicd | "Connection Failed: Unable to get IP address"

I have moved wicd 1.7.0 to [extra] yesterday. So it should be available on your mirror soon. They have fixed several things about the reconnection thing, hopefully it works better for you with the new version.

---

23 page
My blog

allbluedream

Member

Registered: 2008-04-06

Posts: 155

Re: Wicd | "Connection Failed: Unable to get IP address"

After upgrading to wicd 1.7.0-1 I was unable to connect to my WPA2 network. dmesg kept saying that "associated... deauthenticating from [my local AP] by local choice (reason=3)"
I have to downgrade wicd to get my network back again.

yvonney

Member

Registered: 2008-06-11

Posts: 671

Re: Wicd | "Connection Failed: Unable to get IP address"

MAYBE clean out wicd completely as in prefs etc. then reinstall?
I am also finding that with STATIC IP (just) address/netmask/gateway, works.

wicd WAS finding the old name for a router here and many of the things mentioned above that others were having. Perhaps there's a way to deletes prefs of sorts which might help. Carefully here pointing out that with many changes to wicd lately and my own wireless connect perplexities i'd say go carefully with deleting etc. of any prefs. Or have the latest wicd package on the machine for reinstall reinstall I guess.

Last edited by yvonney (2010-01-21 20:39:10)

kgas

Member

From: Qatar

Registered: 2008-11-08

Posts: 718

Re: Wicd | "Connection Failed: Unable to get IP address"

I can confirm this issue with wicd. The problem started after WEP passphrase encryption of wireless connection(both with dhclient / dhcpcd). Default network manager works fine. Currently switching to networkmanager/gnome for the openbox setup.

mcsaba77

Member

From: Ho Chi Minh City, Vietnam

Registered: 2009-09-30

Posts: 52

Re: Wicd | "Connection Failed: Unable to get IP address"

After upgrading to wicd 1.7.0-1 I was unable to connect to my WPA2 network. dmesg kept saying that "associated... deauthenticating from [my local AP] by local choice (reason=3)"
I have to downgrade wicd to get my network back again.

Same here except I use WEP on my home network. After the deauthentication messages it ended with "no ipv6 routers found" as posted above. Disabling ipv6 completely (in modprobe.conf alias net-pf-10 off) helped... for a while. Now with latest wicd, and I tried both wicd from packages and wicd-bzr from AUR, after I disconnect, it won't reconnect most of the time. Sometimes it will though - the behaviour is totally random.

Same here... 2.6.32 has sucked. Virtualbox hard-locked my desktop after upgrading from 2.6.32.1 -> 2.6.32.2, Nvidia hard-locked my desktop (vgaarb Nvidia multi-gpu problem, for patch see http://www.nvnews.net/vbulletin/showthr … ?t=142656), wireless problems, IRQ issues that were not present in 2.6.31... Things were so stable for such a long time, what happened with 2.6.32?

Yeah... and it's getting worst. The kernel guys decided to make 2.32 an LTS kernel. Why? One of the reasons is that Ubuntu includes this version in their LTS release. I hate to see that Ubuntu has such a sway over kernel developer's decision. Or any distro for that matter. I think whether or not a kernel release becomes LTS should be decided on technical merit, not what certain not very well tested distributions do. I mean why not choose a kernel that is relatively problem free across multiple distributions?

brianhanna

Member

Registered: 2009-10-30

Posts: 157

Re: Wicd | "Connection Failed: Unable to get IP address"

I didn't know .32 would be an LTS.  .31 would have been a much better choice (at least on all my hardware).

I'm also having a problem with wicd 1.7.0.  It works fine on initial boot but won't reconnect after suspend/resume.  It used to do that just fine.  I haven't figured out where the problem is yet but it seems to not always be the same thing.  Sometimes unloading/reloading the iwl3945 module works for me.  Sometimes it doesn't and it's something else.  A few times I just got tired and rebooted (that always seems to work at least).

jvalecillos

Member

Registered: 2009-02-25

Posts: 24

Re: Wicd | "Connection Failed: Unable to get IP address"

I have the same problem, 100% reproducible. Wicd connects on startup, if I disconnect and then try to connect again, I get the Connection Failed error.

I have exactly the same problem, and if i do:

modprobe -r ath5k

and

modprobe ath5k

Then Wicd connects, the problem persists on kernel 2.6.32.4. I don't think that this is a wicd problem because i've installed a bzr version of "AUR" and i  have not updated in a while. The wicd 1.7.0 and current bzr version presents the problem too, but as i said before i think that is a kernel's problem (or his modules).

It seems to be the same bug here http://bbs.archlinux.org/viewtopic.php?pid=694349

Last edited by jvalecillos (2010-01-24 14:02:41)

fadec

Member

Registered: 2010-01-25

Posts: 12

Re: Wicd | "Connection Failed: Unable to get IP address"

I have the same problem with a 5300AGN. It will connect to wifi on the first try after reboot but further attempts to connect fail. It is 100% reproducible. The workaround is to remove and install the kernel module. I do not have to power down the wifi card in my case.

rmmod iwlagn
modprobe iwlagn

This has been pretty frustrating as I was setting up a new laptop. Glad I found this thread.

Last edited by fadec (2010-01-25 03:00:39)

jvalecillos

Member

Registered: 2009-02-25

Posts: 24

Re: Wicd | "Connection Failed: Unable to get IP address"

I think that could be related with this bug https://bugs.launchpad.net/wicd/+bug/510512

I uploaded a bug report here: http://bugs.archlinux.org/task/18011

Can you please comment it and confirm it, so the maintainers can do something about it?...

Last edited by jvalecillos (2010-01-26 04:33:23)

mcsaba77

Member

From: Ho Chi Minh City, Vietnam

Registered: 2009-09-30

Posts: 52

Re: Wicd | "Connection Failed: Unable to get IP address"

I saw this on wicd bugtracker: https://bugs.launchpad.net/wicd/+bug/495369 - they claim it's a kernel/driver issue. On the other hand, networkmanager works fine (switched 2 days ago, though I'd prefer using wicd).

kgas

Member

From: Qatar

Registered: 2008-11-08

Posts: 718

Re: Wicd | "Connection Failed: Unable to get IP address"

Now wicd is working.