[Solved] Chrony NTS broken?

Archive > 21.7 Legacy Series

(1/1)

Mr.Goodcat:
Hi,

I just noticed that chrony doesn't seem to work with NTS anymore. Once I enable this setting, no synchronization takes places which results in the "tracking" tab showing the date as 1970...
Even when only one NTS server (e.g. cloudfare) is used nothing happens.
As it worked flawlessly before, this might have crept in during the last update?
Does anyone else experience such behaviour?

Thanks!

gpb:
It's working fine here...NTS via cloudflare.

--- Quote ---
Name/IP address Mode KeyID Type KLen Last Atmp NAK Cook CLen
=========================================================================
time.cloudflare.com NTS 4 15 256 13d 0 0 8 100

--- End quote ---

What sort of issue are you seeing? Anything in logs? You have ntpd disabled?

abulafia:
Works fine for me (latest opnsense version); these are the public NTS servers known to me:

--- Quote ---Name/IP address Mode KeyID Type KLen Last Atmp NAK Cook CLen
=========================================================================
time.cloudflare.com NTS 3 15 256 4d 0 0 8 100
sth1.nts.netnod.se NTS 1 15 256 8d 0 0 8 100
sth2.nts.netnod.se NTS 1 15 256 10d 0 0 8 100
ptbtime1.ptb.de NTS 1 15 256 10d 0 0 8 100
ptbtime2.ptb.de NTS 1 15 256 10d 0 0 8 100
ptbtime3.ptb.de NTS 1 15 256 10d 0 0 8 100
nts1.time.nl NTS 1 15 256 10d 0 0 8 104
nts.ntp.se NTS 1 15 256 10d 0 0 8 100
ntp1.glypnod.com NTS 19 15 256 447m 0 0 3 104
ntp2.glypnod.com NTS 1 15 256 7d 0 0 8 104
ntpmon.dcs1.biz NTS 1 15 256 7d 0 0 8 104

--- End quote ---

Mr.Goodcat:
Thank you all for the feedback!
After playing around and looking at logs this issue is now solved: a reboot finally fixed it :P
It's the little things that get you... ;D

Navigation

[0] Message Index

Go to full version