Control: tags -1 moreinfo Hi
On Friday 16 May 2014, Ritesh Raj Sarraf wrote:
> Package: wpasupplicant
> Version: 1.1-1
> Severity: normal
>
>
> Dear Maintainers,
>
> I get the following error when trying to connect to a wifi network that
> support EAP FAST.
EAP-FAST is enabled in wpa_supplicant's configuration and should work,
but off hand I have no way to actually test it against a network using
it.
> wlan0: Trying to associate with b4:14:89:83:57:80 (SSID='corp' freq=2412
> MHz)
> FT: Stored MDIE and FTIE from (Re)Association Response - hexdump(len=0):
> wlan0: Cancelling scan request
> wlan0: WPA: clearing own WPA/RSN IE
> wlan0: Automatic auth_alg selection: 0x1
> wlan0: RSN: using IEEE 802.11i/D9.0
> wlan0: WPA: Selected cipher suites: group 16 pairwise 16 key_mgmt 1
> proto 2
> wlan0: WPA: clearing AP WPA IE
> WPA: set AP RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00
> 0f ac 04 01 00 00 0f ac 01 28 00
> wlan0: WPA: using GTK CCMP
> wlan0: WPA: using PTK CCMP
> wlan0: WPA: using KEY_MGMT 802.1X
> wlan0: WPA: not using MGMT group cipher
> WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 04
> 01 00 00 0f ac 04 01 00 00 0f ac 01 00 00
> wlan0: No keys have been configured - skip key clearing
> wlan0: State: SCANNING -> ASSOCIATING
> wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> netlink: Operstate: linkmode=-1, operstate=5
> Limit connection to BSSID b4:14:89:83:57:80 freq=2412 MHz based on scan
> results (bssid_set=0)
> wpa_driver_wext_associate
> wpa_driver_wext_set_drop_unencrypted
> wpa_driver_wext_set_psk
Is there a particular reason why you're using wext as wpa-driver?
Modern linux wlan drivers, basically all except staging ones, are
mac80211 based and according use cfg80211 and the nl80211 wpa-driver.
While the kernel's cfg80211 subsystem has a basic wext compatibility
layer, it is considered to be strongly discouraged and has known
problems and bugs. If your wlan card is using a mainline (non-staging)
driver, you should always prefer nl80211 (which is default, unless
specifically overriden in your wpa_supplicant configuration).
> ioctl[SIOCSIWFREQ]: Device or resource busy
> wlan0: Association request to the driver failed
> wlan0: Setting authentication timeout: 5 sec 0 usec
> EAPOL: External notification - EAP success=0
> EAPOL: Supplicant port status: Unauthorized
> EAPOL: External notification - EAP fail=0
> EAPOL: Supplicant port status: Unauthorized
> EAPOL: External notification - portControl=Auto
> EAPOL: Supplicant port status: Unauthorized
> RSN: Ignored PMKID candidate without preauth flag
> RSN: Ignored PMKID candidate without preauth flag
> RSN: Ignored PMKID candidate without preauth flag
> RSN: Ignored PMKID candidate without preauth flag
> RSN: Ignored PMKID candidate without preauth flag
> RSN: Ignored PMKID candidate without preauth flag
> RSN: Ignored PMKID candidate without preauth flag
> RSN: Ignored PMKID candidate without preauth flag
> wlan0: Checking for other virtual interfaces sharing same radio (phy0)
> in event_scan_results
> RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
> WEXT: if_removed already cleared - ignore event
> Wireless event: cmd=0x8b1a len=16
> RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
> WEXT: if_removed already cleared - ignore event
> Wireless event: cmd=0x8b06 len=12
> RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
> WEXT: if_removed already cleared - ignore event
> Wireless event: cmd=0x8b1a len=20
> EAPOL: Supplicant port status: Unauthorized
[...]
Which wlan card/ driver and kernel version are you using?
Regards
Stefan Lippers-Hollmann
signature.asc
Description: This is a digitally signed message part.
