I am using feisty and have been experiencing the same bug since some month ago (may be an upgrade). I can't even associate using iwconfig, however I found the following workaround: when I use iwconfig to associate to the AP, I also specify the channel as follows
I am using feisty and have been experiencing the same bug since some month ago (may be an upgrade). I can't even associate using iwconfig, however I found the following workaround: when I use iwconfig to associate to the AP, I also specify the channel as follows
iwconfig eth1 ESSID <MY_ESSID> mode Managed channel <MY_CHANNEL>
Channels can be listed by issuing the command "iwlist scan".
This suffices to associate to the AP, and makes the subsequent "dhclient eth1" work and obtain an address.