From: Denis Kenzior <denkenz@gmail.com>
To: KeithG <ys3al35l@gmail.com>
Cc: iwd@lists.linux.dev, James Prestwood <prestwoj@gmail.com>
Subject: Re: [RFC PATCH v1 0/2] External Auth support
Date: Fri, 23 Aug 2024 22:21:39 -0500 [thread overview]
Message-ID: <f36d03e4-e85a-438e-adef-b6c2da0c8f72@gmail.com> (raw)
In-Reply-To: <CAG17S_NjMwU4=qn_jJzUJwPEOTT1H-SPVb7Re0P4fyPNUg=WqA@mail.gmail.com>
Hi Keith,
On 8/23/24 7:38 PM, KeithG wrote:
> Denis,
>
>
> On Fri, Aug 23, 2024 at 12:42 PM Denis Kenzior <denkenz@gmail.com> wrote:
>>
>> This series implements External Auth support on Full MAC cards that do
>> not support SAE offload. I have not been able to test this fully since
>> the brcmfmac firmware on the RPi 5 does not actually work properly.
>> Maybe some enterprising person can test it on a firmware that does work?
>>
>> Denis Kenzior (2):
>> netdev: external auth support
>> sae: Allow ability to force Group 19 / Hunt and Peck
>>
>> src/netdev.c | 258 +++++++++++++++++++++++++++++++++++++++++-----
>> src/nl80211util.c | 4 +-
>> src/sae.c | 20 ++++
>> src/sae.h | 3 +
>> src/wiphy.c | 19 ++--
>> 5 files changed, 263 insertions(+), 41 deletions(-)
>>
>> --
>> 2.45.2
>>
>>
> I was watching for this. I built iwd from git and tried it on my Pi5.
> As you said, it did not work:
>
> Aug 23 19:24:29 pi5 iwd[16297]: SAE unsupported: brcmfmac needs
> CMD_EXTERNAL_AUTH for SAE
I don't think you applied the patch correctly. You should see:
+ /* Case 3 */
+ iwd_notice(IWD_NOTICE_CONNECT_INFO,
+ "FullMAC driver: %s using SAE. Expect EXTERNAL_AUTH",
wiphy->driver_str);
> Aug 23 19:24:29 pi5 iwd[16297]: src/wiphy.c:wiphy_select_akm() Can't
> use SAE, trying WPA2
> Aug 23 19:24:32 pi5 iwd[16297]: src/agent.c:agent_disconnect() agent
> :1.471 disconnected
> Aug 23 19:24:32 pi5 iwd[16297]: src/agent.c:agent_free() agent free
> 0x5555946ddaf0
>
> I believe this is the latest firmware from Infineon for the RPi fmac cards:
> Firmware: BCM4345/6 wl0: Aug 29 2023 01:47:08 version 7.45.265
> (28bca26 CY) FWID 01-b677b91b
> Firmware: BCM43430/1 wl0: Jun 14 2023 07:27:45 version 7.45.96.s1
> (gf031a129) FWID 01-70bd2af7 es7
>
> I know there are a number of fmac cards. Does the firmware on these
> work differently to other brcmfmac cards? Do all of them use
> CMD_EXTERNAL_AUTH?
No idea. All other brcmfmac cards used SAE offload. Cypress firmware seems to
have gone with EXTERNAL_AUTH. Not sure about other full mac cards. I can see
references to EXTERNAL_AUTH in two upstream drivers:
[denkenz@archdev linux]$ grep -R "cfg80211_external_auth_request" *
drivers/net/wireless/microchip/wilc1000/hif.c:
cfg80211_external_auth_request(vif->ndev, &vif->auth,
drivers/net/wireless/quantenna/qtnfmac/event.c: ret =
cfg80211_external_auth_request(vif->netdev, &auth, GFP_KERNEL);
But the hardware seems to be unobtanium. Maybe others can report what other
solutions use EXTERNAL_AUTH? Maybe Pinephone?
Regards,
-Denis
next prev parent reply other threads:[~2024-08-24 3:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 17:41 [RFC PATCH v1 0/2] External Auth support Denis Kenzior
2024-08-23 17:41 ` [RFC PATCH v1 1/2] netdev: external auth support Denis Kenzior
2024-08-26 12:03 ` James Prestwood
2024-08-23 17:41 ` [RFC PATCH v1 2/2] sae: Allow ability to force Group 19 / Hunt and Peck Denis Kenzior
2024-08-24 0:38 ` [RFC PATCH v1 0/2] External Auth support KeithG
2024-08-24 3:21 ` Denis Kenzior [this message]
2024-08-24 16:20 ` KeithG
2024-08-24 23:32 ` KeithG
2024-08-26 15:43 ` Denis Kenzior
2024-08-26 16:54 ` Arend Van Spriel
2024-09-02 19:32 ` KeithG
2024-09-07 18:43 ` KeithG
2024-09-21 18:58 ` Yuxuan Shui
2024-09-22 3:35 ` Denis Kenzior
[not found] ` <CAG17S_NOs=rdUFsFRk4ZPsC=GER2J7nHikGEw=3AW0SBYHUEfg@mail.gmail.com>
2024-09-22 4:23 ` Denis Kenzior
2024-09-22 6:09 ` Arend Van Spriel
2024-09-22 15:36 ` KeithG
2024-09-22 16:20 ` Arend Van Spriel
2024-09-22 16:29 ` KeithG
2024-10-10 15:38 ` KeithG
2024-12-11 22:59 ` Jeremy Blum
2024-12-12 14:33 ` KeithG
2024-09-22 18:56 ` KeithG
2024-09-22 21:01 ` Denis Kenzior
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=f36d03e4-e85a-438e-adef-b6c2da0c8f72@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