Ok, I found it. Gosh, do you know this situation, you tell your customers all day long to check their restriction settings and then find yourself running into exactly the same config error? Thank god its (almost) Friday and we are approaching a long weekend ..
Sorry to have bothered you, kind regards, Heiko Heiko Gerstung schrieb: > Hi! > > Despite the fact that my ACTS synchronized time server seems to be > working fine, my client does not accept it. > > Any other parameters I have to change? > > "ntpq -p" on server > (the GPS/PPS sources are noselect and only used for measuring the > accuracy of the ACTS source) > > remote refid st t when poll reach delay offset > jitter > ============================================================================== > > > server .INIT. 16 l - 1024 0 0.000 0.000 > 0.000 > GENERIC(0) .GPS. 0 l 5 64 377 0.000 47.289 > 0.391 > PPS(0) .PPS. 0 l 36 64 377 0.000 47.228 > 0.341 > *ACTS_MODEM(1) .PTB. 0 l 127 1024 377 0.000 -4.530 > 4.289 > > > "ntpq -p" on client > (the server is the second association) > > remote refid st t when poll reach delay offset > jitter > ============================================================================== > > > *gateway.py.mein .GPSi. 1 u 3 64 377 0.131 3.278 > 0.042 > rsvd-heiko-229. .INIT. 16 u 50 1024 0 0.000 0.000 > 0.000 > > > Best Regards, > Heiko _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
