IEEE 802.11w support in wpa_supplicant ("Management frame protection required, but client did not enable it" error)

Jouni Malinen j at w1.fi
Sat May 5 11:30:09 EDT 2012


On Sat, May 05, 2012 at 03:26:07PM +0100, Michael Zintakis wrote:
> > Which driver are you using on the station?
> >   
> wl1251 (Android :-( ).

I don't think this driver supports IEEE 802.11w.

> > CONFIG_EAP_GPSK_SHA256=y has nothing to do with IEEE 802.11w, but you do

> 1. When I have "ieee80211w=2" and "key_mgmt=WPA-EAP-SHA256" in 
> wpa_supplicant.conf I get this in my log (wpa_supplicant side):
> 
> E/wpa_supplicant( 1337): Line 30: invalid key_mgmt 'WPA-EAP-SHA256'
> E/wpa_supplicant( 1337): Line 30: no key_mgmt values configured.
> E/wpa_supplicant( 1337): Line 30: failed to parse key_mgmt 'WPA-EAP-SHA256'.
> E/wpa_supplicant( 1337): Line 51: failed to parse network block.
> 
> Strange! I do have "CONFIG_EAP_GPSK_SHA256" in my .config file when 
> compiling the supplicant. Have I missed something?

At least my comment above pointing out that this parameter has nothing
to do with IEEE 802.11w.. ;-)

This looks a bit odd.. WPA-EAP-SHA256 support is conditional on
CONFIG_IEEE80211W=y, so as long as you have that enabled and have
rebuilt wpa_supplicant/config.c in that configuration, you should not
get this error..

> 2. When I have "ieee80211w=1" and "key_mgmt=WPA-EAP" in 
> wpa_supplicant.conf I get this in my log (hostapd as well as 
> wpa_supplicant sides):

> 1336227344.542935: Management frame protection required, but client did 
> not enable it

I would assume that the driver you used does not support setting of the
MFPC/MFPR flags in RSN IE (which is not too surprising taken into
account that it does not support IEEE 802.11w).

> So, no luck here either - it times out as before! Any help?

You may have to change the station driver/hardware to get this working..

-- 
Jouni Malinen                                            PGP id EFC895FA


More information about the HostAP mailing list