Comment 4 for bug 728749

This might be the same bug as I encountered on Ubuntu 10.04 LTS. The prblem seems to be that right after the authenticate step the associate step somehow destroys the connection again which makes the dhcp step fail.
The following patch which comments out the associate step makes wicd work. I do not understand why this step is neccessary at all, at least not for all types of wireless connections.

------------------

--- networking.py.orig 2010-01-15 05:49:11.000000000 +0100
+++ networking.py 2011-03-14 23:09:01.063528703 +0100
@@ -866,8 +866,8 @@
             self.generate_psk_and_authenticate(wiface)

         # Associate.
- wiface.Associate(self.network['essid'], self.network['channel'],
- self.network['bssid'])
+# wiface.Associate(self.network['essid'], self.network['channel'],
+# self.network['bssid'])

         # Authenticate after association for Ralink legacy cards.
         if self.wpa_driver == 'ralink legacy':

------------------

This is my kernel log without the patch and after that dhcp fails:

Mar 14 22:02:36 habanero kernel: [14077.209605] wlan0: direct probe to AP 00:15:f2:6a:d6:bb (try 1)
Mar 14 22:02:36 habanero kernel: [14077.211864] wlan0: direct probe responded
Mar 14 22:02:36 habanero kernel: [14077.211873] wlan0: authenticate with AP 00:15:f2:6a:d6:bb (try 1)
Mar 14 22:02:36 habanero kernel: [14077.214671] wlan0: authenticated
Mar 14 22:02:36 habanero kernel: [14077.214709] wlan0: associate with AP 00:15:f2:6a:d6:bb (try 1)
Mar 14 22:02:36 habanero kernel: [14077.217792] wlan0: RX AssocResp from 00:15:f2:6a:d6:bb (capab=0x411 status=0 aid=2)
Mar 14 22:02:36 habanero kernel: [14077.217800] wlan0: associated
Mar 14 22:02:36 habanero kernel: [14077.272656] wlan0: deauthenticating from 00:15:f2:6a:d6:bb by local choice (reason=3)
Mar 14 22:02:36 habanero kernel: [14077.279944] wlan0: direct probe to AP 00:15:f2:6a:d6:bb (try 1)
Mar 14 22:02:36 habanero kernel: [14077.282191] wlan0: direct probe responded
Mar 14 22:02:36 habanero kernel: [14077.282199] wlan0: authenticate with AP 00:15:f2:6a:d6:bb (try 1)
Mar 14 22:02:36 habanero kernel: [14077.284156] wlan0: authenticated
Mar 14 22:02:36 habanero kernel: [14077.300771] wlan0: associate with AP 00:15:f2:6a:d6:bb (try 1)
Mar 14 22:02:36 habanero kernel: [14077.302953] wlan0: RX AssocResp from 00:15:f2:6a:d6:bb (capab=0x411 status=0 aid=2)
Mar 14 22:02:36 habanero kernel: [14077.302960] wlan0: associated

This is my kernel log with the patch and after that DHCP works:

Mar 15 10:00:27 habanero kernel: [21361.792281] wlan0: authenticate with AP 00:15:f2:6a:d6:bb (try 1)
Mar 15 10:00:27 habanero kernel: [21361.794210] wlan0: authenticated
Mar 15 10:00:27 habanero kernel: [21361.794250] wlan0: associate with AP 00:15:f2:6a:d6:bb (try 1)
Mar 15 10:00:27 habanero kernel: [21361.797709] wlan0: RX AssocResp from 00:15:f2:6a:d6:bb (capab=0x411 status=0 aid=2)
Mar 15 10:00:27 habanero kernel: [21361.797717] wlan0: associated
Mar 15 10:00:27 habanero kernel: [21361.816592] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

Hope this helps you, I needed serveral hours to find this.
Harald.