1.1.6 build fails on FC30
Udo van den Heuvel
udovdh at xs4all.nl
Thu Apr 16 10:34:04 UTC 2020
On 16-04-2020 11:31, Hal Murray wrote:
>> I could switch to a NMEA clock sans PPS and a dedicated PPS clock?
>
> That's what I would try.
So I went to:
##NMEA zonder PPS
refclock nmea unit 0 mode 7 flag3 1 flag2 0 flag1 0 time1 0.00000006
time2 0.260 baud 4800
#
## PPS van dezelfde NMEA GPS
refclock pps unit 0 flag2 0
A NMEA clock without, a PPS clock with PPS.
(If I did that correctly)
I also switches the two Garmin GPS18X's between this box and the firewall.
On this workstation I see:
$ ntpq -pn
remote refid st t when poll reach delay offset
jitter
==============================================================================
xNMEA(0) .GPS. 0 l 18 64 377 0.0000 -331.787
23.4930
xPPS(0) .PPS. 0 l 7 64 377 0.0000 -0.8792
0.1323
+192.168.10.98 .GPS. 1 u 98 128 377 0.2679 -0.7279
0.1074
*fd00:c0a8:a00: .GPS. 1 u 126 128 377 0.2856 -0.5707
0.2049
2606:4700:f1:: .STEP. 16 1 - 512 0 0.0000 0.0000
0.0010
-2405:fc00:0:1: .PPS. 1 8 104 128 377 172.2620 1.3215
1.2845
-2001:470:e815: .PPS. 1 8 115 128 377 174.3298 -8.0867
1.0422
(cut)
So I start to think the serial port might have an issue?
The firewall shows:
# ntpq -pn
remote refid st t when poll reach delay offset
jitter
===============================================================================
oNMEA(0) .GPS. 0 l 40 64 377 0.0000 0.1373
0.0000
fd00:c0a8:a00:1 165.216.214.155 2 u 8 64 377 0.3301 0.9063
0.1030
192.168.10.70 165.216.214.155 2 u 55 64 377 0.2456 0.8751
0.0562
2606:4700:f1::1 .NTS. 16 4 - 256 0 0.0000 0.0000
0.0010
-2a01:3f7:2:202: 194.58.202.20 2 8 30 64 377 36.1680 2.4365
0.9056
#2a03:b0c0:1:d0: 37.15.221.189 2 8 43 64 377 23.1451 2.6572
1.8014
+2001:888:0:7::2 193.67.79.202 2 u 23 64 377 14.3002 3.6927
0.3338
(cut)
(also with kernel discipline)
This looks more normal?
Udo
More information about the devel
mailing list