Charles Swiger wrote: > I wonder how many of the Windows users do anything > with ntpd which needs crypto?
(Shrug) <http://www.eecis.udel.edu/~mills/ntp/html/manyopt.html#mcst> I use ntpd with MD5 symmetric keys for manycast on all clients / servers. ... keys "/etc/ntp.keys" # e.g. contains: 123 M LAN_MD5_KEY , 321 M Corp_MD5_KEY , ... trustedkey 123 321 tos cohort 1 orphan 10 restrict source nomodify manycastserver 224.0.1.1 manycastclient 224.0.1.1 key 123 preempt ... As you can see, its trivial to setup, and I find it makes adding and removing clients / servers trivial on the LAN. No matter what other refclocks any given client / server may or may not have; they end up picking the best of what is available. If LAN and internet based Stratum One &/or Two Servers become unavailable, they follow each other around, until better sources are available again; they they automatically switch back to following the S1 &/or S2 servers again. Add GPS RefClock to any NTP Client / Server, anywhere on the LAN, it will be discovered and used, no configuration changes needed in all the other NTP Clients / Servers on the LAN. -- E-Mail Sent to this address <[email protected]> will be added to the BlackLists. _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
