Hello,

I am running ntp (ntpd 4.1.2) on a linux box running RHEL4.

I configured an interface on that machine and want ntpd to listen and 
respond on that interface.

Somehow I can't get that to work. The clients get sync-ed via the 
"original" ip address (the one of the hostname) but not when using the 
alias of the interface that has a different ip-address.

Can ntpd be configured to listen on a certain ip-address and respond as 
if the response is coming from that same ip-address ?

thanks,

Ron

As I recall, "not yet".  I expect this will be possible with 4.2.2, which
should happen within a few months of the release of 4.2.1, which will be
happenning Soon.

H

cool...

Harlan Stenn wrote:
> As I recall, "not yet".  I expect this will be possible with 4.2.2, which
> should happen within a few months of the release of 4.2.1, which will be
> happenning Soon.
> 
> H

In article <dfr322$gs9$1@news.csc.depauw.edu> Ron Croonenberg
<ronc@depauw.edu> writes:
>
>I am running ntp (ntpd 4.1.2) on a linux box running RHEL4.
>
>I configured an interface on that machine and want ntpd to listen and 
>respond on that interface.
>
>Somehow I can't get that to work. The clients get sync-ed via the 
>"original" ip address (the one of the hostname) but not when using the 
>alias of the interface that has a different ip-address.
>
>Can ntpd be configured to listen on a certain ip-address and respond as 
>if the response is coming from that same ip-address ?

Harlan rsponded to the question as read "listen *only* on a certain
ip-address" I believe - if you don't mind that it listens on other IP
addresses too, it should work already, but depending on version and OS
you may need to give it the -L option to have it listen on "alias"
addresses a.k.a. "virtual interfaces". Regardless, responses will always
be sent with the source address taken from the destination address of
the query.

--Per Hedeland
per@hedeland.org

Ron Croonenberg wrote:
> Hello,
> 
> I am running ntp (ntpd 4.1.2) on a linux box running RHEL4.
> 
> I configured an interface on that machine and want ntpd to listen and 
> respond on that interface.
> 
> Somehow I can't get that to work. The clients get sync-ed via the 
> "original" ip address (the one of the hostname) but not when using the 
> alias of the interface that has a different ip-address.
> 
> Can ntpd be configured to listen on a certain ip-address and respond as 
> if the response is coming from that same ip-address ?
> 
Upgrade to the latest ntp-dev tarball. It will only respond on the same
address to which the request was sent.

Danny
> thanks,
> 
> Ron
> 
> _______________________________________________
> questions mailing list
> questions@lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/questions
> 


_______________________________________________
questions mailing list
questions@lists.ntp.isc.org
https://lists.ntp.isc.org/mailman/listinfo/questions

Harlan Stenn wrote:
> As I recall, "not yet".  I expect this will be possible with 4.2.2, which
> should happen within a few months of the release of 4.2.1, which will be
> happenning Soon.
> 
> H
> 
I think you misunderstood the question. He's talking about a bug I
already fixed, not about dynamic interfaces.

Danny

_______________________________________________
questions mailing list
questions@lists.ntp.isc.org
https://lists.ntp.isc.org/mailman/listinfo/questions

Per Hedeland wrote:
> In article <dfr322$gs9$1@news.csc.depauw.edu> Ron Croonenberg
> <ronc@depauw.edu> writes:
> 
>>I am running ntp (ntpd 4.1.2) on a linux box running RHEL4.
>>
>>I configured an interface on that machine and want ntpd to listen and 
>>respond on that interface.
>>
>>Somehow I can't get that to work. The clients get sync-ed via the 
>>"original" ip address (the one of the hostname) but not when using the 
>>alias of the interface that has a different ip-address.
>>
>>Can ntpd be configured to listen on a certain ip-address and respond as 
>>if the response is coming from that same ip-address ?
> 
> 
> Harlan rsponded to the question as read "listen *only* on a certain
> ip-address" I believe - if you don't mind that it listens on other IP
> addresses too, it should work already, but depending on version and OS
> you may need to give it the -L option to have it listen on "alias"
> addresses a.k.a. "virtual interfaces". Regardless, responses will always
> be sent with the source address taken from the destination address of
> the query.
> 

Per, there was a bug that I fixed a while ago which could cause this
kind of thing to happen due to the packet arriving on the wildcard port.
That can no longer happen so it should now always return a packet from
the same address.

