From: Denis Kenzior <denkenz@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Fiona Klute <fiona.klute@gmx.de>, iwd@lists.linux.dev
Subject: Re: [PATCH] Log falling back from SAE to WPA2
Date: Wed, 10 Jan 2024 10:47:09 -0600 [thread overview]
Message-ID: <44da90d8-88c4-4a92-9114-0ed875e86cc7@gmail.com> (raw)
In-Reply-To: <BD87F517-7D4C-48AA-BB73-D18C9AE6322C@holtmann.org>
Hi Marcel,
On 1/10/24 07:12, Marcel Holtmann wrote:
> Hi Denis,
>
>>> I've had connections to a WPA3-Personal only network fail with no log
>>> message from iwd, and eventually figured out to was because the driver
>>> would've required using CMD_EXTERNAL_AUTH. With the added log messages
>>> the reason becomes obvious.
>>
>> Interesting. Last time I checked only the quantenna driver used this feature and it wasn't very common. If it isn't a secret, what card / driver do you have?
>
> according to Arend on an email thread with the Apple WiFi support, he hinted that Broadcom with their devices/firmware opted for the CMD_EXTERNAL_AUTH option while the Cypress/Infineon devices with their firmware (like Raspberry Pi) are using the SAE offload feature.
Yeah I saw that as well. I don't have any Cypress devices. AFAIK Raspberry Pi
uses brcmfmac + firmware that supports SAE authentication in CMD_CONNECT, not
CMD_EXTERNAL_AUTH. Someone who knows better please correct me.
>
> So maybe it is time to implement support for CMD_EXTERNAL_AUTH.
Sure. I don't have any devices that use CMD_EXTERNAL_AUTH, however. Patches
are always welcome though.
Regards,
-Denis
next prev parent reply other threads:[~2024-01-10 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 9:59 [PATCH] Log falling back from SAE to WPA2 Fiona Klute
2024-01-10 3:33 ` Denis Kenzior
2024-01-10 11:33 ` Fiona Klute
2024-01-10 16:51 ` Denis Kenzior
2024-01-10 13:12 ` Marcel Holtmann
2024-01-10 16:47 ` Denis Kenzior [this message]
2024-01-10 17:05 ` Marcel Holtmann
2024-01-10 17:10 ` 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=44da90d8-88c4-4a92-9114-0ed875e86cc7@gmail.com \
--to=denkenz@gmail.com \
--cc=fiona.klute@gmx.de \
--cc=iwd@lists.linux.dev \
--cc=marcel@holtmann.org \
/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