You've only shown the portion of the config from R1 and based on this config, R1 is getting its time from 22.214.171.124.
The 'ntp server 126.96.36.199' command won't make R1 the server. On Cisco routers, you can make a device a NTP server by getting its time from an authoritative NTP server or by entering the 'ntp master' command.
So R1 get it's time from R3 without authentication. But what about R2 getting it's time from R1 ? We do not configure on NTP server it's clients. How R1 will know which key should it use returning response to R2 ?
Is the key number globally significiant ? Or R1 will return response to R2 signed by all possible keys ?
Could you describe how R1 process the request from R2 ?
On R2, you've configured 'md5 Cisco' for key 1 authentication and you've also added key 1 as part of the 'ntp server' command so R2 will use 'md5 Cisco' to authenticate to R1 and R1 will use no authentication to obtain time from R3.
You said: "R1 would accept authentication from NTP clients that matches any of the configured keys."
So - this mean that client sending request to server is sending key hash which is compared with all the hashes on server ? And then server responds once with the key that matches ? Could you describe what information is sending client in request (key or hash), what comparison is done on server and what information is returned to client ?
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...