From: Denis Kenzior <denkenz@gmail.com>
To: KeithG <ys3al35l@gmail.com>
Cc: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [Request] iwd to support brcmfmac 'SAE with AUTHENTICATE'
Date: Sun, 11 Aug 2024 14:38:52 -0500 [thread overview]
Message-ID: <de951e97-547f-4c14-841c-267f64b0020b@gmail.com> (raw)
In-Reply-To: <CAG17S_P_MO4_BZYTCp4WDkJ_q4j=0s_s3azCOWrsvqmLD0ravw@mail.gmail.com>
Hi Keith,
> Supported extended features:
> * [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
> * [ DFS_OFFLOAD ]: DFS offload
>
<snip>
>
> The pcap is uploaded to my gdrive:
> https://drive.google.com/file/d/1vIuje60MGFPklcXtSNMi9-IOlV_6sBJ8/view?usp=drivesdk
What is the PCAP supposed to show? There's no Connection attempt in there.
>
> Hopefully, this helps to get started.
>
Anyway, I was curious and snooped on wpa_s from git trying to connect to an
iPhone 12 Personal Hotspot (Maximum Compatibility option off, so it uses SAE).
Not a pretty sight. Firmware fails with errno=-52, Invalid exchange. Has
anyone from RPI team actually tested this firmware before pushing it out?
I also tried the old firmware with SAE_OFFLOAD bits, and that doesn't work with
wpa_s or iwd either.
Until someone sends me a iwmon trace showing CMD_EXTERNAL_AUTH exchange working
on an WPA3-Personal Only network, I remain skeptical that any of the Cypress
firmwares actually work.
Regards,
-Denis
next prev parent reply other threads:[~2024-08-11 19:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-04 17:08 [Request] iwd to support brcmfmac 'SAE with AUTHENTICATE' KeithG
2024-08-05 12:34 ` James Prestwood
2024-08-05 13:56 ` Denis Kenzior
2024-08-11 14:35 ` KeithG
2024-08-11 19:38 ` Denis Kenzior [this message]
2024-08-12 1:19 ` KeithG
2024-08-12 11:36 ` James Prestwood
2024-08-17 20:49 ` KeithG
2024-08-17 22:03 ` KeithG
2024-08-17 23:36 ` KeithG
2024-08-30 16:37 ` Any recent wifi certifications with IWD? Bryce Johnson
2024-09-04 18:59 ` James Prestwood
2024-09-05 14:26 ` Bryce Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=de951e97-547f-4c14-841c-267f64b0020b@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=prestwoj@gmail.com \
--cc=ys3al35l@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox