[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ntp problem in broadcastclients



On Thursday 25 October 2018 16:50:11 Greg Wooledge wrote:

> On Thu, Oct 25, 2018 at 04:40:46PM -0400, Gene Heskett wrote:
> > I added the router to the server list for this machine and get this
> > for an ntpq -p: remote           refid      st t when poll reach  
> > delay   offset  jitter
> > ====================================================================
> >========== router.coyote.d .INIT.          16 u    -  512    0   
> > 0.000    0.000   0.000 -ip7.nsg.sbbsnet 64.113.44.54     2 u   31  
> > 64   17   43.611    5.083   2.148 +142.147.92.5.st 216.218.192.202 
> > 2 u   37   64  377   82.436   -3.643   1.587 *dfw1.m-d.net   
> > 204.9.54.119     2 u   99   64  376   49.024   -0.327   1.700
> > +12.167.151.2    198.148.79.210   3 u   31   64  377   15.694   
> > 0.584   2.247 192.168.71.255  .BCST.          16 u    -   64    0   
> > 0.000    0.000   0.000
>
> The first line (router.coyote.d, which I presume is your router)
> is showing stratum 16, which means it does not consider itself to be
> a valid time source yet. 

I wondered about that since I couldn't find a place in the  recent dd-wrt to enable broadcasting. So the last best step is to remove that ntp.conf 
entry, and either just leave the router to its own resources, or even change its server setting to this machine..

> This could be because you haven't given it 
> enough time to stabilize (i.e. you just restarted it), or because it
> can't actually contact any time servers in order to synchronize at
> all.
>
> If it remains "st 16" for more than a few minutes, then something is
> probably wrong.

I put the router back on pool.ntp.org, but had to reboot it to take effect.

Now this machine shows for ntpq -p:
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+159.203.158.197 45.33.103.94     3 u   59   64    3   19.551   -1.356  61.116
*tick.mdacore.ne 130.207.244.240  2 u   61   64    3   30.488   -2.042   3.042
-ntp3.junkemailf 216.218.254.202  2 u   59   64    3   82.196   -7.491   2.306
+208.76.53.137   216.218.254.202  2 u   64   64    3   40.852   -2.476   0.889
 192.168.71.255  .BCST.          16 u    -   64    0    0.000    0.000   0.000

But should the .BCST. be a 16 ?? Or is that just the nature of the beast?
>
> Meanwhile, this system is getting valid time synchronization from four
> other sources (three of them stratum 2, one stratum 3).  Your offset
> values look good (the offset is shown in milliseconds, so you are
> within about 5 milliseconds of all your valid sources).

Thanks Greg.

-- 
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 <http://geneslinuxbox.net:6309/gene>


Reply to: