2nd 'ft_ds' fails for 802.11R setup

Yogesh Ashok Powar yogeshp
Fri Jul 12 05:29:07 PDT 2013

Hi Jouni,

For 802.11R, We are referring to the setup mentioned by 'Carlos Fern?ndez' can be
accessed with following link
http://lists.shmoo.com/pipermail/hostap/2011-March/022860.html .

In our setup, using latest hostapd and wpa_supplicant, with following as the top
        >commit 1075b2957169d8f9d6dddd7679339c751dc9515b
        >Author: Jouni Malinen <jouni at qca.qualcomm.com>
        >Date:   Thu Jul 11 16:42:13 2013 +0300,
we are seeing that 2nd 'ft_ds' is failing consistently.

We have captured the steps and screen log at http://ix.io/6Cf . We can share the
supplicant and hostapd logs of the same if some one needs to look at.

For the first run, we get

>> ft_ds 02:00:00:00:01:00
>Trying to associate with 02:00:00:00:01:00 (SSID='ft-psk' freq=2417 MHz)
>wlan1: STA 02:00:00:00:02:00 IEEE 802.11: association OK (aid 1)
>wlan1: STA 02:00:00:00:02:00 IEEE 802.11: associated (aid 1)
>wlan1: STA 02:00:00:00:02:00 MLME: MLME-REASSOCIATE.indication(02:00:00:00:02:00)
>wlan1: STA 02:00:00:00:02:00 WPA: event 6 notification
>wlan1: STA 02:00:00:00:02:00 WPA: FT authentication already completed - do not start 4-way handshake
>Associated with 02:00:00:00:01:00
>WPA: Key negotiation completed with 02:00:00:00:01:00 [PTK=CCMP GTK=CCMP]
>CTRL-EVENT-CONNECTED - Connection to 02:00:00:00:01:00 completed [id=0 id_str=]

Notice the 'do not start 4-way handshake' which means it was successful FT-DS.

But for 2nd ft_ds we get following
>> ft_ds 02:00:00:00:00:00
>Trying to associate with 02:00:00:00:00:00 (SSID='ft-psk' freq=2412 MHz)
>SME: Association request to the driver failed

Are you aware of any such issue?
Let us know if we are missing something obvious.


Note: http://ix.io/6Cf contains all the steps and screen logs.

More information about the Hostap mailing list