On 12-04-2020 17:35, Udo van den Heuvel via devel wrote:
> On 12-04-2020 17:25, ASSI via devel wrote:
>>> # ppswatch /chroot/ntpd/dev/pps0
>>> (shows similar output)
>>
>> Good, but does ntpd see the same?
>
> Well, devices look like this:
And pps debug messages:
# dmesg|grep event
[ 408.583301] pps pps0: PPS event at 1586955482.000224958
[ 408.783290] pps pps0: PPS event at 1586955482.200221526
[ 409.583276] pps pps0: PPS event at 1586955483.000216947
[ 409.783279] pps pps0: PPS event at 1586955483.200224550
[ 410.583256] pps pps0: PPS event at 1586955484.000219902
[ 410.783257] pps pps0: PPS event at 1586955484.200224501
[ 411.583231] pps pps0: PPS event at 1586955485.000214265
[ 411.783227] pps pps0: PPS event at 1586955485.200217887
[ 412.583211] pps pps0: PPS event at 1586955486.000214565
[ 412.783209] pps pps0: PPS event at 1586955486.200217559
[ 413.583183] pps pps0: PPS event at 1586955487.000207532
[ 413.783188] pps pps0: PPS event at 1586955487.200214856
[ 414.583161] pps pps0: PPS event at 1586955488.000204200
[ 414.783164] pps pps0: PPS event at 1586955488.200212572
[ 415.583138] pps pps0: PPS event at 1586955489.000201916
[ 415.783140] pps pps0: PPS event at 1586955489.200209170
[ 416.583115] pps pps0: PPS event at 1586955490.000202426
[ 416.783117] pps pps0: PPS event at 1586955490.200206886
We can recognise the 200 ms pulse length of the gps.
And some messages:
# grep ntp /var/log/messages|grep -v NTSc
Apr 15 14:57:52 doos ntpd[13057]: INIT: ntpd ntpsec-1.1.8
2019-08-02T00:00:00Z: Starting
Apr 15 14:57:52 doos ntpd[13057]: INIT: Command line: /usr/sbin/ntpd -u
ntp:ntp -g -N -p /var/run/ntpd.pid
Apr 15 14:57:52 doos ntpd[13058]: INIT: precision = 1.466 usec (-19)
Apr 15 14:57:52 doos ntpd[13058]: INIT: successfully locked into RAM
Apr 15 14:57:52 doos ntpd[13058]: CONFIG: readconfig: parsing file:
/etc/ntp.conf
Apr 15 14:57:52 doos ntpd[13058]: AUTH: authreadkeys: reading /etc/ntp/keys
Apr 15 14:57:52 doos ntpd[13058]: AUTH: authreadkeys: added 0 keys
Apr 15 14:57:52 doos ntpd[13058]: CONFIG: 'monitor' cannot be disabled
while 'limited' is enabled
Apr 15 14:57:52 doos ntpd[13058]: INIT: Using SO_TIMESTAMPNS
Apr 15 14:57:52 doos ntpd[13058]: IO: Listen and drop on 0 v6wildcard
[::]:123
Apr 15 14:57:52 doos ntpd[13058]: IO: Listen and drop on 1 v4wildcard
0.0.0.0:123
Apr 15 14:57:52 doos ntpd[13058]: IO: Listen normally on 2 lo 127.0.0.1:123
Apr 15 14:57:52 doos ntpd[13058]: IO: Listen normally on 3 eth0
192.168.10.70:123
Apr 15 14:57:52 doos ntpd[13058]: IO: Listen normally on 4 lo [::1]:123
Apr 15 14:57:52 doos ntpd[13058]: IO: Listen normally on 5 eth0
[fd00:c0a8:a00:1::70]:123
Apr 15 14:57:52 doos ntpd[13058]: IO: Listen normally on 6 eth0
[2001:981:a812:0:b62e:99ff:fe92:5264]:123
Apr 15 14:57:52 doos ntpd[13058]: IO: Listen normally on 7 eth0
[fe80::b62e:99ff:fe92:5264%2]:123
Apr 15 14:57:52 doos ntpd[13058]: IO: Listening on routing socket on fd
#24 for interface updates
Apr 15 14:57:52 doos ntpd[13058]: SYNC: Found 14 servers, suggest
minsane at least 3
Apr 15 14:57:52 doos ntpd[13058]: INIT: MRU 10922 entries, 13 hash bits,
65536 bytes
Apr 15 14:57:52 doos ntpd[13058]: INIT: OpenSSL 1.1.1d FIPS 10 Sep
2019, 1010104f
Apr 15 14:57:52 doos ntpd[13057]: 2020-04-15T14:57:52 ntpd[13057]: INIT:
ntpd ntpsec-1.1.8 2019-08-02T00:00:00Z: Starting
Apr 15 14:57:52 doos ntpd[13057]: 2020-04-15T14:57:52 ntpd[13057]: INIT:
Command line: /usr/sbin/ntpd -u ntp:ntp -g -N -p /var/run/ntpd.pid
Apr 15 14:57:56 doos ntpd[13058]: EX-REP: Count=1 Print=1, Score=0.500,
M4 V4 from [2606:4700:f1::1]:123, lng=84
Apr 15 14:57:56 doos ntpd[13058]: EX-REP: e4000000 00000000 00000000
4e54534e 00000000 00000000 68b79e8c 7aba3928 00000000 00000000 00000000
00000000 01040024 ab1ba90e 83b3398e b52bc6be 4326e979 982bfea5 f885c05a
718c2243 47483da8
Apr 15 14:59:01 doos ntpd[13058]: EX-REP: Count=2 Print=2, Score=0.996,
M4 V4 from [2606:4700:f1::1]:123, lng=84
Apr 15 14:59:01 doos ntpd[13058]: EX-REP: e4000000 00000000 00000000
4e54534e 00000000 00000000 fcbd5032 7356fdea 00000000 00000000 00000000
00000000 01040024 e445b468 d2d8f320 ea459fd8 86e68505 33cf4112 3f7d5a7d
9f2969df 4627b682
So no error messages about gps/NMEA.
ntpq:
# ntpq -pn
remote refid st t when poll
reach delay offset jitter
=======================================================================================================
NMEA(0) .GPS. 0 l 15 64
377 0.0000 0.0000 0.0019
192.168.10.98 .GPS. 1 u 12 16
377 0.3325 0.8299 0.1966
fd00:c0a8:a00:1::1 .GPS. 1 u 4 64
377 0.3462 0.8608 0.7197
2606:4700:f1::1 .NTS. 16 0 - 64
0 0.0000 0.0000 0.0019
2405:fc00:0:1::123 .PPS. 1 8 - 64
377 172.2785 2.9948 0.8281
2001:470:e815::24 .PPS. 1 8 57 64
177 175.7728 -6.3917 0.7093
(cut)
No system peer....
Udo
_______________________________________________
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
