As some of you found out the unpleasant way: WPA3 is broken with the last RoPieee release.
I’ve spending most part of the weekend of diving into kernels, firmware updates (there is firmware of the WiFi chipset involved) and figuring out why is it broken now.
It seems this is a combination of things: so far I’ve figured out for the Pi 3 (the 4 and 5 are next on my list) why it doesn’t work: we needed to switch to the new kernel for the Pi 5, but it seems that WPA3 is broken for the Pi 3. Which is very strange oc, but simply swapping out kernels solves the problem. Although simply… not entirely. Because I also upgraded the firmware blobs for the wifi chipset(s) and guess what… it breaks WPA 3 support on the chipset side of things as well.
So… I can ‘fix’ it (lab conditions) by going back to the previous kernel for the Pi 3 and ignore the updated chipset firmware.
This is all far from ideal (to put it mildly), but fortunately RoPieee’s architecture supports different kernels and different software components for the various hardware platforms. It only brings more work for me
This does not mean you can expect a fix tonight. I still need to verify the Pi 4 and 5, because right now I don’t trust any of this.
If there’s someone bitten by this issue and has a Pi 3, and is up for an experiment, just let me know. I’m planning on releasing a beta build for the Pi 3 asap (probably tomorrow) and it would be great if we can gather some test evidence that stuff is working now.
Harry, thank you for the investigative work. I don’t use WPA3 but I hope someone will be willing to help test for the others that have experienced the problem.
As I have said many times before, I am deeply appreciative of RoPieee. I just donated enough for two beverages of your choice and quality, as a small thank you from Vancouver.
Hey Harry, I don’t use WPA3 (I avoid wireless as much as possible) but from what I can tell all my infrastructure supports WPA3 and I have both pi3 and pi4’s I can test with. It’ll take me a little time, longer than overnight, but I’ll see if I can switch things over to WPA3 and be a guinea pig.
@spockfish
Hi Harry,
My WiFi is on WPA2, so I don’t have any issue with my RPI 3A+ and RPI 3B+
I see that I can set my WiFi in WAP2/WPA3. So as a test I have changed my WiFi from WPA2 to WPA2/WPA3, and then the WiFi-connection is lost on my RPIs.
I have put the WiFi back to only WPA2, and all the RPIs are back in service.
I have put those RPIs in “Beta”, so when you have pushed a candidate, I can test it (although I am not a WiFi-specialist!).
Thank you for all your hard work.
Kind regards, Frank.
@spockfish
Hi Harry
Have hit this problem because my router (sky max) can only be set to WP3A personal transition.
I just have ropieee on one device (4b) but am happy to test as and when. Have set as beta updates as this is still part of a wider project.
Also have made a we donation to the cause for all your work and in appreciation of the huge frustrations you must feel when things go awry…
@spockfish
Hi Harry
Just applied the beta. Initially it gave an error but after rebooting with Ethernet attached and then reapplying the Wi-Fi settings and a further reboot all seems well. If I see any issues I’ll let you know.
I have sent feedback in case it is useful.
c3fd257ce1a234c3
