What's new

RT-AC66U forgets time & date during reboot

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

bheiser1

Occasional Visitor
I posted this here as I'm not sure if it's an RT-AC66U issue or a firmware issue. I'm running Asuswrt-Merlin 3.0.0.4.260.21.

I installed 3.0.0.4.260.21 last night. This morning we experienced a brief power outage of maybe 30 seconds or so. When the RT-AC66U came back up, and while studying the System Log, I noticed the Time & Date were incorrect. They indicated Dec 31 16:00. I verified under Administration->System that the Timezone is set correctly.

I checked the System Log more carefully and found this:

Dec 31 16:00:11 WAN Connection: ISP's DHCP did not function properly.

I am guessing the RT-AC66U booted more quickly than the ISP cable modem, so it wasn't able to do a time sync during boot-up.

Question: shouldn't the RT-AC66U maintain the current date & time during a power cycle, just like most other computing devices do?
 
The router (like most small integrated devices) does not have a built-in Real Time Clock. Time is maintained in software by the OS, so it needs to be re-entered on every boot.
 
The router (like most small integrated devices) does not have a built-in Real Time Clock. Time is maintained in software by the OS, so it needs to be re-entered on every boot.

OK, thanks. These days the line between "small integrated device" and "computer" is blurry :).
 
The router (like most small integrated devices) does not have a built-in Real Time Clock. Time is maintained in software by the OS, so it needs to be re-entered on every boot.
Really? It can't grab the time from a time server at boot up?
 
Really? It can't grab the time from a time server at boot up?

That's what I meant by it needing to be re-entered at boot up. For obvious reasons, it won't set its clock until the moment the WAN interface is up and running. That's why first syslog entries will show the incorrect date, until the time the NTP client has had the chance to setup the OS clock.
 
I am having the same problem. Have the newest stock firmware from Asus. Router is configured as an AP. Have tried various time servers, but time defaults to 12/31/2010. How do I get it to update the time?
 
I just upgraded my firmware; same issue. It's been at least five minutes since the reboot and despite my having a properly configured NTP server (time-b.nist.gov), I'm still at December 31, 2010. I also don't see a way to manually adjust the date.
 
I had to switch to pool.ntp.org and apply to get a date update. Not my preferred setup, but it will do for now.
 
Have another time issue. Running RT-n66u with firmware 3.0.0.4.264.2. Parental controls was not blocking Internet access to the kids Xbox. What I noticed was that whilst the time being displayed under the parental controls was the correct local time. If you executed the unix command "date" under tools --> run CMD it will show the correct local time but have gmt . Even though the time zone is set for +10. I think some where in the system the time zones are getting screwy.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Top