Re: [ntp:questions] Reason for sys_jitter stuck to 0.001907 ?

[Brian Inglis]

On 2015-02-03 03:32, François Meyer wrote:

Hi,

I have 2 stratum 1 Freebsd boxes in roughly the same configuration,
ie a network stratum 1 peer and a Cs 1PPS ; they are working
ok afaics, but both report a sys_jitter of 0.001907 that seem to be an
impasable lower limit. Does anyone have some link/explanation
regarding the mechanism behind this limit ?


What are your Cs drift rates?
What do your peerstats and loopstats show for these servers?


Below are ntpq -p and ntpq -c rv output for both machines :

saturne :

remote   refid  st t when poll reach   delay   offset  jitter
==
oPPS(0)  .PPS.   0 l   25   64  3770.0000.001   0.002
+192.168.12.7.PPS.   1 s   31   64  3770.3660.042   0.040
*ntp-p1.obspm.fr .TS-4.  1 s  123   64  372   11.3990.012   0.378

associd=0 status=0115 leap_none, sync_pps, 1 event, clock_sync,
version="ntpd 4.2.8@1.3265-o Wed Jan  7 15:31:43 UTC 2015 (1)",
processor="i386", system="FreeBSD/10.1-RC3", leap=00, stratum=1,
precision=-19, rootdelay=0.000, rootdisp=1.375, refid=PPS,
reftime=d87b1e49.6f35f1e4  Tue, Feb  3 2015 10:15:37.434,
clock=d87b1e63.2e1257cd  Tue, Feb  3 2015 10:16:03.179, peer=5700, tc=6,
mintc=3, offset=0.000750, frequency=-196.055, sys_jitter=0.001907,
clk_jitter=0.002, clk_wander=0.000, tai=35, leapsec=20150701,
expire=20151228, host="saturne.obs-besancon.fr", flags=0x80003,
digest="md5", signature="md5WithRSAEncryption", update=201501291235,
cert="saturne.obs-besancon.fr saturne.obs-besancon.fr 0x1",
until=201601151330


Note frequency drift is -196ppm - is this reasonable for this machine, and
is this number constantly increasing or just varying around this value?


192.168.12.7:

remote   refid  st t when poll reach   delay   offset  jitter
==
oPPS(0)  .PPS.   0 l5   64  3770.000   -0.001   0.002
*saturne.obs-bes .PPS.   1 s   44   64  1770.362   -0.033   0.029
ntp-p1.obspm.fr .INIT.  16 s- 102400.0000.000   0.000

associd=0 status=01f8 leap_none, sync_pps, 15 events, no_sys_peer,
version="ntpd 4.2.8@1.3265-o Wed Jan 14 20:49:48 UTC 2015 (1)",
processor="i386", system="FreeBSD/10.1-RELEASE", leap=00, stratum=1,
precision=-19, rootdelay=0.000, rootdisp=1.090, refid=PPS,
reftime=d87b1c7d.57c3637c  Tue, Feb  3 2015 10:07:57.342,
clock=d87b1c83.53a0827a  Tue, Feb  3 2015 10:08:03.326, peer=28975, tc=6,
mintc=3, offset=-0.000736, frequency=-2.064, sys_jitter=0.001907,
clk_jitter=0.002, clk_wander=0.000, tai=35, leapsec=20150701,
expire=20151228


Note 192.168.12.7 shows no_sys_peer and ntp-p1.obspm.fr stuck in INIT.

Rootdisp on both systems seems pretty high for PPS sources.
Normally there is a GPS associated with each PPS source.
What are your PPS and time sources?
Do you have local preferred sources in both configs to provide UTC?

Are both servers defined to each other as peers?
Peers can not share any sources.
Common sources cause a timing loop error which should be logged.
What do your logs show?

Could you share your configs?
--
Take care. Thanks, Brian Inglis
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Cross Compile Can't Find arc4random

[Harlan Stenn]

Joe Walsh writes:
> Has the fix for 2666 (http://bugs.ntp.org/show_bug.cgi?id=2666) affected cros
> s-compile?
> 
> I tried to cross compile for ARMv7  today and got "ntp-4.2.8/libntp/ntp_crypt
> o_rnd.c:93: undefined reference to `arc4random_buf'"
> 
> It appears I'm not the only one: http://unix.stackexchange.com/questions/1790
> 70/ntp-compilation-failed-without-ssl.
> 
> Has the 2666 fix introduced new requirements for arguments to ./configure whe
> n cross compiling?
> 
> Thanks,
> 
> Joe Walsh

Link with sntp/libevent/libevent .

There is probably stuff in the configure framework already to handle
extra libraries for cross-compile targets, so it shuold be possible to
handle this one.

H
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] CVE-2014-9296 and xntp3

[Harlan Stenn]

Kevin Fowler writes:
> Does this vulnerability apply to xntp3 versions, in particular to v5.93?
> There is an xntpd/ntp_proto.c file in that release, but the code is
> substantially different from ntp4, so I am not clear if the vulnerability
> actually applies.
> 
> Yes - I realize how ancient this release is...:-)

I didn't look hard.  I don't think so.  But...

http://queue.acm.org/detail.cfm?id=2717320 has a nice "Table 1".

The other things I'll point out in that article are:

- Implement BCP38
- Watch Dan Geer's Blackhat 2014 keynote talk

-- 
Harlan Stenn 
http://networktimefoundation.org - be a member!
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Shared PPS source/Multiple PPS sources

[Brian Inglis]

On 2015-02-06 13:17, walter.preunin...@gmail.com wrote:

Ok, so these questions might be off the wall.

Is there any reason why I could not share the PPS output of say, my u-blox 7 
GPS module on multiple computers?


No reason not to as long as the splitter added no delay/phase error/offset.
Is it a timing module supporting position survey, hold, and sawtooth error 
output?


Would it be good or bad to peer these 2 systems with each other?


Not recommended as the time sources are not independent, but not bad for time 
sync, as long as
each server also uses four or more other different accurate, reliable, 
independent sources.


On the opposite end of the spectrum, would it be reasonable to have a PPS 
output from said module on a computer,
with a second PPS (from another GPS module) on that same computer?


Multiple accurate, independent sources of PPS and time are good and handled 
appropriately.


The Chronodot/DS323X chips have 1 Hz sqaure wave output and they have +/- 2ppm.
It seems that the ATOM clock driver could be used, but would it be better to 
write a driver specifically for this chip?


Those chips are clock sources with a bit better than wristwatch quality time 
source, tempco of .1ppm/C,
and.
It requires an I2C or SPI interface to set and read it - how accurately can you 
set it to UTC,
and what will you use to keep it synced?
It says it handles leap years up to 2100 - but how does it or do you handle 
leap seconds?


And a side question: Is it the GPS module that calculates when the PPS goes 
active?
Is this signal compensated for the time it takes the signal from the sats in 
the module, or on the SV?


You need a good view of at least four satellites to solve for x, y, z, and t of 
the antenna position.
You can add fudge times to compensate for LNA processing, antenna cable delay, 
GPS solution, and system
overhead if you have some way to calculate or calibrate the delay.


Does someone know the admin of tick.uh.edu? I am not getting a response from 
them or the server.

See ToE for http://support.ntp.org/bin/view/Servers/PublicTimeServer000313
or message to this list/group:
Message-ID: 
From: Evandro Menezes 
Injection-Date: Fri, 25 Apr 2014 19:59:35 +
or look for public civilian contacts at USNO or UH.
--
Take care. Thanks, Brian Inglis
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] How the "peer candidate" is selected?

[Harlan Stenn]

Gene Heskett writes:
> On Monday 29 December 2014 08:52:48 Nomen Nescio did opine
> And Gene did reply:
> > chrony rulez
> > 
> > shalu.sysc...@gmail.com wrote:
> > > "Swimming pool Our company designs and installs deluxe indoor and
> > > outdoor swimming pools in Central and Greater London areas. More at
> > > : http://www.swimmingpoolquotes.co.uk/swimming-pool-maintenance/
> 
> How come you let spam like this thru, but I still cannot post a week after 
> subscribing (and looking at several messages that I have to be moderator 
> approved when I have tried)

Because the former was posted to the unmoderated newsgroup, and we don't
have enough mailing list managers for the mailing lists.

I just posted about this.

If you want to help with list management, please email
listmas...@lists.nwtime.org.

H
--
> > ___
> > questions mailing list
> > questions@lists.ntp.org
> > http://lists.ntp.org/listinfo/questions
> 
> 
> Cheers, Gene Heskett
> -- 
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Genes Web page 
> US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS
> ___
> questions mailing list
> questions@lists.ntp.org
> http://lists.ntp.org/listinfo/questions
> 
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] moving from ntpdc to ntpq

[Harlan Stenn]

Pretty much the same thing, except with ":config addpeer ..." and
":config unconfig ...".

I think...

Please feel free to add examples to:

 http://support.ntp.org/Support/MonitoringAndControllingNTP
 http://support.ntp.org/Dev/DeprecatingNtpdate

H
Richard writes:
> What is ntpq's equivelant of -c "addpeer "   and  -c "unconfig
> "  ?
> 
> 
> I just upgraded from ntp 4.2.6 to 4.2.8 and ntpdc isn't connecting to my
> local ntpd. According to the ntpdc man page:
> 
> "ntpdc is deprecated. Please use ntpq(1) instead - it can do everything
> ntpdc used to do,"
> 
> 
> In ntpq how do I do the equivalent of ntpdc's -c "addpeer "  or -c
> "unconfig" commands?
> 
> 
> Here is part of what previously did with ntpdc:
> 
> /usr/sbin/ntpc -4 -c "keyid 5" -c "passwd  mypassword" \
>  -c "addpeer   "  localhost
> 
> 
> ___
> questions mailing list
> questions@lists.ntp.org
> http://lists.ntp.org/listinfo/questions
> 
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Shared PPS source/Multiple PPS sources

[William Unruh]

On 2015-02-07, Paul  wrote:
> On Fri, Feb 6, 2015 at 3:17 PM,  wrote:
>
>> Is this signal compensated for the time it takes the signal from the sats
>> in the module, or on the SV?
>>
>
> I've decided I have no idea what this question means.

I think he meant is the time delivered the raw time on the sattelite, or
is there compensation for the time it takes the signal to get from the
sattelite to your receiver. If it were the former, then that time would
be out by about 10-100ms depending on where the sattelite were in the
sky. That would be pretty bad timing. 


___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] ntp-4.2.8 problem

[Harlan Stenn]

This problem was fixed right after 4.2.8 was released.

And now, folks should be running 4.2.8p1.

H
--
William Unruh writes:
> On 2015-02-04, Wei, Catherine  wrote:
> > Hi,
> > I met a problem when I was building ntp-4-2.8 on Linux. The log is
> > on below. I really appreciate if you could you give me some advice? It
> > was used OK with ntp-4.2.6 before I upgraded.
> >
> >  CCLD   ntp-keygen
> > ../libntp/libntp.a(ntp_crypto_rnd.o): In function `ntp_crypto_random_buf':
> > /home/catherine/work/KREATV-27230/platform/3pp/ntp/bcm45/ntp-4.2.8/libntp/n
> tp_crypto_rnd.c:93:
> > undefined reference to `arc4random_buf'
> > collect2: ld returned 1 exit status
> > make[6]: *** [ntp-keygen] Error 1
> > make[5]: *** [all] Error 2
> > make[4]: *** [all-recursive] Error 1
> > make[3]: *** [all] Error 2
> > make[2]: *** [bcm45/ntp-4.2.8/.done] Error 2
> > make[1]: *** [.target_bcm45_] Error 2
> 
> You do not seem to have arc4. Perhaps somehow you are compiling witht he
> HAVE_ARC4RANDOM flag set when you do not have it?
> 
> Look in the make files whether that flag is being defined somewhere.
> 
> ___
> questions mailing list
> questions@lists.ntp.org
> http://lists.ntp.org/listinfo/questions
> 
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Shared PPS source/Multiple PPS sources

[William Unruh]

On 2015-02-06, walter.preunin...@gmail.com  wrote:
> On Friday, February 6, 2015 at 3:38:14 PM UTC-6, William Unruh wrote:
>
>> > Is there any reason why I could not share the PPS output of say, my u-blox 
>> > 7 GPS module on multiple computers? Would it be good or bad to peer these 
>> > 2 systems with each other?
>> 
>> By share you mean run the PPS output to each of the computers? The main
>> thing you would need to do is make sure that the gps is able to handle
>> the current load, and that the signals had the appropriate level at each
>> of the computers. 
>
> Yes, exactly what I mean.
>> 
>> 
>> >
>> > On the opposite end of the spectrum, would it be reasonable to have a PPS 
>> > output from said module on a computer, with a second PPS (from another GPS 
>> > module) on that same computer?
>> 
>> Sure. you need to have two differnt interrupt lines available (GPIO,
>> serial ports, parallel ports)
>> 
>
> Awesome!
>
>> >
>> > The Chronodot/DS323X chips have 1 Hz sqaure wave output and they have +/- 
>> > 2ppm. It seems that the ATOM clock driver could be used, but would it be 
>> > better to write a driver specifically for this chip?
>> 
>> 2PPM is not that great. That is one second out per 6 day. A minute out
>> per year. 
>> What is that chip. 
>> 
>
> I was thinking more as a worst case, offline for hours situation. Perhaps a 
> new driver could 'sync' the Dallas Semiconductor/Maxim DS3231 OXCO Real Time 
> Chip periodically.
>
> What is the ppm error of the RTC in a pc or my MacBook?

from a few to many PPM. The uncompensated one can be up to 50PPM. But if
you computer is on, and ntp has disciplined the clock and the machines
internal temp does not change by much (eg yousuddenly start doing some
massive numerical calculation or start playing a game) then you computer
itself should be able to do 2PPM without any help. 

>
>> > Does someone know the admin of tick.uh.edu? I am not getting a response 
>> > from them or the server.
>> 
>> What reponse do you want? Why should they respond to you?
>
> I would like to use tick.uh.edu as one of my 'local' Stratum 1's. I have 1 
> from Oklahoma, but I'm in Texas... and the server is either down, or the name 
> has changed on Pulic Strat 1's list hasnt been updated.

Ah, response from the computer, not response from the people there. Yes,
it seems down to me as well. 

>

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Shared PPS source/Multiple PPS sources

[Paul]

On Fri, Feb 6, 2015 at 3:17 PM,  wrote:

> Ok, so these questions might be off the wall.
>

Yes.


>
> Is there any reason why I could not share the PPS output of say, my u-blox
> 7 GPS module on multiple computers?


 Of course you can.  However the correct way to do this is with a
distribution amplifier and it would be cheaper to buy another GPS.

Would it be good or bad to peer these 2 systems with each other?
>

It depends.  What are you trying to do?


>
> On the opposite end of the spectrum, would it be reasonable to have a PPS
> output from said module on a computer, with a second PPS (from another GPS
> module) on that same computer?
>

It depends on why you would do it.  Again what are you trying to do?


> The Chronodot/DS323X chips have 1 Hz sqaure wave output and they have +/-
> 2ppm. It seems that the ATOM clock driver could be used, but would it be
> better to write a driver specifically for this chip?
>

RTC parts are not intended for hold-over input into NTP.  Unless you've
lost network access you'd do better to use a remote system.


>
> And a side question: Is it the GPS module that calculates when the PPS
> goes active?


If by calculate you mean determine then yes the PPS source (typically but
not exclusively a GPS in the NTP community) completely determines when the
PPS signal is active but I suspect you have a different question in mind.


> Is this signal compensated for the time it takes the signal from the sats
> in the module, or on the SV?
>

I've decided I have no idea what this question means.
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] ntp-4.2.8 problem

[William Unruh]

On 2015-02-04, Wei, Catherine  wrote:
> Hi,
> I met a problem when I was building ntp-4-2.8 on Linux. The log is
> on below. I really appreciate if you could you give me some advice? It
> was used OK with ntp-4.2.6 before I upgraded.
>
>  CCLD   ntp-keygen
> ../libntp/libntp.a(ntp_crypto_rnd.o): In function `ntp_crypto_random_buf':
> /home/catherine/work/KREATV-27230/platform/3pp/ntp/bcm45/ntp-4.2.8/libntp/ntp_crypto_rnd.c:93:
> undefined reference to `arc4random_buf'
> collect2: ld returned 1 exit status
> make[6]: *** [ntp-keygen] Error 1
> make[5]: *** [all] Error 2
> make[4]: *** [all-recursive] Error 1
> make[3]: *** [all] Error 2
> make[2]: *** [bcm45/ntp-4.2.8/.done] Error 2
> make[1]: *** [.target_bcm45_] Error 2

You do not seem to have arc4. Perhaps somehow you are compiling witht he
HAVE_ARC4RANDOM flag set when you do not have it?

Look in the make files whether that flag is being defined somewhere.

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Shared PPS source/Multiple PPS sources

[Steven Sommars]

https://groups.google.com/forum/#!topic/comp.protocols.time.ntp/P7qY3gBvHTM

On Friday, April 25, 2014 1:09:45 AM UTC-5, Evandro Menezes wrote:
> The NTP ST1 server at the University of Houston has been offline for
about a month. Any information about its demise? Yet another victim of a
DOS attack?

Alan Pfeiffer-Traum from UH was kind enough to explain:

"tick.uh.edu has been offline to the internet since mid-February. About
that time we saw a sudden sharp increase in traffic from many sources. The
high level of traffic overwhelmed tick and made it unusable. We hope that
this event will eventually fade away so we can allow access to the service
again."

On Fri, Feb 6, 2015 at 5:37 PM,  wrote:

> On Friday, February 6, 2015 at 3:38:14 PM UTC-6, William Unruh wrote:
>
> > > Is there any reason why I could not share the PPS output of say, my
> u-blox 7 GPS module on multiple computers? Would it be good or bad to peer
> these 2 systems with each other?
> >
> > By share you mean run the PPS output to each of the computers? The main
> > thing you would need to do is make sure that the gps is able to handle
> > the current load, and that the signals had the appropriate level at each
> > of the computers.
>
> Yes, exactly what I mean.
> >
> >
> > >
> > > On the opposite end of the spectrum, would it be reasonable to have a
> PPS output from said module on a computer, with a second PPS (from another
> GPS module) on that same computer?
> >
> > Sure. you need to have two differnt interrupt lines available (GPIO,
> > serial ports, parallel ports)
> >
>
> Awesome!
>
> > >
> > > The Chronodot/DS323X chips have 1 Hz sqaure wave output and they have
> +/- 2ppm. It seems that the ATOM clock driver could be used, but would it
> be better to write a driver specifically for this chip?
> >
> > 2PPM is not that great. That is one second out per 6 day. A minute out
> > per year.
> > What is that chip.
> >
>
> I was thinking more as a worst case, offline for hours situation. Perhaps
> a new driver could 'sync' the Dallas Semiconductor/Maxim DS3231 OXCO Real
> Time Chip periodically.
>
> What is the ppm error of the RTC in a pc or my MacBook?
>
> > > Does someone know the admin of tick.uh.edu? I am not getting a
> response from them or the server.
> >
> > What reponse do you want? Why should they respond to you?
>
> I would like to use tick.uh.edu as one of my 'local' Stratum 1's. I have
> 1 from Oklahoma, but I'm in Texas... and the server is either down, or the
> name has changed on Pulic Strat 1's list hasnt been updated.
>
> ___
> questions mailing list
> questions@lists.ntp.org
> http://lists.ntp.org/listinfo/questions
>
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Shared PPS source/Multiple PPS sources

[walter . preuninger]

On Friday, February 6, 2015 at 3:38:14 PM UTC-6, William Unruh wrote:

> > Is there any reason why I could not share the PPS output of say, my u-blox 
> > 7 GPS module on multiple computers? Would it be good or bad to peer these 2 
> > systems with each other?
> 
> By share you mean run the PPS output to each of the computers? The main
> thing you would need to do is make sure that the gps is able to handle
> the current load, and that the signals had the appropriate level at each
> of the computers. 

Yes, exactly what I mean.
> 
> 
> >
> > On the opposite end of the spectrum, would it be reasonable to have a PPS 
> > output from said module on a computer, with a second PPS (from another GPS 
> > module) on that same computer?
> 
> Sure. you need to have two differnt interrupt lines available (GPIO,
> serial ports, parallel ports)
> 

Awesome!

> >
> > The Chronodot/DS323X chips have 1 Hz sqaure wave output and they have +/- 
> > 2ppm. It seems that the ATOM clock driver could be used, but would it be 
> > better to write a driver specifically for this chip?
> 
> 2PPM is not that great. That is one second out per 6 day. A minute out
> per year. 
> What is that chip. 
> 

I was thinking more as a worst case, offline for hours situation. Perhaps a new 
driver could 'sync' the Dallas Semiconductor/Maxim DS3231 OXCO Real Time Chip 
periodically.

What is the ppm error of the RTC in a pc or my MacBook?

> > Does someone know the admin of tick.uh.edu? I am not getting a response 
> > from them or the server.
> 
> What reponse do you want? Why should they respond to you?

I would like to use tick.uh.edu as one of my 'local' Stratum 1's. I have 1 from 
Oklahoma, but I'm in Texas... and the server is either down, or the name has 
changed on Pulic Strat 1's list hasnt been updated.

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] ntp Segmentation fault

[Harlan Stenn]

Shai,

Sorry for the delay - your message (along with a bunch of others) were
in a moderation queue.

Please try 4.2.8p1, and also what OS is this on?

You may need to make sure ntpd was built with debug symbols in it, and
you might need to run 'ntpd -n ...' from a debugger, so you can get a
stack backtrace.

H
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] PPS and PLL frequency

[Neil Green]

Hello all,

I'm using a Raspberry Pi B+ with a U-Blox Max7q GPS to drive a stratum 1 NTP 
server. At the moment I'm at the point of following instructions and learning 
as much as I can, and would like to know, based on the info below, if there's 
anything I should do with things like PPS and/or PLL frequency and, if so, what:

associd=0 status=041d leap_none, sync_uhf_radio, 1 event, kern,
version="ntpd 4.2.7p483@1.2483-o Thu Dec 11 09:04:07 UTC 2014 (1)",
processor="armv6l", system="Linux/3.12.34", leap=00, stratum=1,
precision=-19, rootdelay=0.000, rootdisp=1.630, refid=NMEA,
reftime=d83e9df1.d85b58fa  Fri, Dec 19 2014 12:52:01.845,
clock=d83e9e1c.128dbc16  Fri, Dec 19 2014 12:52:44.072, peer=22016, tc=6,
mintc=3, offset=0.000317, frequency=-29.344, sys_jitter=0.001907,
clk_jitter=0.001, clk_wander=0.009, tai=35, leapsec=20120701,
expire=20150628
     remote           refid      st t when poll reach   delay   offset  jitter
==
o127.127.20.0    .NMEA.           0 l   43   64  377    0.000    0.000   0.002
-87.124.126.49   195.66.241.2     2 u   57   64  377   29.529    7.658   5.192
+130.88.200.6    130.88.212.143   3 u   65   64  377   17.293    2.666   1.470
+217.114.59.3    158.43.192.66    2 u   52   64  377   15.972    4.004   1.486
*158.43.128.66   193.67.79.202    2 u   58   64  377   10.612    1.694   1.242
ntp_gettime() returns code 0 (OK)
  time d83e9e1c.471b6914  Fri, Dec 19 2014 12:52:44.277, (.277762324),
  maximum error 22500 us, estimated error 0 us, TAI offset 35
ntp_adjtime() returns code 0 (OK)
  modes 0x0 (),
  offset 0.000 us, frequency -29.344 ppm, interval 256 s,
  maximum error 22500 us, estimated error 0 us,
  status 0x2107 (PLL,PPSFREQ,PPSTIME,PPSSIGNAL,NANO),
  time constant 6, precision 0.001 us, tolerance 500 ppm,
  pps frequency -29.344 ppm, stability 0.016 ppm, jitter 0.806 us,
  intervals 38, jitter exceeded 7, stability exceeded 0, errors 0.
associd=0 status= no events, clk_unspec,
device="NMEA GPS Clock",
timecode="$GPRMC,125243.000,A,5255.1858,N,00129.3135,W,0.01,127.64,191214,,,A*7B",
poll=35, noreply=0, badformat=0, baddata=0, fudgetime2=400.000,
stratum=0, refid=NMEA, flags=5

Relevant bit of ntp.conf:

server 127.127.20.0 mode 17 prefer
fudge 127.127.20.0 time2 0.400 flag1 1 flag2 0 flag3 1 flag4 0 refid NMEA

Thanks in advance,
Neil. 
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] How to improve precision on stratum 1 Raspberry Pi

[ncg uk]

Hi all,

This is my first post to the list. I have a Raspberry Pi B+ and Adafruit 
Ultimate GPS connected to a Virgin Media Superhub (broadband router) by a 0.5m 
cat6 ethernet cable. The GPS is attached to the Pi's GPIO and has an external 
active antenna placed on an inside window sill. The Pi is running Raspbian on a 
fast Class10 microSD card and has a kernel rebuilt to disable tickless and 
enable all appropriate PPS options, and has NTP 4.2.7p483 compiled with:

./configure --enable-linuxcaps --enable-ATOM --enable-NMEA --disable-ipv6 
--disable-all-clocks --disable-parse-clocks --disable-debugging 
--srcdir=/home/pi/ntp-dev-4.2.7p483

and with my ntp.conf file set up thus:

driftfile /var/lib/ntp/ntp.drift
logfile /var/log/ntp.log
statsdir /var/log/ntpstats/
statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable

server ntp0.catn.com iburst
server ntp2c.mcc.ac.uk iburst
server ntp1.luns.net.uk iburst
server ntp1.uk.uu.net iburst

server 127.127.20.0 mode 17 prefer minpoll 4 maxpoll 4 iburst
fudge 127.127.20.0 time2 0.400 flag1 1 flag2 0 flag3 1 flag4 0

restrict default limited kod nomodify notrap nopeer

restrict 127.0.0.1

After an hour or so, "ntpq -crv -pn; ntptime; ntpq -c clockvar" shows:

associd=0 status=041d leap_none, sync_uhf_radio, 1 event, kern,
version="ntpd 4.2.7p483@1.2483-o Thu Dec 11 09:04:07 UTC 2014 (1)",
processor="armv6l", system="Linux/3.12.33", leap=00, stratum=1,
precision=-19, rootdelay=0.000, rootdisp=1.210, refid=GPS,
reftime=d8341156.ff1da5ba  Thu, Dec 11 2014 12:49:26.996,
clock=d8341165.9d93d89e  Thu, Dec 11 2014 12:49:41.615, peer=39341, tc=4,
mintc=3, offset=-0.000519, frequency=-29.184, sys_jitter=0.001907,
clk_jitter=0.001, clk_wander=0.002
     remote           refid      st t when poll reach   delay   offset  jitter
==
o127.127.20.0    .GPS.            0 l   15   16  377    0.000   -0.001   0.002
-87.124.126.49   195.66.241.2     2 u    1   64  377   29.582    7.636   1.092
+130.88.200.6    130.88.202.49    3 u    -   64  377   17.822    3.209   0.636
+217.114.59.3    75.12.230.181    2 u    4   64  377   15.857    3.992   1.545
*158.43.128.66   193.67.79.202    2 u   15   64  377   10.594    1.805   0.851
ntp_gettime() returns code 0 (OK)
  time d8341165.d6c093d8  Thu, Dec 11 2014 12:49:41.838, (.838876471),
  maximum error 8500 us, estimated error 1 us, TAI offset 0
ntp_adjtime() returns code 0 (OK)
  modes 0x0 (),
  offset 0.000 us, frequency -29.199 ppm, interval 256 s,
  maximum error 8500 us, estimated error 1 us,
  status 0x2107 (PLL,PPSFREQ,PPSTIME,PPSSIGNAL,NANO),
  time constant 4, precision 0.001 us, tolerance 500 ppm,
  pps frequency -29.199 ppm, stability 0.021 ppm, jitter 0.930 us,
  intervals 34, jitter exceeded 13, stability exceeded 0, errors 0.
associd=0 status= no events, clk_unspec,
device="NMEA GPS Clock",
timecode="$GPRMC,124941.000,A,5255.1768,N,00129.3123,W,0.02,343.63,111214,,,A*74",
poll=224, noreply=0, badformat=0, baddata=0, fudgetime2=400.000,
stratum=0, refid=GPS, flags=5

I've tried using Banana Pi and Beagleboard Black SBCs and have also used u-blox 
Max-7Q and Trimble Copernicus II GPS breakout boards with no improvement, 
leading me to believe the roadblock to a more precise clock is in the Pi, so my 
questions are: can I improve upon this and, if so, how? Have I made any obvious 
errors? I've seen Pi Stratum servers with a precision of -20 and would like to 
achieve that if at all possible (I know we're talking microseconds here, but 
the more precise the better, right?). Any help much appreciated, thank you. 

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Jesus Christ! -> even internet time-sync (NTP)is vulnerable to exploitation?

[cool hand luke]

On 12/21/2014 10:30 PM, Virus Guy wrote:

Under what conditions would someone who is NOT operating an NTP server
expect to see external IP's hit his router on port 123?


When hosts behind that router are running an NTP client. If the router 
was also performing NAT, the destination IP of those packets would be 
the router's.


Depending on how the packets were captured/logged, they might have even 
been caught if NAT wasn't being performed (if a poorly constructed 
filter was used; for example, filtering just for UDP port 123 and not by 
the destination IP address).


/chl
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] Re. Sure GPS - PPS not working

[Richard Steedman]

Back in Dec 2013, Chris North wrote:

>I have managed to fix it, and it was a bit unexpected. When I first 
>installed the Sure, I used a USB connection and got it working OK. I then 
>used a Serial-USB adapter and was pleased to find that it passed DCD and 
>that PPS was working. The jitter was rather high, though - about 0.3 mS. I 
>bought a 2-port serial PCI card and a serial cable, and immediately had a 
>massive improvement in performance. Recently, however, I found that PPS had

>stopped working, as you have seen above.
>
>What I think happened was this: when I plugged in the new card it used the 
>standard Windows serial.sys, which I replaced with serialpps.sys. Now this 
>card is part of a range of multifunction cards that offer various I/O 
>interfaces. At some time Windows Update probably found the manufacturer's 
>drivers and installed them (automatically, or as an option that I just 
>accepted). The new driver ignores serial.sys and has its own software. So I

>poked around in the registry and changed the ImagePath for one of the
card's 
>new services to point to serialpps.sys. This seems to have fixed it. As I 
>don't use the COMn ports for anything else, I won't worry about possible 
>side-effects.

I am trying to get PPS working with a Sure GPS board connected to a laptop
running Win7.  I'm not getting very far and I'm guessing it's because
neither of the interface options available to me use the serial.sys driver:
- Direct connection of the Sure's USB port to the laptop means using the
  Silicon Labs 2102 chip on the Sure board and it uses drivers called
  silabenm.sys and silabser.sys
- Connecting the Sure board's RS-232 output to the laptop via a Prolific
  USB to serial adaptor means using the Prolific driver ser2pl.sys

Chris, if you still follow this listserv, could you tell me which
serial-to-USB adaptor you were using which successfully passed PPS to ntp?
I am not expecting the jitter to be any better than of the order of 1ms
since the USB interface samples the DCD line at 1024Hz but would still like
to try to get my setup working.

Thanks,

Richard Steedman.

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] ntp-4.2.8 problem

[Wei, Catherine]

Hi,
I met a problem when I was building ntp-4-2.8 on Linux. The log is
on below. I really appreciate if you could you give me some advice? It
was used OK with ntp-4.2.6 before I upgraded.

 CCLD   ntp-keygen
../libntp/libntp.a(ntp_crypto_rnd.o): In function `ntp_crypto_random_buf':
/home/catherine/work/KREATV-27230/platform/3pp/ntp/bcm45/ntp-4.2.8/libntp/ntp_crypto_rnd.c:93:
undefined reference to `arc4random_buf'
collect2: ld returned 1 exit status
make[6]: *** [ntp-keygen] Error 1
make[5]: *** [all] Error 2
make[4]: *** [all-recursive] Error 1
make[3]: *** [all] Error 2
make[2]: *** [bcm45/ntp-4.2.8/.done] Error 2
make[1]: *** [.target_bcm45_] Error 2

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Request to test patch for ntpd

[Richard Steedman]

On 28/01/2015 17:30, Martin Burnicki wrote:
> Hi all,
>
> several months ago I have opened NTP bug #2592
> "Leap second warning from refclock lost, and time offsets may not be
> accepted if refclock driver uses PPS"
> http://bugs.ntp.org/show_bug.cgi?id=2592
>
> By intensive testing with the current NTP tarball 4.2.8p1-RC1
> http://archive.ntp.org/ntp4/ntp-4.2/ntp-4.2.8p1-RC1.tar.gz
>
> we have found out that a leap second status from a refclock is still not
> picked up in 4.2.8, and even worse, that initial synchronization may not
> work if the initial time offset is in a certain range. See the bug
> report for details.
>
> As far as we have seen there's a simple fix for this. Anyway, I'd like
> to ask if folks who are using refclocks with PPS support could test the
> patch to make sure it doesn't break something else.
>
> To do so, you can just download the tarball mentioned above, then change
> into the base directory and extract this tarball there:
> http://people.ntp.org/burnicki/ntp-2592-ntp_proto.tar.gz
>
> This just overwrite ntpd/ntp_proto.c with a version containing the patch
> mentioned in the bug report.
>
> We have already run the following tests successfully:
>
> - parse driver (driver 8) with built-in PPS enabled
> - parse driver 8 without built-in PPS, but ATOM in addition
> - network peer marked as "prefer", and ATOM in addition
>
> It would be great if some folks who use a refclock with PPS run this
> test and see if everything still works as before, or even better. ;-)
>
> Martin
===

Martin,

I have tested your patch successfully using the NMEA driver with build-in
PPS (i.e. server 127.127.20.1 fudged with flag1=1).

My setup is a Sure Electronics GPS board connected to a Raspberry PI.  The
NMEA data comes over the GPS board's USB serial interface (a Silicon Labs
CP2102) and the PPS output of the GPS board is connected to one of the Pi's
GPIO inputs.

I am *not*, however, able to observe your 'failure to sync' issue when
running ntp4.2.8 without your patch.  If the Pi's clock is set fairly close
to correct time but more than 0.5s adrift from the time signalled by the GPS
board and ntpd is then started, the computer's clock comes into sync
correctly.

I'd be interested in trying to re-create your issue and then see it go away
by applying your patch.  Is there a simple setup that is guaranteed to make
the system fail to synchronise in the manner described in the bug report?

Richard Steedman
 

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] Reason for sys_jitter stuck to 0.001907 ?

[François Meyer]

Hi,

I have 2 stratum 1 Freebsd boxes in roughly the same configuration,
ie a network stratum 1 peer and a Cs 1PPS ; they are working
ok afaics, but both report a sys_jitter of 0.001907 that seem to be an
impasable lower limit. Does anyone have some link/explanation
regarding the mechanism behind this limit ?

Thank you in advance.

Below are ntpq -p and ntpq -c rv output for both machines :

saturne :

remote   refid  st t when poll reach   delay   offset  jitter
==
oPPS(0)  .PPS.   0 l   25   64  3770.0000.001   0.002
+192.168.12.7.PPS.   1 s   31   64  3770.3660.042   0.040
*ntp-p1.obspm.fr .TS-4.  1 s  123   64  372   11.3990.012   0.378

associd=0 status=0115 leap_none, sync_pps, 1 event, clock_sync,
version="ntpd 4.2.8@1.3265-o Wed Jan  7 15:31:43 UTC 2015 (1)",
processor="i386", system="FreeBSD/10.1-RC3", leap=00, stratum=1,
precision=-19, rootdelay=0.000, rootdisp=1.375, refid=PPS,
reftime=d87b1e49.6f35f1e4  Tue, Feb  3 2015 10:15:37.434,
clock=d87b1e63.2e1257cd  Tue, Feb  3 2015 10:16:03.179, peer=5700, tc=6,
mintc=3, offset=0.000750, frequency=-196.055, sys_jitter=0.001907,
clk_jitter=0.002, clk_wander=0.000, tai=35, leapsec=20150701,
expire=20151228, host="saturne.obs-besancon.fr", flags=0x80003,
digest="md5", signature="md5WithRSAEncryption", update=201501291235,
cert="saturne.obs-besancon.fr saturne.obs-besancon.fr 0x1",
until=201601151330

192.168.12.7:

remote   refid  st t when poll reach   delay   offset  jitter
==
oPPS(0)  .PPS.   0 l5   64  3770.000   -0.001   0.002
*saturne.obs-bes .PPS.   1 s   44   64  1770.362   -0.033   0.029
ntp-p1.obspm.fr .INIT.  16 s- 102400.0000.000   0.000

associd=0 status=01f8 leap_none, sync_pps, 15 events, no_sys_peer,
version="ntpd 4.2.8@1.3265-o Wed Jan 14 20:49:48 UTC 2015 (1)",
processor="i386", system="FreeBSD/10.1-RELEASE", leap=00, stratum=1,
precision=-19, rootdelay=0.000, rootdisp=1.090, refid=PPS,
reftime=d87b1c7d.57c3637c  Tue, Feb  3 2015 10:07:57.342,
clock=d87b1c83.53a0827a  Tue, Feb  3 2015 10:08:03.326, peer=28975, tc=6,
mintc=3, offset=-0.000736, frequency=-2.064, sys_jitter=0.001907,
clk_jitter=0.002, clk_wander=0.000, tai=35, leapsec=20150701,
expire=20151228

--
François MeyerTel : (+33) 3 81 66 69 27   Mob : 6 27 28 56 83
Observatoire de Besancon - BP1615 - 25010 Besancon cedex - FRANCE
Institut UTINAM * Universite de Franche-Comte * CNRS UMR 6213 ***___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] shm driver for linux parallel port updated for nanoseconds

[gnu not unix]

Hi Folks--

I've updated the shm driver for linux parallel port pps to support
the nanosecond timestamp via clock_gettime. The version has been
added to my web page as shm-ns.c:

http://www.wraith.sf.ca.us/ntp/index.html#parallel-port

It's worked for a day now so it must be ready for release. Cough.

My test system was Gentoo running  linux 3.18.3 with glibc (Gentoo
2.20-r1 p3). BTW its cool to see the extra resolution bits reported
via ntpq -c rv in the "offset" field. My test system has routinely
been reporting offsets less than a microsecond:

http://www.wraith.sf.ca.us/ntp/rrd/index.html

If you have comments, bug reports, patches, well they are appreciated.

Yours for happy chiming--

Steve
g...@wraith.sf.ca.us
 

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Request to test patch for ntpd

[Richard Steedman]

On 28/01/2015 17:30, Martin Burnicki wrote:
> Hi all,
>
> several months ago I have opened NTP bug #2592
> "Leap second warning from refclock lost, and time offsets may not be
> accepted if refclock driver uses PPS"
> http://bugs.ntp.org/show_bug.cgi?id=2592
>
> By intensive testing with the current NTP tarball 4.2.8p1-RC1
> http://archive.ntp.org/ntp4/ntp-4.2/ntp-4.2.8p1-RC1.tar.gz
>
> we have found out that a leap second status from a refclock is still not
> picked up in 4.2.8, and even worse, that initial synchronization may not
> work if the initial time offset is in a certain range. See the bug
> report for details.
>
> As far as we have seen there's a simple fix for this. Anyway, I'd like
> to ask if folks who are using refclocks with PPS support could test the
> patch to make sure it doesn't break something else.
>
> To do so, you can just download the tarball mentioned above, then change
> into the base directory and extract this tarball there:
> http://people.ntp.org/burnicki/ntp-2592-ntp_proto.tar.gz
>
> This just overwrite ntpd/ntp_proto.c with a version containing the patch
> mentioned in the bug report.
>
> We have already run the following tests successfully:
>
> - parse driver (driver 8) with built-in PPS enabled
> - parse driver 8 without built-in PPS, but ATOM in addition
> - network peer marked as "prefer", and ATOM in addition
>
> It would be great if some folks who use a refclock with PPS run this
> test and see if everything still works as before, or even better. ;-)
>
> Martin
===

Martin,

I have tested your patch successfully using the NMEA driver with build-in
PPS (i.e. server 127.127.20.1 fudged with flag1=1).

My setup is a Sure Electronics GPS board connected to a Raspberry PI.  The
NMEA data comes over the GPS board's USB serial interface (a Silicon Labs
CP2102) and the PPS output of the GPS board is connected to one of the Pi's
GPIO inputs.

I am *not*, however, able to observe your 'failure to sync' issue when
running ntp4.2.8 without your patch.  If the Pi's clock is set fairly close
to correct time but more than 0.5s adrift from the time signalled by the GPS
board and ntpd is then started, the computer's clock comes into sync
correctly.

I'd be interested in trying to re-create your issue and then see it go away
by applying your patch.  Is there a simple setup that is guaranteed to make
the system fail to synchronise in the manner described in the bug report?

Richard Steedman
 

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] Cross Compile Can't Find arc4random

[Joe Walsh]

Has the fix for 2666 (http://bugs.ntp.org/show_bug.cgi?id=2666) affected 
cross-compile?

I tried to cross compile for ARMv7  today and got 
"ntp-4.2.8/libntp/ntp_crypto_rnd.c:93: undefined reference to `arc4random_buf'"

It appears I'm not the only one: 
http://unix.stackexchange.com/questions/179070/ntp-compilation-failed-without-ssl.

Has the 2666 fix introduced new requirements for arguments to ./configure when 
cross compiling?

Thanks,

Joe Walsh

This document and/or data may contain information proprietary to Scaled 
Composites. This document and/or data may contain technical data whose export 
is restricted by the Arms Export Control Act (22USC 2751 et seq) or the Export 
Administration Act of 1979, as amended (50 USC 2401 et seq). Violation of these 
laws is subject to severe civil and/or criminal penalties. This information, in 
any form, including attachments and exhibits, if found to meet the above 
referenced regulations, may not be exported, released or disclosed to foreign 
persons in the USA or abroad without first obtaining the proper export 
authority. Recipient shall include this notice, or such similar notice, with 
any reproduced portion of this document as appropriate.
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] Re. Sure GPS - PPS not working

[Richard Steedman]

Back in Dec 2013, Chris North wrote:

>I have managed to fix it, and it was a bit unexpected. When I first 
>installed the Sure, I used a USB connection and got it working OK. I then 
>used a Serial-USB adapter and was pleased to find that it passed DCD and 
>that PPS was working. The jitter was rather high, though - about 0.3 mS. I 
>bought a 2-port serial PCI card and a serial cable, and immediately had a 
>massive improvement in performance. Recently, however, I found that PPS had

>stopped working, as you have seen above.
>
>What I think happened was this: when I plugged in the new card it used the 
>standard Windows serial.sys, which I replaced with serialpps.sys. Now this 
>card is part of a range of multifunction cards that offer various I/O 
>interfaces. At some time Windows Update probably found the manufacturer's 
>drivers and installed them (automatically, or as an option that I just 
>accepted). The new driver ignores serial.sys and has its own software. So I

>poked around in the registry and changed the ImagePath for one of the
card's 
>new services to point to serialpps.sys. This seems to have fixed it. As I 
>don't use the COMn ports for anything else, I won't worry about possible 
>side-effects.

I am trying to get PPS working with a Sure GPS board connected to a laptop
running Win7.  I'm not getting very far and I'm guessing it's because
neither of the interface options available to me use the serial.sys driver:
- Direct connection of the Sure's USB port to the laptop means using the
  Silicon Labs 2102 chip on the Sure board and it uses drivers called
  silabenm.sys and silabser.sys
- Connecting the Sure board's RS-232 output to the laptop via a Prolific
  USB to serial adaptor means using the Prolific driver ser2pl.sys

Chris, if you still follow this listserv, could you tell me which
serial-to-USB adaptor you were using which successfully passed PPS to ntp?
I am not expecting the jitter to be any better than of the order of 1ms
since the USB interface samples the DCD line at 1024Hz but would still like
to try to get my setup working.

Thanks, Richard.

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Leap second to be introduced in June

[Mike Cook]

"Ceux qui sont prêts à abandonner une liberté essentielle pour obtenir une 
petite et provisoire sécurité, ne méritent ni liberté ni sécurité."
Benjimin Franklin



> Le 16 janv. 2015 à 08:42, Harlan Stenn  a écrit :
> 
> Terje Mathisen writes:
>> cmad...@cmadams.net (Chris Adams) wrote:
>>> Also, you can't properly represent future timestamps (necessary for some
>>> things) as seconds since an epoch, and that's pretty widely used.  By
>>> that I mean that the number of seconds between 2015-06-30 23:59:00 and
>>> 2015-07-01 00:00:00 has changed since last month.
> 
> The General Timestamp API handles this case, as those timestamps track
> the "version number" of the timescale.  If you specify "noon at (some
> future date)", an absolute timestamp, and between now and then some leap
> seconds are added, they'll be added here, too.

 How can we take into account an unknown number of leaps? I will listen 
attentively to your presentation in Bruxelles.
 I can see how it might be feasible…. But I will have to check with 
Schrodinger's cat first.

> 
>> And this is _exactly_ why it is always a bad idea to use (UTC) seconds 
>> for those future timestamps:
>> 
>> If you actually mean that something has to happen N seconds from now, 
>> that future timestamp has to be in TAI, since using UTC would obviously 
>> blow up across any leap second, right?
> 
> If one used a relative/difference timestamp for this, then we're in the
> same boat and we might need some sort of trigger or signal to indicate
> that a leap event has happened.
> 
> We're often in a similar boat though, if the clock "steps" during the
> interval this relative/difference timestamp covers.  This should
> arguably be an option for cron jobs and timer events.

cron is a notoriously bad scheduler. It only wakes up every minute to check the 
schedule tasks, so you can’t be sure of getting accurate execution times. 
It am not sure it is relevant either, as events are scheduled in terms of 
absolute times so will be correct whether or not a leap second is scheduled. 
Task execution on a callback, interval timer event is different. One scheduled 
for execution in 5 seconds, 3 seconds prior to a positive leap second will  get 
dispatched 4 TAI seconds later, but from a legal point of view will be dead on. 
 However if that is not already fixed, it could be.


> 
> H
> --
>> If you instead meant a calendar event, then you need a different 
>> timescale which is either Julian Day Number (JDN) or YMD, followed by 
>> either HMS or an offset into the day, followed by the applicable time zone.
>> 
>> Terje
>> 
>> -- 
>> - 
>> "almost all programming can be viewed as an exercise in caching"
>> 
>> ___
>> questions mailing list
>> questions@lists.ntp.org
>> http://lists.ntp.org/listinfo/questions
>> 
> ___
> questions mailing list
> questions@lists.ntp.org
> http://lists.ntp.org/listinfo/questions

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] Compiling 4.2.8 for windows.

[Young, David]

Greetings, I have a need to compile 4.2.8 for windows, and I'm having some 
problems and have questions.  I have followed documents like the hints.html 
linked off ntp.org.

Does the source tarball on the front page of ntp.org/downloads[1] actually 
compile on windows unmodified? I am perusing the list and see comments on the 
"NTP for Windows Not Branded" thread that refer to certain modifications 
required to get ntp to compile under windows, additional files or tweaks to .h 
and project files.  Are these modifications documented elsewhere or is there an 
[official] ntp.org download of a patch to apply these fixes?

Also, what version of visual studio is preferred for compiling ntp lately? I've 
seen some comments that the Visual Studio 2013 may not be a complete feature 
yet, but again the comments in the "NTP for Windows Not Branded" thread 
indicate that 2013 is currently in use.  I'd kind of prefer 2008 since that's 
what I happen to have in my environment already, especially if that version of 
the build is considered more stable. 

[1] http://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/ntp-4.2/ntp-4.2.8.tar.gz
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] UK pool server denying access

[Mike Cook]

This guy needs bouncing


> Le 30 déc. 2014 à 07:56, shalu.sysc...@gmail.com a écrit :
> 
> "Swimming pool Our company designs and installs deluxe indoor and outdoor 
> swimming pools in Central and Greater London areas.
> More at : http://www.swimmingpoolquotes.co.uk/pool-liners/
> 
> ___
> questions mailing list
> questions@lists.ntp.org
> http://lists.ntp.org/listinfo/questions

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] NTP recommendations for mid size network

[G9 - Nuno Pereira]

Hello,

 

Introduction:

At our company we have 50+ hosts, most of them are virtual (Xen) servers,
having a limited number of physical machines available to be an NTP server.

We're a small telecom company and we prefer to have the same time in all of
our hosts (time island), rather than an absolutely accurate time.

 

Current configuration:

Our normal config is with 2 prefered IPs (same server, not dedicated to NTP)
and 2 non-prefered external hosts (either from the pool or some selected
server). In some cases there aren't external hosts.

We just use server peers: no peer connections, no multicast and no broadcast.

This NTP server is also used by our internet clients.

 

We monitor 3 parameters of the NTP service: offset, reference peer (server)
and active peers.

 

But this configuration has some problems for us:

-  Once in a while we get warning offsets, mainly when one of our
external peers goes insane and we get 30+ ms offsets, when we normally have
less than 1 ms, having spikes that can go to 10-15 ms. With this, our goal of
having "the same time in all of our hosts" is compromised;

-  Also with little frequency one or many of our hosts loose a
reference peer, like yesterday, when 2 external peers (in the pool) got an
offset of ~1000 ms, having many of our hosts having 2 good peers (our internal
server) and 1 or 2 rejected peers (with ~1000 ms offset);

-  Obviously, if we do some maintenance in our server, of if it has a
problem, and then we get some problems in our ntp network, having clients
without reference clock and/or with bad offset when the server returns to
life;

-  Our goal of having excellent synchronization between our hosts
isn't achieved.

 

 

The question:

Given that, or ignoring what I've said, what are your recommendations?

. How many peers to configure for each client, at least? Only one (the
same for all)? or a higher number?

. Should we keep preferred servers, having alternatives?

. Should we use peer connections?

. Are broadcast or multicast better options?

. Could we use virtual servers as internal alternatives in the
network?

. Pool servers aren't available everywhere, but are they good options?

 

Our server is configured with 4-5 delay stratum 1 external servers with 60-70
ms of delay (preferred), and 2 or 3 external servers with stratum 2+ with <5
ms of delay (not preferred).

Is that a good option?

 

Thank you all,

Nuno Pereira

Software engineer at G9Telecom

 

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Nice fanless high-perf NTP server: Fitlet!

[Gene Heskett]

On Thursday, January 15, 2015 08:41:17 AM Terje Mathisen did opine
And Gene did reply:
> http://linuxgizmos.com/tiny-fanless-mini-pc-runs-linux-on-quad-core-am
> d-soc/
> 
> This little guy starts at $129 and includes a serial port which should
> make it trivial to attach a Sure GPS board.
> 
> With a dual or quad 64-bit CPU, both SATA and SD storage connectors
> and versions that support multiple Gbit/s Ethernet ports, it would
> seem to be a nice NTPD startum 1 server.
> 
> Terje

With the proper I/O card in that weird shape format that would give the 
equ of one of the Mesanet cards such as a 5i25, this might also be a 
great bit of kit for the entry level CNC machining crowd.  We are 
currently using a pair of the D525MW Intel dual core atom based boards, 
which does come with a header for a parport, one setup for software 
stepper driving a 4 axis mill, and one with a 5i25 card driving a lathe.  
But the D525MW  was disco'd better than a year ago.

Does anyone know what the IRQ latency is?  It might be competition for 
the beaglebone black with its mass of programmable I/O.  That CNC 
project, based on LinuxCNC, which you can google, is known as MachineKIT.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Leap second to be introduced in June

[Mike Cook]

strange response!

> Le 11 janv. 2015 à 21:18, Paul  a écrit :
> 
> Why do folks mention leap seconds on this list?

  part of the NTP protocol deals with the scheduling insertion/deletion of leap 
seconds.

> Why do people point to leap-seconds.NTPtimestamp instead of just
> leap-seconds.list?

  leap-seconds.list is not the file itself, but a symbolic link, which in 
itself contains no relevant information other than the pathname, in this case 
relative, to the actual file.
  The symbolic link leap-seconds.list does not exist on some repositories of 
the information, for example on the navy server tyco.
  Using the full timestamped name is also the only way of unambiguously 
identifying this data. The time stamp differs on different sources. 

> 
> My five line leap second file with comments and one extra line for
> (completely unnecessary) context.
> 
> #$  3629404800
> #@  3660249600
> 3550089600  35  # 1 Jul 2012
> 3644697600  36  # 1 Jul 2015
> #h  6eb5f274 cb8c4f5d 6ac15b69 6b095017 f219e7c
> ___
> questions mailing list
> questions@lists.ntp.org
> http://lists.ntp.org/listinfo/questions

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] CVE-2014-9296 and xntp3

[Kevin Fowler]

Does this vulnerability apply to xntp3 versions, in particular to v5.93?
There is an xntpd/ntp_proto.c file in that release, but the code is
substantially different from ntp4, so I am not clear if the vulnerability
actually applies.

Yes - I realize how ancient this release is...:-)
Thanks,
Kevin
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] What to do for clients less than 4.2.8?

[Gene Heskett]

On Tuesday 23 December 2014 00:47:14 William Unruh did opine
And Gene did reply:
> On 2014-12-23, Harlan Stenn  wrote:
> > Martin Burnicki writes:
> >> Rob wrote:
> >> > Martin Burnicki  wrote:
> >> >> And of course, the information flow was really bad here, so that
> >> >> it is very hard to figure out which systems are affected.
> >> > 
> >> > Indeed.  Only after 3 days there was a statement on the pool
> >> > mailing list that the problem only affected servers that can be
> >> > queried.  Well, that had better be stated in the original
> >> > release, so that 99.9% of the users of ntpd could immediately
> >> > move it to "not for me" and not be worried.
> >> 
> >> Yes. I agree that this information should have been available
> >> immediately with the first alert. This would have avoided much
> >> trouble.
> > 
> > And if we had realized all of this at first alert we would have.
> > 
> > The announcement came out 3 days' later than I wanted.  I'd been
> > working on this for 2 solid weeks by then.
> 
> Thank you very much.

I'll certainly second that. 3 days after it went public did seem like a 
very short time.  To all who have been working on it, many thanks.

And, the fix has made its way to the 10.04.4 LTS repo's already, so my 
build problem is solved.

And I could cut the traffic to the servers by 2/3rds if I could make this 
machine a server for my local network.  But thats a separate question I'll 
ask once the moderator clears my posts.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] How the "peer candidate" is selected?

[Gene Heskett]

On Monday 29 December 2014 08:52:48 Nomen Nescio did opine
And Gene did reply:
> chrony rulez
> 
> shalu.sysc...@gmail.com wrote:
> > "Swimming pool Our company designs and installs deluxe indoor and
> > outdoor swimming pools in Central and Greater London areas. More at
> > : http://www.swimmingpoolquotes.co.uk/swimming-pool-maintenance/

How come you let spam like this thru, but I still cannot post a week after 
subscribing (and looking at several messages that I have to be moderator 
approved when I have tried)
 
> ___
> questions mailing list
> questions@lists.ntp.org
> http://lists.ntp.org/listinfo/questions


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] flash=0 , sel_reject

[Mike Cook]

> Le 3 déc. 2014 à 02:37, ganeshsubramon...@gmail.com a écrit :
> 
> Is there any scenario where the flash code show 00,ok, but the condition will 
> show server rejected ?
> more details on 
> http://lists.ntp.org/pipermail/questions/2014-December/039065.html
> 
> Hope I am not posting in the wrong forum.

It’s the right forum.

I did trawl bugzilla for the symptom but did not find a match. There are issues 
decoding flash when ntpq version and ntpd version are not matched and there are 
differences in bit interpretation introduced over time but a zero report 
doesn’t appear to fit those. 
If you are able to reproduce the problem with the latest dev code, I would open 
a bug at .

> ___
> questions mailing list
> questions@lists.ntp.org
> http://lists.ntp.org/listinfo/questions

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] Transmit timestamp older than receive timestamp...?

[marco danti]

Hi, looking at some sniffer traces I noticed NTP packets containing confusing 
timestamps like this:
Receive Timestamp : Jul 26, 2012 06:49:13.652482000 UTC   (T2)
Transmit Timestamp: Jul 26, 2012 06:49:13.652217000 UTC   (T3)

According to the above timestamps, that packet was transmitted *before* it was 
received.The messages sent by the server in question have correct timestamps 
most of the time, but every once in a while, a packet show up with T3 < T2.
I can't figure out  what could possibly explain this curious behaviour; on the 
other side, I wonder what would a client do upon reception of such a packet. My 
best guess is that it should be discarded.




___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Number of Stratum 1 & Stratum 2 Peers

[Mike Cook]

>> 
>>> Three are fine, as long as only one dies or goes nuts.
>> 
>> Again, define "goes nuts". You don't seem to like the term 
>> "falseticker", so how do you define "goes nuts"? If one "goes nuts" or 
>> even goes offline, if the remaining two do not agree then it is like 
>> having no server at all.
> 
> No, it is like having two, with one being out. 
> falseticker is a term with a very specific internal definition. Thus a
> server whose time is right on UTC could be a falseticker, because the
> other two servers were both exactly 3 days out, with tiny jitter estimates. 
> I would say then that you had two servers going nuts, and one good, even
> though ntpd would say there were two good and one false ticker. 

In fact this does not happen. I just tested the hypothesis.
What happens depends on how the two wayward get there exaggerated offset:
a) someone,something resets the date:
result: ntp on both those servers crashes due to the panic_stop limit.

  So in this case  the client has only one reference and continues using that. 
It is not flagged as a falsticker.
  That is normal.
   
b) someone restarts ntp on the servers with the wrong date. Here the servers 
ntpd has no way of knowing that it has bad time and so continues serving 
normally. 
On the client. The running ntp sees immediately a huge offset and huge 
jitter.

Tue Dec  9 13:15:04 CET 2014
 remote   refid  st t when poll reach   delay   offset  jitter
==
*192.168.1.15.GPS1.   1 u  320   64  3600.5490.040   0.037
+192.168.1.16.GPS2.   1 u   37   64  3770.6060.006   0.028
+192.168.1.17.GPS1.   1 u  309   64  3600.5760.027   0.025
Tue Dec  9 13:16:08 CET 2014
 remote   refid  st t when poll reach   delay   offset  jitter
==
 192.168.1.15.GPS1.   1 u   55   64  3410.5650.042 9660780
*192.168.1.16.GPS2.   1 u   37   64  3770.6060.006   0.024
 192.168.1.17.GPS1.   1 u   42   64  3410.5790.041 9660773

After 5 mins the client is unable to resolve this and declares all clock 
falsetickers and then panics. I did not have ntpd in debug mode here, but it is 
reasonable to assume that it panics due to the selected clock being too far out 
and hitting the panic limit.

Tue Dec  9 13:23:37 CET 2014
 remote   refid  st t when poll reach   delay   offset  jitter
==
 192.168.1.15.GPS1.   1 u   45   64  3770.596  -255600 155.539
*192.168.1.16.GPS2.   1 u   25   64  3770.6140.024   0.008
 192.168.1.17.GPS1.   1 u   30   64  3770.583  -255600  52.806
Tue Dec  9 13:24:41 CET 2014
 remote   refid  st t when poll reach   delay   offset  jitter
==
x192.168.1.15.GPS1.   1 u   43   64  3770.596  -255600 179.609
x192.168.1.16.GPS2.   1 u   23   64  3770.6140.024   0.008
x192.168.1.17.GPS1.   1 u   27   64  3770.618  -255599   6.009
/usr/local/bin/ntpq: read: Connection refused
Tue Dec  9 13:25:45 CET 2014
/usr/local/bin/ntpq: read: Connection refused

This is exactly what happens if the client is restarted.

clock_filter: n 1 off -255599.997967 del 0.000662 dsp 7.937502 jit 0.02
select: endpoint -1 -255600.000806
select: endpoint  1 -255599.995128
select: survivor 192.168.1.17 0.002839
select: combine offset -255599.997967134 jitter 0.0
event at 1 192.168.1.17 903a 8a sys_peer
clock_update: at 1 sample 1 associd 18641
event at 1 0.0.0.0 c617 07 panic_stop -255600 s; set clock manually within 1000 
s.
event at 1 0.0.0.0 c61d 0d kern kernel time sync disabled

So ntp does NOT continue in your test case. Your case may be better if the time 
difference is less than the panic limit. Say if the two servers do not insert a 
leap second, but the  « correct » one does. I’ll try that for my own 
satisfaction if I can figure how to do it.

Like

> 
>> 
>> 
>> Brian Utterback
> 
> ___
> questions mailing list
> questions@lists.ntp.org
> http://lists.ntp.org/listinfo/questions

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] new 4.2.8 build on older buntu

[Gene Heskett]

Greetings all;

1. Several of these questions below really ought to be in the not built 
man pages, or in the tarballs html files, but are not.

2. Where does it expect to find its ntp.conf file?  On old buntu, its 
/etc/default/ntp where ntp is the file.  This is the location and filename 
used in the /etc/init.d/ntp control script.

3. I first built it with --enable-clockctl, but this is failing and the 
ntpq responses are showing a steady negative drift.

So next I tried configureing it with a few more of the usual suspects 
enabled:
./configure --enable-clockctl --enable-linuxcaps --enable-accurate-adjtime

But the make then bails out:

