r1 - 2006-04-24 - 09:32:47 - RobertJenkinsYou are here: NTP >  Support Web > HelpWanted > LassenSQ
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.8p15 was released on 23 June 2020. It addresses 1 medium-severity security issue in ntpd, and provides 13 non-security bugfixes over 4.2.8p13.

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.
REFACTOR See LassenSQDev for discussion of this topic.
I'm trying to get NTP working with a Trimble 'Lassen SQ' GPS module. I have used NTP for a few years, but previously only with peers & internet servers, this is my first attempt at a 'real' local refclock.

The machine is running Centos 4.3 on x86_64 architecture (Athlon 64 CPU). I have built NTP 4.2.0a with Parse & TSIP configured. (I have not figured out how to get it to run from /usr/sbin but that's another question..)

As far as I can see from the info I can find, the Lassen SQ appears to use exactly the same TSIP commands as the SV6 the parse refclock is supposed to support, but it does not give any sign of seeing data from the 'generic' server. ntpq -c peers shows all zeros except a '-' in the 'when' column.

I have enabled debugging in the parse module and initially I was seeing errors relating to invalid time data. The strings being dumped looked reasonable except occasional 0xff bytes, which I guessed were due to parity settings. The default parity for the module was Odd, I've changed this to None and the data errors have stopped.

I'm still getting an occasional error along the lines of 'data not received within poll interval'.

Notes: I have built the kernel with pps support. It's with the latest ppskit-lite patch (for 2.6.15 with rejects added by hand). I have not yet included any reference to pps in ntp.conf, I believe the basic parse clock should work regardless? (I've got to do a mod on the GPS module to extend it's PPS pulse & not got around to this yet).

I also have three other servers (one local & two internet) to ensure ntpd can get it's initial sync.

Does anyone have any ideas on getting this setup working? Or, is there another refclock that supports standard TSIP GPSs rather than just the dedicated time receivers?

-- RobertJenkins - 24 Apr 2006

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r1 | More topic actions
SSL security by CAcert
Get the CAcert Root Certificate
This site is powered by the TWiki collaboration platform
IPv6 Ready
Copyright & 1999-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding the site? Send feedback