BlackList wrote:
> Dave Hart wrote:
>> Marc-Andre Alpers wrote:
>>> I have restarted my NTPd and the following happened.
>>>
>>> root@amd-x4:~# ntpq -p
>>> evie.fra1.as411 78.47.148.174 3 u 1 64 1 36.242 8.622 4.338
>>> evie.fra1.as411 78.47.148.174 3 u 2 64 1 27.690 9.442 2.231
>>>
>>> Twice the same NTP server in the list.
>>>
>>> root@amd-x4:~# ntpq -pn
>>> 2a01:4f8:d13:23 78.47.148.174 3 u 5 64 1 36.242 8.622 4.338
>>> 78.46.221.42 78.47.148.174 3 u 4 64 1 27.690 9.442 3.712
>>>
>>> I use the pool server and I have IPv6 connectivity.
>>> How can i prevent that the same NTP Server is in the list?
>>
>> While you could add -4 to each of the server lines for the pool,
>> that would disable IPv6 use of the pool. not only the ones that
>> happen to be the same remote clock. I don't recommend it.
>>
>> Moreover, I argue you shouldn't be dismayed to be reaching
>> the same remote clock via two versions of IP, as the networks
>> are in fact different, though they share fate on at least your
>> last mile (your internet connection).
>
> I thought there was something in one of the clock algorithms
> that discarded some servers >= stratum 2,
> that had the same association refid,
> unless it had already reduced to min clock?
>
> {I can't spot that in the docs at a quick glance,
> however I'm certain I read it somewhere; continuing to look.}
I guess I was thinking of Test12;
It doesn't go that far out into the tree,
just covers local & remote both having the same refid,
rather than two remotes having the same refid.
--
E-Mail Sent to this address <[email protected]>
will be added to the BlackLists.
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
