Web lists-archives.com

Re: ntp problem in broadcastclients




On Wednesday 24 October 2018 10:27:04 john doe wrote:

> On 10/24/2018 2:44 PM, Greg Wooledge wrote:
> > On Wed, Oct 24, 2018 at 08:22:49AM -0400, Gene Heskett wrote:
> >> I has this machine running ntp normally, and set to broadcast on
> >> the $local/24 network.
> >
> > I've never used NTP in "broadcast" mode.
The idea is to reduce the loading of 7 machines all banging one the level 
1 and 2 servers by designating one machine to bang of the debian pool, 
and then broadcast it on the local 192.169.xx.xx net so all the others 
stay within a millisecond of this machine.
2 machines report:
pi@picnc:/etc $ ntpq -p
No association ID's returned

One is keeping perfect time, the otheris off about 35 seconds, eveb after 
a warm reboot.
All the other machines show:
gene@sheldon:~$ ntpq -p
     remote           refid      st t when poll reach   delay   offset  
jitter
==============================================================================
*coyote.coyote.d 65.223.27.156    2 u  387  512  377    0.137   -2.334   
0.667

Or very similar, One machine, an armhrpi-3b an armhf running jessie, 
makes me be root before ntpq -p will return good data.

> >
> > If it were me, I would simply use the normal configuration in which
> > each client system has the NTP server's hostname or IP address in
> > the /etc/ntp.conf file.  If it turns out this "broadcast" thing
> > is the problem, then I'm not the right person to help.
> >
> > But...
> >
> >> Any clues of what else to check/change?
> >
> > Well, the obvious starting point would be "ntpq -p" on each system.
> > This is the new version of "ntptrace" which apparently has been
> > deprecated in order to make everyone's life harder.

I see you've noticed. I look at doing away with ntpdate with a semi 
juandiced viewpoint.

> > In addition to that, check the logs.  If these are wheezy boxes (or
> > older) then you want /var/log/daemon.log*.  If they're systemd
> > boxes, then you want (as root) journalctl -u ntp.
>
> In addition to the above, I would look at any kind of restriction
> (FW...) between the clients and the server.

Firewall? whuzat?  I'm behind dd-wrt and all the radios are off to keep 
out the neighbors cell phones. firewall by shutting out the outside 
world IOW.

daemon.log.1 looks normal and reports its listening on eth0. daemon.log 
was rotated this morning and was empty until I did a warm reboot half an 
hour ago. And after the reboot its still 25 seconds slow.

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