Martin wrote: > (I changed the subject for this separate issue, > it was: multicast - wrong interface) > > Peter Pramberger wrote: >>> That's a separate question and most likely a bug. I don't know why the >>> ttl is set to 96, there aren't that many hops in the world... >> That's by design. Please see >> >> https://ntp.isc.org/bugs/show_bug.cgi?id=715#c16 >> http://lists.ntp.isc.org/pipermail/questions/2005-August/006427.html > > Such behavior seems to be not in line with the documentation: > - - - - - - - > ttl ttl > This option is used only with broadcast server and manycast client modes. > It specifies the time-to-live ttl to use on broadcast server and multicast > server ... > > http://www.eecis.udel.edu/~mills/ntp/html/confopt.html > - - - - - - - >
Yes, and this whole idea troubles me. The phrase "Principle of Least Astonishment" comes to mind. Danny _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
