uh oh, lol. I have no clue what happened then. I thought it didn't auto-upgrade too, I lost internet, logged into to router and found that it was updated.Not supposed to be possible for auto-upgrade of Merlin firmware.
uh oh, lol. I have no clue what happened then. I thought it didn't auto-upgrade too, I lost internet, logged into to router and found that it was updated.Not supposed to be possible for auto-upgrade of Merlin firmware.
I didn't realized my auto-upgrade was enabled, and haven't had any problems in the past at 6 months.
I think this is something new for .14 for rt-ac68u.
It appears many rt-ac68u have began doing this for the first time in their life since .14 releases.
Does this version have a fix for Tri-Band on router AC5300 as the original works better.
When I want to go to 2.4Ghz from 5Ghz than it doesn't work. The Signal doesn't reach, example the mobilephones goes to 4G network instead of wifi 2.4Ghz as the signal doesn't reach when switching from 5Ghz to 2.4Ghz.
The original Asus firmware doesn't have this issue.
Will try the latest but what can be wrong if there is issues?Wifi code is closed source, and therefore 100% identical to Asus's 3.0.0.4.384_81219.
Will try the latest but what can be wrong if there is issues?
There is no auto-upgrade capabilities in my firmware.
There is no auto-upgrade capabilities in my firmware.
winner winner, chicken dinnerUpdated my R7000 to Vortex 384.14, unfortunately no client detection with cfe 1.3.0.7.
- flashed it from 384.13 to 384.14, rebooted without luck
- factory reset with reload of my config without luck
- finally reflashed back to 384.13 and client detection remains to work
My 68U did not blink either this time. Downloaded the update .zip manually after receiving a notification email from my router (Diversion).I noticed my RT-AC68P router is not blinking anymore letting me know there is a firmware update.. was it backed out?
I am still on 384.13.
There is no auto-upgrade capabilities in my firmware.
Static but not empty (manually assigned server1 and server2).have you ipv6 dns servers automatic or static (empty)?
I also disable and enable IPv6 but no luck...On reboot, IPv6 (native) is dead. Disable IPv6 (apply), then re enable (apply) fixes it.
When setting up a router running an older firmware version the setup wizard asks if the user wants to upgrade to available 384.14. At least this is what happens on RT-AC86U.
on the initial setup page the router asks me that 384.14 is available and you should update. I clicked okay and the spinning wheel just keeps on spinning.
try to keep asutomatic dns, should help I guess and doesn't break DoT
Thank you for confirming that Asus were still making AC87U's in 2018, hopefully we can expect few more years of support from them, though it probably won't get the 384 codebase due to it having a separate Quantenna chipset for the 5 Ghz radio.
Hopefully Asus can continue providing RMerlin with the binary blobs needed to support it. And not being on the 384 codebase so far has been a good thing as the router has been more stable than the 384 models without missing any of the features you need.
Welcome to the forum! Take a look at some of the popular threads for ways to expand the functionality of your router.
It's an old long-standing issue, widely discussed throughout the forums already.
That is up to Asus, and outside of my control.
Just an RT-AX88U.
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!