public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Hendrik Farr <kernel@jfarr.cc>
To: James Prestwood <prestwoj@gmail.com>
Cc: 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: Fri, 9 May 2025 17:37:22 +0200	[thread overview]
Message-ID: <aB4hMsBfyawYatoj@archlinux> (raw)
In-Reply-To: <15943a1f-0e5d-4705-b8ef-3f22fa3fe672@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 678 bytes --]

> Yep that's it. At least we can take that out of the equation.
> 
> And yes, in the PCAP I do see the confirm's being sent but no ACK. We'll
> have to wait for an iwlwifi person to chime in. I suspect we'll need some
> iwlwifi debugging enabled to see if the confirm was received at some level
> in the driver and dropped, or never received at all.

I have captured and attached a trace collected using:

trace-cmd record -e iwlwifi -e mac80211 -e cfg80211 -e iwlwifi_msg

At the start of the trace iwd is shutdown. I start it and force it to
connect to a 6ghz network. There should be at least two failed
connections.

> 
> Thanks,
> 
> James
> 
> > 
> > Best Regards
> > Jan

[-- Attachment #2: trace.dat --]
[-- Type: application/octet-stream, Size: 3158988 bytes --]

  reply	other threads:[~2025-05-09 15:37 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 [this message]
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
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=aB4hMsBfyawYatoj@archlinux \
    --to=kernel@jfarr.cc \
    --cc=iwd@lists.linux.dev \
    --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