[FS#4201] Broken 802.11r roaming if 802.11w is enabled (WPA3 or WPA2+802.11w)

[OpenWrt Bugs]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - enmaskarado (enmaskarado) 

Attached to Project - OpenWrt/LEDE Project
Summary - Broken 802.11r roaming if 802.11w is enabled (WPA3 or WPA2+802.11w)
Task Type - Bug Report
Category - Kernel
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - openwrt-21.02
Due in Version - Undecided
Due Date - Undecided
Details - Tested on TP-LINK CPE510 (ath9k) and TP-LINK WDR3600 (ath9k). Other users reported the same error: https://github.com/openwrt/mt76/issues/278

Steps to reproduce:

  - Put two WiFi routers at the desk and enable the same SSID on both. The SSIDs should belong to a unique network (using the two routers as APs, or one as a router and another as a AP)
  - Enable WPA2-PSK in CCMP mode, and 802.11w with "Generate PMK locally" (ft_psk_generate_local) enabled and FT protocol "FT Over the Air". I have not filled in the "NAS ID" and "Mobility Domain" options, but checking the /var/run/hostapd-phy0.conf file, I see that they have been autoconfigured correctly.
  - Test with a bunch of Android phones (in my case, Huawei, Xiaomi & Motorola, all w/Android 10). I've used Termux (ping 192.168.1.1 and/or iperf3)
  - Roam with the phones. All works seamless, the ping and iperf3 does not break.
  - Enable 802.11w (optional) and reboot the routers.
  - Roam doesn't work.
  - Disable 802.11w and reboot
  - Roam works
  - Enable WPA3/WPA2 Mixed Mode and reboot
  - Roam doesn't work. All the devices insist on mantain a connection with the original AP. They only connect to the nearest new router if they are previously disassociated with the previous router (breaking the ping and iperf3 tests).

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=4201

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.