[Thumbgps-devel] decoding ntp... does anyone really know what time it is?

[Thumbgps-devel] decoding ntp... does anyone really know what time it is?

[Dave Taht]

I should probably get back on the timenuts list but perhaps someone
here can explain this:

http://www.eecis.udel.edu/~mills/ntp/html/decode.html

So I have a pps configuration of the gpsd configured. Or thought I
did. Actually, in this case, gpsd had failed to start on beagle-1 for
some reason, ntpd started without it, and I started it after ntpd.

I'm still waiting for ntp to pick it up, so far, which I talk to
below. I'm just curious as to how viable tickers evolve over time....

Anyway, a - means it's discarded from the cluster algorithm. Beagle-1
is my gps served ntp server

on a remote client:

ntpq> peer
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
-beagle-1        199.102.46.72    2 u  984 1024  377    0.779  -23.343   3.593
*pool-test.ntp.o 127.67.113.92    2 u  937 1024  357   35.216   -4.543   5.157
-d7.hotfile.com  220.183.68.66    2 u  726 1024  377   81.001   -8.452   4.082
-ntp.westbrook.c 120.119.68.211   3 u  830 1024  375   29.350  -11.324  13.744
+208.79.16.124   198.60.22.240    2 u  797 1024  377  123.573  -10.639  12.673
+golem.canonical 193.79.237.14    2 u   83 1024  377  161.633    2.891   8.818

on beagle-1 (after I restarted gpsd)

 ntpq -n -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 127.127.28.0    .GPS.            0 l   21   16   76    0.000  302.125   0.858
 127.127.28.1    .GPS1.           0 l    -   16    0    0.000    0.000   0.000
+69.50.219.51    209.51.161.238   2 u  446  512  173   78.353    4.241  15.379
-216.229.0.49    216.229.0.179    2 u  876  512  376  157.278  -14.828   4.858
+2001:4f8:fff7:1 66.220.9.122     2 u  237  512  377   24.358   16.313   7.613
*199.102.46.72   .GPS.            1 u  457  512  333  155.082    0.735   9.664

My assumption is that after a suitable period, the client box will
grok that the beagle-1 box is stratum 1 and move over to it, or are
their other heuristics involved?

After a while, the above became marked with an X (and I think pps
didn't kick in)

root@beagle-1:/var/spool# ntpq -n -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
x127.127.28.0    .GPS.            0 l  123   16  200    0.000  302.125   0.972
 127.127.28.1    .GPS1.           0 l    -   16    0    0.000    0.000   0.000
+69.50.219.51    209.51.161.238   2 u   20  512  367   75.973    2.586  14.346
+216.229.0.49    216.229.0.179    2 u  978  512  376  157.278  -14.828   4.858
-2001:4f8:fff7:1 66.220.9.122     2 u  339  512  377   24.358   16.313   7.613
*199.102.46.72   .GPS.            1 u   20  512  267  140.874  -11.207   6.531


which is  "discarded by intersection algorithmn"

Does
-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

Re: [Thumbgps-devel] decoding ntp... does anyone really know what time it is?

[Gary E. Miller]

[-- Attachment #1: Type: text/plain, Size: 924 bytes --]

Yo Dave!

On Mon, 22 Jul 2013 16:30:26 -0700
Dave Taht <dave.taht@gmail.com> wrote:

> After a while, the above became marked with an X (and I think pps
> didn't kick in)
> 
> root@beagle-1:/var/spool# ntpq -n -p
>      remote           refid      st t when poll reach   delay
> offset  jitter
> ==============================================================================
> x127.127.28.0    .GPS.           0 l  123   16  200  0.000  302.125   0.972
> 127.127.28.1    .GPS1.           0 l    -   16  0    0.000    0.000   0.000

Yeah, reach zero means you are not seeing the PPS.  The priveledge separation
got broken a while back in gpsd.  You might have to run gpsd as
root in the foreground for PPS.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97701
	gem@rellim.com  Tel:+1(541)382-8588

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [Thumbgps-devel] decoding ntp... does anyone really know what time it is?

[Dave Taht]

I ran it with the -n option and restarted ntp and it worked. So it
looks like the beagle kernel has the pps stuff after all.

root@beagle-1:/var/spool# ntpq -n -pn
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
x127.127.28.0    .GPS.            0 l    -   16  377    0.000  283.988   1.878
*127.127.28.1    .GPS1.           0 l   15   16  377    0.000   -1.045   3.570
-206.253.165.93  216.45.49.100    3 u   21   64    7   34.315    2.912  11.894
+97.107.129.217  129.6.15.29      2 u   24   64    7   89.570   -4.246   5.943
+2001:470:1:24f: 204.123.2.72     2 u   88   64    6   24.392   -6.482   3.163
-50.23.135.154   173.13.85.5      2 u   20   64    7   46.942    4.639   9.237


On Mon, Jul 22, 2013 at 5:58 PM, Gary E. Miller <gem@rellim.com> wrote:
> Yo Dave!
>
> On Mon, 22 Jul 2013 16:30:26 -0700
> Dave Taht <dave.taht@gmail.com> wrote:
>
>> After a while, the above became marked with an X (and I think pps
>> didn't kick in)
>>
>> root@beagle-1:/var/spool# ntpq -n -p
>>      remote           refid      st t when poll reach   delay
>> offset  jitter
>> ==============================================================================
>> x127.127.28.0    .GPS.           0 l  123   16  200  0.000  302.125   0.972
>> 127.127.28.1    .GPS1.           0 l    -   16  0    0.000    0.000   0.000
>
> Yeah, reach zero means you are not seeing the PPS.  The priveledge separation
> got broken a while back in gpsd.  You might have to run gpsd as
> root in the foreground for PPS.
>
> RGDS
> GARY
> ---------------------------------------------------------------------------
> Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97701
>         gem@rellim.com  Tel:+1(541)382-8588



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

Re: [Thumbgps-devel] decoding ntp... does anyone really know what time it is?

[Gary E. Miller]

[-- Attachment #1: Type: text/plain, Size: 635 bytes --]

Yo Dave!

On Mon, 22 Jul 2013 18:01:56 -0700
Dave Taht <dave.taht@gmail.com> wrote:

> I ran it with the -n option and restarted ntp and it worked. So it
> looks like the beagle kernel has the pps stuff after all.

That shows you PPS is working, but says nothing about the kernel.
Kernel support is not required for PPS, it just makes PPS more accurate.
Which is prolly not a issue given the GR-601W limited by the USB 1.1/

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97701
	gem@rellim.com  Tel:+1(541)382-8588

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]