You are not logged in.
A corrupted filesystem forced me to do a fresh install on a new hard drive. Now wpa_supplicant, which previously worked with my wireless NIC and router is unable to associate with the access point. Without encryption I am able to connect to the access point and the internet works etc. I have no idea how to go about fixing this, any help would be greatly appreciated.
kernel: 2.6.17-ARCH
NIC driver: ndiswrapper (works without encryption)
# wpa_supplicant -dd -Dndiswrapper -iwlan0 -c/etc/wpa_supplicant.conf
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'ndiswrapper' ctrl_interface 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
eapol_version=1
ap_scan=1
fast_reauth=1
Line: 264 - start of a new network block
ssid - hexdump_ascii(len=8):
68 61 63 69 65 6e 64 61 hacienda
PSK (ASCII passphrase) - hexdump_ascii(len=13): [REMOVED]
priority=9 (0x9)
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 9
id=0 ssid='hacienda'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=20 WE(source)=18 enc_capa=0xd
capabilities: key_mgmt 0x5 enc 0xf
Own MAC address: [REMOVED]
Driver does not support WPA.
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
Setting scan request: 0 sec 100000 usec
Added interface wlan0
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 494 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 9
0: 00:11:24:5d:f1:ed ssid='hacienda' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
selected based on WPA IE
Trying to associate with 00:11:24:5d:f1:ed (SSID='hacienda' freq=2412 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
Association request to the driver failed
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:00:00:00:00:00 into blacklist
State: ASSOCIATING -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 494 bytes of scan results (2 BSSes)
Scan results: 2
Offline
If you are using the latest version of wpa-supplicant (later than v1.12) you need to use wext rather than ndiswrapper. Try:
wpa_supplicant -dd -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
instead of
wpa_supplicant -dd -Dndiswrapper -iwlan0 -c/etc/wpa_supplicant.conf
Offline
thank you fatbird. problem solved.
Offline
Credit goes to the Arch Linux ndiswrapper/wpa-supplicant wiki. I lost my wifi after an upgrade and that's where I found the answer.
Offline
embarassing for me that I did not find the info in such an obvious place, but thank you all the same
Offline
No need for embarrassment. My prior post wasn't an RTFM - I dislike those. I simply wanted to give credit where it was due.
I don't think everyone should have to read the all the doc's every time - if there is a simple answer to a common problem I think the forums are an appropriate place to look for that answer. Hopefully anyone who has the same problem we had can find the answer here and not have to spend half an hour reading the wiki and running tests.
Offline