ntpd.c:108:29: error: sys/capability.h: No such file or directory
ntpd.c: In function ‘ntpdmain’:
ntpd.c:970: error: ‘cap_t’ undeclared (first use in this function)
ntpd.c:970: error: (Each undeclared identifier is reported only once
ntpd.c:970: error: for each function it appears in.)
ntpd.c:970: error: expected ‘;’ before ‘caps’
ntpd.c:976: error: ‘caps’ undeclared (first use in this function)
ntpd.c:976: warning: implicit declaration of function ‘cap_from_text’
ntpd.c:983: warning: implicit declaration of function ‘cap_set_proc’
ntpd.c:988: warning: implicit declaration of function ‘cap_free’
make[3]: *** [ntpd.o] Error 1
make[3]: Leaving directory `/usr/src/ntp-4.2.8/ntpd'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/usr/src/ntp-4.2.8/ntpd'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/ntp-4.2.8'
make: *** [all] Error 2

This file exists in several locations, the most obvious being:
/usr/include/linux/capability.h

This looks to be a correctable by a configuration argument, but which one?

Thanks everybody.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] moving from ntpdc to ntpq

[Richard]

What is ntpq's equivelant of -c "addpeer "   and  -c "unconfig
"  ?


I just upgraded from ntp 4.2.6 to 4.2.8 and ntpdc isn't connecting to my
local ntpd. According to the ntpdc man page:

"ntpdc is deprecated. Please use ntpq(1) instead - it can do everything
ntpdc used to do,"


In ntpq how do I do the equivalent of ntpdc's -c "addpeer "  or -c
"unconfig" commands?


Here is part of what previously did with ntpdc:

/usr/sbin/ntpc -4 -c "keyid 5" -c "passwd  mypassword" \
 -c "addpeer   "  localhost


___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] server reject reason

[ganesh subramonian]

Hi,

I see that randomly the ntp condition says reject (with configuration below). 
Can someone help me understand why ?
I thought that if there is a "reject" it is always accompanied by a non-zero 
flash code ?

ntpq> as

ind assid status  conf reach auth condition  last_event cnt
===
  1 55971  901a   yes   yes  
none    reject    sys_peer  1
  2 55972  8811   yes  none  
none    reject    mobilize  1
  3 55973  9094   yes   yes  
none    reject   reachable  9

ntpq> rv 55971
associd=55971 status=901a conf, reach, sel_reject, 1 event, sys_peer,
srcadr=10.255.251.133, srcport=123, dstadr=10.255.252.190, dstport=123,
leap=00, stratum=5, precision=-10, rootdelay=39.810, rootdisp=31.509,
refid=10.55.6.1,
reftime=d81f76f7.f88179f8  Tue, Nov 25 2014 21:45:27.970,
rec=d81f78ec.c321c518  Tue, Nov 25 2014 21:53:48.762, reach=377,
unreach=0, hmode=3, pmode=4, hpoll=9, ppoll=9, headway=0, flash=00 ok,
keyid=0, offset=5.572, delay=47.398, dispersion=21.375, jitter=11.026,
xleave=-0.118,
filtdelay=    95.51  119.15   83.34   
47.40   92.38   78.00  107.02   72.85,
filtoffset=    2.11   -3.60  
-11.89    5.57  -13.18    
8.22    2.02   -3.29,
filtdisp=  1.95    9.72   
17.57   25.41   33.38   41.07   
49.08   57.20

ntpd -n -U 180 -c /etc/ntpd.conf -A -p /tmp/ntpd.pid

server 10.255.251.133 iburst prefer minpoll 4 maxpoll 9
enable calibrate
tinker panic 2112912000 stepout 128
broadcast 127.1.255.255 minpoll 4
server 127.127.1.1 minpoll 4 maxpoll 5
fudge 127.127.1.1 stratum 6
interface listen all
logfile /tmp/ntpd.log
logconfig +allinfo +allevents +allstatistics +allstatus
driftfile /tmp/ntpd.drift

thanks
ganesh

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] server reject reason

[ganesh subramonian]

Hi,



I see that randomly  the ntp condition says reject (with configuration below).

Can someone help me understand why ?

I thought that if there is a "reject" it is always accompanied by a non-zero 
flash code ?



ntpq> as



ind assid status  conf reach auth condition  last_event cnt

===

  1 55971  901a   yes   yes  nonerejectsys_peer  1

  2 55972  8811   yes  none  nonerejectmobilize  1

  3 55973  9094   yes   yes  nonereject   reachable  9



ntpq> rv 55971

associd=55971 status=901a conf, reach, sel_reject, 1 event, sys_peer,

srcadr=10.255.251.133, srcport=123, dstadr=10.255.252.190, dstport=123,

leap=00, stratum=5, precision=-10, rootdelay=39.810, rootdisp=31.509,

refid=10.55.6.1,

reftime=d81f76f7.f88179f8  Tue, Nov 25 2014 21:45:27.970,

rec=d81f78ec.c321c518  Tue, Nov 25 2014 21:53:48.762, reach=377,

unreach=0, hmode=3, pmode=4, hpoll=9, ppoll=9, headway=0, flash=00 ok,

keyid=0, offset=5.572, delay=47.398, dispersion=21.375, jitter=11.026,

xleave=-0.118,

filtdelay=95.51  119.15   83.34   47.40   92.38   78.00  107.02   72.85,

filtoffset=2.11   -3.60  -11.895.57  -13.188.222.02   -3.29,

filtdisp=  1.959.72   17.57   25.41   33.38   41.07   49.08   57.20



ntpd -n -U 180 -c /etc/ntpd.conf -A -p /tmp/ntpd.pid



server 10.255.251.133 iburst prefer minpoll 4 maxpoll 9

enable calibrate

tinker panic 2112912000 stepout 128

broadcast 127.1.255.255 minpoll 4

server 127.127.1.1 minpoll 4 maxpoll 5

fudge 127.127.1.1 stratum 6

interface listen all

logfile /tmp/ntpd.log

logconfig +allinfo +allevents +allstatistics +allstatus

driftfile /tmp/ntpd.drift



thanks

ganesh
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] Remove NTP server during runtime

[Adrian Nedelcu]

Hi,

I was wondering if it's possible to temporarily remove a server that was
set in /etc/ntp.conf, during runtime (using ntpq). Also how can I change
the minpoll or maxpoll of an already configured NTP server during runtime
and also turn it into a prefered server.

I've tried ntpq -i 
 :config server  minpoll 4 maxpoll 4

The command returns configuration succeeded, but the polling interval does
not change to 16 seconds.

Regards,
Adrian
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] ntp Segmentation fault

[Shai Ben-Naphtali]

Hello,

I didn't get any response. Was the message not approved?


---
Shai


On Mon, Oct 27, 2014 at 9:52 AM, Shai Ben-Naphtali  wrote:

> Hello,
>
> I've got a problem with one of my servers, where it doesn't take more then
> 10min or so for ntpd to crash with a Segmentation fault. I tried looking
> for a solution online and found nothing related to my error.
>
> I would like to submit a bug to support but since the debug log contains a
> lot of IPs, how do I submit the log without revealing confidential
> information (ie. IPs)?
>
> Thanks in advance!
>
> ---
> Shai
>
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] problem with pool directive?

[Mike Cook]

Sorry if this is a dup. My first went through in a non text format. Just 
upgraded to Yosemite.

> Le 12 nov. 2014 à 00:15, Brian Utterback  a écrit 
> :
> 
> I believe that the number of pool servers used is determined by the minclock 
> and maxclock parameters.
> 


Hmmm. Good idea, but looks like there may be work required. Results of a quick 
test on a cubietruck with :

mike@cubieez:~$ ntpq --version
ntpq 4.2.7p452@1.2483 Fri Jul 18 15:35:11 UTC 2014 (2)

mike@cubieez:~$ ntpq -pn
 remote   refid  st t when poll reach   delay   offset  jitter
==
+192.168.1.23.GPS.1 u   33   64  3770.429   -0.031   0.005
 0.europe.pool.n .POOL.  16 p-   6400.0000.000   0.002
*192.168.1.4 .PPS1.   1 u   64   64  3770.6480.027   0.024
+192.168.1.15.GPS1.   1 u   24   64  3770.5950.068   0.031
-149.210.163.34  80.94.65.10  2 u1  128  377   22.0701.290   0.013
-212.51.144.44   .PPS.1 u  105  128  377   32.5210.185   0.024
-212.70.148.17   109.160.0.1543 u   78  128  377   51.914   -1.027   0.077
-46.4.205.42 192.53.103.108   2 u  104  128  377   33.453   -2.408   0.031
-91.240.0.5  212.82.32.15 2 u   36  128  377   25.9435.495   0.106

  add our limiter and restart ntpd

mike@cubieez:~$ sudo vi /etc/ntp.conf
[sudo] password for mike: 
mike@cubieez:~$ sudo /etc/init.d/ntp restart
[sudo] password for mike: 
[ ok ] Stopping NTP server: ntpd.
[ ok ] Starting NTP server: ntpd.
mike@cubieez:~$ ntpq -pn
 remote   refid  st t when poll reach   delay   offset  jitter
==
+192.168.1.23.GPS.1 u6   16   370.193   -0.017   0.038
 0.europe.pool.n .POOL.  16 p-   6400.0000.000   0.002
*192.168.1.4 .PPS1.   1 u7   16   370.498   -0.055   0.062
+192.168.1.15.GPS1.   1 u5   16   370.5780.065   0.036
-62.75.236.38192.53.103.108   2 u2   643   26.994   -1.179   0.091
-193.225.118.163 121.131.112.137  2 u   56   641   43.189   -0.369   0.441
mike@cubieez:~$ 

  so tos maxclock 5 limits those allocated as Brian suggests, but removing 
access to a local clock leads to instability from which the pool allocations do 
not recover. 

mike@cubieez:~$ # pull a local clock
mike@cubieez:~$ 
mike@cubieez:~$ bin/ntpchk
NOTICE: using /usr/local/bin/ntpq to query ntpd.

ntp is up and running - checking peer status
Wed Nov 12 08:50:27 CET 2014
 remote   refid  st t when poll reach   delay   offset  jitter
==
+192.168.1.23.GPS.1 u   19   32  3770.4500.008   0.022
 0.europe.pool.n .POOL.  16 p-   6400.0000.000   0.002
*192.168.1.4 .PPS1.   1 u4   32  3770.6290.022   0.053
+192.168.1.15.GPS1.   1 u2   32  3770.6180.055   0.034
-62.75.236.38192.53.103.108   2 u   23   64  177   27.043   -1.064   0.065
-193.225.118.163 165.94.197.402 u   24   64  177   43.191   -0.371   0.543
Wed Nov 12 08:51:32 CET 2014
 remote   refid  st t when poll reach   delay   offset  jitter
==
+192.168.1.23.GPS.1 u   51   32  3760.450   -0.044   0.045
 0.europe.pool.n .POOL.  16 p-   6400.0000.000   0.002
*192.168.1.4 .PPS1.   1 u4   32  3770.6290.022   0.045
+192.168.1.15.GPS1.   1 u2   32  3770.6180.055   0.043
-62.75.236.38192.53.103.108   2 u   20   64  377   27.030   -1.169   0.081
-193.225.118.163 165.94.197.402 u   22   64  377   43.173   -0.369   0.483

  So 192.168.1.23 is down and unreachable.


Wed Nov 12 08:59:01 CET 2014
 remote   refid  st t when poll reach   delay   offset  jitter
==
 192.168.1.23.GPS.1 u  500   6400.450   -0.044   0.000
 0.europe.pool.n .POOL.  16 p-   6400.0000.000   0.002
*192.168.1.4 .PPS1.   1 u3   32  3770.6260.007   0.008
+192.168.1.15.GPS1.   1 u   30   32  3770.6130.003   0.015
+139.112.153.37  146.213.3.1812 u   17   647   45.515   -3.319   0.214
-147.231.100.5   147.231.100.11   2 u   18   647   51.684  -10.521   0.300
^C
mike@cubieez:~$ #   this appears stable

 An extra pool server is not allocated to fill the hole. This may be as 
designed as the association has not disappeared but ideally one would like the 
hole filled with something that works.
But worse is to come.

Nov 12 09:06:33 cubieez ntpd[16279]: 147.231.100.5 local addr 192.168.1.124 -> 

Nov 12

[ntp:questions] NTP startup question

[scherniak]

I was messing around with my NTP configuration, and I wanted to make sure that 
the server changes were valid, so I would make sure that NTP was down, jump the 
clock, change the configuration, and restart NTP. The first 2 times I did this, 
the clock synched within a matter of seconds. The third time I did this the 
clock did not synch for 7+ minutes. Does the repetitive starts cause this to 
happen, or are there other situations when NTP will not do an initial synch 
quickly. To the best of my knowledge, the servers configured were all available 
during this period. I did not see anything unusual in the /var/log/ntp. I am 
running redhat RHEL 6.5.

Thanks,
Steve
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] ntp Segmentation fault

[Shai Ben-Naphtali]

Hello,

I've got a problem with one of my servers, where it doesn't take more then
10min or so for ntpd to crash with a Segmentation fault. I tried looking
for a solution online and found nothing related to my error.

I would like to submit a bug to support but since the debug log contains a
lot of IPs, how do I submit the log without revealing confidential
information (ie. IPs)?

Thanks in advance!

---
Shai
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] problem with pool directive?

[Mike Cook]

> Le 12 nov. 2014 à 00:15, Brian Utterback  a écrit 
> :
> 
> I believe that the number of pool servers used is determined by the minclock 
> and maxclock parameters.
> 

Hmmm. Good idea, but looks like there may be work required. Results of a quick 
test on a cubietruck with :

mike@cubieez:~$ ntpq --version
ntpq 4.2.7p452@1.2483 Fri Jul 18 15:35:11 UTC 2014 (2)

mike@cubieez:~$ ntpq -pn
 remote   refid  st t when poll reach   delay   offset  jitter
==
+192.168.1.23.GPS.1 u   33   64  3770.429   -0.031   0.005
 0.europe.pool.n .POOL.  16 p-   6400.0000.000   0.002
*192.168.1.4 .PPS1.   1 u   64   64  3770.6480.027   0.024
+192.168.1.15.GPS1.   1 u   24   64  3770.5950.068   0.031
-149.210.163.34  80.94.65.10  2 u1  128  377   22.0701.290   0.013
-212.51.144.44   .PPS.1 u  105  128  377   32.5210.185   0.024
-212.70.148.17   109.160.0.1543 u   78  128  377   51.914   -1.027   0.077
-46.4.205.42 192.53.103.108   2 u  104  128  377   33.453   -2.408   0.031
-91.240.0.5  212.82.32.15 2 u   36  128  377   25.9435.495   0.106

  add our limiter and restart ntpd

mike@cubieez:~$ sudo vi /etc/ntp.conf
[sudo] password for mike: 
mike@cubieez:~$ sudo /etc/init.d/ntp restart
[sudo] password for mike: 
[ ok ] Stopping NTP server: ntpd.
[ ok ] Starting NTP server: ntpd.
mike@cubieez:~$ ntpq -pn
 remote   refid  st t when poll reach   delay   offset  jitter
==
+192.168.1.23.GPS.1 u6   16   370.193   -0.017   0.038
 0.europe.pool.n .POOL.  16 p-   6400.0000.000   0.002
*192.168.1.4 .PPS1.   1 u7   16   370.498   -0.055   0.062
+192.168.1.15.GPS1.   1 u5   16   370.5780.065   0.036
-62.75.236.38192.53.103.108   2 u2   643   26.994   -1.179   0.091
-193.225.118.163 121.131.112.137  2 u   56   641   43.189   -0.369   0.441
mike@cubieez:~$ 

  so tos maxclock 5 limits those allocated as Brian suggests, but removing 
access to a local clock leads to instability from which the pool allocations do 
not recover. 

mike@cubieez:~$ # pull a local clock
mike@cubieez:~$ 
mike@cubieez:~$ bin/ntpchk
NOTICE: using /usr/local/bin/ntpq to query ntpd.

ntp is up and running - checking peer status
Wed Nov 12 08:50:27 CET 2014
 remote   refid  st t when poll reach   delay   offset  jitter
==
+192.168.1.23.GPS.1 u   19   32  3770.4500.008   0.022
 0.europe.pool.n .POOL.  16 p-   6400.0000.000   0.002
*192.168.1.4 .PPS1.   1 u4   32  3770.6290.022   0.053
+192.168.1.15.GPS1.   1 u2   32  3770.6180.055   0.034
-62.75.236.38192.53.103.108   2 u   23   64  177   27.043   -1.064   0.065
-193.225.118.163 165.94.197.402 u   24   64  177   43.191   -0.371   0.543
Wed Nov 12 08:51:32 CET 2014
 remote   refid  st t when poll reach   delay   offset  jitter
==
+192.168.1.23.GPS.1 u   51   32  3760.450   -0.044   0.045
 0.europe.pool.n .POOL.  16 p-   6400.0000.000   0.002
*192.168.1.4 .PPS1.   1 u4   32  3770.6290.022   0.045
+192.168.1.15.GPS1.   1 u2   32  3770.6180.055   0.043
-62.75.236.38192.53.103.108   2 u   20   64  377   27.030   -1.169   0.081
-193.225.118.163 165.94.197.402 u   22   64  377   43.173   -0.369   0.483

  So 192.168.1.23 is down and unreachable.


Wed Nov 12 08:59:01 CET 2014
 remote   refid  st t when poll reach   delay   offset  jitter
==
 192.168.1.23.GPS.1 u  500   6400.450   -0.044   0.000
 0.europe.pool.n .POOL.  16 p-   6400.0000.000   0.002
*192.168.1.4 .PPS1.   1 u3   32  3770.6260.007   0.008
+192.168.1.15.GPS1.   1 u   30   32  3770.6130.003   0.015
+139.112.153.37  146.213.3.1812 u   17   647   45.515   -3.319   0.214
-147.231.100.5   147.231.100.11   2 u   18   647   51.684  -10.521   0.300
^C
mike@cubieez:~$ #   this appears stable

 An extra pool server is not allocated to fill the hole. This may be as 
designed as the association has not disappeared but ideally one would like the 
hole filled with something that works.
But worse is to come.

Nov 12 09:06:33 cubieez ntpd[16279]: 147.231.100.5 local addr 192.168.1.124 -> 

Nov 12 09:12:19 cubieez ntpd[16279]: 139.112.153.37 local addr 192.168.1.124 -> 


Wed Nov 12 09:05:59 

[ntp:questions] NTPD not associating

[Martin Beynon]

Hi All,

I am running ntpd version:
$ ntpd --version
ntpd 4.2.6p5
ntpd 4.2.6p5@1.2349 Mon Sep  1 10:44:08 UTC 2014 (1)

The computer has an Ethernet interface and a WiFi interface. NTP works fine
when connected to the internet via the Ethernet interface, but when the
system boots without Ethernet and uses WiFi ntpd does not sync the time (no
matter how long I wait) - note everything else works, just ntpd:

$ ntpq -p
 remote   refid  st t when poll reach   delay   offset
jitter
==
 0.pool.ntp.org  .INIT.  16 --   6400.0000.000
0.000
 lafkor.de   .INIT.  16 --   6400.0000.000
0.000
 2.pool.ntp.org  .INIT.  16 --   6400.0000.000
0.000
 3.pool.ntp.org  .INIT.  16 --   6400.0000.000
0.000


Starting the daemon in debug mode (ntpd -D 4) produces the following output:
ntpd 4.2.6p5@1.2349 Mon Sep  1 10:44:08 UTC 2014 (1)
filegen_register(peerstats, 0x8a400)
filegen_register(loopstats, 0x8a3c4)
filegen_register(clockstats, 0x8a3ec)
filegen_register(rawstats, 0x8a3d8)
filegen_register(sysstats, 0x8a420)
filegen_register(protostats, 0x8a3b0)
sntp[316]: Started sntp
 8 Oct 11:15:29 ntpd[294]: set_process_priority: Leave priority alone:
priority_done is <2>
 8 Oct 11:15:29 ntpd[294]: proto: precision = 7.250 usec
loop_config: item 1 freq 0.00
event at 0 0.0.0.0 c01d 0d kern kernel time sync enabled
yylex: lexeme 'driftfile' -> T_Driftfile
yylex: lexeme '/etc/ntp.drift' -> T_String

yylex: lexeme 'server' -> T_Server
yylex: lexeme '0.pool.ntp.org' -> T_String

yylex: lexeme 'server' -> T_Server
yylex: lexeme '1.pool.ntp.org' -> T_String

yylex: lexeme 'server' -> T_Server
yylex: lexeme '2.pool.ntp.org' -> T_String

yylex: lexeme 'server' -> T_Server
yylex: lexeme '3.pool.ntp.org' -> T_String

Finished Parsing!!
create_sockets(123)
interface_action: wildcard 0.0.0.0 default wildcard drop
 8 Oct 11:15:29 ntpd[294]: ntp_io: estimated max descriptors: 1024, initial
socket boundary: 16
setsockopt SO_TIMESTAMP enabled on fd 16 address 0.0.0.0
bind(16) AF_INET, addr 0.0.0.0%0#123, flags 0x89
flags for fd 16: 0x802
Searching for addr 0.0.0.0 in list of addresses - NOT FOUND
Added addr 0.0.0.0 to list of addresses
 8 Oct 11:15:29 ntpd[294]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
created interface #0: fd=16, bfd=-1, name=v4wildcard, flags=0x89,
ifindex=0, sin=0.0.0.0, bcast=0.0.0.0, mask=255.255.255.255, Disabled:
update_interfaces(123)
interface_action: lo 127.0.0.1 IPv4 loopback - listen
examining interface #0: fd=-1, bfd=-1, name=lo, flags=0x5, ifindex=0,
sin=127.0.0.1, mask=255.0.0.0, Enabled:
Searching for addr 127.0.0.1 in list of addresses - NOT FOUND
create_interface(127.0.0.1#123)
set SO_REUSEADDR to on on 0.0.0.0
set SO_REUSEADDR to off on 0.0.0.0
setsockopt SO_TIMESTAMP enabled on fd 17 address 127.0.0.1
bind(17) AF_INET, addr 127.0.0.1%0#123, flags 0x5
flags for fd 17: 0x802
 8 Oct 11:15:29 ntpd[294]: Listen normally on 1 lo 127.0.0.1 UDP 123
restrict: op 1 addr 127.0.0.1 mask 255.255.255.255 mflags 3000 flags
0001
Searching for addr 127.0.0.1 in list of addresses - NOT FOUND
Added addr 127.0.0.1 to list of addresses
created interface #1: fd=17, bfd=-1, name=lo, flags=0x5, ifindex=0,
sin=127.0.0.1, mask=255.0.0.0, Enabled:
refreshing peers due to new addr 127.0.0.1
updating interface #1: fd=17, bfd=-1, name=lo, flags=0x5, ifindex=0,
sin=127.0.0.1, mask=255.0.0.0, Enabled: new - created
interface_action: wlan0 192.168.1.28 default listen
examining interface #0: fd=-1, bfd=-1, name=wlan0, flags=0x19, ifindex=0,
sin=192.168.1.28, bcast=0.0.0.0, mask=255.255.255.0, Enabled:
Searching for addr 192.168.1.28 in list of addresses - NOT FOUND
create_interface(192.168.1.28#123)
set SO_REUSEADDR to on on 0.0.0.0
set SO_REUSEADDR to off on 0.0.0.0
setsockopt SO_TIMESTAMP enabled on fd 18 address 192.168.1.28
bind(18) AF_INET, addr 192.168.1.28%0#123, flags 0x19
flags for fd 18: 0x802
 8 Oct 11:15:29 ntpd[294]: Listen normally on 2 wlan0 192.168.1.28 UDP 123
restrict: op 1 addr 192.168.1.28 mask 255.255.255.255 mflags 3000 flags
0001
Searching for addr 192.168.1.28 in list of addresses - NOT FOUND
Added addr 192.168.1.28 to list of addresses
add_interface mcast-capable 192.168.1.28
added 192.168.1.28 to head of IPv4 multicast-capable unicast local address
list
created interface #2: fd=18, bfd=-1, name=wlan0, flags=0x19, ifindex=0,
sin=192.168.1.28, bcast=0.0.0.0, mask=255.255.255.0, Enabled:
refreshing peers due to new addr 192.168.1.28
updating interface #2: fd=18, bfd=-1, name=wlan0, flags=0x19, ifindex=0,
sin=192.168.1.28, bcast=0.0.0.0, mask=255.255.255.0, Enabled: new - created
 8 Oct 11:15:29 ntpd[294]: peers refreshed
setting SO_REUSEADDR on wlan0@192.168.1.28 to off
setting SO_REUSEADDR on lo@127.0.0.1 to off
create_sockets: Total interfaces = 3
 8 Oct 11:15:29 ntpd[

Re: [ntp:questions] NTP server not reducing polling interval on upstream hosts

[Hrant Dadivanyan]

 [snip]
> >I could put my current version binaries into a Zip file and upload it 
> >for you to try, if you like.
> 
> I just tried that, with the binaries of ntp-4.2.7p364_2 and
> ntp-devel-4.2.7.p411.
> Ntp crashed and burned when attempting to start - it looks like they
> rely on later libraries, which only a proper install will give me.
> 

Using libmap (see man libmap.conf for details) you can tell ntpd to load
existing version library instead of expected, but missing one.

First, check with ldd what libraries ntpd depends on and which one(s) it's
unable to find/load. Then look for existing version of that library in /lib,
/usr/lib and /usr/local/lib . And finally edit /etc/libmap.conf .

HTH,
Hrant

> I'm glad I'm testing all this in a virtual instance of the real
> machine, instead of the real machine itself.
> 
> ___
> questions mailing list
> questions@lists.ntp.org
> http://lists.ntp.org/listinfo/questions

-- 
Hrant Dadivanyan (aka Ran d'Adi)hrant(at)dadivanyan.net
/* "Feci quod potui, faciant meliora potentes." */   ran(at)psg.com
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] NTP client sync not happened until it restarts, when there was a network failure for some time.

[Bollipally, Ramgopal (NSN - IN/Bangalore)]

Hi,

We have hit a scenario where ntp client doesn't sync with the external NTP 
server till its restarted.
Following are the sequence of events, as the issue was seen
1)  Initially everything is working fine.
2)  There was a 3 hours network break, so ntp client unable to connect to 
the external server.
3)  Once network is up, ntp client unable to sync with the external server 
even  ntp request /response pkts are sending/receiving properly.
4)  Once we restart ntp client , it's started working fine.

(When there is no network, NTP client is synced with local clock as it's confi 
contain below line:
fudge 127.127.1.0 stratum 0
)

Please let me know why, NTP client sync not happened until it restarts (when 
there was a network failure for some time)

This issue is not able to reproduce :).

Thanks,
Ramgopal.


___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] good "NTP Citizen"

[George Rosamond]

I am looking to get a sense of what it means for a vendor to be a good
"NTP citizen."  I see it's been discussed before, but maybe we could use
this thread to provide an instructive checklist, in particular for
vendors with a designated pool.

The obvious starting is for the vendor to configure a pool with a
corresponding and regular donation.

In terms of the client configuration, I've read in various places that
besides using IBURST and synching on start, polling shouldn't happen
more than every three hours.

What else does being a "good NTP citizen" entail?

George
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] GPS wrong date?

[Marcin Gondek]

Hi,

I'm using a Garmin 18x LVC to sync my server with NTP.

Before two day I just got that GPS is out of sync.

When I can, there is a something strange with date on GPS data, it looks that 
date is stopped TWO DAYS AGO, what can to fix it or check what is the correct 
problem?

[root@fido pps-tools]# date
Fri Sep 26 23:25:05 CEST 2014
[root@fido pps-tools]# cat /dev/gps0
$GPRMC,211218,A,5218.0866,N,02055.7025,E,000.0,324.7,240914,005.3,E*75

$GPGGA,211218,5218.0866,N,02055.7025,E,1,00,1.0,-495.2,M,35.5,M,,*6A

$GPRMC,211219,A,5218.0866,N,02055.7024,E,000.0,324.7,240914,005.3,E*75

$GPGGA,211219,5218.0866,N,02055.7024,E,1,00,1.0,-495.2,M,35.5,M,,*6A

$GPRMC,211220,A,5218.0866,N,02055.7024,E,000.0,324.7,240914,005.3,E*7F

[root@fido pps-tools]# ./ppstest /dev/gpspps0
trying PPS source "/dev/gpspps0"
found PPS source "/dev/gpspps0"
ok, found 1 source(s), now start fetching data...
source 0 - assert 1411766593.506479898, sequence: 32925873 - clear  
1411766593.706511871, sequence: 513
source 0 - assert 1411766594.506501606, sequence: 32925874 - clear  
1411766593.706511871, sequence: 513
source 0 - assert 1411766594.506501606, sequence: 32925874 - clear  
1411766594.706476667, sequence: 514
source 0 - assert 1411766595.506511285, sequence: 32925875 - clear  
1411766594.706476667, sequence: 514
source 0 - assert 1411766595.506511285, sequence: 32925875 - clear  
1411766595.706502029, sequence: 515
^C
[root@fido pps-tools]# ./ppswatch /dev/gpspps0
trying PPS source "/dev/gpspps0"
found PPS source "/dev/gpspps0"
timestamp: 1411766599, sequence: 518, offset: -293516872
timestamp: 1411766600, sequence: 519, offset: -293516636
timestamp: 1411766600, sequence: 519, offset: -293516636
timestamp: 1411766601, sequence: 520, offset: -293530233
^C

Total number of PPS signals: 4
Maximum divergence: 293530233
[root@fido pps-tools]# ll /dev/pps*
crw-rw. 1 root root 249, 0 Sep 10  2013 /dev/pps0
[root@fido pps-tools]# ll /dev/gps*
lrwxrwxrwx. 1 root root 10 Sep 26 22:37 /dev/gps0 -> /dev/ttyS5
lrwxrwxrwx. 1 root root  9 Sep 10  2013 /dev/gpspps0 -> /dev/pps0
[root@fido pps-tools]#


--
Marcin Gondek / Drixter
http://fido.e-utp.net/
AS56662

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] Thunderbolt problem

[Jeff Woolsey]

I have a Trimble Thunderbolt that I might as well use on the machine I'm 
building near it.


It's running OpenIndiana Hipster, which came with ntp-4.2.7p453, 
apparently built with DEBUG.  I'm using the Palisade driver, with 
appropriate tweaks for the TBolt.   The relevant part of ntp.conf:


server 127.127.29.0 mode 2 minpoll 4 maxpoll 5  # Trimble Thunderbolt (PALISADE)
fudge 127.127.29.0 flag2 1 stratum 8

It's fudged to stratum 8 because NTP finds it about 30ms off from the 
rest of the world (and it's an 8-channel GPS :-).  This problem should 
go away if I ever get PPS working here.  However, while trussing it, 
looking for any evidence of PPS activity, I saw it try to issue once per 
second the message in the following code to fd#1, which wasn't attached 
to anything because ntp was a daemon here.


// && intended, but & also works -jlw
if ((up->type != CLK_THUNDERBOLT) & (up->type != CLK_ACUTIME)){
if ((up->rpt_buf[0] == (char) 0x41) ||
(up->rpt_buf[0] == (char) 0x46) ||
(up->rpt_buf[0] == (char) 0x54) ||
(up->rpt_buf[0] == (char) 0x4B) ||
(up->rpt_buf[0] == (char) 0x6D)) {

/* standard time packet - GPS time and GPS week number 
*/
#ifdef DEBUG
printf("Palisade Port B packets detected. Connect to Port 
A\n");
#endif

return 0;
}
}


This starts at about line 462 in refclock_palisade.c .  The comment is 
in my local version because I was trying something else months ago and 
just noted that.


So, would the suggested change make a difference?  (A Thunderbolt only 
has one serial port, so there is no distinction between port A and port B.)


--
Jeff Woolsey {woolsey,jlw}@{jlw,jxh}.com first.last@{gmail,jlw}.com
Spum bad keming.
Nature abhors a straight antenna, a clean lens, and unused storage capacity.
"Delete! Delete! OK!" -Dr. Bronner on disk space management
"Card sorting, Joel." -me, re Solitaire

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] ntpd starts despite having an invalid configuration

[Sam Kottler]

Greetings,

Today I ran into a rather strange behavior in ntpd on Ubuntu 14.04 (ntpd
4.2.6p3@1.2290-o Tue Jun  5 20:12:08 UTC 2012 (1)). There was a
configuration which was invalid deployed to systems and ntpd still started
up and properly listened on port 123 (some rows removed):

COMMAND  PID USER   FD   TYPE   DEVICE SIZE/OFF NODE NAME
ntpd1554  ntp   16u  IPv4  495  0t0  UDP *:ntp
ntpd1554  ntp   17u  IPv6  496  0t0  UDP *:ntp
ntpd1554  ntp   20u  IPv4  504  0t0  UDP 10.30.0.2:ntp
ntpd1554  ntp   21u  IPv6  505  0t0  UDP ip6-localhost:ntp
ntpd1554  ntp   25u  IPv416089  0t0  UDP 192.168.122.1:ntp
ntpd1554  ntp   26u  IPv4 76370284  0t0  UDP 172.30.1.1:ntp

The expected behavior is that the daemon would not properly start up, but
it seems this is ignored.

Instead, the daemon starts (this is ntpd -d -q), printing that its
configuration is invalid and hangs forever:

ntpd 4.2.6p3@1.2290-o Tue Jun  5 20:12:08 UTC 2012 (1)
30 Sep 04:21:17 ntpd[21902]: proto: precision = 0.559 usec
event at 0 0.0.0.0 c01d 0d kern kernel time sync enabled
30 Sep 04:21:17 ntpd[21902]: line 56 column 27 syntax error, unexpected
T_String, expecting T_EOC
30 Sep 04:21:17 ntpd[21902]: syntax error in /etc/ntp.conf line 56, column
27
Finished Parsing!!
30 Sep 04:21:17 ntpd[21902]: ntp_io: estimated max descriptors: 1024,
initial socket boundary: 16
30 Sep 04:21:17 ntpd[21902]: Listen normally on 0 v4wildcard 0.0.0.0 UDP 123
30 Sep 04:21:17 ntpd[21902]: Listen normally on 1 v6wildcard :: UDP 123
30 Sep 04:21:17 ntpd[21902]: Listen normally on 2 lo 127.0.0.1 UDP 123
restrict: op 1 addr 127.0.0.1 mask 255.255.255.255 mflags 3000 flags
0001
30 Sep 04:21:17 ntpd[21902]: Listen normally on 3 lo ::1 UDP 123
restrict: op 1 addr ::1 mask ::::::: mflags
3000 flags 0001
30 Sep 04:21:17 ntpd[21902]: peers refreshed
30 Sep 04:21:17 ntpd[21902]: Listening on routing socket on fd #20 for
interface updates
restrict: op 1 addr 0.0.0.0 mask 0.0.0.0 mflags  flags 05d0
restrict: op 1 addr :: mask :: mflags  flags 05d0
restrict: op 1 addr 127.0.0.1 mask 255.255.255.255 mflags  flags

restrict: op 1 addr ::1 mask ::::::: mflags
 flags 
key_expire: at 0 associd 14560
peer_clear: at 0 next 1 associd 14560 refid INIT
event at 0 74.207.242.71 8011 81 mobilize assoc 14560
newpeer: ->74.207.242.71 mode 3 vers 4 poll 6 10 flags 0x101 0x1 ttl
0 key 
key_expire: at 0 associd 14561
peer_clear: at 0 next 2 associd 14561 refid INIT
event at 0 216.93.242.12 8011 81 mobilize assoc 14561
newpeer: ->216.93.242.12 mode 3 vers 4 poll 6 10 flags 0x101 0x1 ttl
0 key 
key_expire: at 0 associd 14562
peer_clear: at 0 next 3 associd 14562 refid INIT
event at 0 204.9.54.119 8011 81 mobilize assoc 14562
newpeer: ->204.9.54.119 mode 3 vers 4 poll 6 10 flags 0x101 0x1 ttl 0
key 
key_expire: at 0 associd 14563
peer_clear: at 0 next 4 associd 14563 refid INIT
event at 0 50.22.155.163 8011 81 mobilize assoc 14563
newpeer: ->50.22.155.163 mode 3 vers 4 poll 6 10 flags 0x101 0x1 ttl
0 key 
key_expire: at 0 associd 14564
peer_clear: at 0 next 5 associd 14564 refid INIT
event at 0 91.189.89.199 8011 81 mobilize assoc 14564
newpeer: ->91.189.89.199 mode 3 vers 4 poll 6 10 flags 0x101 0x1 ttl
0 key 
event at 0 0.0.0.0 c016 06 restart
event at 0 0.0.0.0 c012 02 freq_set kernel 16.510 PPM
auth_agekeys: at 1 keys 1 expired 0

Is this the expected behavior or should I submit a patch? We've already got
one in place to prevent this happening on our systems and I'm happy to pass
it along.

Thanks!

-s
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] no drift-file on 2008 R2 vps and the time diff. is getting bigger and bigger?

[Carl A. Schreiber]

Insist to whom? I doubt that your provider feels that is their
obligation. Nor that he deliver a monotonic, non-jumping clock to you.
And ntp cannot discipline a clock which it decides is off by more than
500PPM as averaged over a number of cycles.

Well, I don't know much about the Windows-Server 2008 R2 but couldn't it 
be that if I share the realy server with too many other clients not only 
my performance goes down but as well the clock is getting slower?
If so (?) I can ask him to either reduce the no. of clients or I will 
look for another provider - no?


But as I said I don't know enough yet about this.

Do you know a tool to check easily the available performance of the vps?

Gooly
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] Constant jitter value

[Andrew Luebke]

I've setup a NTP server with an OXCO and GPS PPS and it works great,
however, after it's had time to stabilize the jitter for the PPS (and the
system clock) is constant at 1.907us.  I'm at a loss as to why it would have
a constant jitter.  Seems like jitter should move around.  Here is a sample
of the peerstats which show the constant jitter:

 

56925 85226.572 -0.00827 -0.012 0.01907 0.12 3
56925 85234.567 0.00173 -0.012 0.01907 0.11 3
56925 85242.601 -0.00097 -0.012 0.01907 0.10 3
56925 85250.601 -0.00546 -0.012 0.01907 0.11 3
56925 85258.589 -0.00214 -0.012 0.01907 0.12 3
56925 85266.606 0.00145 -0.012 0.01907 0.11 3
56925 85274.588 -0.00249 -0.012 0.01907 0.10 3
56925 85282.572 -0.00688 -0.012 0.01907 0.11 3
56925 85290.578 -0.00571 -0.012 0.01907 0.15 3
56925 85298.579 -0.00238 -0.012 0.01907 0.14 3

 

Any ideas?

 

Thanks,

Andrew.



---
This email is free from viruses and malware because avast! Antivirus protection 
is active.
http://www.avast.com
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] no drift-file on 2008 R2 vps and the time diff. is getting bigger and bigger?

[Carl A. Schreiber]

Am 13.09.2014 16:09, schrieb Joe Gwinn:

In article <5414139e.60...@gmx.at>, gooly  wrote:


Hi,

I just installed ntp (Meinberg, once on Win7, once on a vps 2008 R2).
On my Win 7 I see in C:\Program Files (x86)\NTP\etc the drift file
but on the vps there is no drift-file?

And after starting (and several restarts) the time-difference getting
bigger and bigger.
What's going wrong?

Ntp is running, I can see it in the Task-Manager.
The conf file (without comments):


restrict default nomodify notrap nopeer noquery
restrict 127.0.0.1
restrict -6 ::1

driftfile "C:\Program Files (x86)\NTP\etc\ntp.drift"

  server 0.de.pool.ntp.org iburst
  server 1.de.pool.ntp.org iburst
  server 2.de.pool.ntp.org iburst
  server 1.nl.pool.ntp.org iburst
  server 2.uk.pool.ntp.org iburst




# Use specific NTP servers
server 'ts2.aco.net' iburst
server 'ts1.univie.ac.at' iburst
server '0.at.pool.ntp.org' iburst
server '1.at.pool.ntp.org' iburst
server ntp1.m-online.net iburst
server ptbtime1.ptb.de iburst
server 0.de.pool.ntp.org iburst
server 1.de.pool.ntp.org iburst
server ntps1-0.eecsit.tu-berlin.de iburst

server time.fu-berlin.de iburst
server ntp.probe-networks.de iburst
server zeit.fu-berlin.de iburst

# End of generated ntp.conf --- Please edit this to suite your needs


If the NTP daemon is running yet the local clock drifts ~linearly, a
common cause is that the daemon does not have sufficient privilege to
adjust the local clock, and so the clock-adjust requests are being
silently ignored by the operating system kernel.

Joe Gwinn

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions


On Win Server 2008 R2:
lusrmgr: user => ntp => properties => Profil
Profil path: (empty)
"Anmelde" (=login or register or sign in?) script: 婍

seems to be a ASCII - ANSI problem here but does it matter?

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] Query regarding the relationship between jitter and Polling frequency

[Sumesh_Surendran]

Hi,

 This is a query regarding synchronization with the NTP server. Whether 
the initial synchronization (for testing purpose we use large skew) at any cost 
depends on the reference clock's precision. I am trying to synchronize with two 
NTP servers and for one it is taking pretty much time to do initial synch up. 
The other one it happens pretty much quick. We are seeing, while doing ntpq -c 
peer, the difference lie in the jitters. When there is more value in jitter it 
is doing more numbers of polling before synchronization. The poll interval is 
default which is 64 sec.

Can you please confirm the relationship between jitters and polling frequency 
before synch. Or is there any other possibility for the duration difference..?

Thank you.


With regards
Sumesh S
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] How to get ntp clients details

[Abdul Khader]

Dear All,
How to get ntp clients details on linux ntp server.
I want to get ntp number of clients currently connected. How many total ntp
requests per second on server.
How many clients were denied by server, how many synced properly.

Thanks
Abdul Khader
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] Query regarding the relationship between jitter and Polling frequency

[Sumesh_Surendran]

Hi,

 This is a query regarding synchronization with the NTP server. Whether 
the initial synchronization (for testing purpose we use large skew) at any cost 
depends on the reference clock's precision. I am trying to synchronize with two 
NTP servers and for one it is taking pretty much time to do initial synch up. 
The other one it happens pretty much quick. We are seeing, while doing ntpq -c 
peer, the difference lie in the jitters. When there is more value in jitter it 
is doing more numbers of polling before synchronization. The poll interval is 
default which is 64 sec.

Can you please confirm the relationship between jitters and polling frequency 
before synch. Or is there any other possibility for the duration difference..?

Thank you.


With regards
Sumesh S
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] How to get ntp clients details

[Abdul Khader]

Dear All,
How to get ntp clients details on linux ntp server.
I want to get ntp number of clients currently connected. How many total ntp
requests per second on server.
How many clients were denied by server, how many synced properly.

Thanks
Abdul Khader
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] ntp listmaster help wanted

[Harlan Stenn]

Folks,

We need listmaster help for NTP and NTF.

If you want to help with this, please send an email to
listmas...@lists.nwtime.org .

Thanks...

-- 
Harlan Stenn 
http://networktimefoundation.org  - be a member!
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Mitigating the ::1 spoof vulnerability

[Harlan Stenn]

Marco Marongiu writes:
> Hi there
> 
> I'm referring to this one in particular: "::1 can be spoofed on some
> OSes, so ACLs based on IPv6 ::1 addresses can be bypassed".
> 
> Debian Squeeze doesn't have a patched package available in the
> squeeze-lts series yet. On those clients would a restriction like
> 
> restrict ::1 ignore
> 
> mitigate the vulnerability?

I think so, but it will also make it much harder to use ntpq and other
things.  It also won't do anything to protect other services that might
use source ACLs for protection

Better to:

- fix your firewall rules to block ::1 incoming packets on external
  interfaces

- just build 4.2.8p1 and install it

H
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Shared PPS source/Multiple PPS sources

[A C]

On 2015-02-06 13:37, William Unruh wrote:

> No idea what an SV is. But yes, it is compensated for the time from the
> sattelite to the receiver. That is why to determine time, the receiver
> needs to know where it is on the earth. It is not compensated for the
> time from the gps receiver to anywhere else. 

SV = Space Vehicle which is what the satellites are technically called
in official documentation.
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Shared PPS source/Multiple PPS sources

[William Unruh]

On 2015-02-06, walter.preunin...@gmail.com  wrote:
> Ok, so these questions might be off the wall.
>
> Is there any reason why I could not share the PPS output of say, my u-blox 7 
> GPS module on multiple computers? Would it be good or bad to peer these 2 
> systems with each other?

By share you mean run the PPS output to each of the computers? The main
thing you would need to do is make sure that the gps is able to handle
the current load, and that the signals had the appropriate level at each
of the computers. 


>
> On the opposite end of the spectrum, would it be reasonable to have a PPS 
> output from said module on a computer, with a second PPS (from another GPS 
> module) on that same computer?

Sure. you need to have two differnt interrupt lines available (GPIO,
serial ports, parallel ports)

>
> The Chronodot/DS323X chips have 1 Hz sqaure wave output and they have +/- 
> 2ppm. It seems that the ATOM clock driver could be used, but would it be 
> better to write a driver specifically for this chip?

2PPM is not that great. That is one second out per 6 day. A minute out
per year. 
What is that chip. 

. 
>
> And a side question: Is it the GPS module that calculates when the PPS goes 
> active? Is this signal compensated for the time it takes the signal from the 
> sats in the module, or on the SV?
>

No idea what an SV is. But yes, it is compensated for the time from the
sattelite to the receiver. That is why to determine time, the receiver
needs to know where it is on the earth. It is not compensated for the
time from the gps receiver to anywhere else. 


> Does someone know the admin of tick.uh.edu? I am not getting a response from 
> them or the server.

What reponse do you want? Why should they respond to you?
>
> Thanks
>
>
> Walter

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] Shared PPS source/Multiple PPS sources

[walter . preuninger]

Ok, so these questions might be off the wall.

Is there any reason why I could not share the PPS output of say, my u-blox 7 
GPS module on multiple computers? Would it be good or bad to peer these 2 
systems with each other?

On the opposite end of the spectrum, would it be reasonable to have a PPS 
output from said module on a computer, with a second PPS (from another GPS 
module) on that same computer?

The Chronodot/DS323X chips have 1 Hz sqaure wave output and they have +/- 2ppm. 
It seems that the ATOM clock driver could be used, but would it be better to 
write a driver specifically for this chip?

And a side question: Is it the GPS module that calculates when the PPS goes 
active? Is this signal compensated for the time it takes the signal from the 
sats in the module, or on the SV?

Does someone know the admin of tick.uh.edu? I am not getting a response from 
them or the server.

Thanks


Walter

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Mitigating the ::1 spoof vulnerability

[Marco Marongiu]

Hi David, and thanks for answering

On 06/02/15 14:44, David Woolley wrote:
>> Debian Squeeze doesn't have a patched package available in the
>> squeeze-lts series yet. On those clients would a restriction like
>>
>> restrict ::1 ignore
>>
>> mitigate the vulnerability?
>>
> 
> Sounds more like you need to fix the firewall.

That's understood and it's the advised solution. However, for reason I
can't elaborate here, I can't fire up a firewall on every node just for
this. If using restrict ignore would prevent the vulnerability to be
exploited, we'd be fine with that on pre-wheezy nodes.

What do you think?

Ciao
-- bronto


___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Mitigating the ::1 spoof vulnerability

[David Woolley]

On 06/02/15 12:17, Marco Marongiu wrote:


I'm referring to this one in particular: "::1 can be spoofed on some
OSes, so ACLs based on IPv6 ::1 addresses can be bypassed".

Debian Squeeze doesn't have a patched package available in the
squeeze-lts series yet. On those clients would a restriction like

restrict ::1 ignore

mitigate the vulnerability?



Sounds more like you need to fix the firewall.  Firewalls should not 
allow incoming source address 127.0.0.1 and internet level firewalls 
should not allow private use only source addresses.


___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] Mitigating the ::1 spoof vulnerability

[Marco Marongiu]

Hi there

I'm referring to this one in particular: "::1 can be spoofed on some
OSes, so ACLs based on IPv6 ::1 addresses can be bypassed".

Debian Squeeze doesn't have a patched package available in the
squeeze-lts series yet. On those clients would a restriction like

restrict ::1 ignore

mitigate the vulnerability?

Thanks
-- bronto


___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Cross-compiling NTP for the Raspberry Pi

[David Taylor]

On 06/02/2015 07:58, Brian Inglis wrote:
[]

The VM approach below may be more straightforward for the kernel, and by
adapting, for NTP:
https://learn.adafruit.com/raspberry-pi-kernel-o-matic
using VirtualBox and Vagrant.
Note at the end there are links for different configs for different
kernel distributions,
other than Raspbian, and hints on adaptation.

Also you may be able to xcompile using Windows Cygwin:
https://www.google.ca/search?q=cygwin+arm+linux+toolchain
especially:
http://www.raspberrypi.org/forums/viewtopic.php?f=7&t=4058#p117498
and followups.
YMMV


Thanks, Brian.

Yes, the Adafruit approach is one I should look at, although now the 
kernel has PPS support built in the only thing I need to do there is 
push the Raspian team to support nohz=off, which seems to produce a 
noticeably lower jitter.  Many of the users I help find recompiling NTP 
difficult enough, without having to recompile and install a new kernel 
and modules as well.


With NTP, with the faster Raspberry Pi 2, compiling NTP is now less of 
an issue.  The configure step still takes a grossly long time and seems 
to have repeated tests for e.g. "what is the size of an integer", but 
the make step can now be run with -j5 to make it multi-task, and is much 
quicker.


What I have yet to discover is whether NTP compiled on the RPi 2 with 
its ARMv7 instructions will run correctly on the basic RPi with its 
ARMv6 instruction set.  Some say it will, but doesn't the compiler take 
advantage of the newer instructions?


I would recommend the RPi 2 to anyone developing software, though.  It's 
much faster.

--
Cheers,
David
Web: http://www.satsignal.eu

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] questions] Cross-compiling NTP for the Raspberry Pi

[catherine . wei1989]

On Friday, February 6, 2015 at 3:10:01 PM UTC+8, Harlan Stenn wrote:
> This is a test from libevent, because it needs to know if the select()
> function will yield in threads.  I say that as if I know what I'm
> talking about, but it's "close enough".
> 
> We can run a test and figure out whether or not select() will yield, but
> we cannot run a test in a cross-compile environment, so in that case we
> expect the person running the build to know how the target behaves.
> 
> Personally, I think that specific autoconf macro,
> 
>  sntp/libevent/m4/openldap-thread-check.m4
> 
> is not well-written and it seems to have some problems.  But it's also
> 683 lines of autoconf macro, and it's not indented using a style I find
> easy to read, so I haven't been able to clean it up yet.
> 
> H

OK, thank you so much. Best wishes.

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions