date:20180806

On 2018-08-06, ashishchugh@gmail.com  wrote:
> This time i made some changes and i can see below output at this time i am 
> using aws time sync ip on my ntp.conf
>
> ntpa -p
>
> output -
>
> remote   refid  st t when poll reach   delay   offset  jitter
>==
> *169.254.169.123 10.25.3.142  3 u  350  512  3770.2250.372   0.120
>  pugot.canonical .STEP.  16 u- 102400.0000.000   0.000
>
That billboard indicates that your ntp server has reached and synchronized with
169.254.169.123.  The other server 'pugot.canonical' has not been seen by
your instance.  It's reach number is 0.

You have a good start on your ntp operation.  You should have a minimum of 4
servers for good timekeeping so that a bad poll reply can be out voted by
the other servers.  The pool server directive is designed to give you a fair
number of good servers automatically and will dynamically replace them as
needed.  One 'pool' directive is all that is required.  It will be fanned
out at the other end to supply a minimum of 4 IP addresses for your server
to synchronize.

Tom

-- 
Public Keys:
PGP KeyID = 0x5F22FDC1
GnuPG KeyID = 0x620836CF

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

Re: [ntp:questions] How can i make sure that how much time ntp is adjusting one day

On 2018-08-06, aashish.ch...@fonantrix.com  wrote:
> here is my ntp.conf file.
>...
>
> and destination ip is (169.254.169.123) 
>
> I am using ntp on my aws ec2 instance.
>
The IP address 169.254.169.123 is an IANA reserved non-routable internal one.
Is this address one that is local to your Amazon EC2 instance region and
availability location?  When you send a query:

ntpq -c as

Does the billboard show that address as reachable?

Tom


-- 
Public Keys:
PGP KeyID = 0x5F22FDC1
GnuPG KeyID = 0x620836CF

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

Re: [ntp:questions] What is the mean of below output?

On 2018-08-06, ashishchugh@gmail.com  wrote:
> Hi 
>
> I am facing time drifting problem in my linux , i install ntp. first of all i 
> am unable to execute ntpstat command as it is saying command not found.
>
> Then i execute ntpq -p and can see below ouuput
>
>  remote   refid  st t when poll reach   delay   offset  jitter
>==
>  time.tritn.com  .INIT.  16 u- 102400.0000.000   0.000
>  ntp1.wiktel.com .INIT.  16 u- 102400.0000.000   0.000
>  clocka.ntpjs.or .INIT.  16 u- 102400.0000.000   0.000
>  ntp.your.org.INIT.  16 u- 102400.0000.000   0.000
>  chilipepper.can .INIT.  16 u- 102400.0000.000   0.000
>
> But i am unable to understand what is the mean of this output.
>
> Is that mean my system time is synced with ntp and at current time there is 
> no time delay in my local linux.
>
This billboard shows that none of your ntp servers are reachable from your EC2
instance.  Try turning off all of the crypto configuration.  You will want to 
make
things operate with a simple configuration first and then add features to a
working system.  Use just the suggested server:

pool pool.ntp.org

As your only one and not use the Amazon pool to start.  If it works and the
associations look good, then there is something incorrect on the EC2 side.

> 2- May i execute the ntp every time or it will run at back end automatically.
>
>
>  Local time: Mon 2018-08-06 07:15:02 UTC
>   Universal time: Mon 2018-08-06 07:15:02 UTC
> Timezone: Etc/UTC (UTC, +)
>  NTP enabled: yes
> NTP synchronized: no
>  RTC in local TZ: no
>   DST active: n/a
>
NTP is not working on this instance.  Get it to syncronize first and then ask
your questions/

Tom


-- 
Public Keys:
PGP KeyID = 0x5F22FDC1
GnuPG KeyID = 0x620836CF

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

Re: [ntp:questions] does this make sense?

On 2018-04-04, Maria Iano  wrote:
> I'm purchasing ntp appliances to put into three datacenters. Does it make 
> sense to purchase two that use GPS and two that use WWVB, and configure them 
> as peers?
The USA Bureau of Time Standards has a link for timing receiver
vendors:
https://www.nist.gov/pml/time-and-frequency-division/time-services/manufacturers-time-and-frequency-receivers

There are a few manufacturers of CDMA systems that receive the timing
signals from the USA cellphone systems.  They have a high degree of
accuracy and are a better choice than WWVB in most cases.

Tom

-- 
Public Keys:
PGP KeyID = 0x5F22FDC1
GnuPG KeyID = 0x620836CF

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

Re: [ntp:questions] How can i make sure that how much time ntp is adjusting one day

2018-08-06 Thread aashish . chugh

here is my ntp.conf file.


# Use public servers from the pool.ntp.org project.
# Please consider joining the pool (http://www.pool.ntp.org/join.html).
pool 2.amazon.pool.ntp.org iburst

# Reduce the maximum number of servers used from the pool.
tos maxclock 5

# Enable public key cryptography.
#crypto

includefile /etc/ntp/crypto/pw

# Key file containing the keys and key identifiers used when operating
# with symmetric key cryptography. 
keys /etc/ntp/keys

# Specify the key identifiers which are trusted.
#trustedkey 4 8 42

# Specify the key identifier to use with the ntpdc utility.
#requestkey 8

# Specify the key identifier to use with the ntpq utility.
#controlkey 8

# Enable writing of statistics records.
#statistics clockstats cryptostats loopstats peerstats

# Enable additional logging.
logconfig =clockall =peerall =sysall =syncall

# Listen only on the primary network interface.
interface listen eth0
interface ignore ipv6

# Disable the monitoring facility to prevent amplification attacks using ntpdc
# monlist command when default restrict does not include the noquery flag. See
# CVE-2013-5211 for more details.
# Note: Monitoring will not be disabled with the limited restriction flag.
disable monitor

and destination ip is (169.254.169.123) 

I am using ntp on my aws ec2 instance.

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

[ntp:questions] Vendor Granularity

2018-08-06 Thread gkitchen

Re: http://www.pool.ntp.org/en/ 

With a vendor zone file the docs say 0.pool.ntp.org becomes 
0.vendor.pool.ntp.org.  Does this cascade to europe.vendor.pool.ntp.org and 
ch.vendor.pool.ntp.org for example?

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

[ntp:questions] Sending NTP broadcast and multi-cast messages from single demon via two Ethernet interfaces

2018-08-06 Thread Sukanya K @ ASSPL

Hello everyone,


I am working on "dual Ethernet interface hardware". We have successfully 
installed NTPD demon and its working fine.

Now i am trying to send ntp broadcast and multi cast messages through dual 
Ethernet interfaces. I am able to send both multi-cast and broadcast ntp 
messages using single Ethernet interface (any one Ethernet port only). But, Is 
there any way or possibility to send ntp broadcast and multi cast messages from 
ntp demon via both Ethernet port ?

NTPD version: ntp-4.2.8p10.



Thanks & Regards,




 The information transmitted is intended for the person or entity to which it 
is addressed and may contain confidential and/or privileged material. Any 
review, retransmission, dissemination, copying or other use of, or taking any 
action in reliance upon, this information by persons or entities other than the 
intended recipient is prohibited. If you have received this in error, please 
contact the sender and delete the material from your system. Accord Software & 
Systems Pvt. Ltd. (ACCORD) is not responsible for any changes made to the 
material other than those made by ACCORD or for the effect of the changes on 
the meaning of the material. 

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

[ntp:questions] Strange monitoring

2018-08-06 Thread Erwan David


On pool.ntp.org my server (212.83.179.156) has a score of 20. However I receive 
almost
each day a notification from the beta monitoring with a very low
score. It seems some of the new monitoring stations cannot rach my
server. What should I check ? There is no special treatment for
monitoring on my server.

-- 
Les simplifications c'est trop compliqué

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

