Package: madwifi-source Followup-For: Bug #385599
Hi Ken, You've probably noticed I've been all over trying to find a solution for this. I made a bit of progress today. Following advice from the NM mailing list, I did: 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 } 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 even tried the latest svn snapshot). Is there any way to pass that option to wpa_supplicant through NM? and if so, what effect does this have? Thanks a lot. Carlos -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.092306 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]