Date: Tue, 31 Aug 2004 14:57:50 -0500 From: "W. D." <NewsGroups@US-Webmasters.com> To: Danny Mayer <mayer@gis.net> Cc: david-taylor@blueyonder.co.uk Subject: Re: ntpd as broadcastclient - not working? Message-ID: <4134D83E.64DC@US-Webmasters.com> References: <412F8064.353E@US-Webmasters.com> <413108CA.6826@US-Webmasters.com> <cgr4r5$pfd$1@dewey.udel.edu> <413124A7.476@US-Webmasters.com> <cgru7u$4dd$1@dewey.udel.edu> <41317FC5.3B5C@US-Webmasters.com> <4132C360.386D@US-Webmasters.com> <nPmdnYcopc3gEa7cRVn-hQ@comcast.com> <4133B4AD.1C74@US-Webmasters.com> <20040830215514.790$9k@newsreader.com> <4133ED52.79E@US-Webmasters.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for looking into this, Danny! Reply below... At 12:49 8/31/2004, Danny Mayer, wrote: >At 11:15 PM 8/30/2004, W. D. wrote: >>Hi Danny, >> >>Reply below... >> >>At 19:02 8/30/2004, Danny Mayer wrote: >> >At 07:13 PM 8/30/2004, W. D. wrote: >> >>30 Aug 21:50:05 ntpd[88]: logging to file /var/log/ntpd.log >> >>30 Aug 21:50:05 ntpd[88]: ntpd 4.2.0a@1.1219-o Mon Aug 30 14:14:07 GMT >> >>2004 (1) >> >>30 Aug 21:50:05 ntpd[88]: precision = 4.191 usec >> >>30 Aug 21:50:05 ntpd[88]: Listening on interface dc0, >> >>fe80:1::2a0:ccff:fe50:e7c7#123 >> >>30 Aug 21:50:05 ntpd[88]: Listening on interface dc0, 192.168.2.177#123 >> >>30 Aug 21:50:05 ntpd[88]: Listening on interface lo0, ::1#123 >> >>30 Aug 21:50:05 ntpd[88]: Listening on interface lo0, fe80:3::1#123 >> >>30 Aug 21:50:05 ntpd[88]: Listening on interface lo0, 127.0.0.1#123 >> >>30 Aug 21:50:05 ntpd[88]: kernel time sync status 2040 >> >>30 Aug 21:50:05 ntpd[88]: frequency initialized 0.000 PPM from >> >>/etc/ntp.drift >> >>30 Aug 21:50:05 ntpd[88]: Unable to listen for broadcasts, no broadcast >> >>interfaces available >> > >> >What does ifconfig -a tell you? >> >> >>dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 >> inet6 fe80::2a0:ccff:fe50:e7c7%dc0 prefixlen 64 scopeid 0x1 >> inet 192.168.2.177 netmask 0xffffff00 broadcast 192.168.2.255 >> ether 00:a0:cc:50:e7:c7 >> media: Ethernet autoselect (100baseTX <full-duplex>) >> status: active >>lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500 >>lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 >> inet6 ::1 prefixlen 128 >> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 >> inet 127.0.0.1 netmask 0xff000000 >>ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500 >>sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552 >>faith0: flags=8002<BROADCAST,MULTICAST> mtu 1500 >> > >That means the broadcast flag is set for the dc0 interface for IP address >192.168.2.177. >You appear to be missing the following patch to libisc/ifiter_ioctl.c: > >http://ntp.bkbits.net:8080/ntp-dev/diffs/libisc/ifiter_ioctl.c@1.15?nav=inde >x.html|src/.|src/libisc|hist/libisc/ifiter_ioctl.c http://tinyurl.com/66see Most of these files in libisc are dated 2004 Feb 24. More... >Basically you are missing the following: > > > if ((lifreq.lifr_flags & IFF_BROADCAST) != 0) { > iter->current.flags |= INTERFACE_F_BROADCAST; > } > >That should have been in the latest ntp-dev tarball. I downloaded the 2004 Aug 26 version from: ftp://ftp.starhub.net.sg/pub/funet/unix/tcpip/ntp/xntp/udel/ntp4/ For some reason, I can't get to the UDel.edu FTP site. Do you happen to know why? ftp://ftp.udel.edu/pub/ntp/ntp4/ >Otherwise please add it >and rebuild. In the 2004 Aug 26 version that I have, the libisc/ifiter_ioctl.c file is dated 2004 Feb. 24. Within it, I can't find the places to edit this file. I suspect that this file is probably far out of date compared to the current version. Here is what I have: http://www.us-webmasters.com/Temp/ifiter_ioctl.c.txt Rather than trying to edit this C file, would it be better to just download the 2004 Aug 30, or later version? ftp://ftp.starhub.net.sg/pub/funet/unix/tcpip/ntp/xntp/udel/ntp4/ ntp-dev-4.2.0a-20040830.tar.gz http://www.FileSearching.com/cgi-bin/s?q=ntp-dev-4.2&t=f&d=&l=en More... >> >>The Windows computer generating the Tardis NTP broadcasts is >> >>at IP address: 192.168.2.119. Does anyone have any idea >> >>why it's not picking up these broadcasts? >> > >> >Also, that's not a broadcast address as I recall. >> >>It's the internal, NAT address, that my DHCP server/router >>assigned to the Windows box that is sending out NTP >>broadcast signals on port 123. > > >That doesn't really matter. What address is it broadcasting on? 255.255.255.255 However, Tardis can be configured to broadcast on any address. What is/are the recommended IP address(es)?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4134D83E.64DC>