On Mon, 14 Apr 2025, Lars Tunkrans wrote:
What does:
sysctl compat.linuxkpi.80211.hw_crypto compat.linuxkpi.iwlwifi_11n_disable
compat.linuxkpi.iwlwifi_disable_11ac
show for all three?
compat.linuxkpi.80211.hw_crypto: 0
compat.linuxkpi.iwlwifi_11n_disable: 0
compat.linuxkpi.iwlwifi_disable_11ac: 1
Okay, that explains and hw_crypto is indeed disabled (avoids the TKIP
problem) and my fallback caught this disabling AMPDU-RX. Good.
Though I am still wondering why the AX201 does not freak out given it cannot
decrypt frames when doing HT. Some hoemwork for me tonight to test on
AX200 or AX210 w/ and /wo VHT enabled. I hope some others are reading
along as they may be curious to try this too.
Did you do change the hw_crypto and iwlwifi_disable_11ac value yourself
(in loader.conf.local) or did the firmware update not do the right thing?
For me it looks like:
cat /boot/loader.conf.d/iwlwifi-ax210.conf
compat.linuxkpi.80211.hw_crypto=1
compat.linuxkpi.iwlwifi_11n_disable=0
compat.linuxkpi.iwlwifi_disable_11ac=0
I am just asking in order to catch any possible general problems early.
If you've done it manually then that's all fine.
/bz
And once you are associated and have some traffic, what does
sysctl compat.linuxkpi.80211.wlan0
say?
# sysctl sysctl compat.linuxkpi.80211.wlan0
compat.linuxkpi.80211.wlan0.dump_stas:
lsta 0xfffff8005bb37000 sta 0xfffff8005bb371c0 added_to_drv 1
nl80211_sta_info (valid fields)
0x00004503<BEACON_RX,BEACON_SIGNAL_AVG,SIGNAL_AVG,RX_BITRATE,TX_BITRATE>
connected_time 0 inactive_time 0
rx_bytes 0 rx_packets 0 rx_dropped_misc 0
rx_duration 0 rx_beacon 76120 rx_beacon_signal_avg -34
tx_bytes 0 tx_packets 0 tx_failed 0
tx_duration 0 tx_retries 0
signal 0 signal_avg -24 ack_signal 0 avg_ack_signal 0
generation 0 assoc_req_ies_len 0 chains 0
rxrate: flags 5<MCS,SGI> bw 3(40) legacy 0 kbit/s mcs 15 nss 0
he_dcm 0 he_gi 0 he_ru_alloc 0 eht_gi 0
txrate: flags 5<MCS,SGI> bw 3(40) legacy 0 kbit/s mcs 7 nss 1
he_dcm 0 he_gi 0 he_ru_alloc 0 eht_gi 0
Great!
Lots of joy,
Bjoern
--
Bjoern A. Zeeb r15:7
