Ath10k and ath10k-ct: same config?

Installing and Using OpenWrt Network and Wireless Configuration
1

Hello,
i've started back testing CT drivers in place of plain ath10k, mainly because of the huge performance advantage on 160MHz channel width.
I'm wondering if there are different configs to be managed switching between the two drivers because what i see is really ugly and i can't believe someone is using the CT drivers with this performance level.
An example: my phone, a MI 10 Lite (2x2 80MHz) is giving this with a simple ping from the router:

451 packets transmitted, 214 packets received, 52% packet loss
round-trip min/avg/max = 1.420/7604.221/62850.020 ms

i can't even use whatsapp web with these pings..

My config is i think very basic, if not for the number of wifi (2x5GHz and 3x2.4GHz)

config wifi-device 'radio0'
        option type 'mac80211'
        option channel 'auto'
        option hwmode '11a'
        option path 'soc/1b500000.pci/pci0000:00/0000:00:00.0/0000:01:00.0'
        option htmode 'VHT160'
        option country 'IT'
        option distance '10'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option ssid 'xxx'
        option encryption 'sae-mixed'
        option key 'xxx'
        option wpa_disable_eapol_key_retries '1'
        option disassoc_low_ack '0'

config wifi-device 'radio1'
        option type 'mac80211'
        option channel 'auto'
        option hwmode '11g'
        option path 'soc/1b700000.pci/pci0001:00/0001:00:00.0/0001:01:00.0'
        option htmode 'HT40'
        option country 'IT'
        option distance '20'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option ssid 'xxx'
        option encryption 'sae-mixed'
        option key 'xxx'
        option wpa_disable_eapol_key_retries '1'
        option disassoc_low_ack '0'

config wifi-iface 'wifinet0'
        option device 'radio0'
        option mode 'ap'
        option ssid 'xxx'
        option network 'Guest'
        option encryption 'psk2'
        option key 'xxx'
        option wpa_disable_eapol_key_retries '1'
        option isolate '1'

config wifi-iface 'wifinet1'
        option device 'radio1'
        option mode 'ap'
        option ssid 'xxx'
        option network 'Guest'
        option encryption 'psk2'
        option key 'xxx'
        option isolate '1'

config wifi-iface 'wifinet4'
        option encryption 'psk2'
        option device 'radio1'
        option isolate '1'
        option network 'IOT'
        option mode 'ap'
        option wpa_disable_eapol_key_retries '1'
        option hidden '1'
        option key 'xxx'
        option ssid 'Iot'

My system: R7800 with OpenWrt SNAPSHOT r14777+74-c4ab1b7dd9 with NSS drivers, but the very same config built with normal ath10k is perfect (if not slow under 160MHz chnnel width).

Thanks

2

A bit late to reply, but yes, I have used the exact same config when switching from ath10 to ath10k-ct driver and firmware. I have a lot better user experience with old, mainline ath10k. I stay away from -ct driver and firmware. I have a mix in clients, macOS, iOS, Android, Windows 10, Chromecast 2, WiFi speakers, Shelly devices.

From what I understand BTW, the "huge performance advantage" on VHT160 is mostly theoretical. Circumstances for a stable, sustainable 160MHz bandwidth connection need to be ideal. Your client needs to support it too. I only have one that does; a MacBook Pro.