System log date, after nightly reboot

[SaintNick]

On my RT68U I've set the Merlin "Enable Reboot Scheduler" for nightly reboots at 5:30am (timezone is set). It seems sensible to me to have that.

But just after the reboot, before it does the NTP sync but after the WAN connect, the system log date is always Aug 1 02:00am (what year??). Does the device have no RTC that keeps the real time?

Is this normal?

Typical log entry:

Aug 1 02:00:28 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Aug 1 02:00:29 kernel: nf_conntrack_rtsp v0.6.21 loading
Aug 1 02:00:29 kernel: nf_nat_rtsp v0.6.21 loading
Aug 1 02:00:29 WAN Connection: WAN was restored.
Aug 1 02:00:30 rc_service: ip-up 536:notify_rc start_upnp
Aug 1 02:00:30 rc_service: waitting "stop_upnp" via ip-up ...
Aug 1 02:00:32 ntp: start NTP update
Mar 11 05:32:30 rc_service: ntp 690:notify_rc restart_upnp
Mar 11 05:32:31 rc_service: ntp 690:notify_rc restart_diskmon
Mar 11 05:32:31 disk_monitor: Finish
Mar 11 05:32:32 disk monitor: be idle
Mar 11 05:32:35 pppd[520]: System time change detected.
Mar 11 05:32:39 dnsmasq-dhcp[451]: DHCPDISCOVER(br0) xx:xx:xx:xx:xx:xx
Mar 11 05:32:39 dnsmasq-dhcp[451]: DHCPOFFER(br0) 192.168.1.112 xx:xx:xx:xx:xx:xx
Mar 11 05:32:42 dnsmasq-dhcp[451]: DHCPDISCOVER(br0) xx:xx:xx:xx:xx:xx
Mar 11 05:32:42 dnsmasq-dhcp[451]: DHCPOFFER(br0) 192.168.1.46 xx:xx:xx:xx:xx:xx
Mar 11 05:32:42 dnsmasq-dhcp[451]: DHCPREQUEST(br0) 192.168.1.112 xx:xx:xx:xx:xx:xx

 

[RMerlin]

This is normal. The router has no battery-backed clock. The clock is entirely handled in software by the OS.

 

[Blinkyz]

And the clock is syncro when this happen :

Aug 1 02:00:32 ntp: start NTP update
Mar 11 05:32:30 rc_service: ntp 690:notify_rc restart_upnp

 

[SaintNick]

This is normal. The router has no battery-backed clock. The clock is entirely handled in software by the OS.

Ah, got it.

I really like your FW by the way.