Do you realize you're not clever yourself because it doesn't do anything you are implying it does.
I don't think the "auto" setting works like how everyone else thinks it works. I believe auto just means, when it starts up or reboots, it will auto find the best channel. That's it. There is no more auto after that. So lets say it starts at 36/160, gets kicked off because of dfs. Then it will go to the next best, maybe 100/160. because dfs doesn't always block the whole dfs channels. Then it gets kicked off 100/160, so it uses 149-165. Then it just stays there just like how everyone in the forums describes it's behavior.I'm well aware of why DFS exists and that regulations differ by region. The necessity of DFS isn't the point of contention.
The problem is the 'one-way' behavior in the ASUS implementation. After a DFS hit, the router frequently fails to switch back to 160MHz, leaving the status stuck at 'IDLE' forever. A robust firmware should be able to re-evaluate the environment and restore the configured bandwidth once the interference is gone, rather than requiring a manual reboot or toggle.
I understood none of this. Please try again.unfortunately even with the script which does get back to 160 withi9ng about a half hour.. the brothers trend and tp link ethernet bridges both drop out when it changes from 160 to 80..
We use essential cookies to make this site work, and optional cookies to enhance your experience.