This basically is a followup to:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=385599 .
wpa_supplicant's failing also causes NM to fail
(this thread: http://mail.gnome.org/archives/networkmanager-list/2006-November/msg00194.html)
For the bug, when one does:
wpa_supplicant -i ath0 -Dwext -c wpa_supplicant.conf -d
with wpa_supplicant.conf:
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="Atlantic"
key_mgmt=NONE
auth_alg=OPEN
}
It is impossible to associate to a AP + getting a IP.
The output of this seemed pretty similar to the one obtained by NM.
wpasupplicant would just keep trying to associate, and then keep
scanning. Finally, I decided to try ap_scan=0. Then, wpa_supplicant
would say connected and I could (most times) get an IP using dhclient -1 ath0.
Does this give you any clue why the problem exist in newer versions of madwifi (I am using the latest svn).
Note that this was working with r1500.
