Danny Mayer wrote:
> Martin Burnicki wrote:
>
>>Danny,
>>
>>Danny Mayer wrote:
>>
>>>Ronan Flood wrote:
>>>
[EMAIL PROTECTED] (Danny Mayer) wrote:
>4.1.0 was a long time ago in a galaxy far, far away.
"The code is out there."
>>>
>>>That doesn't matter. We only supp
Martin Burnicki wrote:
> Danny,
>
> Danny Mayer wrote:
>> Ronan Flood wrote:
>>> [EMAIL PROTECTED] (Danny Mayer) wrote:
>>>
4.1.0 was a long time ago in a galaxy far, far away.
>>> "The code is out there."
>>>
>> That doesn't matter. We only support the current current unless there's
>> a pai
Martin Burnicki wrote:
[]
> I don't think I've read a request where this should be fixed in an
> older version.
>
> The problem in this NG seems to be that some insiders seem to assume
> all users are running a very recent version of NTP, and I'm pretty
> sure this is not the case.
>
> I think most
Danny,
Danny Mayer wrote:
> Ronan Flood wrote:
>> [EMAIL PROTECTED] (Danny Mayer) wrote:
>>
>>> 4.1.0 was a long time ago in a galaxy far, far away.
>>
>> "The code is out there."
>>
>
> That doesn't matter. We only support the current current unless there's
> a paid contract to maintain some
Ronan Flood wrote:
> [EMAIL PROTECTED] (Danny Mayer) wrote:
>
>> 4.1.0 was a long time ago in a galaxy far, far away.
>
> "The code is out there."
>
That doesn't matter. We only support the current current unless there's
a paid contract to maintain some other version. Dave was concerned about
On 2008-04-03, Ray <[EMAIL PROTECTED]> wrote:
> I now know I have to update. So what is the last stable version?
The current stable release is 4.2.4p4 2007/09/10
Current version information is published at:
http://www.ntp.org/
http://support.ntp.org/
http://support.ntp.org/rss/releases.xml (as
Ray wrote:
> Thanks to everyone who replied.
> I now know I have to update. So what is the last stable version?
>
> I just wanted to know how the daemon could be so selective to deny IP
> 69.x.x.x
>
> Ray
It depends on what's in your config file. You may be restricting 69/8
addresses.
Danny
__
Thanks to everyone who replied.
I now know I have to update. So what is the last stable version?
I just wanted to know how the daemon could be so selective to deny IP
69.x.x.x
Ray
--
"Ray" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Harlan,
>
Ronan,
You are right. The oldest version I have here is 4.1.2 circa July 2003
and the port check had been removed. Also, my warning to not change
ntp_proto.c without my permission was not in that version. So, nobody
did anything wrong, just misguided. I just don't want somthing to leave
here n
On 2008-04-02, Ronan Flood <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] (Danny Mayer) wrote:
>
>> 4.1.0 was a long time ago in a galaxy far, far away.
>
> "The code is out there."
That NTP_PORT test appears to be present in ntp-4.1.0 but not in
ntp-4.1.1. So it was obviously removed after it wa
[EMAIL PROTECTED] (Danny Mayer) writes:
>Dave,
>4.1.0 was a long time ago in a galaxy far, far away. We don't care about
>that version any more. Anyone who wants help needs to upgrade to a more
>recent version.
IF you knoww that this was a bug in a particular old version and that the
new versi
[EMAIL PROTECTED] (Danny Mayer) wrote:
> 4.1.0 was a long time ago in a galaxy far, far away.
"The code is out there."
--
Ronan Flood <[EMAIL PROTECTED]>
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questi
On 2008-04-02, David L. Mills <[EMAIL PROTECTED]> wrote:
> I was afraid this might happen. There is no such port check in the
> development branch, so somebody broke my rules not to change ntp_proto.c
> withhout my permission. The result not only breaks the specification, it
> disables symmetri
Dave,
4.1.0 was a long time ago in a galaxy far, far away. We don't care about
that version any more. Anyone who wants help needs to upgrade to a more
recent version.
Danny
David L. Mills wrote:
> Guys,
>
> I was afraid this might happen. There is no such port check in the
> development bran
"David L. Mills" <[EMAIL PROTECTED]> wrote:
> I was afraid this might happen. There is no such port check in the
> development branch
Relax, Dave: the original poster is running old code, version 4.1.0.
This port check was removed in 2002.
--
Ronan Flood <[EMAIL PROTECTED]>
__
Guys,
I was afraid this might happen. There is no such port check in the
development branch, so somebody broke my rules not to change ntp_proto.c
withhout my permission. The result not only breaks the specification, it
disables symmetric active/active modes. Any check like this has to be
mode
On Tue, 1 Apr 2008 12:44:17 -0400, "Ray" <[EMAIL PROTECTED]> wrote:
> input_handler: if=2 fd=6 length 48 from 453fdb02 69.63.219.2
> receive: at 38 132.246.168.2<-69.63.219.2 restrict 00
> receive: at 182 132.246.168.2<-69.156.105.192 restrict 00
> receive: at 182 132.246.168.2<-69.156.105.192 mo
How do you know that the problem is specific to systems that have
addresses that begin with 69? If you take the failing system in this
debug and change nothing else but it's IP address, does it work okay?
Do you have more than one system that is having this problem and they
are all on the 69.*.
Ray,
I don't know if Danny has any ideas, but I think we may need a higher level
of debugging.
--
Harlan Stenn <[EMAIL PROTECTED]>
http://ntpforum.isc.org - be a member!
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/
Harlan,
Here are sample of the debug output, which include IP addresses that start
with 69.
This first sample gave no reply. I assume it is version 3.
---
MCAST *sendpkt(fd=6 dst=192.70.172.132, src=132.246.168.2
Ray,
>>> In article <[EMAIL PROTECTED]>, "Ray" <[EMAIL PROTECTED]> writes:
Ray> I am running stratum-1 servers with NTP version 4.1.0. There are no
Ray> restrictions in the NTP configuration and no restrictions in the
Ray> firewall. Yet, when I receive NTP request, from version3, and with an
Ray
I am running stratum-1 servers with NTP version 4.1.0. There are no
restrictions in the NTP configuration and no restrictions in the firewall.
Yet, when I receive NTP request, from version3, and with an IP address
starting with 69, the daemon does not reply to it. The server will reply to
NTP pac
22 matches
Mail list logo