Re: TP-Link BE65 and VHT/160

On Sun, 15 Jun 2025, ltning-freebsd-wireless@anduin.net 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.


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

-- 
Bjoern A. Zeeb                                                     r15:7