Perhaps the ntp.keys file doesn't have the same key for key 13 as the Cisco has?
qwe qwe wrote: > I have NTP server(xntpd3-5.93e) on Solaris 9. > With such configuration: > > ---ntp.conf--- > server 213.X.X.X prefer > enable auth > driftfile /var/ntp/ntp.drift > statsdir /var/ntp/ntpstats/ > filegen peerstats file peerstats type day enable > keys /etc/inet/ntp.keys > trustedkey 13 > --- > > Also, there is Cisco 2610 as client. > > --- cisco config ---- > ntp authentication-key 13 md5 ******** 7 > ntp authenticate > ntp trusted-key 13 > ntp server 10.10.10.8 key 13 prefer > ---------------------- > > > Client can't sync with ntpserver. By means of a Wireshark I have got the > following dump: > > cisco2610 -> NtpServer: NTP "request" (keyID= 13, authcode=xxxx) > cisco2610 <- NtpServer: NTP "answer" (keyID=0, authcode=xxxx) > > Why xntpd use keyID=0 to sign a answer? Is it a bug? or I do something wrong? > -- > This message posted from opensolaris.org > _______________________________________________ > ntp-discuss mailing list > ntp-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/ntp-discuss -- blu There are two rules in life: Rule 1- Don't tell people everything you know ---------------------------------------------------------------------- Brian Utterback - Solaris RPE, Sun Microsystems, Inc. Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom
