My best guess at the moment is that is due to using interleaved mode.
As far as I can tell from the debugging and code reading I've done,
chrony, when acting as a server, will eventually call
`NCR_ProcessRxUnknown' for each request from the client.
Then, chrony will try to figure out if its seen this client before by
calling `CLG_LogNTPAccess' and `CLG_GetNtpTimestamps', but that is
based on ip address only, not port.
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.
Is this something that should work, or is the thing I'm trying to do
not intended to work?
On Wed, Jul 26, 2017 at 1:59 PM, Chris Perl <cp...@janestreet.com> wrote:
> On Wed, Jul 26, 2017 at 12:23 PM, Chris Perl <cp...@janestreet.com> wrote:
>> Fwiw, I also have the `xleave' option specified for the second instance.
> But, interestingly, the `measurements.log' file from the second
> instance always reports "B" packets:
> 2017-07-26 17:32:18 192.168.1.100 N 1 111 111 1111 4 4 0.00
> -8.916e-06 4.595e-05 3.401e-07 0.000e+00 1.526e-05 50545030 4B K K
> 2017-07-26 17:32:34 192.168.1.100 N 1 111 111 1111 4 4 0.00
> -8.401e-06 4.537e-05 3.402e-07 0.000e+00 1.526e-05 50545030 4B K K
> 2017-07-26 17:32:50 192.168.1.100 N 1 111 111 1111 4 4 0.00
> -2.156e-05 7.147e-05 3.954e-07 0.000e+00 1.526e-05 50545030 4B K K
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email listmas...@chrony.tuxfamily.org.