Hi Johannes,
On 5/13/25 9:53 AM, Johannes Berg wrote:
On Tue, 2025-05-13 at 09:03 -0500, 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?.
[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)
I think it's expecting a confirm in response, but that was already lost
before.
Sorry, what is 'it' referring to here?
iwd sends the Commit and Confirm via CMD_AUTHENTICATE. You can see that Commit
frame from the AP was received and then iwd submits a Confirm to the kernel:
May 09 22:10:56 archlinux iwd[31729]: [SAE]: Sending Commit to 96:2a:6f:b6:d7:9f
May 09 22:10:56 archlinux iwd[31729]: [SAE]: Received frame transaction=1
status=126 state=committed
May 09 22:10:56 archlinux iwd[31729]: [SAE]: Sending Confirm to
96:2a:6f:b6:d7:9f sc=1
The kernel then transmits the Confirm three times, but attempt 2 and 3 somehow
never make it out over the air. I find that strange since they should still go
out, regardless whether the Confirm from the AP was lost initially.
Regards,
-Denis
