> interface listen wildcard > interface listen all I tried these on a Windows 8, 64-bit machine. It does not solve any problems; NTP still puts the following messages into the Event Log on startup:
bind(308) AF_INET 192.168.1.255#123 flags 0x419 failed: Can't assign requested address failed to listen for broadcasts to 192.168.1.255 on interface #3 Ethernet 5 bind(308) AF_INET 192.168.0.255#123 flags 0x419 failed: Can't assign requested address failed to listen for broadcasts to 192.168.0.255 on interface #5 Ethernet 4 Unable to listen for broadcasts, no broadcast interfaces available However, broadcasts still work fine, with the exception that now, with the above two copied lines in the conf file, NTPD now puts the following two lines in the Windows Event Log every 16 seconds: 192.168.1.88 local addr 192.168.1.100 -> 0.0.0.0 192.168.1.88 local addr 0.0.0.0 -> 192.168.1.100 192.168.1.88 is the broadcast server, and 192.168.1.100 is this machine, one of the recipients. Charles Elliott > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On > Behalf Of Gary Johnson > Sent: Thursday, April 25, 2013 2:35 PM > To: [email protected] > Subject: Re: [ntp:questions] ntpd 4.2.6p5 will not synchronize to > broadcast servers > > Brian Utterback <[email protected]> wrote: > > I think this is a duplicate of bug 629. > > > > On 4/24/2013 9:54 PM, Harlan Stenn wrote: > > > Gary, > > > > > > The short answer is "I don't know". I believe we have successfully > used > > > broadcast clients in 4.2.6. > > > > > > Please see if ntp-dev works for you though - if there is a problem > there > > > we want to fix that before releasing 4.2.8. > > > > > > And having written the above: > > > > > > http://bugs.ntp.org/show_bug.cgi?id=2261 > > Thank you both! I had found those bug reports earlier, but I didn't > think that wildcards and "255.255.255.255" applied in my case, so I > didn't look closely at either one. I read the discussions associated > with both last night and applied Dave Hart's suggestion at the bottom > of > the bug 629 discussion to add > > interface listen wildcard > interface listen all > > to my /etc/ntp.conf. Broadcast now works! > > I changed the simple test case I posted originally to > > $ ntpd -4 -b -D2 -c /etc/ntp.conf.test & > > where /etc/ntp.conf.test contains only those two interface commands. > It > still emits the message > > 25 Apr 16:50:38 ntpd[31987]: Unable to listen for broadcasts, no > broadcast interfaces available > > but broadcast works anyway. > > I then added those two interface commands to the top of our normal > /etc/ntp.conf file and broadcast now works in the context of our > application as well. > > Does it matter where in /etc/ntp.conf those commands are put? > > I will download and install ntp-dev later today and let you know how > that goes. > > Thanks again, > Gary > > _______________________________________________ > questions mailing list > [email protected] > http://lists.ntp.org/listinfo/questions _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
