From: Eric Park <me@ericswpark.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: ath10k@lists.infradead.org
Subject: Re: QCA6174 showing terrible performance when connecting via WPA3-SAE
Date: Mon, 29 Apr 2024 15:26:28 +0200 [thread overview]
Message-ID: <483bc3022513fd0740b5342b59ce94ad@ericswpark.com> (raw)
In-Reply-To: <87o79sfjlf.fsf@kernel.org>
On 2024-04-29 14:18, Kalle Valo wrote:
> If you run wpa_supplicant -dddt (or similar) you get a lot of debug
> output, I'm sure it will also include the cipher.
Good to know, thank you. Will keep this in mind the next time I'm
troubleshooting WPA-levels.
> Very good that you found this is 802.11w related. What is the make and
> model of your router?
I'm using a GL-AXT1800 (Slate AX) router from GL.iNet.
> I don't know how well ath10k 802.11w support is tested and then it was
> last tested. Do you happen to have other Access Points supporting
> 802.11w? That might help to pinpoint if 802.11w is completely broken in
> ath10k or if this is an interoperability issue with ath10k and your AP.
I unfortunately do not have access to any other routers I can modify
settings on at the moment (or any other APs to connect to, to test on,
really...) I may have some routers to test it on next week, but I'm
unsure whether they allow me to modify the 802.11w settings as they're
mostly proprietary and don't run something like OpenWRT.
Do you know if it'll be possible to add a flag to enable/disable 802.11w
on ath10k's side? Even if it turns out to be an interoperability issue,
it will most likely be useful to have the ability to switch it off for
APs that don't play nice. Especially for public APs and proprietary
APs where the end-user can't realistically turn off 802.11w for the
entire network.
- Eric
next prev parent reply other threads:[~2024-04-29 13:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 15:08 QCA6174 showing terrible performance when connecting via WPA3-SAE Eric Park
2024-03-11 10:21 ` Kalle Valo
2024-03-21 4:05 ` Eric Park
2024-04-25 9:51 ` Kalle Valo
2024-04-28 3:04 ` Eric Park
2024-04-29 12:18 ` Kalle Valo
2024-04-29 13:26 ` Eric Park [this message]
2024-04-29 16:32 ` Kalle Valo
2024-04-29 17:53 ` Eric Park
2024-05-03 21:52 ` Eric Park
2024-05-06 9:04 ` Kalle Valo
2024-05-07 1:37 ` Eric Park
2024-05-14 15:27 ` Kalle Valo
2024-05-14 22:23 ` Eric Park
2024-05-15 8:04 ` Kalle Valo
2024-05-17 8:43 ` Eric Park
2024-05-17 9:41 ` Kalle Valo
2024-04-29 18:23 ` James Prestwood
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=483bc3022513fd0740b5342b59ce94ad@ericswpark.com \
--to=me@ericswpark.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@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