Re: Chrony on Asus router - no reduction of offset

Bob McDonald <[email protected]>
Newsgroups gmane.comp.time.chrony.user
Message-ID <CAM-YpteYCVi0dzNEWreUg=25pyECAgF6AGp6aUtA3PNNag83Dw@mail.gmail.com>
Does the noselect clause on the config statements for the servers have
anything to do with it?

On Sat, Jun 10, 2023, 14:09 Torsten Wolf <[email protected]> wrote:

> 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
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.