On Sun, Oct 17, 2010 at 03:43 UTC, Joe Smithian <[email protected]> wrote: > I've compiled ntp-4.2.6p2 from the source code with crypto, openssl and > autokey enabled on CentOS 5.4 platform. I've configured my CentOS 5.4 client > to use Autokey but it doesn't sync as you can see below.
What I see looks normal, given your configuration. Linux distributions in particular seem to include the local clock driver 127.127.1.0 ill-advisedly, and you are the latest victim. You have instructed both your client and autokey server to freewheel using the PC's clock while claiming to be synchronized. Unless some other software is disciplining that clock outside of ntpd, you probably don't want that. > Authentication is OK but it rejects the trusted server. Right, so if you remove 127.127.1.0 from the client's configuration, it should sync to its single remaining source. > I've done the same configuration using > ntp-4.2.4p5 on an old RedHat 7.2 machine and it syncs to the same trusted > server. So I guess the problem might be in the new version of NTP. There was a three-year-long development process between 4.2.4 and 4.2.6 stable releases. During that time, autokey was substantially updated. Configurations that worked with 4.2.4 may not work with 4.2.6 without change. Good luck, Dave Hart _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
