From: Johannes Berg <johannes@sipsolutions.net>
To: Benson Bear <benson.bear@gmail.com>,
Pablo MARTIN-GOMEZ <pablomg@eskapa.be>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Wi-Fi speeds degrade from 600Mps to 30Mps while using WPA2 security, but not on open network, shortly after ISP firmware upgrade.
Date: Thu, 16 Apr 2026 15:58:14 +0200 [thread overview]
Message-ID: <49f35f3dfe84c564585bd3bc014a6931a7789624.camel@sipsolutions.net> (raw)
In-Reply-To: <CACM6vn7Dau9cX4tUCVQZmEpRmd7JiNtALUfR_fFARMbR_VZ_7A@mail.gmail.com>
On Thu, 2026-04-16 at 08:34 -0400, Benson Bear wrote:
>
> Thanks again. Sadly it looks like linux (the wpa_supplicant) is
> in the wrong here, just reasoning about it. I assume the AP
> always offers the option. It doesn't get a rejection before it
> even makes an offer. So that means when it offered it when
> PMF was not disabled in the client, the client must have
> accepted the offer. Because we know in the other case,
> when PMF *is* disabled, that it works fine, which must mean
> the AP received correctly a rejection of the offer. So had
> the client sent a rejection in the first case, like it did in the
> second, there is no reason the AP would not have accepted
> that rejection. So the client must have sent an acceptance.
Doesn't mean they both negotiated the use correctly, or even encrypted
the frames correctly. Could even be that they both agreed on PMF, but
then the AP sent unencrypted AddBA request (or response, depending on
the direction) and the client dropped it, or any other weird things.
> Not iron clad, because maybe the AP is just plain crazy.
My bet would be on that but we'd have to see a sniffer capture. But in
general, we definitely know that PMF works with Linux/wpa_s and WiFi7
requires it, etc.
johannes
next prev parent reply other threads:[~2026-04-16 13:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 8:47 Wi-Fi speeds degrade from 600Mps to 30Mps while using WPA2 security, but not on open network, shortly after ISP firmware upgrade Benson Bear
2026-04-16 9:39 ` Pablo MARTIN-GOMEZ
2026-04-16 11:03 ` Benson Bear
2026-04-16 11:09 ` Johannes Berg
2026-04-16 11:28 ` Benson Bear
2026-04-16 11:47 ` Pablo MARTIN-GOMEZ
2026-04-16 12:34 ` Benson Bear
2026-04-16 13:58 ` Johannes Berg [this message]
2026-04-16 14:03 ` Pablo MARTIN-GOMEZ
2026-04-17 13:24 ` Benson Bear
2026-04-18 12:04 ` Benson Bear
2026-04-18 13:45 ` Benson Bear
2026-04-20 9:35 ` Pablo MARTIN-GOMEZ
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=49f35f3dfe84c564585bd3bc014a6931a7789624.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=benson.bear@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pablomg@eskapa.be \
/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