[chrony-users] Chrony on Asus router - no reduction of offset |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-users] Chrony on Asus router - no reduction of offset
- From: Torsten Wolf <torsten.wolf@xxxxxxx>
- Date: Sat, 10 Jun 2023 20:09:04 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.com; s=s31663417; t=1686420546; x=1687025346; i=torsten.wolf@xxxxxxx; bh=YYmDVjc64ULbxShriuJHSvATbCXe/QbuRozFBy/sS9k=; h=X-UI-Sender-Class:To:From:Subject:Date; b=f8JOLxAr2yLnO8JmRlCBpCGN7RSDUvLanj1/aIZVGFDqiQ6ThfVsJP+py0IXCLNNKbc8yCG fLfqQjZN//W+fjc2t7Wl6THTiwh37DceaG2BVh8KL1EEfWtxUzrerJIDAAsKEPoOHsI1gb12j 2zeANK/17Y2fKTZ+ZWOSnQ4hEX5StFt5ULKsDaSy5PLq2w2DWyDJl3fo6VuNb0Y7wUO3ZJVkK X3JGAW61NDcLCeTw4lwuDN3fTyKf2A66ikHFHA8ExCStNYSL4NmevFudR8l9BlkOYA7mWPG+W PRbIBz4KJEmVNpgZNQx4CWzU7EjXiWEOaYU/dvSMYAsS/MYeEL1g==
- Ui-outboundreport: notjunk:1;M01:P0:cTQO62wgXps=;1l81owe+0UosPbOz506j+3LXP3o DR5xM7yw8GGs/lgpF7HdTBmdgfH1FalL9Rls/S4VjdNnZYsrKc/1EI0k4hcUoKZJQ6x3XU4+e L2JKY1NDJfFAv29jj5r0vHREIgaUeA4orb44rkjjwwA+LRMiPaoBqtOa3BmpIBUqy6rvnttcv as4J/hH8l4j7ufG76Op/0YXi5JeL9b3rWHABMROExL8UzoygaoCeL4TY3HGcQD3nxvM/Iq+A7 gb/Soia5VtktIHzTdcRrw7upDd1AR40Hoe8fXk/YA/67UKyxITizE+IbIrQGUs3cWIML5gbOp aKf+APQAXVXRtOfsduWCmf1/O73Il7o/NIXh3LiJ3qNGBms065MgGttPz4HfhdB1bDPSpnu5V 4Ctykbr2HGFr/r1uL9CImAu/ZvUF1xJv8yxjUhaoueJAqo1o5LbkVVka3sNUy0upRBeEibBRa /y22J+x9oV0v+UwpuqYX9dYDLSVdBaFLGadeiKWD8jFgeDTZ1dONWTwpw3Lfa4KPKMXoo+jlz yuBcC12/w47Qohp4vfxZdzgkey22loa4nhwYpB73HSI/6YJdaS6SZUaVvixpYnkgwaAnenUGA YN6XmzafpI40Or3wIxoag0JLZUEWTsUMp8Pq2ftOXrnWj/TLkkCtDQcn6elFUVPsFh457ckx4 1AXol+L4sdB/vpXGewqpqoqKoNLs6cTT2clKuiV28dJD0AtdsWuVfB+a07nhj27FusLS5rNm1 K4d0pPsoppyfohuqIKxvZa0f3lSloJ1I1csRL3K5QC5uJTfp+zGzOBODWL3OMBaKbNfhkoqba 7Jln1061UAUhS/cUFmtaET/2q2MWp0pB1KYXuEwJ5ghn1njALOd4NL4bj1IvcsB1NIJKh0eZO 79ZbUuTOxSvebBCu+9wsNZ3GGDPUo6oxpNQ1ZpeI5wbMjROCAKuV3g/GiLcH4wAH5TYC0J+Oh Xxp9nQ==
Hi,
I am running chrony 4.3 on an Asus RT-AX86U Pro router which acts as
server for my local network. No matter if I use
a) remote ntp servers
b) a network client Raspberry Pi with GPS module as sole server
c) that Raspberry synchronised to the same publich servers as in a) as
sole server
the offset is always in the order of -160ms. I also tried makestep but
it quickly wanders off to the usual offset. Shouldn't the offset be
corrected towards zero? At least that is what's happening on the raspi
for b) and c). Here is the config and some data. I played a bit with
maxupdateskew and tried to poll the raspi more frequently for b) and c)
but that did not reduce the offset. I also don't seem to have a loop as
in my previous problem report...
chrony.conf (for scenario c))
# raspi
server 192.168.1.105 iburst
server zeit.fu-berlin.de iburst noselect
server ptbtime1.ptb.de iburst noselect
server ptbtime2.ptb.de iburst noselect
server ptbtime3.ptb.de iburst noselect
server times.tubit.tu-berlin.de iburst noselect
maxupdateskew 15
driftfile /opt/var/lib/chrony/drift
dumponexit
dumpdir /opt/var/lib/chrony
pidfile /opt/var/run/chrony/chronyd.pid
makestep 1.0 3
rtcsync
logdir /tmp/mnt/TRANSFER/Transfer/chrony
log measurements statistics tracking
allow 192.168.0.0/16
# prevent raspi from polling
deny 192.168.1.104
deny 192.168.1.105
broadcast 60 192.168.1.255
local stratum 1
logchange 0.5
chronyc sources
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^* 192.168.1.105 2 6 377 33 -226ms[ -409ms] +/-
8215us
^? zeit.fu-berlin.de 1 6 377 52 -228ms[ -410ms]
+/- 56ms
^? ptbtime1.ptb.de 1 6 377 7 -227ms[ -227ms] +/-
7441us
^? ptbtime2.ptb.de 1 6 377 17 -229ms[ -229ms] +/-
9255us
^? ptbtime3.ptb.de 1 6 377 4 -227ms[ -227ms] +/-
7839us
^? ns.tu-berlin.de 2 6 377 4 -227ms[ -227ms] +/-
8129us
chronyc tracking
Reference ID : C0A80169 (192.168.1.105)
Stratum : 3
Ref time (UTC) : Sat Jun 10 18:02:37 2023
System time : 0.135086194 seconds slow of NTP time
Last offset : -0.174640983 seconds
RMS offset : 0.178150147 seconds
Frequency : 13.519 ppm slow
Residual freq : -2691.479 ppm
Skew : 1.982 ppm
Root delay : 0.015255394 seconds
Root dispersion : 0.100952275 seconds
Update interval : 64.3 seconds
Leap status : Normal
chronyc sourcestats
Name/IP Address NP NR Span Frequency Freq Skew Offset
Std Dev
==============================================================================
192.168.1.105 44 19 46m -2691.479 161.086 -91ms 242ms
zeit.fu-berlin.de 48 21 50m -2636.146 123.263 +17ms 218ms
ptbtime1.ptb.de 57 25 60m -2632.208 101.466 +45ms 232ms
ptbtime2.ptb.de 54 23 57m -2651.780 111.097 -18ms 234ms
ptbtime3.ptb.de 55 24 58m -2601.458 110.065 +114ms 233ms
ns.tu-berlin.de 49 21 51m -2600.763 126.308 +79ms 245ms
chronyc ntpdata
Remote address : 192.168.1.105 (C0A80169)
Remote port : 123
Local address : 192.168.1.1 (C0A80101)
Leap status : Normal
Version : 4
Mode : Server
Stratum : 2
Poll interval : 6 (64 seconds)
Precision : -25 (0.000000030 seconds)
Root delay : 0.014679 seconds
Root dispersion : 0.000671 seconds
Reference ID : C035676C ()
Reference time : Sat Jun 10 17:58:36 2023
Offset : +0.226437911 seconds
Peer delay : 0.000576439 seconds
Peer dispersion : 0.000000198 seconds
Response time : 0.000195511 seconds
Jitter asymmetry: +0.00
NTP tests : 111 111 1111
Interleaved : No
Authenticated : No
TX timestamping : Daemon
RX timestamping : Kernel
Total TX : 2707
Total RX : 2706
Total valid RX : 2706
Total good RX : 2705
N������y隊W!���������n���\��"������z)�.n7��Z+��f����|�������'��}���*+�����)�.n7��:蹹^f��X��f����'��}���*+