You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
WPA3 SAE is not supported on Pi 400 (BCM43456) #7610
WPA3-Personal SAE Wi-Fi standard doesn't seem to be supported by the firmware/driver of Raspberry Pi 400.
The 400 has BCM43456 module (brcm/brcmfmac43456-sdio firmware), compared to Pi 3B/4/5, which use SYM43455 (cypress/cyfmac43455-sdio firmware).
So far there were issues here and on forum, firmware and code updates from Infineon for 43455 only as far as I could see.
Raspberry Pi 400 on the latest official OS version does not report anything related to SAE in iw phy, as well as wpa_cli get_capability key_mgmt.
Connecting to WPA3-Personal Only networks on Raspberry Pi 400 does not work.
Steps to reproduce the behaviour
Try to connect to WPA3-Personal Only network using Rasberry Pi 400
The updated firmware from New WiFi clm_blob file for BCM43456 (Pi 400) forum topic does not support SAE either: although that firmware (unlike the one in the Raspberry distro) has extsae feature as seen with strings, it is not supported:
(*) This appears to be different from extsae, as used by Synaptics, which isn't supported here yet, although both appear as extsae in the firmware version. It's necessary to run strings on the firmware and grep for sae_ext to be sure. And obviously, both are different to the in-firmware WPA3 support provided by the sae feature, but which only works with iwd.
The linked firmware has only extsae, not sae_ext. The stock firmware has none.
It looks like the culprit is RPi-Distro/firmware-nonfree@348a967. IMO pretty bad nonsense to me (sorry for the wording, but need to be honest here). (Re)move /usr/lib/modprobe.d/rpi-brcmfmac.conf, reboot, retry. If you face stability issues, a confirmation of in raspberrypi/firmware#1973 would be good. Then testing to narrow down the instability to one of the 4 disabled features. Disabling SAE (WPA3) all together cannot be a solution.
This is not applicable to 43456, as the bundled firmware doesn't have SAE support at all.
I've also tested the updated firmware from the linked forum topic on Orange Pi 4a, mainline 7.1 kernel, Debian 13, it has Ampak AP6256 module with the same BCM43456 chip. Does not work, because the kernel driver can't handle that special extsae command.
Oh good point. However, this config file is shipped to all RPi models. If SAE really needs to be actively disabled on 43430 (Zero 2W) to mitigate stability issues (which has not been verified in the related issue), then in a different way, conditionally via udev rules for affected models/chips only or such. But this is OOT here then, aside of the fact that, if any new firmware is tested regarding WPA3, one must not forget to (re)move/override/mask /usr/lib/modprobe.d/rpi-brcmfmac.conf first.
Are you saying that you get WPA3 working on a Pi 400 without this change, or is this just ill-informed comment? My understanding is that the 0x80000 flag disables the modem's internal handling of the SAE four way handshake. The flag's state makes no difference to Pi 5/43455 connecting to a Netgear AP configured to demand WPA3 - it works either way.
Yeah sorry, a premature conclusion, SAE still works on an RPi 5 (BCM43455) with the module parameters applied. But I'd still vote for narrowing down the stability issues to 1 of the 4 features, if possible, and/or apply it more selectively for affected boards. Sadly, I have no Zero 2W to replicate and test myself.
Pull request #7762 adds three commits which together should allow both Zero 2 variants to connect to WPA3 APs. It should not need the brcmfmac feature_disable flags, but they should be harmless.
For it also to work on Pi 400 you will need an updated Pi 400 firmware. Synaptics are in the process of making an official release, but in the meantime you can test a trial build of the 43456 firmware: https://drive.google.com/file/d/1c6JX--IXy5RzhfFEB5nKQpxe1Z3A9six/view?usp=sharing
Install the firmware by downloading it to the 400 and running:
You can install a trial kernel build by running sudo rpi-update pulls/7762, but read the caveats first.
N.B. This is intended to be run with wpasupplicant 2:2.10-24+rpt3, but install the trial kernel before updating wpasupplicant if you aren't running +rpt3 already.
Activity
ValdikSS commentedon Sep 7, 2026
The updated firmware from New WiFi clm_blob file for BCM43456 (Pi 400) forum topic does not support SAE either: although that firmware (unlike the one in the Raspberry distro) has
extsaefeature as seen withstrings, it is not supported:#5945
The linked firmware has only
extsae, notsae_ext. The stock firmware has none.MichaIng commentedon Sep 7, 2026
It looks like the culprit is RPi-Distro/firmware-nonfree@348a967. IMO pretty bad nonsense to me (sorry for the wording, but need to be honest here). (Re)move
/usr/lib/modprobe.d/rpi-brcmfmac.conf, reboot, retry. If you face stability issues, a confirmation of in raspberrypi/firmware#1973 would be good. Then testing to narrow down the instability to one of the 4 disabled features. Disabling SAE (WPA3) all together cannot be a solution.ValdikSS commentedon Sep 7, 2026
This is not applicable to 43456, as the bundled firmware doesn't have SAE support at all.
I've also tested the updated firmware from the linked forum topic on Orange Pi 4a, mainline 7.1 kernel, Debian 13, it has Ampak AP6256 module with the same BCM43456 chip. Does not work, because the kernel driver can't handle that special extsae command.
MichaIng commentedon Sep 7, 2026
Oh good point. However, this config file is shipped to all RPi models. If SAE really needs to be actively disabled on 43430 (Zero 2W) to mitigate stability issues (which has not been verified in the related issue), then in a different way, conditionally via udev rules for affected models/chips only or such. But this is OOT here then, aside of the fact that, if any new firmware is tested regarding WPA3, one must not forget to (re)move/override/mask
/usr/lib/modprobe.d/rpi-brcmfmac.conffirst.ValdikSS commentedon Sep 8, 2026
@pelwell is it something Infineon could address, or is it for Broadcom?
pelwell commentedon Sep 10, 2026
Neither - it's a Synaptics part. I've asked the question.
pelwell commentedon Sep 10, 2026
Are you saying that you get WPA3 working on a Pi 400 without this change, or is this just ill-informed comment? My understanding is that the 0x80000 flag disables the modem's internal handling of the SAE four way handshake. The flag's state makes no difference to Pi 5/43455 connecting to a Netgear AP configured to demand WPA3 - it works either way.
MichaIng commentedon Sep 10, 2026
Yeah sorry, a premature conclusion, SAE still works on an RPi 5 (BCM43455) with the module parameters applied. But I'd still vote for narrowing down the stability issues to 1 of the 4 features, if possible, and/or apply it more selectively for affected boards. Sadly, I have no Zero 2W to replicate and test myself.
pelwell commentedon Nov 16, 2026
Pull request #7762 adds three commits which together should allow both Zero 2 variants to connect to WPA3 APs. It should not need the brcmfmac feature_disable flags, but they should be harmless.
For it also to work on Pi 400 you will need an updated Pi 400 firmware. Synaptics are in the process of making an official release, but in the meantime you can test a trial build of the 43456 firmware: https://drive.google.com/file/d/1c6JX--IXy5RzhfFEB5nKQpxe1Z3A9six/view?usp=sharing
Install the firmware by downloading it to the 400 and running:
and revert with:
You can install a trial kernel build by running
sudo rpi-update pulls/7762, but read the caveats first.N.B. This is intended to be run with wpasupplicant 2:2.10-24+rpt3, but install the trial kernel before updating wpasupplicant if you aren't running
+rpt3already.