[ntp:questions] How to calculate shm + pps offsets?

2018-08-06 Thread Guido Gavilanes




I am currently using a Ublox M8N either for positioning than for time 
synchronization (as stratum0 source and stratum1 server to other 
subsystems). In order to achieve this I have a gpsd listening the device 
in a local port and publishing timing/positioning in shared memory (to 
be visible to NTP.). I have also put PPS electrical signal from the GNSS 
receiver into a gpio handled by a pps-gpio linux driver. That works fine 
in my system.


PPS has been tested with ppstest tool. also ntpshmmon gives 
time/position exports to shared memory for every second.


The problem is that up to now I haven't found a way to calibrate 
accurately the initial calibration time offset estimations given by ntp. 
I used trial-and-error approach to arrive to a combination of 
calibration times for [PPS , SHM]  that keeps my local clock 
synchronized for as long as possible. The most I have got with that 
combination is 300 seconds after ntp service restart.


After the ntp restart, the ntp shows:

|root@hostname:~# ntpq -p remote refid st t when poll reach delay offset 
jitter 
== 
*SHM(0) .UBL. 0 l 6 16 17 0.000 -5.601 7.147 oPPS(1) .PPS. 0 l 5 16 7 
0.000 -2.434 0.391 |


but after a (short) while, ntp marks both sources as false tickers:

|root@hostname:~# ntpq -p remote refid st t when poll reach delay offset 
jitter 
== 
xSHM(0) .UBL. 0 l 4 16 377 0.000 -11.125 5.132 xPPS(1) .PPS. 0 l 3 16 
377 0.000 -2.701 0.200 |


Sometimes it comes back to synch, and it goes back and forth. For my 
purposes, it might be acceptable (since local time clock does not 
diverge much until the next time ntp resync), but when I apply the same 
ntp configuration to another system with the exactly the same 
hardware/software configuration (even the same GNSS antenna in open 
sky), the synchronization state is not stable (ntps declares false 
tickers almost always). This makes me think that the ntp configuration I 
have obtained is not the optimal.


The NTP configuration I have is this:

|driftfile /netlab/log/ntp.drift statsdir /netlab/log/ntpstats/ 
statistics loopstats peerstats clockstats logfile 
/netlab/log/NTP/ntp.log enable calibrate filegen clockstats ntp.stats 
clockstats type day enable # SHM driver doc: # time1 Specifies the time 
offset calibration factor, in seconds and fraction, with default 0.0. # 
time2 Maximum allowed difference between remote and local clock, in 
seconds. Values <1.0 or >86400.0 are ignored, and the default value of 
4hrs (14400s) is used instead. See also flag 1. # stratum Specifies the 
driver stratum, in decimal from 0 to 15, with default 0. # refid 
Specifies the driver reference identifier, an ASCII string from one to 
four characters, with default SHM. # flag1 0 | 1 Skip the difference 
limit check if set. Useful for systems where the RTC backup cannot keep 
the time over long periods without power and the SHM clock must be able 
to force long-distance initial jumps. Check the difference limit if 
cleared (default). # flag2 0 | 1 Not used by this driver. # flag3 0 | 1 
Not used by this driver. # flag4 0 | 1 If flag4 is set, clockstats 
records will be written when the driver is polled. server 127.127.28.0 
mode 1 minpoll 4 maxpoll 6 prefer fudge 127.127.28.0 time1 0.040 time2 
1.00 stratum 0 flag1 1 flag4 1 refid UBL # driver 22 (ATOM PPS) # flag2 
Specifies PPS capture on the rising (assert) pulse edge if 0 (default) 
or falling (clear) pulse edge if 1 # flag3 Controls the kernel PPS 
discipline: 0 for disable (default), 1 for enable server 127.127.22.1 
minpoll 4 maxpoll 4 version 4 prefer # enable PPS API fudge 127.127.22.1 
flag2 0 time1 -0.040 stratum 0 flag3 1 |


(my apologizes for the long intro)

Is there a way to systematically calibrate the offsets so the 
synchronization is stably maintained (obviously under optimal sky 
visibility) ?



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

[ntp:questions] NTP Manycast Server Not Responding to Client Requests

2018-08-06 Thread Potter, Timothy CCS

I am testing out the manycast feature of NTP.  I have a situation where one of 
my machines, acting as the main manycast server, does not reply to incoming 
manycast client requests.  Using tcpdump I see the client requests coming into 
this machine, but they go unanswered.  However, once I restart the ntpd daemon 
on the manycast server, it will almost immediately begin replying to these 
requests.

I am using ntp version 4.2.8p8.  The ntp.conf file on my manycast server looks 
like this:

driftfile /usr/local/etc/ntp.drift
disable auth

# NTP clients will also act like a server once they sync
manycastserver ff0e::101

# Update the realtime clock and override its default
# stratum of 0.
server time.google.com prefer
server 127.127.1.0 #Real Time Clock
server 127.127.1.0 #Real Time Clock
fudge 127.127.1.0 stratum 10

I see that the ntp service is syncing with time.google.com:

 remote   refid  st t when poll reach   delay   offset  jitter
==
LOCAL(0).LOCL.  10 l-   6400.0000.000   0.000
*time2.google.co .GOOG.   1 u  140 1024  377   71.678   -2.836   2.511


The ntp.conf file on the ntp manycast client machines look like this:

driftfile /usr/local/etc/ntp.drift
disable auth

# NTP clients will also act like a server once they sync
manycastserver ff0e::101
manycastclient ff0e::101 iburst

# Enable syncing with servers on the same stratum.  Used for client machines
tos cohort 0

But they are not getting synced with the manycast server:

root@Node00b01973d7d4:~# ntpq -p
 remote   refid  st t when poll reach   delay   offset  jitter
==
ff0e::101   .ACST.  16 a-   6400.0000.000   0.002


Any thoughts on what I am doing wrong?
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] How can i make sure that how much time ntp is adjusting one day

2018-08-06 Thread aashish . chugh

Hi,

I am facing time drifting problem in my production env.

I install ntp on my linux server and configure that.

i enable the ntp, how can end of the day i can get the total time which ntp 
adjusted.

when i execute ntpstat command i can see following output

synchronised to NTP server (169.254.169.123) at stratum 4
   time correct to within 9 ms
   polling server every 8 s


is there is anything need to do.

Please help.

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

[ntp:questions] This is project have any SLA and does it meets th PCI and DSS compliance

2018-08-06 Thread bhuvaneshwaran . r

Hello,

We are going to use these pool servers for our production env, so we need to 
know that you have any SLA for uptime and does this project meets the PCI and 
DSS compliance? 

-- 
DISCLAIMER: The information in this message is "Powerupcloud Technologies" 
confidential and may be legally privileged. It is intended solely for the 
addressee. Access to this message by anyone else is unauthorized. If you 
are not the intended recipient, any disclosure, copying, or distribution of 
the message, or any action or omission taken by you in reliance on it, is 
prohibited and may be unlawful. Please contact h...@powerupcloud.com 
 immediately if you have received this message 
in error. Thank you.

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

Re: [ntp:questions] Issues with decoding Raw DCF77

2018-08-06 Thread Hans Jørgen Jakobsen

On Tue, 20 Mar 2018 21:16:11 +0100, Andreas Mattheiss wrote:
> Hello,
>
> I'm monkeying around with raw DCF again ...
>
> I have slightly modified a DCF77 alarm clock so that it constantly
> receives the DCF77 signal and tapped into the 100/200ms pulses. Receiption
> must be good, since when I pipe this into an Arduino board I get good
> results from the decode. For the PC, I first inverted the 100/200ms pulses
> with a transistor, then feed the inverted signal into a MAX232 level
> converter - inverting is necessary since the MAX232 inverts the CMOS level
> signal itself. The MAX232 has a LED at the output that now duly shows
> 100 and 200ms flashes - i.e. it is out most of the time. Hook up to ttyS2.
>
> So far, so good. Alas I only get crap:
>
> 20 Mar 20:59:53 ntpd[15775]: parse: convert_rawdcf: start bit / parity check 
> FAILED for "###RADMLS1248124P124812P1248121241248112481248P??"
> 20 Mar 20:59:53 ntpd[15775]: parse: convert_rawdcf: start bit / parity check 
> FAILED for "###RADMLS1248124P124812P1248121241248112481248P??"
> 20 Mar 20:59:54 ntpd[15775]: parse: convert_rawdcf: start bit / parity check 
> FAILED for "###RADMLS1248124P124812P1248121241248112481248P??"
> 20 Mar 20:59:54 ntpd[15775]: parse: convert_rawdcf: start bit / parity check 
> FAILED for "###RADMLS1248124P124812P1248121241248112481248P??"
> 20 Mar 20:59:54 ntpd[15775]: parse: convert_rawdcf: start bit / parity check 
> FAILED for "###RADMLS1248124P124812P1248121241248112481248P??"
> 20 Mar 20:59:54 ntpd[15775]: parse: convert_rawdcf: start bit / parity check 
> FAILED for "###RADMLS1248124P124812P1248121241248112481248P??"
> 20 Mar 21:00:00 ntpd[15775]: parse: convert_rawdcf: start bit / parity check 
> FAILED for "###RADMLS1248124P124812P124812124124811248"
> 20 Mar 21:00:03 ntpd[15775]: parse: convert_rawdcf: start bit / parity check 
> FAILED for "#--RADMLS1248124P124812P1248121241248112481248P??"
> 20 Mar 21:00:03 ntpd[15775]: parse: convert_rawdcf: start bit / parity check 
> FAILED for "###RADMLS1248124P124812P1248121241248112481248P??"
> 20 Mar 21:00:03 ntpd[15775]: parse: convert_rawdcf: start bit / parity check 
> FAILED for "###RADMLS1248124P124812P1248121241248112481248P??"
> 20 Mar 21:00:03 ntpd[15775]: parse: convert_rawdcf: start bit / parity check 
> FAILED for "###RADMLS1248124P124812P1248121241248112481248P??"
>

Despite LED shows plausible pulses there might be noise spikes
triggering false pulses.
I have had a DCF77 receiver where I had to filter out fake pulses.
A scope will be able to show if signal quality is ok.

Are you shure that you have polarity right?
I think wrong polarity would make it trigger multiple times pr second.

/hjj

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

Re: [ntp:questions] What is the mean of below output?

On 2018-08-06, David Woolley  wrote:
> On 06/08/18 08:16, ashishchugh@gmail.com wrote:
>> 3- Is there is any way through i can determine that what is the currently 
>> difference between my local system and ntp server.
>
> No.  If you could, NTP could modify the local time to make the value zero.

That is of course what it tries to do, without jumping the local time (which
would be bad). Of course the whole chain (Your program, your network hardware,
the network, various routers etc along the way, the remote machine hardware,
the remote software and back again) introduces noise, so you do not know that
the remote ntp server's time is. But in the logs it will tell you what the
difference is between the local time and the estimate of the remote time is
obtained from that noisy chain. That is the best you can do. 
Of course you could attach your ssytem to gps, and get the remote gps server's
time to 10s or 100s of nanosecond accuracy. And yo ucould use that to see how
far your system is off the remote server, If you could borrow a gps, you could
test your system. If you bought a gps, then the best idea would be to use it
as your server, and get your machine disciplined to sub microsecond accuracy.

 From network servers, you can expect 10s of microseconds (nearby servers--
 like in the same  building) to millisec for distant servers. 
For gps, it depends on how you feed the gps into your system. Here you can get
100s of nanoseconds to a few microseconds using chrony. 

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

Re: [ntp:questions] What is the mean of below output?


On 06/08/18 08:16, ashishchugh@gmail.com wrote:

3- Is there is any way through i can determine that what is the currently 
difference between my local system and ntp server.


No.  If you could, NTP could modify the local time to make the value zero.

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

Re: [ntp:questions] What is the mean of below output?

On 2018-08-06, ashishchugh@gmail.com  wrote:
> Hi 
>
> I am facing time drifting problem in my linux , i install ntp. first of all i 
> am unable to execute ntpstat command as it is saying command not found.
>
> Then i execute ntpq -p and can see below ouuput
>
>  remote   refid  st t when poll reach   delay   offset  jitter
>==
>  time.tritn.com  .INIT.  16 u- 102400.0000.000   0.000
>  ntp1.wiktel.com .INIT.  16 u- 102400.0000.000   0.000
>  clocka.ntpjs.or .INIT.  16 u- 102400.0000.000   0.000
>  ntp.your.org.INIT.  16 u- 102400.0000.000   0.000
>  chilipepper.can .INIT.  16 u- 102400.0000.000   0.000
>
> But i am unable to understand what is the mean of this output.

It means that none of those refclocks has ever been successfully used. You are
not synched at all. 

>
> Is that mean my system time is synced with ntp and at current time there is 
> no time delay in my local linux.
>
> 2- May i execute the ntp every time or it will run at back end automatically.

It depends on how you set things up. You do not say which version of Linux,
how you installed it, what your networking is, etc. 


>
>
>  Local time: Mon 2018-08-06 07:15:02 UTC
>   Universal time: Mon 2018-08-06 07:15:02 UTC
> Timezone: Etc/UTC (UTC, +)
>  NTP enabled: yes
> NTP synchronized: no
As you can see, ntp is not synchronized.


>  RTC in local TZ: no
>   DST active: n/a
>
>
> 3- Is there is any way through i can determine that what is the currently 
> difference between my local system and ntp server.

Once you get it working, sure. Look at the logs.


>
> Please help if someone have idea.
>

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

Re: [ntp:questions] How can i make sure that how much time ntp is adjusting one day

2018-08-06 Thread Jakob Bohm


On 06/08/2018 13:42, Thomas Laus wrote:

On 2018-08-06, aashish.ch...@fonantrix.com  wrote:

here is my ntp.conf file.
...

and destination ip is (169.254.169.123)

I am using ntp on my aws ec2 instance.


The IP address 169.254.169.123 is an IANA reserved non-routable internal one.
Is this address one that is local to your Amazon EC2 instance region and
availability location?  When you send a query:

ntpq -c as

Does the billboard show that address as reachable?

Tom




FYI Amazon EC2 uses the non-routable network 169.254.169.0/24 for
services local to each datacenter, or even to smaller subdivisions.  So
this is probably an extremely local Amazon time server.

That said, the Amazon part of the pool also contains servers not on that
subnet (I tried a DNS lookup from one of my own EC2 instances, and it
gave back routable IPs).


Enjoy

Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S.  https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark.  Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded

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

Re: [ntp:questions] How can i make sure that how much time ntp is adjusting one day

On 2018-08-05, aashish.ch...@fonantrix.com  wrote:
> Hi,
>
> I am facing time drifting problem in my production env.
>
> I install ntp on my linux server and configure that.
>
> i enable the ntp, how can end of the day i can get the total time which ntp 
> adjusted.
>
> when i execute ntpstat command i can see following output
>
> synchronised to NTP server (169.254.169.123) at stratum 4
>time correct to within 9 ms
>polling server every 8 s

That poll interval is really short, and if you are getting the time from a
server that you do not control, they could get really really annoyed with you
and cut you off.

That is a link local address, so I do not know what it is you are using as a
server. Could you post your ntp.conf file.

>
>
> is there is anything need to do.

Use a decent server?
>
> Please help.

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

Re: [ntp:questions] Difference between offset (ntpq -p) and offset (ntpq -crv)


On 02/08/2018 09:14, David Woolley wrote:

On 01/08/18 19:32, David Taylor wrote:
Would I be right in thinking of the "*" line as simply being the 
offset from that particular server, and the "system" variable as being 
the offset from some virtual internal clock which ntp has as its best 
estimate of the correct time (e.g. UTC).


That cannot be correct, as the other side of the comparison is that best 
estimate of system time and the result would always be zero.


Without digging into the code, my guess is that it is the offset from 
the weighted average of the last reading from all the true chimers.


Thanks, David.  Weighted average I can accept unless someone knows better.

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

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

Re: [ntp:questions] How can i make sure that how much time ntp is adjusting one day


On 05/08/18 07:15, aashish.ch...@fonantrix.com wrote:


i enable the ntp, how can end of the day i can get the total time which ntp 
adjusted.


NTP adjusts frequency, not time.  It doesn't predict what the internal 
clock would show if it hadn't been adjusted


when i execute ntpstat command i can see following output

synchronised to NTP server (169.254.169.123) at stratum 4
time correct to within 9 ms
polling server every 8 s


I'm not sure what is being measured to produce the 9ms figure.  It seems 
suspiciously
low for a good estimate of the error bounds for a such a high stratum 
client.


If you are polling the server every 8 seconds you have overridden the 
default settings in a way that is not recommended, is likely to cause 
sub-optimal time keeping, and is likely to get you blacklisted by many 
servers.


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

Re: [ntp:questions] Difference between offset (ntpq -p) and offset (ntpq -crv)


On 01/08/18 19:32, David Taylor wrote:
Would I be right in thinking of the "*" line as simply being the offset 
from that particular server, and the "system" variable as being the 
offset from some virtual internal clock which ntp has as its best 
estimate of the correct time (e.g. UTC).


That cannot be correct, as the other side of the comparison is that best 
estimate of system time and the result would always be zero.


Without digging into the code, my guess is that it is the offset from 
the weighted average of the last reading from all the true chimers.


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

[ntp:questions] Difference between offset (ntpq -p) and offset (ntpq -crv)

I was writing a small script to check on offset, and noticed that the 
offset from the selected server ("*" line in the tally list from ntpq 
-p) differs considerably from the offset reported as a "system" variable 
(ntpq -crv).


Would I be right in thinking of the "*" line as simply being the offset 
from that particular server, and the "system" variable as being the 
offset from some virtual internal clock which ntp has as its best 
estimate of the correct time (e.g. UTC).


This was to answer someone's question: is the NTP on that system working 
as expected, by comparing the offset with a pre-defined threshold.


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

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

Re: [ntp:questions] Next major update of Windows has time improvements


Daniel Gearty wrote:

Windows 10 and Windows 2019
Next major update perhaps October 2018?

Leap second support
PTP client
Software timestamping
QPC granularity drops from 6.4 microsec/sec to 100 nanosec/sec
Traceability logging in Event Viewer and performance counters

Unknown what is and is not implemented within the W32Time service which is 
disabled when using Windows NTPD.

https://arstechnica.com/gadgets/2018/07/windows-10-will-get-better-at-telling-the-time-with-new-leap-second-support/

https://blogs.technet.microsoft.com/networking/2018/07/18/top10-ws2019-hatime/

I read all the news articles about this, it basically brings Windows 
into parity with a 20 year old version of FreeBSD or a 10+ year old 
Linux. :-)


It is still good news!

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

Re: [ntp:questions] understanding assocID and ntpq>readvar

2018-08-06 Thread Miroslav Lichvar

On 2018-07-24, valizadeh...@gmail.com  wrote:
> My questions:
> 1-how assocIDs are assinged to ntp peers?

They are assigned randomly and they cannot be predicted AFAIK.

> 2- is there any way to use Peers IP address instead? to use in "ntpq readvar"

Not addresses, but indexes. E.g. ntpq -c as -c 'rv &1' to get the
variables of the first association.

> 3- why ((ntpq -c "rv 23023 status")) don't work?

I guess it's because associd and status are not variables returned as
data in mode 6 packets, but they have their own special fields in the
packets. I'm not sure if it's possible to get them from ntpq separately
from the real variables.

-- 
Miroslav Lichvar

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

[ntp:questions] Determining the offset of GPS serial data automatically - a Linux script

Angelo Mileto recently sent me some notes about determining the offset 
of serial GPS data automatically using a Linux script.  This value is 
used as the time1 fudge factor.  I hope you find it useful.  My thanks 
to Angelo!


https://www.satsignal.eu/ntp/Raspberry-Pi-NTP.html#average

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

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

Re: [ntp:questions] shm + pps calibration


On 05/07/2018 21:30, Daniel Gearty wrote:

server 127.127.20.3 iburst minpoll 3 mode 17
# COM3, 8 second polling, NMEA GPRMC, 9600 bps, NaviSys GR-8013W u-blox M8 USB 
PPS GPS

fudge 127.127.20.3 time1 0.000142 time2 0.11 flag1 1 flag2 1 flag3 0
# PPS offset, NMEA offset, enable PPS, pulse on falling edge, disable kernel PPS

I am using a u-blox M8.

I had trouble with it until I realized that the pulse is on the falling edge 
rather than the default of the rising edge.

I used a u-blox utility to see timestamps for the NMEA GPRMC sentence coming 
through.  It took about a tenth of a second.  If it is accurate to within four 
tenths of a second, it works.  It not, then it does not work.

Barring access to a more accurate clock, PPS offset is a blind guess.  All I do 
is offset by an average of the NTP loopstats offset over time.  I use 142 
microseconds.


I've compared a number of GSP/PPS sources using an oscilloscope and the 
PPS offset between them is usually within 100 nanoseconds, so I would be 
surprised if the PPS leading edge is as much as 142 microseconds out. 
With a Raspberry Pi, I typically I see offsets reported by ntpq -pn well 
under 20 microseconds:


C:\Windows\System32>ntpq -pn raspi-1
 remote   refid  st t when poll reach   delay   offset 
jitter

==
o127.127.22.0.kPPS.   0 l   13   16  3770.000   -0.001 
0.004
 127.127.28.0.GPSD.   0 l   12   16  3770.000  367.025 
 5.593
*192.168.0.3 .kPPS.   1 u6   32  3770.5420.054 
0.008

.
.

https://www.satsignal.eu/mrtg/raspi1_ntp.html


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

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

Re: [ntp:questions] shm + pps calibration


On 07/07/2018 18:10, William Unruh wrote:

On 2018-07-07, David Taylor  wrote:

[]

On one PC I'm using an add-in PCIe card, a TTL-RS232 converter (tried
without but the signal levels were too low) and a Chinese module sitting


That is really unusual. Most serial cards now will happily use TTL levels.
The converter may (or may not) introduce delays to the pps signal. If they are
sub usec it probably does not matter.
Yes, Bill, that surprised me as well!  Adding the level converter (a 
cheap Chinese board) solved the issue (no data seen on the serial port). 
 As this was for a Windows PC, a sub-microsecond delay didn't matter.


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

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

Re: [ntp:questions] This is project have any SLA and does it meets th PCI and DSS compliance


On 12/05/18 18:55, bhuvaneshwara...@powerupcloud.com wrote:

We are going to use these pool servers for our production env, so we need to 
know that you have any SLA for uptime and does this project meets the PCI and 
DSS compliance?


There is no service level agreement.  If you want a service level 
agreement, you will need to use a commercial source, although, 
ultimately commercial sources are likely to depend on satellite 
navigation systems that are unlikely to have service level agreements 
with anyone, except, possibly, their own military.


Do you mean PCI DSS, rather than both PCI and DSS?  I.e. Payment Card 
Industry Data Security Standard?  Nowhere is payment card data requested 
or stored. There is no-one to pay for any certification that that is the 
case.


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

[ntp:questions] ntp solution file to build on windows10

