Have a couple old G IP Cams that are rock solid on this firmware. 2.4 GHz fixed channel 1, 6 or 11 at 20 MHz. Disable Airtime Fairness and Universal Beamforming. Other 2.4 GHz devices, Ecobee, Roku and printer all stay connected, too.Is it just me, had issues with my 2.4GHz security cameras disconnecting all the time, went back to Version 3.0.0.4.386.41535 from 2020/12/30 and all good again.
Hmmm.
My 2.4Ghz cameras and other IOT devices have been reluctant to use the RT-AX86Us on this version. They prefer my RT-AX88U which has a much weaker signal. I did a full reset last night and some wouldn't connect at all until I disabled Universal Beamforming although this hasn't always been necessary.Is it just me, had issues with my 2.4GHz security cameras disconnecting all the time, went back to Version 3.0.0.4.386.41535 from 2020/12/30 and all good again.
Hmmm.
Let me try that, thank you.If you have wifi issues, try unplugging the power of the router for a few seconds to properly reset the radio in it. I recently started having multiple disconnections from my Roomba following a firmware update, a reboot didn't help, however after actually unplugging the router power, the issue completely disappeared.
Now power cycled...hope that will fix it...If you have wifi issues, try unplugging the power of the router for a few seconds to properly reset the radio in it. I recently started having multiple disconnections from my Roomba following a firmware update, a reboot didn't help, however after actually unplugging the router power, the issue completely disappeared.
On this version my IOT devices definitely won't connect to 2.4Ghz unless I disable Universal Beamforming (which I know is good practice anyway) but even then I find that they are reluctant to use the RT-AX86U when other nodes are available with weaker signals. This is the case even after RMerlin's power off advice.
However, if I use Asuswrt-Merlin 386.2 Beta 3 which is also based on this 42095 GPL build I don't suffer the same issues. Very strange.
Do you have same issue like me? What I did cause 2.4 and 5 Ghz had same SID name, I blocked macadresses on 5 Ghz, may it helps for you.Wondering if they fixed Google Home and other 2.4 devices being dropped.
Had to go back to 384 release.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!