Does GL.iNet GL-B1300 work with WPA3?

I've tried enabling WPA3 wifi on the _ GL.iNet GL-B1300_ following this (quite good) guide:

But now I have weird issues on some devices.

Actually WPA2/WPA3 mode does work on one device (Fedora 33, GNOME), and it even says it is connected via WPA3. WIth WPA3-only mode, I cannot connect there, however.
However, WPA3-only for some reason fails on that device. It shows me a "SSID 1" instead of "SSID" (sometimes also both, I guess in WPA2/WPA3 mode) now (I obviously have not added the SSID with " 1"), but that may be a client issue as I cannot see it on another device.
Edit: Oh well… connecting to that "SSID 1" WLAN does actually work. :laughing: Maybe it is really only a client issue as it needs to separate the new configurations… :laughing:(I kept the SSID the same when fiddeling around with the settings.)

Did anyone got it to work? Or is this a bug?

PS: Also the FP3 could not connect but that is likely caused by a bug of them. However, even in WPA2/WPA3 mode it could not connect altogether… In WPA3-only mode I could not even find the SSID – if IIRC.
Edit: So maybe that router is one of the devices, where client fallback to WPA2 may not work? As the FP3 could not connect via WPA3 it should use WPA2 after all…
Or is it the case that nothing works for such devices when you select the WPA2/WPA3 mode?


Powered by LuCI openwrt-19.07 branch (git-20.247.75781-0d0ab01) / OpenWrt 19.07.4 r11208-ce6496d796
wpad - 2019-08-08-ca8c2bd2-4
wpad-openssl - 2019-08-08-ca8c2bd2-4

QCA4018/ QCA4019, the wireless chipset used in this device can support WPA3/ SAE properly. Some client devices don't really like the AP switching between WPA2 and WPA3, so you might have to delete- and re-create the association data with the AP (I would also change the PSK and ideally the ESSID, to make it more obvious if the clients are properly configured).

1 Like

The strange thing is testing the same client (FP3) with a Fritz!Box 6490 and WPA2/WPA3 mode there it seems to work without any problem, i.e. it connects via WPA2 at least.
So this must have to do with OpenWRT somehow.