NTP offset and dispersion too high when using GPS as source

NETWORKING SOLUTIONS
1

Hello, I have a RUTX50 running the latest software.

I’m using the device as an NTP server, and only use the GPS as a source. The NTP client on the RUTX50 is disabled.

I’ve noticed that the RUTX always has a much higher offset and dispersion than other NTP servers, regularly it’s even seen as an ‘outlyer’ or ‘falseticker’ , which means it won’t be used at all.

Here’s an output of a cisco ios device that has the RUTX as time server amongst others

image

The RUTX50 is ip 172.16.5.1
I also have a raspberry pi with an NTP module (172.16.1.252), and that one is behaving correctly.

Even internet sourced servers behave correctly.

IMO the offset, even though “only” ~10-20 ms, shouldn’t be that big for NTP.

Configuring the RUTX NTP client and referring to other NTP server would defeat the purpose of using the GPS as a single source.

1 Like
2

Bump. I was wondering if somebody could try something similar and report back ?

3

This topic was automatically closed after 15 days. New replies are no longer allowed.