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
Subject: Re: wifi: iwlwifi: SAE fails when AP sends confirm before STA
Date: Tue, 13 May 2025 13:56:05 +0200 [thread overview]
Message-ID: <aCMzVUJlLfuhupzm@archlinux> (raw)
In-Reply-To: <e1b26ee842bc60cfa939874f467a03531871807e.camel@sipsolutions.net>
On 13 13:46:51, Johannes Berg wrote:
> On Tue, 2025-05-13 at 13:29 +0200, Jan Hendrik Farr wrote:
> >
> > There is a an SAE confirm sent by the AP. It's frame 170 in
> > capture2.pcapng. It's also retried a number of times after that.
>
> Oops, yes, I didn't catch the different seqno and thought it was all
> retries of a single frame.
>
> > There is however no ACK from the client in response to it and it also never
> > shows up in iwd.
>
> Right. Clearly this is because we actually leave the channel when we get
> the response to the auth frame.
>
> I guess most cases we have the client much faster than the AP, so this
> might never be an issue. I guess here you were saying the client wasn't
> all that fast in responding.
>
> In fact the AP seems to take ~17.1ms from one frame to the other, and
> the client ~20.4ms, though the client has some propagation delay through
> the software stack too.
>
> I don't think this is really the right fix, but it might help:
> https://p.sipsolutions.net/e852565303ad878b.txt
Thanks for the help! I'll test the patch this evening.
>
> johannes
next prev parent reply other threads:[~2025-05-13 11:56 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 [this message]
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
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=aCMzVUJlLfuhupzm@archlinux \
--to=kernel@jfarr.cc \
--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