Tim said: >> ---------- server configuration file (minus default comments) -----------= >> # the following line added by me: >> restrict 192.168.1.0 mask 255.255.255.0 notrust nomodify notrap
[EMAIL PROTECTED] (Steve Kostecke) posted: > What version of NTP are you using on the server? ntp-4.1.2-0.rc1.2 according to RPM information. > The behavior of notrust changed between versions 4.1 and 4.2. > > * In 4.1 (and earlier) notrust meant "Don't trust this host/subnet for > time". > > * In 4.2 (and later) notrust means "Ignore all NTP packets that are > not cryptographically authenticated." This forces remote time servers > to authenticate themselves to your (client) ntpd. And it will cause > servers to discard unauthenticated NTP packets from clients. See > http://ntp.isc.org/Support/ConfiguringAutokey for information about > configuring NTP Authentication. I'll look into that. I do think that I read the manual files for the versions I was playing with on each machine, individually, though. But that was a while ago. I might be better off starting anew, while reading the docs again, rather than modifying the config files I've got at the moment. I do recall, however, it being difficult to follow whether not trusting it meant not using it to serve out time, or not allowing other things to modify it. I did however get it going (the other PCs setting their clocks by it), so I thought I set that part right. ;-\ -- If you insist on e-mailing me, use the reply-to address (it's real but temporary). But please reply to the group, like you're supposed to. This message was sent without a virus, please delete some files yourself. _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