2018-08-06 Thread sneha b

Hi All,

We are migrating from windows7 to windows10, but we are using vc2005 as
compiler.

Earlier I used visual studio 2005, project files, for windows7, as our
compiler was vc2005.

I want to know, is there any .proj or .sln file specific to windows10, or
the existing  .proj files will work for windows10.

Any insights in this regard will be really helpful.

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

Re: [ntp:questions] shm + pps calibration

On 2018-07-01, ggavila...@gmail.com  wrote:
> I am currently using a Ublox M8N either for positioning than for time 
> synchronization (as stratum0 source and stratum1 server to other subsystems). 
> In order to achieve this I have a gpsd listening the device in a local port 
> and publishing timing/positioning in shared memory (to be visible to NTP.). I 
> have also put PPS electrical signal from the GNSS receiver into a gpio 
> handled by a pps-gpio linux driver. That works fine in my system.
>
> PPS has been tested with ppstest tool. also ntpshmmon gives time/position 
> exports to shared memory for every second.
>
> The problem is that up to now I haven't found a way to calibrate accurately 
> the initial calibration time offset estimations given by ntp. I used 
> trial-and-error approach to arrive to a combination of calibration times for 
> [PPS , SHM] that keeps my local clock synchronized for as long as possible. 
> The most I have got with that combination is 300 seconds after ntp service 
> restart.

I do not know what that means.

>
> After the ntp restart, the ntp shows:
>
> root@hostname:~# ntpq -p
>  remote   refid  st t when poll reach   delay   offset  jitter
>==
> *SHM(0)  .UBL.0 l6   16   170.000   -5.601   7.147
> oPPS(1)  .PPS.0 l5   1670.000   -2.434   0.391
> but after a (short) while, ntp marks both sources as false tickers:

Not surprizing. PPS hs no idea what the seconds are, only the decimal part of
the time. It gets the initial seconds from the local clock. Thus PPS shoulnd
not be started until the system time is within about 1/4 sec of UTC.
The shm should give UTC. So, let the system run a while to lock onto shm time,
then start PPS.
Note that if there are two time souces and they disagree, NTP has no way of
knowing which is right,so the beest it can do is say both are wrong.


>
> root@hostname:~# ntpq -p
>  remote   refid  st t when poll reach   delay   offset  jitter
>==
> xSHM(0)  .UBL.0 l4   16  3770.000  -11.125   5.132
> xPPS(1)  .PPS.0 l3   16  3770.000   -2.701   0.200
> Sometimes it comes back to synch, and it goes back and forth. For my 
> purposes, it might be acceptable (since local time clock does not diverge 
> much until the next time ntp resync), but when I apply the same ntp 
> configuration to another system with the exactly the same hardware/software 
> configuration (even the same GNSS antenna in open sky), the synchronization 
> state is not stable (ntps declares false tickers almost always). This makes 
> me think that the ntp configuration I have obtained is not the optimal.
  >
> The NTP configuration I have is this:
>
> driftfile /netlab/log/ntp.drift
> statsdir /netlab/log/ntpstats/
> statistics loopstats peerstats clockstats
> logfile /netlab/log/NTP/ntp.log
> enable calibrate
> filegen clockstats ntp.stats clockstats type day enable
>  
> # SHM driver doc:
> # time1 Specifies the time offset calibration factor, in seconds and 
> fraction, with default 0.0.
> # time2 Maximum allowed difference between remote and local clock, in 
> seconds. Values <1.0 or >86400.0 are ignored, and the default value of 4hrs 
> (14400s) is used instead. See also flag 1.
> # stratum Specifies the driver stratum, in decimal from 0 to 15, with default 
> 0.
> # refid Specifies the driver reference identifier, an ASCII string from one 
> to four characters, with default SHM.
> # flag1 0 | 1 Skip the difference limit check if set. Useful for systems 
> where the RTC backup cannot keep the time over long periods without power and 
> the SHM clock must be able to force long-distance initial jumps. Check the 
> difference limit if cleared (default).
> # flag2 0 | 1 Not used by this driver.
> # flag3 0 | 1 Not used by this driver.
> # flag4 0 | 1 If flag4 is set, clockstats records will be written when the 
> driver is polled.
>  
> server 127.127.28.0 mode 1 minpoll 4 maxpoll 6 prefer
> fudge 127.127.28.0 time1 0.040 time2 1.00 stratum 0 flag1 1 flag4 1 refid UBL
>  
> # driver 22 (ATOM PPS)
> # flag2 Specifies PPS capture on the rising (assert) pulse edge if 0 
> (default) or falling (clear) pulse edge if 1 
> # flag3 Controls the kernel PPS discipline: 0 for disable (default), 1 for 
> enable
> server 127.127.22.1 minpoll 4 maxpoll 4 version 4 prefer  # enable PPS API
> fudge 127.127.22.1 flag2 0 time1 -0.040 stratum 0 flag3 1
>  
> (sorry for the long intro) 
>
> Is there a way to systematically calibrate the offsets so the synchronization 
> is stably maintained (obviously under optimal sky visibility) ?

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

Re: [ntp:questions] shm + pps calibration


On 06/07/2018 21:18, Daniel Gearty wrote:

In my case, I attribute the PPS delay to the serial to USB 1.1 conversion of 
the Prolific PL2303HXD in my NaviSys GR-8013W GPS.  The offset bounces around 
within +/- 0.5 msec.
It appears the initial PPS offset should be zero if you receive your PPS signal 
directly from a proper serial port.

I am using NTP "Generic NMEA GPS Receiver" driver 20 with the Windows loopback 
driver.

ggavi is using "PPS Clock Discipline" driver 22 for PPS, but perhaps should be using 
"Shared Memory Driver" driver 28 for both NMEA and PPS.
http://www.catb.org/gpsd/gpsd-time-service-howto.html#_feeding_ntpd_from_gpsd

Another, newer driver for NTPD to receive time from gpsd is "GPSD NG client 
driver" driver 46.
http://doc.ntp.org/current-stable/drivers/driver46.html

Although I wonder whether chronyd receiving time from gpsd via a socket has the 
best NTP performance.
https://chrony.tuxfamily.org/doc/3.3/chrony.conf.html


Using different software (Chrony or gpsd) is unlikely to improve 
performance which is inherently limited by the serial-USB conversion, 
unless someone were to write a special driver to average out the USB 
jitter.  NTP will do that to an extent, of course.


For best NTP performance, if you aren't using a portable PC (so no 
serial port), check whether your motherboard has a serial port header, 
or get an add-in PCIe serial port and swap the GPS for one which has a 
real PPS line.  Likely even the low-cost Chinese ones will be good enough.


On one PC I'm using an add-in PCIe card, a TTL-RS232 converter (tried 
without but the signal levels were too low) and a Chinese module sitting 
on the bench.  Needed to add one wire from the u-blox module's PPS pin:


  https://www.satsignal.eu/ntp/NEO-6M-under-initial-test.jpg
  https://www.satsignal.eu/ntp/RasPi-3-with-u-blox-RX.jpg

but you could avoid that with the Adafruit module:

  https://www.adafruit.com/product/746

Here's a link to the PC's performance:

  https://www.satsignal.eu/mrtg/lund-ntp-2.html

The variation on that PC is likely due to the CPU temperature as the 
load varies with receiving new Sentinel-3A satellite data every orbit 
(101 minutes).


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

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

Re: [ntp:questions] shm + pps calibration

On 2018-07-07, David Taylor  wrote:
> On 06/07/2018 21:18, Daniel Gearty wrote:
>> In my case, I attribute the PPS delay to the serial to USB 1.1 conversion of 
>> the Prolific PL2303HXD in my NaviSys GR-8013W GPS.  The offset bounces 
>> around within +/- 0.5 msec.
>> It appears the initial PPS offset should be zero if you receive your PPS 
>> signal directly from a proper serial port.
>> 
>> I am using NTP "Generic NMEA GPS Receiver" driver 20 with the Windows 
>> loopback driver.
>> 
>> ggavi is using "PPS Clock Discipline" driver 22 for PPS, but perhaps should 
>> be using "Shared Memory Driver" driver 28 for both NMEA and PPS.
>> http://www.catb.org/gpsd/gpsd-time-service-howto.html#_feeding_ntpd_from_gpsd
>> 
>> Another, newer driver for NTPD to receive time from gpsd is "GPSD NG client 
>> driver" driver 46.
>> http://doc.ntp.org/current-stable/drivers/driver46.html
>> 
>> Although I wonder whether chronyd receiving time from gpsd via a socket has 
>> the best NTP performance.
>> https://chrony.tuxfamily.org/doc/3.3/chrony.conf.html
>
> Using different software (Chrony or gpsd) is unlikely to improve 
> performance which is inherently limited by the serial-USB conversion, 
> unless someone were to write a special driver to average out the USB 
> jitter.  NTP will do that to an extent, of course.
>
> For best NTP performance, if you aren't using a portable PC (so no 
> serial port), check whether your motherboard has a serial port header, 
> or get an add-in PCIe serial port and swap the GPS for one which has a 
> real PPS line.  Likely even the low-cost Chinese ones will be good enough.
>
> On one PC I'm using an add-in PCIe card, a TTL-RS232 converter (tried 
> without but the signal levels were too low) and a Chinese module sitting 

That is really unusual. Most serial cards now will happily use TTL levels. 
The converter may (or may not) introduce delays to the pps signal. If they are
sub usec it probably does not matter. 

> on the bench.  Needed to add one wire from the u-blox module's PPS pin:
>
>https://www.satsignal.eu/ntp/NEO-6M-under-initial-test.jpg
>https://www.satsignal.eu/ntp/RasPi-3-with-u-blox-RX.jpg
>
> but you could avoid that with the Adafruit module:
>
>https://www.adafruit.com/product/746
>
> Here's a link to the PC's performance:
>
>https://www.satsignal.eu/mrtg/lund-ntp-2.html
>
> The variation on that PC is likely due to the CPU temperature as the 
> load varies with receiving new Sentinel-3A satellite data every orbit 
> (101 minutes).
>

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

Re: [ntp:questions] Unable to find Apline package for "ntpq"

2018-08-06 Thread Martin Burnicki

Hi,

gmurd...@gmail.com wrote:
> Hi There,
> 
> I am trying to monitor NTP for the AWS instance.
> 
> I am not able to find an executable for "ntpq" for Alpine platform!
> 
> I have tried looking online and the only information I could find was these 
> links:
> http://blog.oddbit.com/2015/10/09/running-ntp-in-a-container/
> https://www.eecis.udel.edu/~mills/ntp/html/ntpq.html

If you build the NTP software package from sources then ntpq is also built.

If you are running containers then you should ask the guy who sets up
the container why ntpq hasn#t been added to the container.
> 
> I have tried installing opnntpd

I dont't know if openntpd has something like ntpq, or if it would accept
queries from and sends replies to the ntpq utility from the NTP
reference implementation.

Martin
-- 
Martin Burnicki

Meinberg Funkuhren
Bad Pyrmont
Germany

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

Re: [ntp:questions] This is project have any SLA and does it meets th PCI and DSS compliance

On 2018-05-12, bhuvaneshwara...@powerupcloud.com 
 wrote:
> Hello,
>
> We are going to use these pool servers for our production env, so we need to 
> know that you have any SLA for uptime and does this project meets the PCI and 
> DSS compliance? 
>

No idea what you are asking, but pool.ntp.org is a huge bunch of volunteers
who provice their own ntp servers for the use of others. It meets no
compliance standards, and the uptime of volunteers is random, and certainly
not tracked. Note also that the quality of time served by random members of
pool.ntp.org is highly variable-- from tens of microseconds to hundreds of
milliseconds.

If you want to make sure that you have reliable service, set up your own set
ofservers, fed for example from a GPS-PPS source. If you are an organization
then you should also set up your own pool powerupcloud.pool.ntp.org.
for your clients to use, rather than making use of those volunteers. 

ntp is a time source, not a secure environment. 

So I think that the answer to your question is NO. And also that you are
confused about  what ntp is. 

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

Re: [ntp:questions] does this make sense?


William Unruh wrote:

On 2018-04-05, Terje Mathisen  wrote:

I've designed similar setups a couple of times: Since we're located
in Europe my backup was the German radio transmitter since that one
uses spread spectrum modulation of the carrier, enabling 10-15 us
precision.


That is about 2 miles light travel time. I suspect you are further
than that from the tranmitter. And propagation is all in the
atmosphere, and the speed of radio  varies in the atmosphere,
depending on the pressure, the humidity, clouds, Ie, I am
doubting the 10-15us. Maybe 10-15 ms.?


Bill, please!

This was of course with an initial propagation time measurement period, 
where we used the GPS PPS signal to verify the ground wave propagation 
time of the radio signal, then adjusting for that offset in the radio 
driver.


Yes, propagation time will vary a bit over a 24H period, but this 
provides a very useful backup.


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

Re: [ntp:questions] does this make sense?


David Taylor wrote:

On 04/04/2018 20:47, Maria Iano wrote:

Thanks William, I will go with GPS.
Maria


That's a good choice.  These boxes are low-cost (but not yet multiple
GNSS systems - check with the vendor), and have good hold-over in the
event of GPS failure:


http://www.leobodnar.com/shop/index.php?main_page=product_info&products_id=272


In (parts of?) the US you can get a receiver which uses the US-centric 
cell phone modulation system which requires clock synchronization 
between towers and phones, I installed one of these in Tampa, FL.


It provided ~12 us afair.

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

Re: [ntp:questions] does this make sense?


On 04/04/2018 20:47, Maria Iano wrote:

Thanks William, I will go with GPS.
Maria


That's a good choice.  These boxes are low-cost (but not yet multiple 
GNSS systems - check with the vendor), and have good hold-over in the 
event of GPS failure:



http://www.leobodnar.com/shop/index.php?main_page=product_info&products_id=272

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

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

Re: [ntp:questions] does this make sense?

On 2018-04-04, Maria Iano  wrote:
> I'm purchasing ntp appliances to put into three datacenters. Does it make 
> sense to purchase two that use GPS and two that use WWVB, and configure them 
> as peers?

Well, WWVB is about a million times less accurate than GPS (even with a cheap
GPS it is well over a thousand times less accurate). So it seems a little bit
strange. The WWVB could be used as a backup, although I suspect is would be
flakier than the GPS time signal. 

> Thanks,
> Maria

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

Re: [ntp:questions] ntp.ymartin.com

2018-08-06 Thread Martin Burnicki

Yves Martin wrote:
> I've installed my own ntp server since a year now, using a NTP100 server sync 
> with an external GPS antenna. Just need to know if it's reachable from 
> outside. Thanks.
> 
> ntp.ymartin.com
> 
> YM
> 

Yes it is:

#> ntptest ntp.ymartin.com

ntptest v1.9, (c) Meinberg 2014-2018

Host ntp.ymartin.com
Request packet:
  mode 3, version 4, leap 3, stratum 0, poll 6, prec -18 (3.81 us)
  root delay:   (0.00 s)
  root dispersion:  (0.00 s/s)
  reference id: ("")
  Ref time:   .  1900-01-01 00:00:00.0
  Org time (T1):  .  1900-01-01 00:00:00.0
  Rcv time (T2):  .  1900-01-01 00:00:00.0
  Xmt time (T3):  DE6754EE.E6C1F9DB  2018-03-29 12:05:02.901397338
  Curr time (T4): DE6754EE.E6C1F9DB  2018-03-29 12:05:02.901397338

