On 12/12/24 6:24 AM, KeithG wrote:
Based on a hunch that brcmfmac dbug might reveal something, I turned
it on to see what turned up. I attempted the same as before: using iwd
to connect to the WPA3 AP.
[iwd]# station wlan0 connect deskSAE
Type the network passphrase for deskSAE psk.
Passphrase: *********
[iwd]# station wlan0 show
Station: wlan0
--------------------------------------------------------------------------------
Settable Property Value
--------------------------------------------------------------------------------
Scanning no
State connecting
Connected network deskSAE
IPv4 address 169.254.203.147
the attached log shows brcmfmac debug
it always shows 'State connecting' never connected.
Is one of these what is causing it to error out:
Dec 09 18:11:06 jackrune kernel: brcmfmac: brcmf_fil_cmd_data Firmware
error: BCME_UNSUPPORTED (-23)
Dec 09 18:11:06 jackrune kernel: brcmfmac: brcmf_fil_iovar_data_get
ifidx=0, name=tdls_sta_info, len=296, err=-52
...
Dec 09 18:11:06 jackrune kernel: brcmfmac: brcmf_fil_cmd_data Firmware
error: BCME_BADADDR (-21)
Dec 09 18:11:06 jackrune kernel: brcmfmac: brcmf_fil_iovar_data_get
ifidx=0, name=sta_info, len=296, err=-52
...
Dec 09 18:33:32 jackrune kernel: ieee80211 phy0:
brcmf_cfg80211_get_station: GET STA INFO failed, -52
I do not know what BCME is.
On Mon, Dec 9, 2024 at 8:30 AM KeithG <ys3al35l@xxxxxxxxx> wrote:
I poked at this a while back and decided to try it again over the weekend.
Infineon has released a new firmware:
Firmware: BCM4345/6 wl0: Oct 28 2024 23:27:00 version 7.45.286
(be70ab3 CY) FWID 01-95efe7fa
it is not in the RPiOS release, yet, but I installed it on a Pi3B+ and
decided to give it a try. I have an AP running WPA3 personal on a
desktop in the home and can connect to it with my phone as proof that
it 'works'.
I tried to connect to it once again from the Pi while running this new
firmware. It gets closer than last time I checked, but it does not
actually negotiate a functional connection.
I tried with connman/iwd, NetworkManager/iwd and it gets close, but
still errors out. I get a number of these in the iwmon log:
Response: Get Station (0x11) len 4 38.439787
Status: Invalid exchange (52)
Can I probe this further to assist in diagnosing the cause and
potentially help with a solution?
The log is attached.
Keith, you may want to also include the iwmon logs to show the actual
netlink packets going across.
I looked at those privately and the full SAE exchange is completing
successfully via ext auth. When IWD receives the SAE confirm message it
then sends a NL80211_CMD_EXTERNAL_AUTH with a success code which then
results in the error -52 Invalid Exchange. I'm unsure exactly how
external auth is supposed to work, but if IWD needs to change something
we can do that, we just need to be told what the kernel/driver expects.
Thanks,
James
Regards,
Keith