Danny

> --Per Hedeland
> per@hedeland.org
> 
> _______________________________________________
> questions mailing list
> questions@lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/questions
> 


_______________________________________________
questions mailing list
questions@lists.ntp.isc.org
https://lists.ntp.isc.org/mailman/listinfo/questions

In article <43263510.8000802@gis.net> mayer@gis.net (Danny Mayer) writes:
>Per Hedeland wrote:
>> In article <dfr322$gs9$1@news.csc.depauw.edu> Ron Croonenberg
>> <ronc@depauw.edu> writes:
>> 
>>>I am running ntp (ntpd 4.1.2) on a linux box running RHEL4.
>>>
>>>I configured an interface on that machine and want ntpd to listen and 
>>>respond on that interface.
>>>
>>>Somehow I can't get that to work. The clients get sync-ed via the 
>>>"original" ip address (the one of the hostname) but not when using the 
>>>alias of the interface that has a different ip-address.
>>>
>>>Can ntpd be configured to listen on a certain ip-address and respond as 
>>>if the response is coming from that same ip-address ?
>> 
>> 
>> Harlan rsponded to the question as read "listen *only* on a certain
>> ip-address" I believe - if you don't mind that it listens on other IP
>> addresses too, it should work already, but depending on version and OS
>> you may need to give it the -L option to have it listen on "alias"
>> addresses a.k.a. "virtual interfaces". Regardless, responses will always
>> be sent with the source address taken from the destination address of
>> the query.
>> 
>
>Per, there was a bug that I fixed a while ago which could cause this
>kind of thing to happen due to the packet arriving on the wildcard port.
>That can no longer happen so it should now always return a packet from
>the same address.

Yes, I saw that in your other followup - was this bug ever in a
"released" version? I've never come across it. Anyway, it seems we now
have three different interpretations of the OP's question, so I guess it
would be good if he would clarify...

--Per Hedeland
per@hedeland.org

Per Hedeland wrote:
>>Per, there was a bug that I fixed a while ago which could cause this
>>kind of thing to happen due to the packet arriving on the wildcard port.
>>That can no longer happen so it should now always return a packet from
>>the same address.
> 
> 
> Yes, I saw that in your other followup - was this bug ever in a
> "released" version? I've never come across it. 

It's in the development stream. It will be in the 4.2.1 release.

> Anyway, it seems we now
> have three different interpretations of the OP's question, so I guess it
> would be good if he would clarify...
> 
Agreed.

Danny
_______________________________________________
questions mailing list
questions@lists.ntp.isc.org
https://lists.ntp.isc.org/mailman/listinfo/questions

In article <432966D1.5090304@gis.net> mayer@gis.net (Danny Mayer) writes:
>Per Hedeland wrote:
>>>Per, there was a bug that I fixed a while ago which could cause this
>>>kind of thing to happen due to the packet arriving on the wildcard port.
>>>That can no longer happen so it should now always return a packet from
>>>the same address.
>> 
>> 
>> Yes, I saw that in your other followup - was this bug ever in a
>> "released" version? I've never come across it. 
>
>It's in the development stream. It will be in the 4.2.1 release.

I was asking about the bug, you're (hopefully) talking about the fix.:-)

--Per Hedeland
per@hedeland.org

Per Hedeland wrote:
> In article <432966D1.5090304@gis.net> mayer@gis.net (Danny Mayer) writes:
> 
>>Per Hedeland wrote:
>>
>>>>Per, there was a bug that I fixed a while ago which could cause this
>>>>kind of thing to happen due to the packet arriving on the wildcard port.
>>>>That can no longer happen so it should now always return a packet from
>>>>the same address.
>>>
>>>
>>>Yes, I saw that in your other followup - was this bug ever in a
>>>"released" version? I've never come across it. 
>>
>>It's in the development stream. It will be in the 4.2.1 release.
> 
> 
> I was asking about the bug, you're (hopefully) talking about the fix.:-)
> 

Oh. Yes, all previous versions of ntp had this potential problem. The 
fix is in ntp-dev now and will be in ntp 4.2.1.

Danny

> --Per Hedeland
> per@hedeland.org
> 
> _______________________________________________
> questions mailing list
> questions@lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/questions
> 

_______________________________________________
questions mailing list
questions@lists.ntp.isc.org
https://lists.ntp.isc.org/mailman/listinfo/questions