ConfiguringSHMRefclocks < Support

r4 - 2012-08-28 - 08:44:12 - HarlanStennYou are here: NTP >

Support Web > ConfiguringNTP > ConfiguringRefclocks > ConfiguringSHMRefclocks

NTP users are strongly urged to take immediate action to ensure that their NTP daemons are not susceptible to being used in distributed denial-of-service (DDoS) attacks. Please also take this opportunity to defeat denial-of-service attacks by implementing Ingress and Egress filtering through BCP38.

ntp-4.2.8p13 was released on 07 March 2019. It addresses 1 medium-severity security issue in ntpd, and provides 17 non-security bugfixes and 1 other improvements over 4.2.8p12.

Please see the NTP Security Notice for vulnerability and mitigation details.
Are you using Autokey in production? If so, please contact Harlan - he's got some questions for you.

See ConfiguringSHMRefclocksDev for discussion of this topic.

Under LINUX there is the gpsd service which provides SHM services.

In ntp.conf include lines:-

# ... and use gpsd daemon for time sync
server 127.127.28.0 minpoll 4 maxpoll 4
fudge 127.127.28.0 time1 -0.245 refid GPS stratum 15
server 127.127.28.1 minpoll 4 maxpoll 4 prefer
fudge 127.127.28.1 refid GPS1

gpsd then provides the following (from ntpq):-

remote      refid     st   t   when   poll   reach   delay   offset   jitter
=====      ===     ===   =   ====   ===   =====   ====   =====   ======
LOCAL(0)  .LOCL.     13   l   21   64   377   0   0   0.002
=-SHM(0)  .GPS.     15   l   9   16   377   0   36.775   12.287
*SHM(1)      .GPS1.       0   l   6   16   377   0   0.032   0.003

Note:

SHM(0) is the time from NEMA string (to establish second) this can deviate a lot, recommend you add another server (Not shown).

SHM(1) is the PPS from GPS

Related Topics: SHMRefclockUsers, ImprovingTheSHMRefclock