Re: ntp problem in broadcastclients
On Thu, Oct 25, 2018 at 05:36:21PM -0400, Gene Heskett wrote:
> 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?
According to <http://doc.ntp.org/4.2.2/debug.html>, BCST means "The
association belongs to a broadcast server." And unfortunately, as I
mentioned before, I've never used NTP in broadcast mode. So at this
point you're officially beyond my knowledge level.
Reply to: