Update:
- Fixed cron/ini-start add/removal as it was matching for a partial which may have led to unintended removals. Matching is more explicit now.
- Fixed logging when set to 0, it was still logging
- Reduced the logging so logs aren't so polluted
- Added ability to disable fallback (Not...
I hope you understand what you're implying. The fact that I can use this command means that all asus routers are all operating illegally.
This command runs on reboot, or wireless restart, or when a new client connects that is 160mhz capable. Anytime this happens consecutively, they are...
I know for a fact it doesn't because I tested it out myself during a DFS block and it doesn't make the move under that condition. So nothing is forced in how you think it works. I included verbose logging specifically to log it's behavior.
Until you can provide proof of the behavior your are...
That's what the simple "sticky_160" was made for. But it's fine that you modified the original for yourself. Just wanted to point that out if it suits you better.
On another note, some guy that didn't understand my code came in here insulting me and making accusations about my script bypassing...
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...
As long as you included proper credit, and it looks like you have, I have no issues with it. And how is it working for you? Is it doing it's job of maintaining the 160mhz band without disconnects?
I don't think there's any tuning needed, unless you see something I don't. Any type of adjustments...
The behavior that I experience with the CAC check is this. There is a non operational period, but it's only from a fresh router boot or if from a radio restart caused by a settings change. But once it's up and running, triggering the cac check doesn't cause my 5ghz band to stop working. But...
Also another thing i didn't consider. lol. Maybe the second simpler script would be better for you.
Or you can change it to that. But that's quite long for the script to be waiting for. The purpose of the wait is for CAC check to finish so it gets the updated state for logging, and then trigger...
ooof, i did not consider a triband router. I don't have one myself and won't be able to test or figure out how a triband handles it's radios. So i made a simpler version where you can set a preferred range for your radios to stay on, but you have to create 2 files for each radio and modify 1 for...
Yeah, it's normal, it could be that there's a lot of interference on channel 36, so it picked something else. My script only forces the firmware's normal auto routine to re-establish a 160mhz connection. It will only try to get to your preferred channel.
Edit: sorry, i misread, if you're...
It's because even if your control channel is 124, the channels used still spans 100-128, and the 36 block is 36-64. So these 2 blocks are the only blocks capable of 160mhz width. So if you're on the lower block with a control channel of 52, the channels used are 36-64. Also having channel 36 or...
Sharing this script that helps to maintain and recover the 160mhz connection for wifi 6 routers . There are other scripts in this forum that do something similar, but it disconnects the clients. This script does not disconnect the clients as it uses the built in broadcom command to trigger a...
I wasn't implying FW changed the behavior. I was trying to highlight that before this new firmware, maintaining 160hz connection was impossible for me, and now that it's fixed, I'm witnessing a behavior that never happened before because it was bugged.
My control channel is 100 btw. And it's on...
I apologize for reviving an old thread, but I just want to include in here that the newest firmware fixes the 160hz channel problem for me on my rt-ax86s. I was having the same issue as other people in this thread. Get booted off from 160hz to 80hz. Or even not getting booted off but just...