From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>,
Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: iwd@lists.linux.dev, KeithG <ys3al35l@gmail.com>,
Martin Petzold <martin.petzold@tavla.de>
Subject: Re: IWD 1.27 with brcmfmac not working for roaming
Date: Tue, 22 Oct 2024 13:44:20 -0500 [thread overview]
Message-ID: <b3b58b08-da06-4485-a980-edcc42d2453c@gmail.com> (raw)
In-Reply-To: <06e10782-0c31-4cdd-bd2b-31d1daec03d5@gmail.com>
Hi James, Arend,
> errors out as its unsupported. I don't believe there is any way for IWD to check
> if OWE is supported by the driver, and we just assume it is (Arend, maybe you
> know of a way to check this?). It appears that what you need is a new IWD option
Indeed, there's no explicit way of checking supported AKMs. The NL80211 API
isn't much help either:
/**
* DOC: OWE DH IE handling offload
*
* By setting @NL80211_EXT_FEATURE_OWE_OFFLOAD flag, drivers can indicate
* kernel/application space to avoid DH IE handling. When this flag is
* advertised, the driver/device will take care of DH IE inclusion and
* processing of peer DH IE to generate PMK.
*/
Perhaps for FullMAC, iwd should start checking for EXT_FEATURE_OWE_OFFLOAD
presence, and if not present, do not use OWE. Too bad no upstream driver
actually sets this bit. Unless... maybe OWE works with other FullMAC devices
and we'd break things for those...? Kernel folks really need to chime in here.
Regards,
-Denis
next prev parent reply other threads:[~2024-10-22 18:44 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 9:43 IWD 1.27 with brcmfmac not working for roaming Martin Petzold
2024-10-09 16:07 ` Denis Kenzior
2024-10-09 16:50 ` Arend Van Spriel
2024-10-09 17:54 ` Martin Petzold
2024-10-10 8:06 ` Martin Petzold
2024-10-12 11:06 ` Martin Petzold
2024-10-12 11:51 ` Arend van Spriel
2024-10-13 15:43 ` Martin Petzold
2024-10-30 19:19 ` Martin Petzold
2024-10-30 19:23 ` James Prestwood
2024-10-09 16:58 ` Arend Van Spriel
2024-10-10 13:20 ` Martin Petzold
2024-10-10 13:36 ` James Prestwood
2024-10-10 13:47 ` Martin Petzold
2024-10-10 13:55 ` James Prestwood
2024-10-11 8:35 ` Martin Petzold
2024-10-11 10:46 ` Martin Petzold
2024-10-12 10:59 ` Martin Petzold
2024-10-15 14:43 ` Martin Petzold
2024-10-15 15:17 ` Denis Kenzior
2024-10-15 19:13 ` Arend van Spriel
2024-10-16 2:04 ` Denis Kenzior
2024-10-16 8:32 ` Arend van Spriel
2024-10-17 10:58 ` Martin Petzold
2024-10-19 14:04 ` Martin Petzold
2024-10-19 14:41 ` Denis Kenzior
2024-10-21 13:34 ` Martin Petzold
2024-10-21 14:40 ` Arend Van Spriel
2024-10-21 14:53 ` Martin Petzold
2024-10-21 15:23 ` James Prestwood
2024-10-21 17:08 ` Arend Van Spriel
2024-10-21 17:20 ` Martin Petzold
2024-10-21 17:40 ` Denis Kenzior
2024-10-21 18:26 ` Arend van Spriel
2024-10-21 18:45 ` Martin Petzold
2024-10-21 18:48 ` Martin Petzold
2024-10-21 18:55 ` Denis Kenzior
2024-10-21 19:08 ` Jeremy Blum
2024-10-22 15:26 ` Denis Kenzior
2024-10-22 16:38 ` Jeremy Blum
2024-10-21 19:15 ` Martin Petzold
2024-10-21 19:11 ` James Prestwood
2024-10-21 20:23 ` Martin Petzold
2024-10-22 6:08 ` Arend Van Spriel
2024-10-21 22:01 ` KeithG
2024-10-21 22:10 ` Martin Petzold
2024-10-22 17:40 ` James Prestwood
2024-10-22 18:04 ` Martin Petzold
2024-10-22 18:21 ` Martin Petzold
2024-10-22 18:24 ` James Prestwood
2024-10-22 18:32 ` Martin Petzold
2024-10-22 18:44 ` Denis Kenzior [this message]
2024-10-22 18:47 ` Martin Petzold
2024-10-22 19:10 ` James Prestwood
2024-10-22 18:47 ` James Prestwood
2024-10-22 18:49 ` Martin Petzold
2024-10-22 18:52 ` Denis Kenzior
2024-10-23 12:02 ` Martin Petzold
2024-10-23 12:13 ` James Prestwood
2024-10-23 12:19 ` Martin Petzold
2024-10-23 13:22 ` James Prestwood
2024-10-23 13:34 ` Martin Petzold
2024-10-23 15:22 ` Martin Petzold
2024-10-23 15:27 ` Martin Petzold
2024-10-23 15:30 ` James Prestwood
2024-10-23 15:37 ` Martin Petzold
2024-10-23 15:28 ` James Prestwood
2024-10-23 15:11 ` Arend Van Spriel
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=b3b58b08-da06-4485-a980-edcc42d2453c@gmail.com \
--to=denkenz@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=iwd@lists.linux.dev \
--cc=martin.petzold@tavla.de \
--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