The scan complete event code added to ipw2200-1.1.2 breaks wpa_supplicant when the option ap_scan=1 is used. Association fails. Version-Release number of selected component (if applicable): wpa_supplicant-0.4.8-6.fc5.i386.rpm How reproducible: Everytime Steps to Reproduce: 1. Create a wpa_supplicant.conf file for a broadcasting AP using the option ap_scan=1. 2. Use WEP. 3. Use the wext driver and -ddd option for debugging output. Actual results: association with AP fails Expected results: association with AP Additional info:
Created attachment 127443 [details] wpa_supplicant log ipw2200-1.1.2 with Yi scan_fix.patch wpa_supplicant-0.4.8-7.fc5 FC5 updated /4-6-06 NetworkManager-0.6.2 Since first report, ipw2200-1.1.2 has been patched so that it now works with wpa_supplicant with the option ap_scan=1. When booting to wireless, NM associates and then immediately drops the connection. If you force the connection from the menu, a connection is made. wpa_supplicant log attached with NetworkManager turned off and log attached for NetworkManager.
Created attachment 127444 [details] NetworkManager debug log pw2200-1.1.2 with Yi scan_fix.patch wpa_supplicant-0.4.8-7.fc5 FC5 updated /4-6-06 NetworkManager-0.6.2 Since first report, ipw2200-1.1.2 has been patched so that it now works with wpa_supplicant with the option ap_scan=1. When booting to wireless, NM associates and then immediately drops the connection. If you force the connection from the menu, a connection is made. wpa_supplicant log attached with NetworkManager turned off and log attached for NetworkManager.
I think this one should be OK now, so closing. If it's still an issue, feel free to reopen :)