Rick Jones wrote: > > >> The NTP clock discipline will strive to zero the offset, but cannot >> correct for round trip asymmetry. Any individual offset measurement >> will contain a measurement error. That measurement error will be of >> the same magnitude as the measurement error you will get with your >> application. If you are interested in one way latency, you are >> interested in asymmetry! >> > > I think that in 99 cases out of 10 this would be run on a LAN where I > have a decent expectation of symmetry :) Or at least the first places > _I_ would be running it would be on a LAN :) Netperf can and does get > run over WAN's where any hope of symmetry is out the window, but I'm > willing to caveat that in the documentation. > > ... > > Is that need, Need, or NEED? Is there is a way to be "good enough" > without having the dependence upon anything more than the two > endpoints being sync'ed to the same time source? (Other than the same > GPS constellation received independently by each via their own PPS > pucks that is) > > well, I guess the point is, if you think it's going to be symmetric anyway (in your almost guaranteed sense), why not just simplify tremendously, run ping, and divide by 2?
Otherwise, you'll have to use something like OWAMP and follow it's prerequisites. _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
