Re: [chrony-users] Chrony on Asus router - no reduction of offset

2023-06-14 Thread Torsten Wolf
am 12.06.23 um 09:21: On Sat, Jun 10, 2023 at 08:09:04PM +0200, Torsten Wolf wrote: Name/IP Address    NP  NR  Span  Frequency  Freq Skew  Offset Std Dev == 192.168.1.105  44  19   46m  -2691.479

Re: [chrony-users] All network sources unusable

2023-06-04 Thread Torsten Wolf
I added "noselect" to the NMEA (SHM0) source and restarted chrony. After an hour the output is $ chronyc -m sources sourcestats MS Name/IP address Stratum Poll Reach LastRx Last sample === #? GPS 

Re: [chrony-users] All network sources unusable

2023-06-05 Thread Torsten Wolf
A value of 0 for NP, 0 for Span, 2000.000 for Freq Skew and 4000ms for Std Dev are clear indications that the source is not being tracked. Denny On Jun 4, 2023, at 03:07, Torsten Wolf wrote: I added "noselect" to the NMEA (SHM0) source and restarted chrony. After an hour the o

Re: [chrony-users] All network sources unusable

2023-06-05 Thread Torsten Wolf
an offset of -200ms. If not, I will come back soon. Thanks again for your help! Miroslav Lichvar schrieb am 05.06.23 um 10:02: On Sun, Jun 04, 2023 at 12:07:44PM +0200, Torsten Wolf wrote: Not sure why the Reach value for the PPS source is 113. A few minuts later that value increased to 372, just

[chrony-users] Chrony on Asus router - no reduction of offset

2023-06-10 Thread Torsten Wolf
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

Re: [chrony-users] Chrony on Asus router - no reduction of offset

2023-06-11 Thread Torsten Wolf
No, I still have them in the current config just to be able to compare the router's time obtained from a local GPS receiver with the "official" public servers. Daniel's config solved the problem. As written in my repsonse to him I am not fully sure but think that removing "maxupdateskew" and/or

Re: [chrony-users] Chrony on Asus router - no reduction of offset

2023-06-11 Thread Torsten Wolf
Thanks you, Daniel! It's working beautifully now. Not sure what did the trick. During the past weeks I also tried to poll more often and apply the median filter similar to your server line but it did not improve the offset. Following your config I removed the "maxupdateskew" line and added

[chrony-users] All network sources unusable

2023-06-03 Thread Torsten Wolf
Hi, until last week my Raspberry Pi was querying a handful of ntp servers. Seeing offsets of mostly +/-20ms and up to +/-200ms I wondered if I could improve this and got an Adafruit Ultimate GPS module (USB connector with additional PPS pin). The NMEA data is polled via /dev/ttyUSB0 whereas

Re: [chrony-users] All network sources unusable

2023-06-03 Thread Torsten Wolf
Bryan, many thanks for the explanation and the suggestion regarding SHM0. My only worry is that the sourcestats output is not offering much in terms of offset of the network sources: $ chronyc sourcestats Name/IP Address    NP  NR  Span  Frequency  Freq Skew  Offset  Std Dev

Re: [chrony-users] Chrony on Asus router - no reduction of offset

2023-06-15 Thread Torsten Wolf
will ask on snbforums. Many thanks for your support! Miroslav Lichvar schrieb am 15.06.23 um 09:49: On Wed, Jun 14, 2023 at 06:24:36PM +0200, Torsten Wolf wrote: I have no explanation how this is possible. I don't see anything suspicious in the raspi chrony offset data which I monitor via grafana