Scripsit Ronan Flood <[EMAIL PROTECTED]>
> Henning Makholm <[EMAIL PROTECTED]> wrote:
>> However, I had expected that B.B.B.B would list A.A.A.A as an
>> association in 'symmetric-passive' mode, but it doesn't. Shouldn't it?
> Only if you have authentication turned off, which is inadvisable.
> Better to make both symmetric-active:
> ntpdc -c 'addpeer B.B.B.B' A.A.A.A
> ntpdc -c 'addpeer A.A.A.A' B.B.B.B
I though the point of "addpeer" was that a single association could
transfer time in any direction (and I still have trouble reading
the documentation any other way). If I need to make two associations,
then why not just do
ntpdc -c 'addserver B.B.B.B' A.A.A.A
ntpcd -c 'addserver A.A.A.A' B.B.B.B
i.e. what is the difference between a client connection and a peer
connection if both are unidirectional?
Hm, on further experimentation it does work in two directions with
authentified messages. I tried this before without success, but it
works after I switched to a 'M' (md4) key instead of an 'A' (des) key
with the same password for the authentication. Are there known bugs
in the DES authentication code?
--
Henning Makholm "Jeg køber intet af Sulla, og selv om uordenen griber
planmæssigt om sig, så er vi endnu ikke nået dertil hvor
ordentlige mennesker kan tillade sig at stjæle slaver fra
hinanden. Så er det ligegyldigt, hvor stærke, politiske modstandere vi er."
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions
