Re: QCA6174 showing terrible performance when connecting via WPA3-SAE

[Kalle Valo <kvalo@kernel.org>]

Eric Park <me@ericswpark.com> writes:

> On 2024-04-29 14:18, Kalle Valo wrote:
>> If you run wpa_supplicant -dddt (or similar) you get a lot of debug
>> output, I'm sure it will also include the cipher.
>
> Good to know, thank you. Will keep this in mind the next time I'm
> troubleshooting WPA-levels.
>
>> Very good that you found this is 802.11w related. What is the make and
>> model of your router?
>
> I'm using a GL-AXT1800 (Slate AX) router from GL.iNet.
>
>> I don't know how well ath10k 802.11w support is tested and then it was
>> last tested. Do you happen to have other Access Points supporting
>> 802.11w? That might help to pinpoint if 802.11w is completely broken in
>> ath10k or if this is an interoperability issue with ath10k and your AP.
>
> I unfortunately do not have access to any other routers I can modify
> settings on at the moment (or any other APs to connect to, to test on,
> really...) I may have some routers to test it on next week, but I'm
> unsure whether they allow me to modify the 802.11w settings as they're
> mostly proprietary and don't run something like OpenWRT.
>
> Do you know if it'll be possible to add a flag to enable/disable 802.11w
> on ath10k's side? Even if it turns out to be an interoperability issue,
> it will most likely be useful to have the ability to switch it off for
> APs that don't play nice. Especially for public APs and proprietary
> APs where the end-user can't realistically turn off 802.11w for the
> entire network.

If the problem is on ath10k side I would rather semove support for
802.11w altogether (until it's fixed). It's controlled with this flag:

	ieee80211_hw_set(ar->hw, MFP_CAPABLE);

Alternatively if it works on some hardware and not on others we could
make it per hw, for example disabled on QCA6174 and enabled on all
others.

But I found some old documentation claiming that 802.11w can be disabled
from Network Manager, if it works that sounds like a good temporary
solution:

"pmf int32 0 Indicates whether Protected Management Frames (802.11w)
must be enabled for the connection."

https://developer-old.gnome.org/NetworkManager/stable/settings-802-11-wireless-security.html

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches