[re-sending from correct address]
On 6/15/25 15:27, [email protected] wrote:
On 6/15/25 15:20, Bjoern A. Zeeb wrote:
On Sun, 15 Jun 2025, Bjoern A. Zeeb wrote:
On Sun, 15 Jun 2025, Bjoern A. Zeeb wrote:
On Sun, 15 Jun 2025, [email protected] wrote:
Hi,
I just replaced my AmpliFi devices with a (pair of) TP-Link BE65
and realised I'm unable to get more than 802.11a/54Mbps unless I
set the channel width on the BE65 to 80. If left at the default
160, I can't connect (and I even observe firmware crashes on the
iwlwifi).
Is this expected? I had kinda hoped I could let the others in the
household enjoy vht/160 even if I can't (yet), so this is a bit
puzzling to me.
I can provide debug info if useful, just tell me what you need.
This is my Framework 13", intel 13th gen or something like that
(not the latest Ultra).
Some info below - currently connected with vht80 and getting
>300Mbit/s.
Logs: https://anduin.net/~ltning/iwlwifi-2025-06-15-log.zip
The firmware crashes are releated to key deletion; I have a WIP
here in
my tree but it needs more work; it's all related to net80211 needng
more cleanup.
As to your VHT160 problem, there's a few things you can help:
Once you are associated on 5Ghz with VHT160 enable on the AP, do
(ideally redirect it all into a file):
- ifconfig -v wlan0 (again so we have one coherent view)
- ifconfig -v wlan0 list sta
- ifconfig -v wlan0 list scan
- ifconifg -v wlan0 list chan
- sysctl compat.linuxkpi.80211.wlan0
Then you could try:
ifconfig wlan0 down
ifconfig wlan0 -vht160
ifconfig wlan0 up
ifconfig wlan0 scan
should get you back associating with VHT80 I would hope.
Alternatively try the fllowing change (untested, just pasted in).
You could simply for testing save your /etc/regdomain.xml to a
backup file and adjust it in place. Will likely need a re-creation
of the wlan0 interface (I do not think a down/up cycle applies
it already, but ifconfig -v wlan0 list regdoman / chan would tell).
Next one, are you actually in the US or would you have to do:
country NO regdomain ETSI
on wlan interface creation?
The TP-Link are likely to announce country DE if they are a European
version. At leat I would not be surprised from what I heard and read.
Yeah I'm in NO; I'm not setting country/regdomain on interface bringup.
Is that a problem? I'll add that .. And your patches to the regdomain file.
Expect me when you see me here.. :)
Okay I now have vht/160 on both AP and iwlwifi, and iperf3 gives me
about 500Mbit/s sustained. That's not too shabby, is it?
ifconfig -v below.
Only changes made was the country/regdomain setting on ifconfig, and
your patch to regdomain.xml.
You want me to reproduce the problem without these changes, and get you
the ifconfig -v?
Thank you again!
/Eirik
/Eirik
diff --git lib/lib80211/regdomain.xml lib/lib80211/regdomain.xml
index 9116e54c31cf..c0556bacedac 100644
--- lib/lib80211/regdomain.xml
+++ lib/lib80211/regdomain.xml
@@ -146,6 +146,16 @@
<flags>IEEE80211_CHAN_HT40</flags>
<flags>IEEE80211_CHAN_VHT80</flags>
</band>
+
+ <band>
+ <freqband ref="AC160_5180_5320"/>
+ <maxpower>23</maxpower>
+ <flags>IEEE80211_CHAN_DFS</flags>
+ </band>
+ <band>
+ <freqband ref="AC160_5480_5720"/>
+ <maxpower>24</maxpower>
+ </band>
</netband>
</rd>
@@ -2339,6 +2349,20 @@
<chanwidth>80</chanwidth> <chansep>20</chansep>
<flags>IEEE80211_CHAN_A</flags>
</freqband>
+<freqband id="AC160_5180_5320">
+ <freqstart>5180</freqstart> <freqend>5320</freqend>
+ <chanwidth>160</chanwidth> <chansep>20</chansep>
+ <flags>IEEE80211_CHAN_A</flags>
+ <flags>IEEE80211_CHAN_HT40</flags>
+ <flags>IEEE80211_CHAN_VHT160</flags>
+</freqband>
+<freqband id="AC160_5480_5720">
+ <freqstart>5480</freqstart> <freqend>5720</freqend>
+ <chanwidth>160</chanwidth> <chansep>20</chansep>
+ <flags>IEEE80211_CHAN_A</flags>
+ <flags>IEEE80211_CHAN_HT40</flags>
+ <flags>IEEE80211_CHAN_VHT160</flags>
+</freqband>
<freqband id="H4_5745_5805">
<freqstart>5745</freqstart> <freqend>5805</freqend>
<chanwidth>40</chanwidth> <chansep>20</chansep>
Having written all this there's no VHT160 in regdomain.xml for FCC.
Still does not explain why you cannot get and do VHT80 when your AP
announce VHT160 but the above shoudl help us with that.
/bz
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=0
ether 8c:b8:7e:c9:89:57
inet 192.168.20.10 netmask 0xffffff00 broadcast 192.168.20.255
groups: wlan
ssid "Casa di Mau" channel 40 (5200 MHz 11a vht/160) bssid
98:ba:5f:d7:71:b3
regdomain ETSI country NO anywhere -ecm authmode WPA2/802.11i -wps
-tsn privacy ON deftxkey UNDEF
AES-CCM 2:128-bit
AES-CCM ucast:128-bit
powersavemode OFF powersavesleep 100 txpower 22 txpowmax 50.0 -dotd
rtsthreshold 2346 fragthreshold 2346 bmiss 7
11a ucast NONE mgmt 6 Mb/s mcast 6 Mb/s maxretry 6
11b ucast NONE mgmt 1 Mb/s mcast 1 Mb/s maxretry 6
11g ucast NONE mgmt 1 Mb/s mcast 1 Mb/s maxretry 6
11na ucast NONE mgmt 6 Mb/s mcast 6 Mb/s maxretry 6
11ng ucast NONE mgmt 1 Mb/s mcast 1 Mb/s maxretry 6
11ac ucast NONE mgmt 6 Mb/s mcast 6 Mb/s maxretry 6
scanvalid 60 -bgscan bgscanintvl 300 bgscanidle 250
roam:11a rssi 7dBm rate 12 Mb/s
roam:11b rssi 7dBm rate 1 Mb/s
roam:11g rssi 7dBm rate 5 Mb/s
roam:11na rssi 7dBm MCS 1
roam:11ng rssi 7dBm MCS 1
roam:11ac rssi 7dBm MCS 1
-pureg protmode CTS ht htcompat -ampdutx ampdurx ampdulimit 64k
ampdudensity NA -amsdutx amsdurx shortgi htprotmode RTSCTS -puren
-smps -rifs stbc -ldpctx ldpcrx -uapsd vht vht40 vht80 vht160
-vht80p80 wme -burst -dwds roaming MANUAL bintval 100
AC_BE cwmin 4 cwmax 10 aifs 3 txopLimit 0 -acm ack
cwmin 0 cwmax 0 aifs 0 txopLimit 0 -acm
AC_BK cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm ack
cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm
AC_VI cwmin 3 cwmax 4 aifs 2 txopLimit 94 -acm ack
cwmin 0 cwmax 0 aifs 0 txopLimit 0 -acm
AC_VO cwmin 2 cwmax 3 aifs 2 txopLimit 47 -acm ack
cwmin 0 cwmax 0 aifs 0 txopLimit 0 -acm
parent interface: iwlwifi0
media: IEEE 802.11 Wireless Ethernet VHT mode 11ac
status: associated
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
drivername: wlan0
