Re: [Leaf-user] rdate, udp and Bering
Stephen Lee wrote: On Wed, 2002-03-27 at 17:12, Matt Schalit wrote: Stephen Lee wrote: I noticed that rdate from Bering does not seem to accept the -u switch for time requests using UDP. I suspect many of the RFC868 rdate servers are only accepting UDP requests because under RedHat7.2 I needed the -u switch to get a response for most of the servers tried. It appears that the Bering rdate version is from Busybox and so is there a way to get UDP queries from it? I think tock.usno.navy.mil still accepts rdate queries. You might try there. As far as your UDP question goes, I'm not sure, but people like to use xntpd for setting the time via the internet because it's the standard service for that sort of thing and is well regarded. rdate is old and a part of busybox I think. Thanks. I installed xntpd.lrp and pointed it to one of the public ntp servers. The problem is that my hardware clock is so far off that it's going to take ntpd a long time to synchronize the local time to the remote ntp server time. I would normally use rdate to do a quick fix but in this case rdate doesn't work with tock.usno.navy.mil. It, like all of the other rdate servers tried, only accepts udp queries. I suppose if all else fails I could manually set the time with 'date' and 'hwclock'. Try this: rdate -s ntp0.cornell.edu -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
[Leaf-user] rdate, udp and Bering
On Thu, 2002-03-28 at 12:56, Michael D. Schleif wrote: Thanks. I installed xntpd.lrp and pointed it to one of the public ntp servers. The problem is that my hardware clock is so far off that it's going to take ntpd a long time to synchronize the local time to the remote ntp server time. I would normally use rdate to do a quick fix but in this case rdate doesn't work with tock.usno.navy.mil. It, like all of the other rdate servers tried, only accepts udp queries. I suppose if all else fails I could manually set the time with 'date' and 'hwclock'. Try this: rdate -s ntp0.cornell.edu I get rdate: ntp0.cornell.edu: Connection refused on Bering boxes but it works on Eigerstein2b boxes. Could there be some firewall setting causing this problem? Stephen ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] rdate, udp and Bering
You'll have to open up TCP 37 from your firewall to the net in order to use rdate. -Tom - Original Message - From: Stephen Lee [EMAIL PROTECTED] To: Leaf-user [EMAIL PROTECTED] Sent: Thursday, March 28, 2002 1:05 PM Subject: [Leaf-user] rdate, udp and Bering On Thu, 2002-03-28 at 12:56, Michael D. Schleif wrote: Thanks. I installed xntpd.lrp and pointed it to one of the public ntp servers. The problem is that my hardware clock is so far off that it's going to take ntpd a long time to synchronize the local time to the remote ntp server time. I would normally use rdate to do a quick fix but in this case rdate doesn't work with tock.usno.navy.mil. It, like all of the other rdate servers tried, only accepts udp queries. I suppose if all else fails I could manually set the time with 'date' and 'hwclock'. Try this: rdate -s ntp0.cornell.edu I get rdate: ntp0.cornell.edu: Connection refused on Bering boxes but it works on Eigerstein2b boxes. Could there be some firewall setting causing this problem? Stephen ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] rdate, udp and Bering
On Thu, 2002-03-28 at 13:43, Michael D. Schleif wrote: Tom Eastep wrote: You'll have to open up TCP 37 from your firewall to the net in order to use rdate. -Tom - Original Message - From: Stephen Lee [EMAIL PROTECTED] To: Leaf-user [EMAIL PROTECTED] Sent: Thursday, March 28, 2002 1:05 PM Subject: [Leaf-user] rdate, udp and Bering On Thu, 2002-03-28 at 12:56, Michael D. Schleif wrote: Thanks. I installed xntpd.lrp and pointed it to one of the public ntp servers. The problem is that my hardware clock is so far off that it's going to take ntpd a long time to synchronize the local time to the remote ntp server time. I would normally use rdate to do a quick fix but in this case rdate doesn't work with tock.usno.navy.mil. It, like all of the other rdate servers tried, only accepts udp queries. I suppose if all else fails I could manually set the time with 'date' and 'hwclock'. Try this: rdate -s ntp0.cornell.edu I get rdate: ntp0.cornell.edu: Connection refused on Bering boxes but it works on Eigerstein2b boxes. Could there be some firewall setting causing this problem? rdate works on my several DCD's without tcp/udp 37. All we have open are: ntp 123/udpNetwork Time Protocol Adding port 37 to FW_TCP_OUT_PORTS in Bering got rdate working. Adding port 123 (either udp or tcp) did not work for me. Thanks for the help! Stephen ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] rdate, udp and Bering
Hello Stephen, Michael Stephen Lee wrote: On Thu, 2002-03-28 at 12:56, Michael D. Schleif wrote: Thanks. I installed xntpd.lrp and pointed it to one of the public ntp servers. The problem is that my hardware clock is so far off that it's going to take ntpd a long time to synchronize the local time to the remote ntp server time. I would normally use rdate to do a quick fix but in this case rdate doesn't work with tock.usno.navy.mil. It, like all of the other rdate servers tried, only accepts udp queries. I suppose if all else fails I could manually set the time with 'date' and 'hwclock'. Try this: rdate -s ntp0.cornell.edu I get rdate: ntp0.cornell.edu: Connection refused on Bering boxes but it works on Eigerstein2b boxes. Could there be some firewall setting causing this problem? as Tom allready stated it is. rdate uses port 37 and this is denied by default change shorewall settings 1 ) params FW_TCP_OUT_PORTS=53,37 and restart shorewall (don't forget to backup ) I do not know which `rdate' is in Bering. Dachstein, c. uses busybox rdate. Bering uses also Busybox v0.60.2 rdate Regarding firewalled ports, have you checked these? ntp 123/tcpNetwork Time Protocol ntp 123/udpNetwork Time Protocol With me rdate ntp0.cornell.edu functions after the modification i indicated above. The connection refused comes from your own router not from the timeserver. PS you are talking about using rdate from the router not from a linux machine in the internal network ? The parameter I talked about before is firewall --- timeserver. otherwise the firewall should not be blocking. Regards Eric Wolzak member of the bering crew ;) ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] rdate, udp and Bering
Tom Eastep wrote: - Original Message - From: Michael D. Schleif [EMAIL PROTECTED] Cc: Leaf-user [EMAIL PROTECTED] Sent: Thursday, March 28, 2002 1:43 PM Subject: Re: [Leaf-user] rdate, udp and Bering causing this problem? rdate works on my several DCD's without tcp/udp 37. All we have open are: ntp 123/udpNetwork Time Protocol It produces the following log message here: Shorewall:all2all:REJECT:IN= OUT=eth0 SRC=206.124.146.176 DST=206.124.128.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=33953 PROTO=TCP SPT=1101 DPT=37 WINDOW=5840 RES=0x00 CWR ECE SYN URGP=0 This was in response to rdate 206.124.128.1. Upon further investigation, I agree that this is also true on DCD -- port 37. -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
[Leaf-user] rdate, udp and Bering
Hi, I noticed that rdate from Bering does not seem to accept the -u switch for time requests using UDP. I suspect many of the RFC868 rdate servers are only accepting UDP requests because under RedHat7.2 I needed the -u switch to get a response for most of the servers tried. It appears that the Bering rdate version is from Busybox and so is there a way to get UDP queries from it? Thanks, Stephen ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] rdate, udp and Bering
Stephen Lee wrote: Hi, I noticed that rdate from Bering does not seem to accept the -u switch for time requests using UDP. I suspect many of the RFC868 rdate servers are only accepting UDP requests because under RedHat7.2 I needed the -u switch to get a response for most of the servers tried. It appears that the Bering rdate version is from Busybox and so is there a way to get UDP queries from it? Thanks, Stephen I think tock.usno.navy.mil still accepts rdate queries. You might try there. As far as your UDP question goes, I'm not sure, but people like to use xntpd for setting the time via the internet because it's the standard service for that sort of thing and is well regarded. rdate is old and a part of busybox I think. Regards, Matthew ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
