AX200 (iwlwifi) and 160MHz width Channels?

Hi,

I'm trying to get a 160Mhz AC connection between a Netgear XR500 (based on Ansuels repo) and a AX200 Intel Wifi card running under Linux (Fedora & iwlwifi driver).

But according to the OpenWrt stats the connection is still 80Mhz "only" (rx, tx stucks at 40Mhz channel width)

Station 9c:fc:e8:dd:5b:49 (on wlan0)
	inactive time:	70 ms
	rx bytes:	371572
	rx packets:	2414
	tx bytes:	3052622
	tx packets:	3222
	tx retries:	0
	tx failed:	0
	rx drop misc:	0
	signal:  	-53 [-59, -56, -56, -58] dBm
	signal avg:	-52 [-59, -55, -56, -58] dBm
	tx bitrate:	360.0 MBit/s VHT-MCS 9 40MHz VHT-NSS 2
	tx duration:	4551547 us
	rx bitrate:	780.0 MBit/s VHT-MCS 8 80MHz short GI VHT-NSS 2
	rx duration:	154876 us
	airtime weight: 256
	authorized:	yes
	authenticated:	yes
	associated:	yes
	preamble:	long
	WMM/WME:	yes
	MFP:		yes
	TDLS peer:	no
	DTIM period:	2
	beacon interval:100
	short slot time:yes
	connected time:	100 seconds
	associated at [boottime]:	667419.197s
	associated at:	18446725627465128437 ms
	current time:	18446744073541782965 ms


According to the client, the connection is 160Mhz (at least for rx):
iw dev wlp3s0 link


SSID: XR500
freq: 5180
RX: 2933424 bytes (3200 packets)
TX: 318959 bytes (2091 packets)
signal: -42 dBm
rx bitrate: 1560.0 MBit/s VHT-MCS 9 160MHz VHT-NSS 2
tx bitrate: 780.0 MBit/s VHT-MCS 8 80MHz short GI VHT-NSS 2

bss flags:	short-slot-time
dtim period:	2
beacon int:	100

The iperf3 speed whatsoever is the same as a regular 80Mhz connection :frowning:

My questions is: is the Intel AX200 capable of 160Mhz width channels with the linux iwlwifi driver?

BTW: the 160Mhz mode works with Windows 10 and the AX200 and the same XR500 router.

And the same OpenWrt or you are using the stock firmware for this test?

Yes the same OpenWrt

I did a few more iperf3 test (iperf3 -c ip-address -P5 -b 1000M -u) and now i believe the reported bitrates on the router are wrong.

I get a rx bitrate 800 - 900 mbit/s and tx bitrate around 500mbit/s (on the client).

I created an issue for the ath10k_ct driver /firmware: https://github.com/greearb/ath10k-ct/issues/150