Recent content by user114514

This article was written by a complete idiot. Any AP with multiple radios inherently supports STR. EMLMR is not the same thing as STR, and EMLMR has not shipped in WiFi 7. The real problem is there are no other STA chips except WCN785x that support HBS STR, and WiFi 7 APs violate the negotiation...

Just occupy all three independent 320MHz channels and the additional 160MHz channel. Those who don't understand the math fail to realize that for the same distance, 320MHz can achieve the same throughput with lower SNR requirements and a lower duty cycle. Even if your WAN is only 1Gbps, 320MHz...

see https://learn.microsoft.com/en-us/windows/win32/nativewifi/dual-sta-query-config By default, Windows connects only on the primary STA interface. Windows will connect on the secondary STA interface only if all of the following conditions are met: The driver indicates support for secondary...

You don't need MLO to get 1.7Gbps. in fact, even a 6 year old AX200 can get 1.7Gbps in a non-lab environment. real MLO can easily get over 3Gbps.

Because of the Shannon-Hartley theorem. As long as BSSs don't overlap, feel free to increase transmit power to maximize DL speed within regulatory limits. In the US, 5GHz is large enough to accommodate three non-overlapping 160MHz BSSs or seven non-overlapping 80MHz BSSs. Modern STAs are...

AFAIK BCM4912/4916 devices rarely encounter these issues. You can try changing the control channel to 36-48 to see if it can still stay at 160MHz. Even ax86u typically stays at 160MHz when the control channel is within the DFS channels (52-64, 100-144).

Additionally, there is an extremely rare scenario that could also cause an unexpected exit from 160MHz: DFS radar misdetection. I'm not sure if anyone has actually encountered this. Generally, modern WiFi chips don't experience this because they typically have precise characteristics of radar...

These issues exist on all routers with Broadcom chipsets, but occur with higher probability on specific models like ax86u. I recommend all users disable TDCS to avoid such problems. The core idea behind TDCS is that 160MHz should only be used when necessary to improve performance and...

wl2_bw_switch_160 for tri-band models. The specific value depends on your 5GHz radio. For ax86u pro, just set wl1_bw_switch_160. TDCS is a software feature that doesn't require hardware support. wlx_bw_switch_160=0 just completely disables TDCS without any other side effects. To summarize the...

There's no need for pointless speculation, as these 160MHz issues aren't caused by DFS. The real problem is TDCS, and simply disabling it will fix the problems. I advise certain individuals to refrain from giving self-righteous, meaningless opinions without understanding the root cause, as this...

nvram set wl1_bw_switch_160=0 nvram set wl2_bw_switch_160=0 nvram commit

https://rog.asus.com/us/networking/rog-rapture-gt-ax6000-eva-edition-model/ My previous answer was deleted by moderator. TDCS drops to 80MHz when there are no 160MHz devices in the BSS (including low-power states), and then reverts to 160MHz when a 160MHz device rejoins. This idiotic mechanism...

You can disable Smart Connect and manually enter the same SSID for each band. Generally speaking, devices from the ax era generally have reasonable active roaming decisions and do not require active steering by AP. If none of your devices require 2.4 GHz, then same SSID for 5 GHz and 6 GHz is...

Then it's not a problem. 6GHz will be inferior to 5GHz at longer distances due to lower transmit power and higher attenuation, especially for devices like iPhone 16 that don't support 320MHz, even at medium distances. that's the Shannon limit.

You still haven't answered my question: iPhone 16 on 5GHz