ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 21 Mar 2024 05:05:34 +0100	[thread overview]
Message-ID: <a1231edb5e12283f6f5fbbf9e0ba7af8@ericswpark.com> (raw)
In-Reply-To: <87r0ghf4rw.fsf@kernel.org>

Resending as I forgot to CC the mailing list, sorry! I've added some 
more
info since the last email.

On 2024-03-11 11:21, Kalle Valo wrote:
> But with modern CPUs I would have still expected software encryption to
> be faster than 20 Mbps so the chances are it can be something else as
> well.

I just checked and the laptop has an i5-5200U, but I'm not sure if it's 
the
bottleneck. I ran a speedtest while monitoring the load and the CPU 
usage
never went past 20-50% or so.

> That's a user space decision and depends on what connection manager you
> use.

That's the weird part, for some reason I can't get it to force-connect 
via
WPA2-PSK. I've tried KDE's network configuration and `nmtui`, but when I
connect to the network it seems like it tries to negotiate with WPA2-PSK 
first
and then "upgrades" to WPA3-SAE. Or at least that's how it appears in 
the
network details dropdown if I click on the chevron next to the Wi-Fi 
SSID.

I've also used a different USB Wi-Fi card, and that one correctly limits 
to
WPA2 if I set it in the connection manager. (And I've verified it 
connects
through WPA3 as well if I set it so.) So something in the ath10k driver 
won't
actually let me limit it to WPA2.

I'd like to figure out if there's a way of debugging this further, or 
simply
working around the limitation for now by disabling WPA3 at the driver 
level.
Please let me know if there's anything I can try on my end.

- Eric


  reply	other threads:[~2024-03-21  4:05 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 [this message]
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
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=a1231edb5e12283f6f5fbbf9e0ba7af8@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