IEEE 802.11r: RSN: Trying to use FT, but MDIE not included
Ahmad Ali Tabassam
ahmadthe8
Tue Nov 4 09:50:47 PST 2008
1)>>interface=ath1
?bridge=br0
?driver=madwifi
>IEEE 802.11r requires driver support and madwifi does not provide the
needed functionality. At this point, your best bet could be to use ath9k
(or ath5k with a pending patch to enable AP mode).. At this point,
802.11r is still quite recent and not exactly easy to get running due to
the need for additional driver support.
--
Jouni Malinen
2)>> I am using hostapd 0.6.4 and wpa_supplicant 0.6.4 with Atheros AR5212 chipset. I updated my driver, now I am using ath5k?????? (enable AP mode patched). It is working fine with WPA and WPA2 configuration. But for 802.11r I always get the error. Would you guide me, >>how can I over come with this error. Is there something wrong on the wpa_supplicant or hostapd?. Ether would you recommend some >>other chipset. I used wext driver for wpa_supplicant, should I use some other one??
>mac80211 (used by ath5k) does not yet support FT for client mode. In
order to be able to test this now, you would need to build
wpa_supplicant with client MLME code and use that to replace the
implementation in mac80211. This would require getting wireless-testing
git tree and applying following two patches to it:
http://w1.fi/wireless-testing/userspace_mlme_allow_bssid_mismatch.patch
http://w1.fi/wireless-testing/vif_conf.patch
Then you should be able to build wpa_supplicant with
CONFIG_CLIENT_MLME=y in .config and use driver_nl80211 interface with
driver_param=use_mlme=1 in the runtime configuration file.
--
Jouni Malinen
Dear Jouni Malinen or any other
I bring the 802.11r working for AR52512 chipset, I patched?enable AP-mode for ath5k and?compiled the new?kernel ( linux kernel 2.6.27.4)?enabling the AR5xxx support, for the?AP.?I also compiled the wirless-testing git tree for STA patching the userspace_mlme_allow_bssid_mismatch.patch and vif_conf.patchand compiled accordanly your instructions
wpa_supplicant -dd -Dwext -wlan0 -pusemlme=1 -c wpa_supplicant.conf does not give any error. I can see the mobility domain Id on the STA console.?Both are looking working fine, Open authentication is successfull, I sniff the packet in the air and can see the AKMP 00-0F-AC-04 used by the FT-PSK, but association does not successed. Access point tries but the association fails after three tries, getting the same message given below.......but I can see the MDIE on the client side as shown below........Jouni Malinen would you guide, what is going wrong, should I try any other chipset using different?driver (may be ath9k).Best Regards
Ahmad Ali Tabassam
Institute Industrial IT
University of Applied Sciences, Lemgo Germany
hostapd-0.6.5 console output
authentication: STA=00:1d:0f:f9:22:77 auth_alg=0 auth_transaction=1 status_code=0 wep=0
wlan0: STA 00:1d:0f:f9:22:77 IEEE 802.11: authentication OK (open system)
wlan0: STA 00:1d:0f:f9:22:77 WPA: event 0 notification
wlan0: STA 00:1d:0f:f9:22:77 MLME: MLME-AUTHENTICATE.indication(00:1d:0f:f9:22:77, OPEN_SYSTEM)
wlan0: STA 00:1d:0f:f9:22:77 MLME: MLME-DELETEKEYS.request(00:1d:0f:f9:22:77)
authentication reply: STA=00:1d:0f:f9:22:77 auth_alg=0 auth_transaction=2 resp=0 (IE len=0)
MGMT
mgmt::assoc_req
association request: STA=00:1d:0f:f9:22:77 capab_info=0x431 listen_interval=1
RSN: Trying to use FT, but MDIE not included
?
wpa_supplicant-0.6.5 console output
Try to find WPA-enabled AP
0: 00:1d:0f:cb:cb:51 ssid='WLAN-Test' wpa_ie_len=0 rsn_ie_len=20 caps=0x11
?? selected based on RSN IE
?? selected WPA AP 00:1d:0f:cb:cb:51 ssid='WLAN-Test'
Trying to associate with 00:1d:0f:cb:cb:51 (SSID='WLAN-Test' freq=2437 MHz)
FT: Mobility domain - hexdump(len=2): a1b1
Cancelling scan request
?
What is the preffered chipset available in the market for the STA and for the AP to get 802.11r working, and which driver should I use,..................either should I need some changes to get ath5k working. please would you guide me
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20081104/52c5481d/attachment.htm
More information about the Hostap
mailing list