Web lists-archives.com

Re: ntp problem in broadcastclients




On 2018-10-25, Gene Heskett <gheskett@xxxxxxxxxxx> wrote:

> 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?
>>

>From what I can grok, yes, the .BCST line is normal because that is the
broadcast address for the sub-net to which you are broadcasting, and
ntpd cannot sync to itself (default stratum 16). 

I can't seem to find an example of a ntpq -p output that has a .BCST
address with a stratum other than 16 (maybe I'm not looking hard
enough) which leads me to believe it's okey-dokey.

Famous last words: I don't really know anything about this and so could be
partially, if not all, wet.


-- 
"Now she understood that Anna could not have been in lilac, and that her charm
was just that she always stood out against her attire, that her dress could
never be noticeable on her." Leo Tolstoy, Anna Karenina