From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: coldolt <andypalmadi@gmail.com>
Subject: [RFC PATCH 0/2] wifi: detect stuck ECSA
Date: Thu, 18 Jan 2024 12:16:26 +0100 [thread overview]
Message-ID: <20240118111941.549593-4-johannes@sipsolutions.net> (raw)
This is a pretty specific workaround for what's going on with the Asus
AP codolt has (btw, could you actually mention the specific model and
maybe firmware version, just so we have a record of it?). But I've also
asked around internally and while we had encountered this with Windows
(too bad we didn't check before, sorry!), no other case is known.
Could you try these patches? I didn't (yet) attempt to reproduce this
scenario.
Sending as RFC to see if this addresses the issue - I will probably
refine the logic a bit, e.g. if there's no quiet and the channel is
the same, we might still want to connect? Not sure entirely.
johannes
next reply other threads:[~2024-01-18 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 11:16 Johannes Berg [this message]
2024-01-18 11:16 ` [RFC PATCH 1/2] wifi: cfg80211: detect stuck ECSA element in probe resp Johannes Berg
2024-01-18 11:16 ` [RFC PATCH 2/2] wifi: mac80211: improve CSA/ECSA connection refusal Johannes Berg
2024-01-20 14:56 ` [RFC PATCH 0/2] wifi: detect stuck ECSA coldolt
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=20240118111941.549593-4-johannes@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=andypalmadi@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).