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 13:09:38 +0200 [thread overview]
Message-ID: <ee6a0a4e735b3e97fbe96a25d2af59ee0f663fc9.camel@sipsolutions.net> (raw)
In-Reply-To: <CACM6vn6UXfSXw2WpYvzF+ODPGHw-LtsBMgtvc6n7s9iF9eaS6Q@mail.gmail.com>
On Thu, 2026-04-16 at 07:03 -0400, Benson Bear wrote:
>
> (Sadly I think I might have an idea -- it's partly my fault. The
> mac80211 module was disabling all HT and above because it
> felt it could not meet the BCS criteria laid down by the AP.
> Many people have thought these criteria were way too onerous.
> So I first had very low speeds because of that. No HT even.
> I applied a patch to the module that ignored these requirements
> and got back to a high connection speed, and HE or VHT
> enabled, and got back a little of the lost speed. Clearly very
> kludgy but seems a legitimate response to what the patch
> author called "aggressive basic MCS rates". But it may
> have opened up the room for misunderstandings. I have my
> speed back in practice, but I wonder what the "correct" way
> of fixing this would be -- without the kludgy module patch).
I think what you're referring to here might be this?
https://lore.kernel.org/linux-wireless/99Mv9QEceyPrQhSP52MtAVmz0_kWJmzqotJjD9YW6LGLqk-AZloAueUyHCURilFkuqOh6Ecv8i2KKdSE1ujP3AnbU5QEouVisT1w_V3xdfc=@r26.me/
johannes
next prev parent reply other threads:[~2026-04-16 11:09 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 [this message]
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
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=ee6a0a4e735b3e97fbe96a25d2af59ee0f663fc9.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