From: Kalle Valo <kvalo@kernel.org>
To: Eric Park <me@ericswpark.com>
Cc: ath10k@lists.infradead.org
Subject: Re: QCA6174 showing terrible performance when connecting via WPA3-SAE
Date: Mon, 06 May 2024 12:04:38 +0300 [thread overview]
Message-ID: <87jzk7mhuh.fsf@kernel.org> (raw)
In-Reply-To: <b9a07fe0-b50a-4d70-a7f3-3b82d224d90f@ericswpark.com> (Eric Park's message of "Fri, 3 May 2024 17:52:57 -0400")
Eric Park <me@ericswpark.com> writes:
> I had the opportunity to test the connection with another router (Asus
> RT-AX56U) today and it negotiated with WPA2-PSK, PMF default on, on 5
> GHz. I ran a speedtest and got 20 Mbps both up/down.
>
> I then ran the `nmcli connection modify <SSID2> wifi-sec.pmf 1` and
> after reconnecting it connected with PMF disabled. (I think the reason
> it worked this time is because of WPA2-PSK -- there's probably some
> way of making it work with WPA3 APs and `nmcli` but I don't know the
> correct commands to give in order to make that happen.) The speedtest
> increased to 100 Mbps both up/down, and that's the WAN limit -- I'm
> pretty sure if I ran a iperf3 inside the LAN it would've been much
> faster.
>
> I think the PMF implementation in ath10k, at least for the QCA6174
> chip, has some issues as it has consistently worsened performance on
> two out of two sample APs I've tested it on.
Yeah, clearly something is wrong somewhere but difficult to say where
exactly. I got a private comment that one possible cause might be that
the first ADDBA frame is not decrypted correctly and the aggregation is
not working. Broken aggregation would explain the decrease in
throughput.
This is of course just a theory. I don't know how familiar you are with
802.11 protocols but that is something to investigate. Unfortunately I
have very little time for ath10k nowadays.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-05-06 9:04 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
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 [this message]
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=87jzk7mhuh.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=me@ericswpark.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