Time desync can happen, for more than one reason. We should have a way to force NTP synchronization by hand if that happens.
Description
Description
Details
Details
- Version
- -
- Is it a breaking change?
- Perfectly compatible
Related Objects
Related Objects
- Mentioned In
- rVYOSONEX768df77b078a: Merge pull request #2265 from vyos/mergify/bp/sagitta/pr-2262
rVYOSONEX7009ef08a006: T5582: make "force ntp synchronisation" command VRF aware
rVYOSONEX9db289a02892: op mode: T5582: Add 'force ntp synchronization'
rVYOSONEX8e5931c94a4e: op mode: T5582: Add 'force ntp synchronization'
rVYOSONEXc27b0ca1816b: T5582: make "force ntp synchronisation" command VRF aware
rVYOSONEX1fb9dbe0990a: Merge pull request #2262 from dmbaturin/T5582-ntp-force
Event Timeline
Comment Actions
Something like this console command but more handy in op-mode?
sudo ntpdate -u -b ntp.se
For example adding "ntp" as syntax to "set date"?
set date ntp
The above would then use the ntp-servers configured by "set service ntp", note however that the above must also be vrf-aware (that is reuse whatever vrf-config exists for "set service ntp").