Response packet:
  mode 4, version 3, leap 0, stratum 1, poll 10, prec -18 (3.81 us)
  root delay:   (0.00 s)
  root dispersion:  (0.00 s/s)
  reference id:20535047 ("GPS ")
  Ref time:   DE6754EE.F555C728  2018-03-29 12:05:02.958340117
  Org time (T1):  DE6754EE.E6C1F9DB  2018-03-29 12:05:02.901397338
  Rcv time (T2):  DE6754EE.F555C728  2018-03-29 12:05:02.958340117
  Xmt time (T3):  DE6754EE.F55DC584  2018-03-29 12:05:02.958462090
  Curr time (T4): DE6754EF.05EF09BC  2018-03-29 12:05:03.023178680

turnaround:  121781.342 us  (T4 - T1)
server latency: 121.973 us  (T3 - T2)
computed delay:  121659.369 us  ((T4 - T1) - (T3 - T2))
computed offset:  -3886.906 us  (((T2 - T1) + (T3 - T4)) / 2)


Martin
-- 
Martin Burnicki

Meinberg Funkuhren
Bad Pyrmont
Germany

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

Re: [ntp:questions] does this make sense?

On 2018-04-05, Terje Mathisen  wrote:
> Maria Iano wrote:
>> Thanks for your reply, David. Accuracy to within milliseconds is fine
>> for us. We currently have four old GPS appliances in four data
>> centers that we are replacing, and my thought is that some vendor
>> diversity would be good.
>>
>> We are only staying in two of those data centers, so that was where I
>> was thinking of using GPS as we already have a cable to an antenna to
>> the roof. We have a third data center where we currently don't have
>> any ntp appliance, and that's where I was thinking it would be
>> convenient to put a WWVB device. But we do have access to the roof,
>> and from what you say it sounds like we would be better off putting a
>> GPS using all three services there.
>>
>> We have a network of 12 stratum 2 servers that get time from our
>> appliances, and most of our infrastructure points to those, so maybe
>> a fourth stratum 1 server is overkill. Does this make more sense:
>> three GPS appliances using all three services at the three data
>> centers?
>
> I've designed similar setups a couple of times: Since we're located in 
> Europe my backup was the German radio transmitter since that one uses 
> spread spectrum modulation of the carrier, enabling 10-15 us precision.

That is about 2 miles light travel time. I suspect you are further than that
from the tranmitter. And propagation is all in the atmosphere, and the speed
of radio  varies in the atmosphere, depending on the pressure, the humidity,
clouds, Ie, I am doubting the 10-15us. Maybe 10-15 ms.?

>
> With a modern multi-system GNSS receiver and multiple geographical 
> locations I would probably be happy with a very good local clock (at 
> least TCXO, maybe a second-hand Rb?) to provide holdover and using 
> multiple internet sources as a sanity check.
>
> Terje
>

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

Re: [ntp:questions] does this make sense?


Maria Iano wrote:

Thanks for your reply, David. Accuracy to within milliseconds is fine
for us. We currently have four old GPS appliances in four data
centers that we are replacing, and my thought is that some vendor
diversity would be good.

We are only staying in two of those data centers, so that was where I
was thinking of using GPS as we already have a cable to an antenna to
the roof. We have a third data center where we currently don't have
any ntp appliance, and that's where I was thinking it would be
convenient to put a WWVB device. But we do have access to the roof,
and from what you say it sounds like we would be better off putting a
GPS using all three services there.

We have a network of 12 stratum 2 servers that get time from our
appliances, and most of our infrastructure points to those, so maybe
a fourth stratum 1 server is overkill. Does this make more sense:
three GPS appliances using all three services at the three data
centers?


I've designed similar setups a couple of times: Since we're located in 
Europe my backup was the German radio transmitter since that one uses 
spread spectrum modulation of the carrier, enabling 10-15 us precision.


With a modern multi-system GNSS receiver and multiple geographical 
locations I would probably be happy with a very good local clock (at 
least TCXO, maybe a second-hand Rb?) to provide holdover and using 
multiple internet sources as a sanity check.


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

Re: [ntp:questions] does this make sense?


On 04/04/2018 17:29, Maria Iano wrote:

I'm purchasing ntp appliances to put into three datacenters. Does it make sense 
to purchase two that use GPS and two that use WWVB, and configure them as peers?
Thanks,
Maria


Probably, yes, although these days I would suggest that GPS (including 
GLONASS and Galileo) is sufficiently reliable.  WWVB will not be as 
accurate and may be subject to local interference.


I've seen GPS fail due to local jamming (deliberate or accidental), but 
if you separate out the GPS devices across three locations you should 
cover yourself against that.  Be sure to get devices which cover all 
three GPS services I listed to guard against single service failures 
(which have also happened at least once in the past).


What accuracy do you need?  Microseconds, milliseconds, or?

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

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

Re: [ntp:questions] ntp.ymartin.com


On 28/03/2018 21:31, Yves Martin wrote:

I've installed my own ntp server since a year now, using a NTP100 server sync 
with an external GPS antenna. Just need to know if it's reachable from outside. 
Thanks.

ntp.ymartin.com

YM


Yves, this is what I see (edited for brevity):

~
C:\Windows\System32>ntpdate -q ntp.ymartin.com
server 45.73.0.50, stratum 1, offset -0.000736, delay 0.13692
~

so it's reachable.  The offset looks much higher than I see on the Linux 
boxes here (e.g. server 192.168.0.3, stratum 1, offset 0.07, delay 
0.02594).


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

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

Re: [ntp:questions] Issues with decoding Raw DCF77

2018-08-06 Thread Jakob Bohm

On 20/03/2018 21:16, Andreas Mattheiss wrote:

Hello,

I'm monkeying around with raw DCF again ...

I have slightly modified a DCF77 alarm clock so that it constantly
receives the DCF77 signal and tapped into the 100/200ms pulses. Receiption
must be good, since when I pipe this into an Arduino board I get good
results from the decode. For the PC, I first inverted the 100/200ms pulses
with a transistor, then feed the inverted signal into a MAX232 level
converter - inverting is necessary since the MAX232 inverts the CMOS level
signal itself. The MAX232 has a LED at the output that now duly shows
100 and 200ms flashes - i.e. it is out most of the time. Hook up to ttyS2.

So far, so good. Alas I only get crap:

20 Mar 20:59:53 ntpd[15775]: parse: convert_rawdcf: start bit / parity check FAILED for
"###RADMLS1248124P124812P1248121241248112481248P??"
20 Mar 20:59:53 ntpd[15775]: parse: convert_rawdcf: start bit / parity check FAILED for
"###RADMLS1248124P124812P1248121241248112481248P??"
20 Mar 20:59:54 ntpd[15775]: parse: convert_rawdcf: start bit / parity check FAILED for
"###RADMLS1248124P124812P1248121241248112481248P??"
20 Mar 20:59:54 ntpd[15775]: parse: convert_rawdcf: start bit / parity check FAILED for
"###RADMLS1248124P124812P1248121241248112481248P??"
20 Mar 20:59:54 ntpd[15775]: parse: convert_rawdcf: start bit / parity check FAILED for
"###RADMLS1248124P124812P1248121241248112481248P??"
20 Mar 20:59:54 ntpd[15775]: parse: convert_rawdcf: start bit / parity check FAILED for
"###RADMLS1248124P124812P1248121241248112481248P??"
20 Mar 21:00:00 ntpd[15775]: parse: convert_rawdcf: start bit / parity check FAILED for
"###RADMLS1248124P124812P124812124124811248"
20 Mar 21:00:03 ntpd[15775]: parse: convert_rawdcf: start bit / parity check FAILED for
"#--RADMLS1248124P124812P1248121241248112481248P??"
20 Mar 21:00:03 ntpd[15775]: parse: convert_rawdcf: start bit / parity check FAILED for
"###RADMLS1248124P124812P1248121241248112481248P??"
20 Mar 21:00:03 ntpd[15775]: parse: convert_rawdcf: start bit / parity check FAILED for
"###RADMLS1248124P124812P1248121241248112481248P??"
20 Mar 21:00:03 ntpd[15775]: parse: convert_rawdcf: start bit / parity check FAILED for
"###RADMLS1248124P124812P1248121241248112481248P??"

