From: Mathieu Chouquet-Stringer <me@mathieu.digital>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Miri Korenblit <miriam.rachel.korenblit@intel.com>,
linux-wireless@vger.kernel.org, Ilan Peer <ilan.peer@intel.com>
Subject: Re: [PATCH wireless-next v2] wifi: mac80211: Try to overcome bad HE operation in association response
Date: Tue, 21 Oct 2025 14:13:37 +0200 [thread overview]
Message-ID: <aPd48eufR6OY45__@nosurprises> (raw)
In-Reply-To: <6b0634994bc8428f8ebcf4032ff98604660c52fa.camel@sipsolutions.net>
On Mon, Oct 20, 2025 at 04:08:37PM +0200, Johannes Berg wrote:
> On Sun, 2025-10-19 at 11:52 +0300, Miri Korenblit wrote:
> > From: Ilan Peer <ilan.peer@intel.com>
> >
> > Some APs, e.g., some versions of Aruba APs,
>
> My understanding is that both Ruckus and Aruba have fixed these issues
> now (not sure how that'll roll out though), so I think we should
> probably not make this change at this point, unless we know that will be
> a significant number of APs that cannot get updated?
Well, do you have any idea when Aruba could have fixed that? I have an
AP-635 with firmware "8.13.1.0_93688 LSR" which is the latest for the
AOS 8 branch (released in September 2025) and it's clearly not fixed:
Oct 21 13:05:07 nosurprises kernel: wlp1s0: bad HE/EHT 6 GHz operation
Oct 21 13:05:07 nosurprises kernel: wlp1s0: AP 11:22:33:44:55:66 appears to change mode (expected HE, found legacy) in assoc response, disconnect
next prev parent reply other threads:[~2025-10-21 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-19 8:52 [PATCH wireless-next v2] wifi: mac80211: Try to overcome bad HE operation in association response Miri Korenblit
2025-10-20 14:08 ` Johannes Berg
2025-10-21 5:41 ` Peer, Ilan
2025-10-21 12:13 ` Mathieu Chouquet-Stringer [this message]
2025-10-21 12:19 ` Johannes Berg
2025-10-21 13:33 ` Mathieu Chouquet-Stringer
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=aPd48eufR6OY45__@nosurprises \
--to=me@mathieu.digital \
--cc=ilan.peer@intel.com \
--cc=johannes@sipsolutions.net \
--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