Opal - Wrong Router Time on Boot

[Happi]

So, after various small niggling problems, I reverted to a clean install of 3.206 (in place of the Beta release). This seems to have fixed most of the “niggles” but…I found an old problem resurfaced.

I turn my router off overnight. When I boot in the morning I do not have internet (USB modem).
I diagnosed it back to this problem:

OpenVPN Client Disconnect and Wrong Router Time

My OpenVPN client disconnects every few days or somtimes even more frequesntly with a TLS error and I notice that the router time is a few minutes behind actual time. Even if I re-select a time zone or re-sync the time to the computer via the setting in the GL–iNet web interface, the time remains off by a few minutes. It seems wrong router time is known to cause TLS errors in OpenVPN. If I unplug and replug the router, then the client reconnects and I see that the time is exactly correct again. …

Bascially, the router time fails overnight and doesn’t “sync to browser” when booted in the morning (was 13 hours off this morning). This prevents my Wiregard client connecting automatically.
Interestingly, a second reboot (whether cold or hot) seems to fix the issue.

[Happi]

Last night I turned off Wireguard and the Kill Switch before unplugging the router.
This morning I plugged in and the router time was incorrect and the modem didn’t connect.
A second reboot fixed the problem.

[alzhao]

Wireguard, should not have any problem with router’s time. I am sure about this. The problem must be something else.

When the router is off, its time is stored. So next time it boot, it will use that time, until it connect to the Internet and sync with time server.

[s.okamoto]

if router’s time is incorrect, wireguard can connect but no packets will flow.
moreover if DNS server is being accessed via a tunnel, NTP server name cannot resolve and time cannot be adjusted.
a simple solution is to configure NTP server with IP ADDRESS.