Configuring network time on Orbi

[agneev]

Hello!

I'm running Voxel Firmware on my RBRs.

During startup, if there's no internet connection (or DNS is down), the router is not able to set the proper time and as a result, several applications that depend on the availability of correct time, fail to start.
Fortunately, my ISP runs a time server on the gateway (that is available as long as their gateway is up).

Is there a way to change how the router obtains time? I'm not able to find any documentation on this.

 

[R. Gerrits]

Not sure if this works on RBR, but you could try:

nvram set manual_ntp_server=x.x.x.x
nvram commit

or change via router web interface via http://router-ip/NTP_debug.htm

 

[agneev]

Thanks. Is it possible to change the time over SSH?

 

[HELLO_wORLD]

Thanks. Is it possible to change the time over SSH?

I would think so!

Try date -s "27 JUN 2022 20:25:00"

 

[agneev]

I forgot to mention that I was referring to setting the time from a NTP server! @HELLO_wORLD

 

[HELLO_wORLD]

I forgot to mention that I was referring to setting the time from a NTP server! @HELLO_wORLD

Did you try what @R. Gerrits suggested with the line command nvram?

 

[R. Gerrits]

I forgot to mention that I was referring to setting the time from a NTP server! @HELLO_wORLD

stopping and starting the ntpclient would probably force it to immediately try setting the time.

i.e doing:

/etc/init.d/ntpclient restart

note for some reason on my R7800, if I restart that service, it does only stop the service and doesn't restart it.

So for me the only thing that is working is:

/etc/init.d/ntpclient stop; /etc/init.d/ntpclient start

Seems that Netgear made the mistake of giving the init-script the same name as the binary. -> During the stopping, it does a killall ntpclient -> it then kills both the ntpclient AND the ntpclient init-script -> the start part is never executed.

I suspect that the same thing will happen on an RBR.