From: Jan Hendrik Farr <kernel@jfarr.cc>
To: Denis Kenzior <denkenz@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
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 16:25:03 +0200 [thread overview]
Message-ID: <aCNWP906m1ghPfNX@archlinux> (raw)
In-Reply-To: <aCNU2VieKTMasI6R@archlinux>
On 13 16:19:08, Jan Hendrik Farr wrote:
> On 13 09:03:54, Denis Kenzior wrote:
> > Hi Jan,
> >
> > >
> > > 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.
> > >
> >
> > What I also find interesting is that the kernel on the client side reports
> > sending the Authenticate-Confirm 3 times (according to dmesg and
> > trace2.dat), but only a single Confirm from the client is seen in the air
> > trace. I'm guessing the retransmissions (attempt 2 & 3) are lost somehow?.
>
> Yes this is weird. On my first capture I did see those additional
> confirm frames from the client (frame 4007 and 4052 in capture.pcapng).
Correction frame 879 and 940.
Those other frame number were from another capture I didn't send.
> So maybe the capture device missed them in the second capture? Although
> the RSSIs look good in the 2nd capture.
>
> >
> > [64414.164169] wlan0: send auth to 96:2a:6f:b6:d7:9f (try 2/3)
> > [64415.063575] iwlwifi 0000:00:14.3: Not associated and the session
> > protection is over already...
> > [64415.063668] wlan0: Connection to AP 96:2a:6f:b6:d7:9f lost
> > [64416.215729] wlan0: send auth to 96:2a:6f:b6:d7:9f (try 3/3)
> >
> > Regards,
> > -Denis
next prev parent reply other threads:[~2025-05-13 14:25 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
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 [this message]
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=aCNWP906m1ghPfNX@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