Router goes non-responsive after 3 days

[Harry Carplay]

Brand new RT-AC68U running Merlin 380.57.

Router works great for 3 days and then goes non-responsive. I can't ping it from other hard wired computer on LAN (ping 192.168.1.1). Have to cycle power supply to restore life. Are there any logs I can look at to try and diagnose the problem please?

 

[Rhyacaus]

Had the exact same issue, worked fine for 3 or 4 days, then woke up one morning, Wifi was not connected on phone, all lights were on router but could not ping or get to web interface... Hard rebooted to get it back up (took a few tries), It also kept rebooting or freezing every 10min or so after the first event.... Returned DOA.

Have just got new one back today so guess will see in 3 days time... Was on original firmware that came with router before updating on day1 (3.0.0.4.376_3602) and then updated to latest ASUS version. When this started to happen I changed to Merlin, did not fix the issue...

Hope it was hardware after all that and not a firmware issue that broke it? :-/

 

[BreakingDad]

Did you clear Nvram by ssh / telnet "mtd-erase -d nvram" "nvram commit" "reboot" after updating firmware? Then re enter settings manually ? 376 to latest Merlin is quite a leap.

 

[martinr]

You could try System Log >General Log (bottom left on the weg gui), but if it's some sudden glitch, I doubt there will be anything, but you never know. And you should be able to see the previous shutdown periods.

You could look at Administration>Performance Tuning > CPU Temp. On the RT-AC68U, a temp of around 81C is normal and they happily run at that temp without a glitch, If yours is significantly higher then that might be the cause, but one would expect it to build up quicker than 3 days. Again, no point in speculating until you've looked. And you might need to keep checking just in case there's a nearby heat source that alters the ambient temp at different times of the day.

 

[Rhyacaus]

Did you clear Nvram by ssh / telnet "mtd-erase -d nvram" "nvram commit" "reboot" after updating firmware? Then re enter settings manually ? 376 to latest Merlin is quite a leap.

Yea a did a clear of the nvram (holding the WPS button on side for "x" seconds). and a full reset to clear all setting. Did this after the update to latest ASUS pre latest Merlin and also after Merlin...

 

[Harry Carplay]

Did you clear Nvram by ssh / telnet "mtd-erase -d nvram" "nvram commit" "reboot" after updating firmware? Then re enter settings manually ? 376 to latest Merlin is quite a leap.

Procedure I followed:
1) Purchased new router from shop
2) Flashed with Merlin 380.57 (don't think I noted OEM firmware revision down before this)
3) Went to (Merlin) Web GUI and selected Reset to Factory Defaults
4) Setup router and used.

Tried to follow instructions here:
https://github.com/RMerl/asuswrt-merlin/wiki/Installation

 

[Harry Carplay]

You could try System Log >General Log (bottom left on the weg gui), but if it's some sudden glitch, I doubt there will be anything, but you never know. And you should be able to see the previous shutdown periods.

You could look at Administration>Performance Tuning > CPU Temp. On the RT-AC68U, a temp of around 81C is normal and they happily run at that temp without a glitch, If yours is significantly higher then that might be the cause, but one would expect it to build up quicker than 3 days. Again, no point in speculating until you've looked. And you might need to keep checking just in case there's a nearby heat source that alters the ambient temp at different times of the day.

System log is not revealing anything during post-mortem analysis, hence my question about any further logging.. Any logging which survive once power is pulled?

The Web GUI is not accessible. The lights on the router are on, and flash randomly. Even ping requests between device on the RT-AC68U switch are not getting through.

 

[muffintastic]

Why don't you revert back to 378.56_2 as this is VERY stable for me.

I have tried the latest CFW but I don't think it's stable enough as per the people saying the WiFi drivers are broken etc.

 

[BreakingDad]

You could try using the firmware restoration / rescue process

Download chosen firmware

Download the restoration utility https://www.asus.com/uk/Networking/RTAC68U/HelpDesk_Download/

Put the router into rescue mode and Run restoration utility: http://www.manualslib.com/manual/594320/Asus-Rt-Ac68u.html?page=86

When internets back up download Putty http://www.putty.org/

Enable Telnet on router, log into router with putty (select telnet and ip 192.168.1.1)

Enter "mtd-erase -d nvram"
Enter "nvram commit"
Enter "reboot"

Log back in with gui, turn off telnet, enter usual settings manually.

Also see Merlins guide on Nvram http://www.snbforums.com/threads/faq-nvram-and-factory-default-reset.22822/

 

[Harry Carplay]

I've downgraded firmware to 378.56_2 on muffins advice. Shall see how that performs over the next few days.

I have a synology NAS with syslog facility. I've not looked in detail, but would enabling the logging in ASUS firmware to syslog server provide some evidence on what's happening. There appears to be many settings it could take..