Two OpenWrt service releases

Posted Dec 12, 2020 18:03 UTC (Sat) by johill (subscriber, #25196)
In reply to: Two OpenWrt service releases by mangix
Parent article: Two OpenWrt service releases

However, very few frames are actually management frames, so the GP post doesn't really make any sense.

Not sure what's going on there, but MFP *shouldn't* cause data traffic slowdowns, unless somehow MFP is badly implemented in the driver and causes everything to fall back to software crypto? I'd have to check.

Two OpenWrt service releases

Posted Dec 14, 2020 17:17 UTC (Mon) by hmh (subscriber, #3838) [Link] (1 responses)

I am not sure the slowdown is caused router-side, it could be something in the *client* that gets triggered by the 802.11w support, for all I know...

ATM I do have two different routers here I can test OpenWRT on ( Archer C7v4(BR), Archer C6v2(US) ), but only one client that can handle fast enough connections over WiFi that the issue shows up. The routers are running recent openwrt-19.07 snapshot (ath79), default firmware for their models (I think it is the -ct firmware).

The client is running the standard Debian 10 kernel (up-to-date), the hardware is a Dell laptop, with a QCA6174 radio and the standard firmware:
ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1028:0310
ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0
ath10k_pci 0000:02:00.0: firmware ver RM.4.4.1.c2-00057-QCARMSWP-1 api 6 features wowlan,ignore-otp,no-4addr-pad,raw-mode crc32 e061250a
ath10k_pci 0000:02:00.0: htt-ver 3.56 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1

I did notice slowdowns on *both* bands (2.4GHz and 5GHz), but it is far more visible in 5GHz, since it reaches far higher throughput.

Two OpenWrt service releases

Posted Dec 15, 2020 22:00 UTC (Tue) by johill (subscriber, #25196) [Link]

Yeah, I'm beginning to think that somehow it tickles your client into doing software crypto entirely ... but it doesn't look that way in the ath10k code? But I'm far from familiar with this particular driver, even if I maintain the wireless stack :-) You should probably post to linux-wireless@vger.kernel.org with this.