| Re: [chrony-users] chronyc tracking question |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] chronyc tracking question
- From: Chris Perl <cperl@xxxxxxxxxxxxxx>
- Date: Thu, 27 Jul 2017 09:10:17 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=janestreet.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=yz82DO9Dr9cOPX7G2NO3ax2WPLlKsK+Wqc7RPHVlJc0=; b=OEBJ7cKDreiYkAHlA8SCncoZCux9zZWp0QfbrVTCrG6qwJTzGNz5fSHqjDO9NmDAHg wgDn+hAh++YOt57fgcHWvvbpkq3JaqnK8TNW5/32iylvZwytQ00mlIskTPEDVw6gk/K+ oZ0E8+NnQC9Ck4ijb51e+gJEY/R/LiJr4ZEW8=
On Thu, Jul 27, 2017 at 4:57 AM, Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
> On Wed, Jul 26, 2017 at 06:15:13PM -0400, Chris Perl wrote:
>> I'm pretty sure the interleaving gets messed up and I don't wind up
>> getting back the timestamp from the previous exchange (i.e. I'm losing
>> out on the hardware timestamping of t3 on the server). I think that
>> accounts for the extra 15us that I'm seeing.
>
> Your analysis is correct.
Thanks for confirming.
> With the current implementation, interleaved mode with multiple
> clients on the same IP address is not expected to work. The man page
> mentions this issue with multiple clients behind NAT.
Doh. Next time I'll try to read the man page more carefully.
> Modifying the code to keep track of individual ports wouldn't help,
> because clients usually change their port between requests.
I had come to the same realization a few hours after I had sent my prior email.
> The timestamps could be separate from IP addresses completely. This
> would allow multiple clients on the same IP address, or even clients
> that change their address between requests. However, a broken client
> sending too many request would be able to flush timestamps that belong
> to other clients. I'm not sure which is worse. There may be a better
> way to do this.
Interesting thought. I agree with your sentiment, "I'm not sure which
is worse."
> As a workaround in your case, you could configure the monitoring
> client as a peer or you could run a second server instance on a
> different port serving local time.
I had thought of the latter, but not the former. I'll try both and
see how I make out.
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.