From: Jan Hendrik Farr <kernel@jfarr.cc>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: James Prestwood <prestwoj@gmail.com>,
linux-wireless@vger.kernel.org,
Miri Korenblit <miriam.rachel.korenblit@intel.com>,
iwd@lists.linux.dev, Denis Kenzior <denkenz@gmail.com>
Subject: Re: wifi: iwlwifi: SAE fails when AP sends confirm before STA
Date: Thu, 15 May 2025 14:36:27 +0200 [thread overview]
Message-ID: <aCXfy0Uqx6wH32DR@archlinux> (raw)
In-Reply-To: <1a6ee5fb05b32e290fc45e66af4b7dc719f06ed8.camel@sipsolutions.net>
On 13 19:45:45, Johannes Berg wrote:
> On Tue, 2025-05-13 at 19:36 +0200, Jan Hendrik Farr wrote:
>
> > So this test doesn't proof that it would work with the order the other way
> > around. Maybe I should try making iwd sleep while generating the commit.
>
> I guess you could, right.
Just to report back on this:
I added a 20ms delay in iwd's generation of the confirm message and
everything is working as expected with your patch applied.
Connection is succesful with the following order of frames
confirmed by external capture:
1. client sends SAE commit
2. AP sends SAE commit
3. AP sends SAE confirm
4. client sends SAE confirm
Best Regards
Jan
next prev parent reply other threads:[~2025-05-15 12:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 12:24 wifi: iwlwifi: SAE fails when AP sends confirm before STA Jan Hendrik Farr
2025-05-09 13:12 ` James Prestwood
2025-05-09 13:45 ` Jan Hendrik Farr
2025-05-09 14:10 ` James Prestwood
2025-05-09 15:37 ` Jan Hendrik Farr
2025-05-09 18:39 ` Johannes Berg
2025-05-09 20:42 ` Jan Hendrik Farr
2025-05-12 20:52 ` Jan Hendrik Farr
2025-05-12 21:20 ` Jan Hendrik Farr
2025-05-13 7:35 ` Johannes Berg
2025-05-13 11:29 ` Jan Hendrik Farr
2025-05-13 11:46 ` Johannes Berg
2025-05-13 11:56 ` Jan Hendrik Farr
2025-05-13 16:33 ` Jan Hendrik Farr
2025-05-13 17:07 ` Johannes Berg
2025-05-13 17:36 ` Jan Hendrik Farr
2025-05-13 17:45 ` Johannes Berg
2025-05-15 12:36 ` Jan Hendrik Farr [this message]
2025-05-15 12:40 ` Johannes Berg
2025-05-13 14:03 ` Denis Kenzior
2025-05-13 14:19 ` Jan Hendrik Farr
2025-05-13 14:25 ` Jan Hendrik Farr
2025-05-13 14:53 ` Johannes Berg
2025-05-13 15:04 ` Denis Kenzior
2025-05-13 15:14 ` Johannes Berg
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=aCXfy0Uqx6wH32DR@archlinux \
--to=kernel@jfarr.cc \
--cc=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
--cc=prestwoj@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