Re: Cannot connecting to a pure WPA3-SAE access point

I have seen issues with some chipset drivers where PMF needs to be set
to optional (ieee80211w=1), even when in SAE mode.  This is especially
true when the AP is configured to support simultaneous mixed mode
(WPA2/SAE).  What version of wpa_supplicant is running on your laptop?

Best regards,

Dennis


On Wed, Jun 17, 2020 at 9:57 AM John <[email protected]> wrote:
>
> I am trying to get wpa_supplicant on a Raspberry Pi 4 (Arch ARM uses
> v2.9 or Raspbian buster which uses 2.8-dev) to connect to my WPA3-SAE
> access point, but I get the following errors:
>
> # wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/blast.conf
> Successfully initialized wpa_supplicant
> wlan0: Trying to associate with SSID 'blast'
> wlan0: WPA: Failed to select authenticated key management type
> wlan0: WPA: Failed to set WPA key management and encryption suites
>
> Note that I can use the very same config file on my laptop (Arch Linux
> x86_64) and wpa_supplicant is able to connect without issue so I am
> wondering what might be missing on the RPi4 (kernel config, missing
> dependency etc.) that would cause this.
>
> Here is the config file:
> # cat /etc/wpa_supplicant/blast.conf
> ctrl_interface=/run/wpa_supplicant
> country=US
>
> network={
>  ssid="blast"
>  sae_password="mypassword"
>  key_mgmt=SAE
>  ieee80211w=2
> }
>
> _______________________________________________
> Hostap mailing list
> [email protected]
> http://lists.infradead.org/mailman/listinfo/hostap