More NTP fun

From: Desimone, Aurelio (ADesimone@refco.com)
Date: Sun Sep 08 2002 - 14:06:07 GMT-3

• Next message: Guoqi Cui: "Re: bgp: modifying incoming routes based on thei next-hop"
• Previous message: Omer Ansari: "bgp: modifying incoming routes based on thei next-hop"
• Next in thread: Jayashanker Warrier: "Re: More NTP fun"
• Maybe reply: Jayashanker Warrier: "Re: More NTP fun"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

I was able to get ntp authentication working fine with this config:

NTP master (r1)
ntp authentication-key 1 md5 00071A150754 7
ntp trusted-key 1
ntp master 1

NTP clients
ntp authentication-key 1 md5 091C1F58495531435C595C7A7F 7
ntp server 155.10.100.129 key 1

My question is why do many examples (including ones from previous posts)
have 'ntp authenticate' on both clients and masters? Also, I've seen the
'ntp trusted-key 1' on many client configuration examples. I only use these
keywords when authenticating broadcast/multicast clients. Is this correct?
Can someone tell me when we are supposed to use these keywords?

Thanks
Aurelio

• Next message: Guoqi Cui: "Re: bgp: modifying incoming routes based on thei next-hop"
• Previous message: Omer Ansari: "bgp: modifying incoming routes based on thei next-hop"
• Next in thread: Jayashanker Warrier: "Re: More NTP fun"
• Maybe reply: Jayashanker Warrier: "Re: More NTP fun"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Mon Oct 07 2002 - 07:43:46 GMT-3