Re: ntpd as broadcastclient - not working?
At 04:59 AM 9/3/2004, W. D. wrote: Well folks, I got it working--sorta. You message shows that you are not running broadcast. This page has to have the date stuff on the left side edited out: http://tinyurl.com/72c69 The result is then substituted for /libisc/ifiter_ioctl.c, and then the whole thing is rebuilt. More properly you could just have used the latest version of the tarball that you had. The time only seems to be set if I use in /etc/ntp.conf: broadcastclient rather than: broadcastclient 192.168.2.255 This is illegal. There are no additional parameters to broadcastclient. except for novolley. If you didn't get an error message about that then that's a bug. Also, Tardis must be set to send NTP broadcasts to the FreeBSD box's IP address: 192.168.2.177 Again that's not a broadcast address. That's the IP address of that one machine. The address you put in broadcastclient is what should have been put into the tardis configuration. Here is the output from ifconfig -a: dc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::2a0:ccff:fe50:e7c7%dc0 prefixlen 64 scopeid 0x1 inet 192.168.2.177 netmask 0xff00 broadcast 192.168.2.255 ether 00:a0:cc:50:e7:c7 media: Ethernet autoselect (100baseTX full-duplex) status: active lp0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 ppp0: flags=8010POINTOPOINT,MULTICAST mtu 1500 sl0: flags=c010POINTOPOINT,LINK2,MULTICAST mtu 552 faith0: flags=8002BROADCAST,MULTICAST mtu 1500 Here is what is logged in ntpd.log: 3 Sep 03:29:32 ntpd[88]: logging to file /var/log/ntpd.log 3 Sep 03:29:32 ntpd[88]: ntpd [EMAIL PROTECTED] Thu Sep 2 21:37:09 GMT 2004 (1) 3 Sep 03:29:32 ntpd[88]: precision = 4.191 usec 3 Sep 03:29:32 ntpd[88]: Listening on interface dc0, fe80:1::2a0:ccff:fe50:e7c7#123 3 Sep 03:29:32 ntpd[88]: Listening on interface dc0, 192.168.2.177#123 3 Sep 03:29:32 ntpd[88]: Listening on interface lo0, ::1#123 3 Sep 03:29:32 ntpd[88]: Listening on interface lo0, fe80:3::1#123 3 Sep 03:29:32 ntpd[88]: Listening on interface lo0, 127.0.0.1#123 3 Sep 03:29:32 ntpd[88]: kernel time sync status 2040 3 Sep 03:29:32 ntpd[88]: frequency initialized -0.094 PPM from /etc/ntp.drift 3 Sep 03:29:32 ntpd[88]: Unable to listen for broadcasts, no broadcast interfaces available This shows that you are not getting any broadcasts since it can't configure a socket for broadcast. So you don't have the fix in place. 3 Sep 03:29:41 ntpd[88]: synchronized to 192.168.2.119, stratum 2 3 Sep 03:29:34 ntpd[88]: time reset -6.102537 s 3 Sep 03:29:34 ntpd[88]: kernel time sync disabled 2041 3 Sep 03:29:42 ntpd[88]: synchronized to 192.168.2.119, stratum 2 3 Sep 03:29:52 ntpd[88]: kernel time sync enabled 2001 3 Sep 03:30:15 ntpd[88]: no servers reachable This tells you that it's not getting any packets from any server you listed in ntp.conf. Here is the output from ntpdc monlist: remote address port local address count m ver code avgint lstint === localhost 1041 ::15 7 2 0 34 0 192.168.2.119123 192.168.2.177132 5 3 0 3 3 Which is not broadcast. How can I get the FreeBSD box to listen on 192.168.2.255? I told you repeatedly. How would I know when it hears an NTP broadcast? You would see it in the log that it's enabled for broadcast. ntpq -p should show it. Does ntpd adjust for drift against the realtime clock, and then use this if the broadcasts stop for some reason? If nothing is available it just leaves things where they are. Any other glaring errors here? Too many. See above. Danny ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd as broadcastclient - not working?
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 [EMAIL PROTECTED] 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=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet6 fe80::2a0:ccff:fe50:e7c7%dc0 prefixlen 64 scopeid 0x1
inet 192.168.2.177 netmask 0xff00 broadcast 192.168.2.255
ether 00:a0:cc:50:e7:c7
media: Ethernet autoselect (100baseTX full-duplex)
status: active
lp0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet 127.0.0.1 netmask 0xff00
ppp0: flags=8010POINTOPOINT,MULTICAST mtu 1500
sl0: flags=c010POINTOPOINT,LINK2,MULTICAST mtu 552
faith0: flags=8002BROADCAST,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/[EMAIL
PROTECTED]|src/.|src/libisc|hist/libisc/ifiter_ioctl.c
Basically you are missing the following:
if ((lifreq.lifr_flags IFF_BROADCAST) != 0) {
iter-current.flags |= INTERFACE_F_BROADCAST;
}
That should have been the latest ntp-dev tarball. Otherwise please add it
and rebuild.
Danny
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?
Danny
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd as broadcastclient - not working?
At 03:57 PM 8/31/2004, W. D. wrote: 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 Why would you be trying to broadcast to everyone in the world? Try 192.168.2.255. If it's not on the same subnet it would need to be a different address. However, Tardis can be configured to broadcast on any address. What is/are the recommended IP address(es)? No it can't. There are only (relatively) few broadcast addresses and the routers have to support them or it will drop the packets if they are not link local. Danny ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd as broadcastclient - not working?
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 [EMAIL PROTECTED] 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? Danny 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. Somewhere in here I also changed the CMOS Real Time Clock to UTC, and reconfigured for my local time in /stand/sysinstall Now what? How do I get the program to 'hear' the broadcasts? See above. Danny ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
