From: Marvin Greenlee (marvingreenlee@yahoo.com)
Date: Tue Sep 05 2006 - 23:45:26 ART
Both will work, one is overconfigured.
The server does not do authentication, the server
hands out the time and a key.
Clients authenticate whether the time received is
valid.
--- Michy Eika <cciemaster@shingor.net> wrote:
> Hello folks
>
> I'm confused about NTP authentication.
> In accord with following web site, In the side of
> NTP master
> authentification configuration is like below.
>
>
http://www.cisco.com/en/US/tech/tk869/tk769/technologies_white_paper09186a00
> 80117070.shtml
>
>
########################################################
> ntp master 3
>
>
> !--- When the system sends an NTP packet, the
> !--- source IP address is normally set to the
> !--- address of the interface through which the
> !--- NTP packet is sent.
> !--- Change this to use loopback0.
>
>
> ntp source Loopback0
>
>
> !--- Enables NTP authentication.
>
>
> ntp authenticate
> ntp authentication-key 1234 md5 104D000A0618 7
> ntp trusted-key 1234
>
>
########################################################
>
> But in IEWB-RS following website, the configuration
> is such as below.
>
http://www.internetworkexpert.com/resources/ntp-authentication.htm
>
>
########################################################
>
> R1#clock set 00:00:00 1 Jan 2000
> R1#conf t
> Enter configuration commands, one per line. End
> with CNTL/Z.
> R1(config)#ntp master 1
> R1(config)#ntp authentication-key 1 md5 CISCO
>
>
########################################################
>
> Which one is correct ???
>
> TIA
>
> Michy
>
>
This archive was generated by hypermail 2.1.4 : Sun Oct 01 2006 - 16:55:40 ART