RT-AC5300 wrong time and date when rebooted.

[Rick7C2]

I have a RT-AC5300 with merlin 380.58_0.

Everything has been working fine ever since I got it and set it up.

Power goes out and once it come back up I notice I have no Internet for devices setup to use vpn.

Vpn can't connect because the cert isn't valid yet.

I checked the log and the date is Aug 18 2019.

If I ssh into it I can run the following command and vpn will connect again but I have to run this comment everytime the router restarts.

date -s "2016-07-19 12:00"

How do I make it set the correct date automatically when it starts?

 

[RMerlin]

The router has no battery-backed clock, so it needs an Internet connection to synchronize its clock to an NTP server.

 

[Rick7C2]

The router has no battery-backed clock, so it needs an Internet connection to synchronize its clock to an NTP server.

I understand that. The problem is when the Internet is up ntp updates the date to the future and then my vpn can't connect because the cert isn't valid yet.


I just did a fresh start with 59 the date is now in the past. July 31st 2015.

I'm confused as to why this just started happening.

 

[Rick7C2]

Ok so I just setup a ntp server on my synology nas and set the ntp server on the router to my nas ip.

Rebooted router and now it updates the time and date correctly.

I can only assume the router couldn't access ntp servers from wan.

 

[RouterMan]

Anyone ever figure this issue out? I got same issue on 87U fw 380.65. Issue only affects my amazon stick and android tv box.

 

[ColinTaylor]

@RouterMan I think this issue was fixed some time ago. It was specifically related to VPN's. Are you using a VPN for those 2 devices?

 

[Xentrk]

Anyone ever figure this issue out? I got same issue on 87U fw 380.65. Issue only affects my amazon stick and android tv box.

Random thoughts...

Currently, none of the Asus routers has an RTC hardware clock. There are a couple of ways of dealing with this issue.

One solution is to install Entware on the router and install the fake-hwclock package (opkg install fake-hwclock). Fake-hwclock will save the kernel's current clock periodically (including at shutdown) to a file and restore it at boot so that the system clock keeps at least close to real time. This only works if the clock is updated correctly by the NTP client.

At other times, the NTP client cannot reach the NTP server because the DNS servers fail to resolve, which results in the router clock not being able to update. There are a few options to deal with this:

a. Enter the IP address of the NTP server directly on the Administration Menu, System Tab, Time Zone field. Note: You can browse to a specific server by selecting a region and finding a server closest to you http://support.ntp.org/bin/view/Servers/NTPPoolServers and then ping the name of the pool. This IP address will likely change due to it being a pool of servers.

b. You can leave the NTP server name as is and add a list of IP addresses for the corresponding name to the hosts.add file in /jffs/configs. For example, the Canadian server pools below were determined by pinging the server pool:

208.73.56.29 0.ca.pool.ntp.org
70.79.92.55 1.ca.pool.ntp.org
144.217.242.53 2.ca.pool.ntp.org
199.182.221.110 3.ca.pool.ntp.org