WiFi not working on Raspberry Pi 4 with WPA3 5 GHz/6GHz only-Network #6677
Comments
|
Looks like WPA3 does not use "WPA-PSK", but "SAE". And it looks like WPA3 is even mandatory for 6 GHz, probably Wi-Fi 6 in general. Although Wi-Fi 6 with 2.4 GHz seems to work with WPA2 as well. But probably with 5 GHz and 6 GHz is not not work without WPA3: #6636 Can you try to add/replace the related settings from the post you linked to |
|
That's all correct (WPA3 mandatory, requires SAE). I did try the settings, doesn't work. I guess it requires the patch/fix I've linked. |
|
Ah right, they are talking about possibly needed kernel patches. So generally to test, after setting up Wi-Fi via
|
|
FYI, I entered the configuration without any luck, still DHCP discover timeout. Adding |
|
Milestone applied just to keep easier track of the RPi kernel upstream issue. |
|
So if you're like me and you found this thread to be one of the first results for a Google search for "Raspberry WPA3", and you think you can just use the |
|
Jep, as thomaswitt stated. Actually just a few days ago, a new firmware package has been released which others stated adds WPA3 support for RPi 3B+, RPi 4 and 5:
It is on APT servers as well since two days. What I am not sure about is whether this requires an up-to-date driver, hence the new set of (Bookworm) firmware/kernel packages. For DietPi users this would mean to do the migration: #6676 |
|
Any updates on this? Unable to connect to a WiFi 6 access point with WPA2/WPA3 mixed mode :( |
|
You could test whether it works with the new kernel/firmware package stack: #6676 |
|
Same problem here:
dmesg | grep brcmfmac
brcmfmac: F1 signature read @0x18000000=0x15264345
brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Apr 15 2021 03:03:20 version 7.45.234 (4ca95bb CY) FWID 01-996384e2
strings /lib/firmware/cypress/cyfmac43455-sdio-standard.bin | grep --color=auto ext_sae || echo NO ext_sae
NO ext_sae
strings /lib/firmware/cypress/cyfmac43455-sdio-standard.bin | tail -n2 | grep --color=auto sae || echo "NO sae"
43455c0-roml/43455_sdio-pno-aoe-pktfilter-pktctx-wfds-mfp-dfsradar-wowlpf-idsup-idauth-noclminc-clm_min-obss-obssdump-swdiv-gtkoe-roamprof-txbf-ve-sae-dpp-sr-okc-bpd Version: 7.45.234 (4ca95bb CY) CRC: 212e223d Date: Thu 2021-04-15 03:06:00 PDT Ucode Ver: 1043.2161 FWID 01-996384e2
iw phy | grep -i sae
* [ SAE_OFFLOAD ]: SAE offload support
* [ SAE_OFFLOAD_AP ]: AP mode SAE authentication offload supportTested config: Also tested without proto=RSN |
|
Please read through the thread. It is a know limitation with the RPi kernel. See my above post with a link to migrate to a new RPi kernel/firmware stack, which should fix it, according to this PR: raspberrypi/linux#5945 If you have a spare SD card, you can also test it first with a fresh image. The |
Thanks, I did read the thread, but reading #6677 (comment) I mistakenly thought that being on the lastest Dietpi version of Bookworm would imply using the lastest stack (probably because English is not my native language, sorry). I will try DietPi_RPi234-ARMv8-Bookworm.img.xz on a new SD and report back 👍 |
|
The 2nd part of the post is relevant, where I state that a new driver (hence a new kernel) may be required. Obviously, the new firmware alone (meaning the |
|
According to this comment, it still does not work: raspberrypi/linux#4718 (comment) Btw, it does work with any WPA3-capable USB WiFi adapter, doesn't it? Just to assure there is no userland part missing, but really only support in the Broadcom WiFi kernel driver and firmware. |
|
I have updated my #6677 (comment) with all the info I have found relevant. After a few hours reading github issues I've found enough people with working solutions, I thinks this comment summarize the situation:
I will try iwd to see if raspberrypi/linux#4718 (comment) is having another issue. If this doesn't work I will try to use the new firmware with wpa_supplicant without SAE_OFFLOAD. But all this is bit out of my expertise. |
Sorry, I'm possibly being dumb here, but did you actually find a solution? Or is the conclusion just 'it doesn't work yet'? |
|
This one fixed it for me. Super quick fix. |
Which one did you mean exactly? Installing the new kernel only, without updating any firmware? Interesting, I didn't know about |
I just installed that WiFi driver in the first message. Although, it didn't actually fix it for me, but it got me closer. My Pi5 now connects to the WPA3 network, and shows up as connected on the router, but will get disconnected by the router for inactivity after a couple of minutes. |
|
So you updated the firmware but not the kernel (driver). This is then probably the missing part: #6676 In case this works, we could create a small package which replaces this particular firmware binary on RPi systems with the new kernel stack. |
Required Information
Steps to reproduce
I run the latest dietpi on a RPi4. Network Connectivity via Ethernet works fine.
I want to activate the WiFi interface as well, so I did via dietpi-config. Activated, SSID and Password is correctly set (and double checked via wpa_passphrase command). The network I am connecting to is a WPA3 5/6 GHz Network only. When restarting the interface, I constantly get timeouts on the DHCP Discovery:
I tried a different network which also offer 2.4 GHZ with no probems.
Expected behaviour
WiFi should connect to WPA3 Networks.
Actual behaviour
WiFi doesn't connect to WPA3 Networks.
Extra details
iwlist wlan0 scan | grep ESSID, I see the whole Wifi Network list including the ESSID I want to connect to.The text was updated successfully, but these errors were encountered: