Dave,
In late versions the calibration volley is suppressed unconditionally if
broadcastdelay is nonzero. See ntp_proto.c line 919 in ntp_dev.
Dave
Dave Hart wrote:
On Tue, Nov 30, 2010 at 18:50 UTC, Atul Gupta <[email protected]> wrote:
I used broadcastdelay in my client's config, but client is still trying to
send unicast messages to server after receiving multicast messages from
server.
You mentioned using ntp 4.2.0. You can find your version's
"broadcastdelay" documented at:
http://doc.ntp.org/4.2.0/miscopt.html
It reads to me like the behavior has changed in newer versions. For ntpd
4.2.0 (circa 2003), it appears the unicast delay calibration is always
attempted, and the broadcastdelay value is only used if the attempt fails. If
you upgrade to a recent version, using specifying broadcastdelay
short-circuits the attempt.
Cheers,
Dave Hart
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
