Re: ntpd as broadcastclient - not working?

2004-09-04 Thread Danny Mayer
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?

2004-09-01 Thread W. D.
Hi Harlan,

Thanks for your reply.

Harlan Stenn wrote:
 
 I recommend you get the latest ntp-dev stable tarball 

Is there anything more recent than:
http://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/ntp-dev-4.2.0a-20040830.tar.gz


 and build it
 using the instructions I gave you earlier.

Yes, thank you for those instructions.

However, Danny has said that a bug was fixed 
in 'ifiter_ioctl.c' last March:

http://bugzilla.ntp.org/show_bug.cgi?id=267
http://tinyurl.com/66see

If that is true, then with the latest tarball
shown above, how could the fix be included since
the date of this file is 2004 *FEBRUARY* 25th?
http://www.US-Webmasters.com/Temp/NTP-broadcastclient-File-List.gif

Do you see my point?  It appears impossible for
Danny's fix to be included.  Is it hidden somewhere
else?

What am I missing here?






-- 
Start Here to Find It Fast!™ -
http://www.US-Webmasters.com/best-start-page/
$8.77 Domain Names - http://domains.us-webmasters.com/
___
[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?

2004-08-31 Thread Danny Mayer
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?

2004-08-31 Thread W. D.
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 [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]
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.2t=fd=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)?
___
[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?

2004-08-31 Thread Harlan Stenn
If you cannot use FTP it is because there were Serious Hacking attempts
aimed at UDel from that netblock.

You will have to use http instead.

H
___
[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?

2004-08-31 Thread W. D.
At 17:16 8/31/2004, Harlan Stenn, wrote:
At 14:57 8/31/2004, W. D., wrote:
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/

If you cannot use FTP, it is because there were Serious Hacking attempts
aimed at UDel from that netblock.

You will have to use http instead.


Thanks, Harlan.  I tried using Lynx here:

http://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/

Unfortunately, I can't seem to find where Lynx put the 
file after is was downloaded--if it even really 
downloaded it in the first place.

If I download using Windows and burn it to a 
CD, would there be problems because the file date
would be off?

Also, I am still waiting to hear back from Danny.
I have a sneaking suspicion that the 2004 Aug. 20
version does not have his broadcastclient fix in
it.



-- 
Start Here to Find It Fast!™ -
http://www.US-Webmasters.com/best-start-page/
$8.77 Domain Names - http://domains.us-webmasters.com/
___
[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?

2004-08-31 Thread W. D.
Thanks for the info, Brad.

Reply below...

[EMAIL PROTECTED] wrote:
 
 W. D. [EMAIL PROTECTED] wrote:
 
  FreeBSD appears to expect these NTP programs to be
  in:
 
  /usr/sbin/
 
  That is where the 2003 Oct port put them.
 
 That's because the FreeBSD port specification modifies the default location
 that we provide as part of the tarball.
 
 I
  downloaded the most recent 'ntp-dev' tarball I could find:
 
  ftp://ftp.starhub.net.sg/pub/funet/unix/tcpip/ntp/xntp/udel/ntp4/ntp-dev-
  4.2.0a-20040826.tar.gz
 
  I did a 'make install' as we discussed previously.  As
  before, the files were compiled to:
 
  /usr/local/sbin/
 
 Right, which is the standard location we provide, unless you choose to
 over-ride it with something else -- which is what the FreeBSD port
 definition does.

Do you have any idea how to get in touch with
whoever is the FreeBSD port maintainer for NTP?

It would be great to find out why it is done this way.

Also, I'd like to find out if the port maintainer 
could help update the NTP port so that this 
broadcastclient problem could be solved with the
regular FreeBSD port, rather than having to do
everything manually.


 
 As for the rest, I'm not sure I can help you.  I'll have to go back and
 re-read your other posts.

-- 
Start Here to Find It Fast!™ -
http://www.US-Webmasters.com/best-start-page/
$8.77 Domain Names - http://domains.us-webmasters.com/
___
[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?

2004-08-31 Thread Brad Knowles
At 5:59 PM -0500 2004-08-31, W. D. wrote:
 Do you have any idea how to get in touch with
 whoever is the FreeBSD port maintainer for NTP?
	On a FreeBSD machine we use to help support the NTP Project, in 
/usr/ports/net/ntp, looking in the Makefile, I see:

MAINTAINER= [EMAIL PROTECTED]
 It would be great to find out why it is done this way.
It's a FreeBSD standard.  Frankly, it doesn't bother me at all.
 Also, I'd like to find out if the port maintainer
 could help update the NTP port so that this
 broadcastclient problem could be solved with the
 regular FreeBSD port, rather than having to do
 everything manually.
	He will just tell you to update your port definition.  The port 
definition I have is for version 4.2.0, and is fully current with our 
latest release.

	Also note that 4.2.0 was recently integrated into the FreeBSD 5.* 
tree, so if you pick up one of the FreeBSD 5.3-BETA tarballs, that 
will bring you up to current.  This version may also be incorporated 
into the upcoming release of the 4.* tree, if that has not yet 
already happened.

	We have a pretty good relationship with the FreeBSD folks, and 
they tend to track things like ntpd pretty closely.

--
Brad Knowles, [EMAIL PROTECTED]
Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
-- Benjamin Franklin (1706-1790), reply of the Pennsylvania
Assembly to the Governor, November 11, 1755
  SAGE member since 1995.  See http://www.sage.org/ for more info.
___
[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?

2004-08-31 Thread Danny Mayer
At 06:37 PM 8/31/2004, W. D. wrote:
At 17:16 8/31/2004, Harlan Stenn, wrote:
At 14:57 8/31/2004, W. D., wrote:
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/
If you cannot use FTP, it is because there were Serious Hacking attempts
aimed at UDel from that netblock.

You will have to use http instead.

Thanks, Harlan.  I tried using Lynx here:
http://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/
Unfortunately, I can't seem to find where Lynx put the
file after is was downloaded--if it even really
downloaded it in the first place.
Make sure you pull the ntp-dev tarball and not the stable.
If I download using Windows and burn it to a
CD, would there be problems because the file date
would be off?
What has the file time got to do with anything?
Also, I am still waiting to hear back from Danny.
I have a sneaking suspicion that the 2004 Aug. 20
version does not have his broadcastclient fix in
it.
I have no idea what that version is or where you got it.
The problem was fixed back in March.
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?

2004-08-31 Thread Danny Mayer
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?

2004-08-31 Thread W. D.
Hi Danny,

Thanks again for your reply.

More...

At 21:15 8/31/2004, Danny Mayer, wrote:
At 06:37 PM 8/31/2004, W. D. wrote:
At 17:16 8/31/2004, Harlan Stenn, wrote:
 At 14:57 8/31/2004, W. D., wrote:
 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/

 If you cannot use FTP, it is because there were Serious Hacking attempts
 aimed at UDel from that netblock.
 
 You will have to use http instead.
 

Thanks, Harlan.  I tried using Lynx here:

http://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/

Unfortunately, I can't seem to find where Lynx put the
file after is was downloaded--if it even really
downloaded it in the first place.

Make sure you pull the ntp-dev tarball and not the stable.

Understood.



If I download using Windows and burn it to a
CD, would there be problems because the file date
would be off?

What has the file time got to do with anything?

In some cases, I seem to be having problems with
the FreeBSD ports if the file date is not exactly
what was expected.


Also, I am still waiting to hear back from Danny.
I have a sneaking suspicion that the 2004 Aug. 20
version does not have his broadcastclient fix in
it.


I have no idea what that version is or where you got it.
The problem was fixed back in March.

I guess I am just perplexed.  I realize that you have
fixed it, but I don't know how to get a hold of that
code.

Here is a screen shot of the 'ifiter_ioctl.c' file
taken from yesterday's ntp-dev version:
http://www.US-Webmasters.com/Temp/NTP-broadcastclient-File-List.gif

If the problem was fixed in March, as far as I can 
tell it didn't get included in this version because 
the file dates are mostly 2004 February 25.  There
is one file dated 2004 March 26, but according to 
what you indicated earlier the bug was contained 
in 'ifiter_ioctl.c':

http://tinyurl.com/66see

Danny, I am not trying to ruffle anybody's feathers,
or cause problems--I am just trying to get my
FreeBSD box to keep the correct time.  I've spent
the last 6 days primarily trying to get this to
work.  I thought it would be a half hour project.
http://makeashorterlink.com/?O1DB32F29

Please have mercy on me and help me out.  ;^)

I am not a professional 'C' programmer so I don't 
really know where your code fix goes in the file.

Regards,

W. D.







Danny


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
 




-- 
Start Here to Find It Fast!™ -
http://www.US-Webmasters.com/best-start-page/
$8.77 Domain Names - http://domains.us-webmasters.com/
___
[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?

2004-08-30 Thread W. D.
Thanks Harlan for your reply.

More below...

At 01:52 8/29/2004, Harlan Stenn wrote:

I'd recommend the latest ntp-dev tarball

Why the ntp-dev?

From what Danny Mayer says, there was a 
broadcastclient bug that was fixed for -Nix
on 2004 March 25:
http://Bugzilla.NTP.org/show_bug.cgi?id=267

According to this listing:
http://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/

there is a 'stable' version as new as 2004 Jun 17.
I am looking for a simple and reliable solution
to use my existing NTP broadcasts (using Tardis)
to synch up my FreeBSD box.  Using a 'development'
version implies that it hasn't been certified to
be used in a production environment, correct?


once you have it:

 % tar xvzf ntp-dev-whatever.gz
 % cd ntp-dev-whatever
 % mkdir A.x
 % cd A.x
 % ../configure
 % make
 % su
 # make install
 # /usr/local/bin/ntpd -gN -D2  (or whatever)


Thanks for this procedure list.  I actually did
the following:

# cd /usr/ports/net/ntp/
# make deinstall

(went to /etc/rc.conf and commmented out lines concerning NTP,
then rebooted to disallow the ntpd program from running)

# mkdir ntp-stable-4.2.0a-20040617
cd /usr/ports/distfiles/
#ftp
ftp open ftp.starhub.net.sg
ftp cd /pub/funet/unix/tcpip/ntp/xntp/udel/ntp4/
ftp get ntp-stable-4.2.0a-20040617.tar.gz
ftp exit
# cp -p ntp-stable-4.2.0a-20040617.tar.gz
/usr/ports/net/ntp/ntp-stable-4.2.0a-20040617/
# cd /usr/ports/net/ntp/ntp-stable-4.2.0a-20040617/
# tar xvzf ntp-stable-4.2.0a-20040617.tar.gz
# mkdir A.x# Why 'A.x'?  Would 'temp' work?
# cd A.x
# ../configure
# make
# make install

The 'make install' seemed to go smoothly , but
I cannot find the new executables for NTP.  The 
old ones from 2003 Oct 27 are still in /usr/sbin/.

When I try to find any files modified in the
past day and run:

find ./ -name *.* -mtime 1

I don't find 'ntpd' or any other new NTP
related executables.  Does anyone know why 
I can't find the executables, and why the old 
ones are still here?  Where should the new
ones be?


And remember that you need to use authentication by default if you
are using broadcast.

If you do not want to use authentication you will either need a line
in your ntp.conf file (I forget what it is, but it should be easy to find)
or use -A on the command line.

Right.  This is what I have been using in rc.conf:

xntpd_enable=YES
xntpd_flags=-A -c /etc/ntp.conf -p /var/run/ntpd.pid -l
/var/log/ntpd.log 





It's pretty easy to set up authentication.

Well, I am sure it should be, but I can't find a 
clear, step-by-step procedure for it.  ;^)

Again, Tardis does not have the option for
authentication--as far as I know.


H


At 02:46 8/29/2004, Harlan Stenn, wrote:
How about you replace tardis with ntpd?

H

Well, I thought it would be just a simple matter
to get my FreeBSD box to listen to the existing
Tardis NTP broadcasts.  I was hoping to avoid
all the complications of setting up NTP on 
a FreeBSD box to duplicate what Tardis is already
doing.

As an aside, I am very dissapointed that that
there isn't more clear and simple documentation
for FreeBSD/Unix software.  I've found 'man'
pages to be almost useless.  They rarely give
examples, and when they do, they are extremely
complicated.  Criminy, why make it easy for
Bill Gates to keep his stranglehold?



W. D. wrote:
 
 Harlan Stenn wrote:
 
  The timeout on ntpq is strange.
 
  broadcast requires auth.  Are you starting ntpd with -A (bad idea) to get
  around this requirement?
 
 Yes, here are the lines that I added to /etc/rc.conf:
 
 xntpd_enable=YES
 xntpd_flags=-A -c /etc/ntp.conf -p /var/run/ntpd.pid -l
 /var/log/ntpd.log
 
 What else can I do?  Tardis doesn't have the
 authentication option--as far as I know.
 
 Although I have some Pentium III boxes laying around,
 I was hoping to not have to build a complete time
 server--just wanted to use the existing NTP
 broadcasts that Tardis puts out.
 
 
  H
 


-- 
Start Here to Find It Fast!™ -
http://www.US-Webmasters.com/best-start-page/
$8.77 Domain Names - http://domains.us-webmasters.com/
___
[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?

2004-08-30 Thread Harlan Stenn
The ntp-stable tarballs are curently less-complete (less up-to-date) than
the ntp-dev tarballs.

I suspect Danny's patches have only been applied to ntp-dev, but
depending on when I last pulled ntp-dev back to -stable some of them
might be there.

Basically, we run ntp-dev all over and are expecting very few changes
between ntp-dev and what will become ntp-4.2.1.

We know that broadcasts work with networks that use ntpd.  I have no idea
what tardis is doing.  The fact that they apparently do not support any
authentication mechanism for broadcasts is troubling.

As for the documentation, this is a volunteer project.  There are at least
three documentation channels:

- the official pages (submit your ideas to Dave)
- the FAQ (submit your ideas to Ulrich)
- the twiki (edit/add pages as you see fit)

If you post improved documentation to the newsgroup and you post
permission to have your information used in the twiki, there is a chance
somebody will see it and also copy it there.  In general, I do not
copy content from the newsgroup to the twiki without explicit permission.

H
___
[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?

2004-08-30 Thread W. D.
At 01:22 8/30/2004, Harlan Stenn wrote:
The new binaries are probably in /usr/local/bin/ .

Right you are!

Why is that?  Shouldn't there be a compiler directive
for FreeBSD that puts them in /usr/sbin/ ?  I believe
that is where FreeBSD expects them to be.

Shall I just move them over there manually?



I use A.* because I usually build for a Lot of platforms.

The ./build script can also be used, and follows this convention.

H

Start Here to Find It Fast!™ - http://www.US-Webmasters.com/best-start-page/
$8.77 Domain Names - http://domains.us-webmasters.com/

___
[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?

2004-08-30 Thread Harlan Stenn
Better to follow the FreeBSD convention and leave them in /usr/local.

Change xntpd_program in /etc/rc.conf .

H
___
[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?

2004-08-30 Thread W. D.
At 01:46 8/30/2004, Harlan Stenn, wrote:
Better to follow the FreeBSD convention and leave them in /usr/local.

Change xntpd_program in /etc/rc.conf .

H

Thanks Harlan for your reply.

FreeBSD appears to expect these NTP programs to be
in:

/usr/sbin/

That is where the 2003 Oct port put them.  I downloaded
the most recent 'ntp-dev' tarball I could find:

ftp://ftp.starhub.net.sg/pub/funet/unix/tcpip/ntp/xntp/udel/ntp4/ntp-dev-4.2.0a-20040826.tar.gz

I did a 'make install' as we discussed previously.  As
before, the files were compiled to:

/usr/local/sbin/


I added the middle line of these three to rc.conf:

xntpd_enable=YES
xntpd_program=/usr/local/sbin/ntpd
xntpd_flags=-A -b -c /etc/ntp.conf -p /var/run/ntpd.pid -l
/var/log/ntpd.log 

After rebooting, the ntpd program is now running.  
However, it doesn't appear to be able to 'hear' the NTP 
broadcasts that the 2003 Oct version did.  Here
is a log snippet:

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

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?

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?
___
[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?

2004-08-30 Thread Harlan Stenn
 FreeBSD appears to expect these NTP programs to be in:

/usr/sbin/

No, that's where FreeBSD expects the *stock* versions to go.

If that's where something in /usr/ports/ put them, you'd have to ask
the port maintainer why.  Doing so is against normal guidelines.

Danny will have to comment on the broadcast issue.

H
___
[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?

2004-08-30 Thread Danny Mayer
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]


Re: ntpd as broadcastclient - not working?

2004-08-30 Thread W. D.
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



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.


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]


Re: ntpd as broadcastclient - not working?

2004-08-29 Thread W. D.
Hi Danny,

Thanks again for your reply.

More below...

At 18:44 8/28/2004, Danny Mayer wrote:
At 06:35 PM 8/28/2004, W. D. wrote:
I did some fooling around and found some diagnostic programs.

I don't know why you are doing this since I already told you that
I fixed a bug referenced in bugzilla #267 that fixed the broadcastclient
problem. This is a waste of time.

However, the proper way of debugging these problems is to run ntpd
in debug mode: ./ntpd -D 2 -l stdout . You need to rebuild it with
debug turned on.

OK.  I am fairly versed in the ways of Windows, but am a relative
newbie as far as FreeBSD/Unix/Linux goes.  So, rebuilding the
program with debugging turned, may be a simple matter for you,
but is quite a task for me.




The count column in the 192.168.2.119 increments
every 4 seconds.  That IP address is the network
address for the Windows computer running Tardis.
Port 123 is the proper port for broadcast, yes?

Yes.


So, from this ntpd is hearing these broadcasts,
but isn't acting on them correct?

You cannot make any assumptions from what ntpdc tells you.
You need to run ntpd in debug mode to find out.

What could possibly be stopping ntpd from adjusting
the clock?

Without running ntpd in debug mode who can tell?


Does it have something to do with UTC/local time?
When I built this computer, I put in the correct
time (local daylight time) in the CMOS.  Does
ntpd depend on UTC?

ntp doesn't know anything about local time and it's irrelevant.


Any other ideas?

Install the latest tarball and the problem should be fixed. I don't
know why you are continuing to use the wrong tools to figure out
a solved problem.

Danny, I had run CVSup on FreeBSD, and it didn't update anything.
The latest version CVSup downloads is 2004 Oct. 15.

I am not real familiar with how the FreeBSD ports work, but I 
would think that this fairly major bug you fixed would cause
some updating of the ports so that newbies like me aren't
spinning our wheels trying to get broadcastclient to work.

http://Bugzilla.NTP.org/show_bug.cgi?id=267


I think that this is the tarball you are talking about, yes?

   ntp-stable-4.2.0a-20040617.tar.gz

I tried to download it from UDel.edu, but their ftp server wouldn't
let me on.  I found it on the HTTP side:
http://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/

Since I am familiar with FTP on FreeBSD, I needed to get it elsewhere.
I found it in 3 other places:
http://www.FileSearching.com/cgi-bin/s?q=ntp-stable-4.2.0a-20040617.tar.gzt=fd=l=en

I am not certain what to do with it on FreeBSD now that I have it.
However, I'll dink around and see if I can update NTP on my 
computer.

Thanks again for pointing me in the proper direction.  I apologize
for my lack of understanding.  Hopefully, this post will help
others as well.



Danny


Thanks for your help!!
___
[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?

2004-08-29 Thread Harlan Stenn
I'd recommend the latest ntp-dev tarball

once you have it:

 % tar xvzf ntp-dev-whatever.gz
 % cd ntp-dev-whatever
 % mkdir A.x
 % cd A.x
 % ../configure
 % make
 % su
 # make install
 # /usr/local/bin/ntpd -gN -D2  (or whatever)

And remember that you need to use authentication by default if you
are using broadcast.

If you do not want to use authentication you will either need a line
in your ntp.conf file (I forget what it is, but it should be easy to find)
or use -A on the command line.

It's pretty easy to set up authentication.

H
___
[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?

2004-08-29 Thread Matthew Seaman
On Fri, Aug 27, 2004 at 02:07:16AM -0500, W. D. wrote:
 Hi folks,
 
 I have Tardis (Windows) running on my network broadcasting NTP 
 time signals (right now every 4 seconds), but the 
 FreeBSD machine is running 5 seconds faster than 
 all the other computers.
 
 
 Here are the lines that I added to /etc/rc.conf:
 
 xntpd_enable=YES
 xntpd_flags=-A -c /etc/ntp.conf -p /var/run/ntpd.pid -l /var/log/ntpd.log 
 
 (Both 'top' and 'ps -aux' show ntpd running after I rebooted.
 
 
 Here are the lines that I added to /etc/ntp.conf:
 
 driftfile /etc/ntp.drift
 broadcastclient
 
 
 Does anyone have some ideas why it isn't synching up?

Don't you need to use ntp.keys in order to synch to a broadcast or
multicast server?

See ntp.conf(5):

 broadcastclient
 This command enables reception of broadcast server messages to
 any local interface (type b) address.  Upon receiving a message
 for the first time, the broadcast client measures the nominal
 server propagation delay using a brief client/server exchange
 with the server, then enters the broadcast client mode, in which
 it synchronizes to succeeding broadcast messages.  Note that, in
 order to avoid accidental or malicious disruption in this mode,
 both the server and client should operate using symmetric-key or
 public-key authentication as described in Authentication Options.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK


pgpDkSfXko8L1.pgp
Description: PGP signature


Re: ntpd as broadcastclient - not working?

2004-08-29 Thread W. D.
At 06:04 8/29/2004, Matthew Seaman wrote:
Re ntpd as broadcastclient - n1.emsfile://D:\Programs\Eudora\attach\Re ntpd as 
broadcastclient - n1.ems 0880.0002 
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Fri, Aug 27, 2004 at 02:07:16AM -0500, W. D. wrote:
 Hi folks,
 
 I have Tardis (Windows) running on my network broadcasting NTP 
 time signals (right now every 4 seconds), but the 
 FreeBSD machine is running 5 seconds faster than 
 all the other computers.
 
 
 Here are the lines that I added to /etc/rc.conf:
 
 xntpd_enable=YES
 xntpd_flags=-A -c /etc/ntp.conf -p /var/run/ntpd.pid -l /var/log/ntpd.log 
 
 (Both 'top' and 'ps -aux' show ntpd running after I rebooted.
 
 
 Here are the lines that I added to /etc/ntp.conf:
 
 driftfile /etc/ntp.drift
 broadcastclient
 
 
 Does anyone have some ideas why it isn't synching up?

Don't you need to use ntp.keys in order to synch to a broadcast or
multicast server?

See ntp.conf(5):

 broadcastclient
 This command enables reception of broadcast server messages to
 any local interface (type b) address.  Upon receiving a message
 for the first time, the broadcast client measures the nominal
 server propagation delay using a brief client/server exchange
 with the server, then enters the broadcast client mode, in which
 it synchronizes to succeeding broadcast messages.  Note that, in
 order to avoid accidental or malicious disruption in this mode,
 both the server and client should operate using symmetric-key or
 public-key authentication as described in Authentication Options.

Cheers,

Matthew

Thanks Matthew for your reply.

My 'man ntpd' page gives the -A option to turn off authentication:

-A Disable authentication mode

(http://www.Google.com/search?q=%22-A+Disable+authentication+mode%22)

As far as I can tell, there is no way to enable authentication
using Tardis.  I was hoping that there would be a simple solution
utilizing Tardis, since it works great on Windows.


Start Here to Find It Fast!™ - http://www.US-Webmasters.com/best-start-page/
$8.77 Domain Names - http://domains.us-webmasters.com/

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]