Trying to figure out if I need to change a setting but I have WPA3 on with PMF on and some devices are having connectivity issues unless I disable WPA3
It’s mainly a MyQ garage door opener and a few Lifx bulbs and some eufy gear
Was using unifi APs previously so unsure of why it’s not connecting when WPA3 was enabled before but it was set to WPA2/3 transition mode.
Anyone got it working so far since debating putting up a Unifi AP again just to get IoT stuff working
Thanks is it possible to downgrade the firmware?
I’ll let the Alta folks respond to that question.
Have you already confirmed that setting both WPA3 and PMF to required result in the same problem? Please check it with a new SSID to test.
Hi there
I have tried with a new SSID as well and the same issue occurs. The only temp workaround is to disable WPA3 but this shouldn’t be a workaround as I previously had a WPA3 network before in WPA2/WPA3 personal transition mode and all devices worked fine.
Thanks. Can you confirm that you set the values to required instead of on?
Seems like PMF is Required while WPA3 is On, i.e. optional. So, clients connecting with WPA2 but not able to handle PMF will fail? PMF might also need to be set to On?!
Yes, you might be on to something there @ebuckland81 . If I’m understanding properly, setting both PMF and WPA3 to on enables WPA2/WPA3 transition mode whereas setting both to Required gets you WPA3 only. There could be some weirdness with having PMF set to required and WPA3 set to on. That all being said, I do wish there was some more clarity in the interface about what options need to be set to have the effect you want.
I suspect @Alta-Josh is trying to have both options set to required to narrow down if it’s a problem occuring with WPA3 no matter what or if it’s occuring in just the transition mode.
@Cappy
You might be able to get some more information on what’s going on as well by doing a shift+click on the AP in the controller interface and checking the log the AP keeps, like so
Just a couple thoughts!
Thanks! didn’t know that a terminal interface is available via the webUI
Thanks I have tried WPA3 Required and it ended up dropping all of my IoT devices off the network. What I did notice is that with WPA3 required and PMF on all of the normal devices that support WPA3 Personal connect fine but it seems that the issue is related to WPA3 on and PMF on.
I have a dedicated IoT network with WPA2 but for some hard to reach devices (ceiling mounted) and those that need local access I kept it on my main network which should be in WPA2/WPA3 Transition mode.
Adding an edit here
I contacted support via live chat (website froze a bit and was not able to sit in the queue long enough) but they downgraded the APs to 2.2k and that resolved the WPA2/3 transition mode with WPA3 on and PMF set to on. Setting PMF to off does work as well but I figured if PMF being on works leave it as is.
Interesting, thanks for the update!
Hopefully this helps out anyone else who might bump into this scenario. I imagine there’ll will be some firmware in the future to address this as well so you don’t have to keep running the prior version.
We will also be investigating how this regression occurred, with intent to fix it in a future firmware release. Thanks for your patience when dealing with the problem.
