From: James Prestwood <prestwoj@gmail.com>
To: Jan Hendrik Farr <kernel@jfarr.cc>
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 07:10:08 -0700 [thread overview]
Message-ID: <15943a1f-0e5d-4705-b8ef-3f22fa3fe672@gmail.com> (raw)
In-Reply-To: <aB4HC8Iaa6wR5dj7@archlinux>
Hi,
On 5/9/25 6:45 AM, Jan Hendrik Farr wrote:
> On 09 06:12:23, James Prestwood wrote:
>> One thing you could try easily right off the bat would be to try forcing the
>> default SAE group in IWD's config. I've seen some APs really struggle with
>> group negotiation which is why we added the ability to set this. In your
>> network profile (/var/lib/iwd/ssid.psk) set this:
>>
>>
>> [Settings]
>> UseDefaultEccGroup=true
>>
>> And see if that helps.
> Thanks for the suggestion. It does not appear to change the behavior I'm
> seeing. Also I'm pretty convinced that the AP is not at fault here. It
> is sending the confirm, and the STA fails to ACK that and the confirm
> never shows up in iwd.
>
> Confirmed that the settings is applied using these logs from iwd:
>
> [SAE]: Using SAE H2E
> [SAE]: Using group 19
>
> I assume group 19 is the default group?
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.
Thanks,
James
>
> Best Regards
> Jan
next prev parent reply other threads:[~2025-05-09 14:10 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 [this message]
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
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=15943a1f-0e5d-4705-b8ef-3f22fa3fe672@gmail.com \
--to=prestwoj@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=kernel@jfarr.cc \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.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