Those are old firmware versions. You should try 380.59 before trying or reporting anything else.
380.58 is known to be unstable for many (and for many different reasons).
Upgrade to 380.59 as suggested with a reset to factory defaults and a minimal and manual configuration of your router to secure it and connect to your ISP.
http://www.snbforums.com/threads/no...l-and-manual-configuration.27115/#post-205573
Also note that the latest official versions coming from Asus will feature more and more locked down firmware (with the possibility of not being able to use any other third party firmware (like RMerlin's, for example) after you have flashed to that firmware (even once).
Buyer beware has now become firmware updater, beware.![]()
What? Is that true? That's the first time I'm reading this. I'm aware of the discussion regarding the new FCC rules and I remember that people were scared because of this, but the way I understood it was that there was no real concern and that only the Wi-Fi specific parts would be completely separated from the open source parts of the code :-o I've seen no info saying that we'll actually be prevented from flashing 3rd-party firmwares altogether now until I read your post :-oAlso note that the latest official versions coming from Asus will feature more and more locked down firmware (with the possibility of not being able to use any other third party firmware (like RMerlin's, for example) after you have flashed to that firmware (even once).
Buyer beware has now become firmware updater, beware.![]()
(from the second link)Please don't be afraid, when we finish the new method to protect the RF parameter, we will release firmware verification method to developers and you can still using the web GUI to change to 3rd party firmware.
The firmware verification method will be modified in next formal firmware release.
This firmware will not accept older firmware and router's with this new firmware cannot downgrade to older version.
So it will not accept 3rd party firmware for a short time.
Please don't be afraid, when we finish the new method to protect the RF parameter, we will release firmware verification method to developers and you can still using the web GUI to change to 3rd party firmware.
Parts of it. And RMerlin will have no choice but to follow their lead in the very near future (possibly the next RMerlin release).
http://www.snbforums.com/threads/asus-rt-ac68u-firmware-3-0-0-4-380-3264.32506/
http://www.snbforums.com/threads/asus-firmware-will-change-the-verification-method.32357/
I see you updated your first post too. If you did a proper reset to factory defaults and you have issues, it may be a hardware fault and it's time for a new router.
But I would try a reset to factory defaults once more (after reflashing the same 380.59 firmware too).
http://www.snbforums.com/threads/no...l-and-manual-configuration.27115/#post-205573
Because I have an 87U and am having no difficulty (still 59B2 though). Had no difficulty with 58 either.How can this be a hardware failure? I think it's a bug in the firmware.
When booting it will display a start time (mine is July1) until ntp delivers a current time.Why is there August 1 in my log???
This morning (17 May) it didn't work maybe someone can check the log?
When booting it will display a start time (mine is July1) until ntp delivers a current time.
On May 17 at 7:09 it rebooted. Did you do that manually? It had been up for 4 days.
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!