Query about IEEE80211R

Zhiyuan Yang yangzy at marvell.com
Mon Dec 2 22:28:38 EST 2013


Hi All,

I found that IEEE802.11R is only supported when use WPA Supplicant as SME.
In function ft_rx_action() {
         if (!(wpa_s->drv_flags & WPA_DRIVER_FLAGS_SME))
                   return;
......
}
So if we use driver as an internal SME, IEEE802.11R FT-over-DS is not supported by supplicant (FT action will send to supplicant as it is registered).
Thus, when we use driver as an internal SME:
For FT-OVER-DS, FT action will be refused as wpa_s->drv_flags is not WPA_DRIVER_FLAGS_SME.
For FT-OVER-AIR, It did not set psk or pmk/pmkr0 to driver, so driver can't implement IEEE802.11R to support FT-OVER-AIR.

Is there any plan for WPA Supplicant to support IEEE 802.11R with driver as an internal SME? Or is it supported now? How will WPA Supplicant support IEEE 802.11R when we use driver as an internal SME?

I have tried to support IEEE 802.11R with current wpa supplicant when use driver as SME.
1) For FT-OVER-DS, don't check drv_flag in ft_rx_action(), so ft action can be handled at WPA supplicant, and ft roaming ok.
2) For FT-OVER-AIR, in wpa_supplicant_associate(), we check if ft is used and PTK have been installed , then set auth type as WPA_AUTH_ALG_FT, and set PMK/PMKR0 to driver. So driver as SME will support FT-OVER-AIR ok.
Do you approve this solution to support IEEE 802.11R when use driver as SME? Or is there any better solution to support? If it is ok, we will submit patches to support IEEE 80211R when use driver as SME.

Thanks
Best Regards
zhiyuan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.shmoo.com/pipermail/hostap/attachments/20131202/8feb7eb1/attachment.htm>


More information about the HostAP mailing list