... ad nauseam. Look at the time stamps - rather lots of action for 50
baud, isn't it? It looks very strange to me when I do a cat /dev/ttyS2 |
xxd -b:

1d4: ..
1da: ..
1e0: ..
1e6: ..
1ec: ..
1f2: ..
1f8: ..
1fe: ..
204: 1000 ..
20a: ..
210: ..
216: ..
21c: ..
222: ..
228: ..
22e: ..
234: ..

This is being churned out at a surprisingly high speed. The
groups are 100ms pulses, and is supposed to be 200ms. But why the
heck am I getting so much more 0x00 than 0xf0?

http://comp.protocols.time.ntp.narkive.com/oQhF2g2W/aw-convert-rawdcf-parity-check-failed-on-my-embedded-linux-system
mentions

---quote---
you should receive 1 byte ( or a framing error/break ) every second for 59
seconds
every 60 seconds.

100ms --> 5 Bit times -> 1 stop and 4 LSbit low, rest high -> 0xf0
200ms --> 10 bit Times -> 1 stop and 9 LSbit low, the high -> either 0x00 or
framing error
only jitter between leading and trailing edge is relevant.
The distance between acceptable low and high indicating chars is always big
enough.
---unquote---

I have a dark feeling of foreboding that I'm chasing a RS-232 issue here.
Alas my knowledge in this realm is very limited; I do understand that ntpd
is doing something very smart by setting the port to 50 baud, but I am all
at sea to decide whether the strange bit pattern I get from tapping into
the serial port is correct or not. Presumably it isn't; it probably gets
gobs of 0x00's, very quickly (explains the rapid procession of error posts
in the ntpd log), and since it's 0x00's,

[ntp:questions] Many new messages in test results.

2018-08-06 Thread brian utterback

I am in the process of integrating the lasted update and I am running
into a bunch of new messages in the logs. They all appear to be errors
or warnings and the associated tests seem to all be marked PASS. Are
these messages expected?

Here are the diffs from the previous release:

> 12 Mar 08:22:55 test-kodDatabase[820245]: An error occured while
parsing the KoD db file /dev/null
> 12 Mar 08:22:55 test-kodDatabase[820245]: An error occured while
parsing the KoD db file /dev/null
> 12 Mar 08:22:55 test-kodDatabase[820245]: An error occured while
parsing the KoD db file /dev/null
> 12 Mar 08:22:57 test-kodDatabase[820245]: An error occured while
parsing the KoD db file /dev/null

> TEST_PROGNAME[820215]: TESTING sntp_init_logging()

> 12 Mar 08:22:55 test-packetHandling[820227]: KOD code DENY from
192.0.2.1 192.0.2.1
> 12 Mar 08:22:55 test-packetHandling[820227]: 2018-03-12
08:22:55.563271 (+0800) -0.04 +/- 64817.265689  0.0.0.0 s204 unsync

> 12 Mar 08:22:55 test-packetProcessing[820233]: UnitTest: Incredible
packet length: 47.  Discarding.
> 12 Mar 08:22:55 test-packetProcessing[820233]: UnitTest: Incredible
packet length: 47.  Discarding.
> 12 Mar 08:22:55 test-packetProcessing[820233]: UnitTest: Incredible
packet length: 54.  Discarding.
> 12 Mar 08:22:55 test-packetProcessing[820233]: UnitTest: Incredible
packet length: 51.  Discarding.
> 12 Mar 08:22:55 test-packetProcessing[820233]: UnitTest: Missing
extension field.  Discarding.
> 12 Mar 08:22:55 test-packetProcessing[820233]: UnitTest: Packet shows
wrong version (0)
> 12 Mar 08:22:55 test-packetProcessing[820233]: UnitTest: Packet shows
wrong version (5)
> 12 Mar 08:22:55 test-packetProcessing[820233]: UnitTest: mode 3 stratum 0
> 12 Mar 08:22:55 test-packetProcessing[820233]: UnitTest: 0.0.0.0 not
in sync, skipping this server
> 12 Mar 08:22:55 test-packetProcessing[820233]: 0.0.0.0 response org
expected to match sent xmt
> 12 Mar 08:22:55 test-packetProcessing[820233]: resp org:
03e8.  Wed, Feb  6 2036 22:44:56.000
> 12 Mar 08:22:55 test-packetProcessing[820233]: sent xmt:
07d0.  Wed, Feb  6 2036 23:01:36.000

I am also getting a bunch of errors in two timespecops tests:

timespecops.c:54:test_AbsWithFrac:PASS
m_expr which is -2.1
and
n_expr which is -2.18446744073709551613
are not close; diff=0.4nsec
m_expr which is -2.1
and
n_expr which is -2.18446744073709551614
are not close; diff=0.3nsec
m_expr which is -2.1
and
n_expr which is -2.4
are not close; diff=0.3nsec
m_expr which is -2.1
and
n_expr which is -2.5
are not close; diff=0.4nsec
m_expr which is -2.5
and
n_expr which is -2.49996
are not close; diff=0.4nsec
m_expr which is -2.5
and
n_expr which is -2.49997
are not close; diff=0.3nsec
m_expr which is -2.5
and
n_expr which is -2.50003
are not close; diff=0.3nsec
m_expr which is -2.5
and
n_expr which is -2.50004
are not close; diff=0.4nsec
m_expr which is -2.9
and
n_expr which is -2.5
are not close; diff=0.4nsec
m_expr which is -2.9
and
n_expr which is -2.6
are not close; diff=0.3nsec
m_expr which is -2.9
and
n_expr which is -2.12
are not close; diff=0.3nsec
m_expr which is -2.9
and
n_expr which is -2.13
are not close; diff=0.4nsec
m_expr which is -1.1
and
n_expr which is -1.18446744073709551613
are not close; diff=0.4nsec
m_expr which is -1.1
and
n_expr which is -1.18446744073709551614
are not close; diff=0.3nsec
m_expr which is -1.1
and
n_expr which is -1.4
are not close; diff=0.3nsec
m_expr which is -1.1
and
n_expr which is -1.5
are not close; diff=0.4nsec
m_expr which is -1.5
and
n_expr which is -1.49996
are not close; diff=0.4nsec
m_expr which is -1.5
and
n_expr which is -1.49997
are not close; diff=0.3nsec
m_expr which is -1.5
and
n_expr which is -1.50003
are not close; diff=0.3nsec
m_expr which is -1.5
and
n_expr which is -1.50004
are not close; diff=0.4nsec
m_expr which is -1.9
and
n_expr which is -1.5
are not close; diff=0.4nsec
m_expr which is -1.9
and
n_expr which is -1.6
are not close; diff=0.3nsec
m_expr which is -1.9
and
n_expr which is -1.12
are not close; diff=0.3nsec
m_expr which is -1.9
and
n_expr which is -1.13
are not close; diff=0.4nsec
m_expr which is 0.1
and
n_expr which is 0.18446744073709551613
are not close; diff=0.4nsec
m_expr which is 0.1
and
n_expr which is 0.18446744073709551614
are not close; diff=0.3nsec
m_expr which is 0.1
and
n_expr which is 0.4
are not close; diff=0.3nsec
m_expr which is 0.1
and
n_expr which is 0.00

[ntp:questions] ntp-4.2.8p11 for Windows