Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
openwrt-bot opened this issue Dec 24, 2021 · 7 comments
Labels
flyspray kernel pull request/issue with Linux kernel related changes release/21.02 pull request/issue targeted (also) for OpenWrt 21.02 release

Comments

@openwrt-bot
Copy link

enmaskarado:

Tested on TP-LINK CPE510 (ath9k) and TP-LINK WDR3600 (ath9k). Other users reported the same error: openwrt/mt76#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).
@aparcar aparcar added release/21.02 pull request/issue targeted (also) for OpenWrt 21.02 release kernel pull request/issue with Linux kernel related changes labels Feb 22, 2022
@parthkarnawat
Copy link

Has this been fixed in the latest stable version?

@ishanjain28
Copy link

@parthkarnawat Nope

@Livy-Inverse
Copy link

Livy-Inverse commented Feb 8, 2023

Just for information, this bug does not happen on 19.07.10. I have ~20 TP-Link TL-WR740N across several houses, and use psk2 + ieee80211k + ieee80211r + ieee80211w (2) on all of them. My Realme phone roams very fast when I move around.

Change the encryption method to SAE and roaming does not work anymore, regardless of ieee80211k and ieee80211r settings. I suspect it relates to phone drivers rather than access point issues.

@dejayc
Copy link

dejayc commented Feb 9, 2023

This problem stopped happening on my router, because I've abandoned OpenWrt and gone back to using the manufacturer's firmware.

When OpenWrt only delivers 8Mb/s whereas the manufacturer's firmware delivers 650Mb/s, you don't need to wonder whether OpenWrt is ready for primetime or not.

@enmaskarado
Copy link
Contributor

Hello,
I can no longer reproduce the error with 80211w=1 and WPA2 (23.05-rc2).
The error continues with WPA3.

@Vitaliy86
Copy link

23.05-rc3 wpa3 not working

@cotequeiroz
Copy link
Member

WPA3 does not work with 'Generate PMK locally' (ft_psk_generate_local). IIRC, the PMK can't be generated locally, and must be exchanged between APs. Turn it off, and it should work. There's no need to set any keys or other parameters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flyspray kernel pull request/issue with Linux kernel related changes release/21.02 pull request/issue targeted (also) for OpenWrt 21.02 release
Projects
None yet
Development

No branches or pull requests

9 participants