Wireless Daemon for Linux
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, KeithG <ys3al35l@gmail.com>,
	iwd@lists.linux.dev
Subject: Re: [Request] iwd to support brcmfmac 'SAE with AUTHENTICATE'
Date: Mon, 5 Aug 2024 08:56:48 -0500	[thread overview]
Message-ID: <b0ef10a2-c30b-4b6c-8370-66f9e0ace7b1@gmail.com> (raw)
In-Reply-To: <ef38aa12-634e-4870-888c-219c961f301c@gmail.com>

Hi James,

>> ...
>>   Device supports SAE with AUTHENTICATE command
> 
> So this is interesting... IWD does not expect a fullmac card to support 
> AUTHENTICATE but if this is the direction brcmfmac is going I guess we can 

That's because iw output is misleading.  This driver uses CMD_EXTERNAL_AUTH to 
tell iwd/wpa_s to transfer SAE authenticate frames via CMD_FRAME (similar to how 
iwd does FT-Auth frames).

Unfortunately the kernel never dedicated an actual capability bit to tell 
userspace that CMD_EXTERNAL_AUTH is being used.  They just reuse the generic 
FEATURE_SAE.

> support it. This is such a mess though and brcmfmac just needs to decide what 
> they are doing. This just makes things even more complicated as we now have 3 
> (?) ways to do SAE just on brcmfmac.

Its still just 2, SAE_OFFLOAD and EXTERNAL_AUTH

Regards,
-Denis

  reply	other threads:[~2024-08-05 13:56 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 [this message]
2024-08-11 14:35     ` KeithG
2024-08-11 19:38       ` Denis Kenzior
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=b0ef10a2-c30b-4b6c-8370-66f9e0ace7b1@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