02-25-2014, 04:14 PM
OK Mauro,
How will I know that the response is too slow and the connection has timed out?
Only by the fact that it fails to report the time? Does the error code mean anything useful ?
Why should an 18 hop path (reporting long time delay) be faster than 12 hops (reporting shorter delay)?
I would guess you have only half a dozen hops to Torino.
If the problem is delays caused at the NTP end, can your software open its own time window more?
Otherwise we will need to know which NTPs are responding rapidly enough to be used reliably to work with BktTimeSync, when the path is many-hop.
Sorry to be a pain, but I had come to rely heavily on BktTimeSync and I want to understand the risks.
73 Robin, 9H1ZZ
How will I know that the response is too slow and the connection has timed out?
Only by the fact that it fails to report the time? Does the error code mean anything useful ?
Why should an 18 hop path (reporting long time delay) be faster than 12 hops (reporting shorter delay)?
I would guess you have only half a dozen hops to Torino.
If the problem is delays caused at the NTP end, can your software open its own time window more?
Otherwise we will need to know which NTPs are responding rapidly enough to be used reliably to work with BktTimeSync, when the path is many-hop.
Sorry to be a pain, but I had come to rely heavily on BktTimeSync and I want to understand the risks.
73 Robin, 9H1ZZ