On 06/06/11 16:11, Vincent Schonau wrote:
I see the same thing; it seems the monitor probe is not getting some of my
return packets.
Comparing the timestamps in the below tcpdump with those in the monitor CSV,
I'm pretty sure I do see and respond to all requests, but some of my responses
are getting lost or ignored.
I think it may be more complicated than that.
I've been comparing the output from tcpdump and my csv log. Clearly,
both machines have pretty accurately synchronized clocks, so they should
agree closely.
When the monitor manages a successful poll of my machine I see the query
at exactly the same time.
When it shows an unsuccessful poll, I don't see a query at that time,
but I do typically see a couple of others at about the relevant time,
perhaps 4 - 6 seconds apart. These ones don't appear in the monitor log.
18:35:10.619492 IP6 2607:f238:2::11.41001 > sheeva6.sinodun.org.uk.ntp:
NTPv3, Client, length 48
18:35:10.619814 IP6 sheeva6.sinodun.org.uk.ntp > 2607:f238:2::11.41001:
NTPv3, Server, length 48
18:35:32.913637 IP6 2607:f238:2::11.37979 > sheeva6.sinodun.org.uk.ntp:
NTPv3, Client, length 48
18:35:32.913960 IP6 sheeva6.sinodun.org.uk.ntp > 2607:f238:2::11.37979:
NTPv3, Server, length 48
18:35:49.633674 IP6 2607:f238:2::11.12222 > sheeva6.sinodun.org.uk.ntp:
NTPv3, Client, length 48
18:35:49.633869 IP6 sheeva6.sinodun.org.uk.ntp > 2607:f238:2::11.12222:
NTPv3, Server, length 48
18:35:51.635679 IP6 2607:f238:2::11.30553 > sheeva6.sinodun.org.uk.ntp:
NTPv3, Client, length 48
18:35:51.635878 IP6 sheeva6.sinodun.org.uk.ntp > 2607:f238:2::11.30553:
NTPv3, Server, length 48
1307381753,"2011-06-06 17:35:53",,-5,-24
1307381732,"2011-06-06 17:35:32",0.00999212265014648,1,-20
1307381710,"2011-06-06 17:35:10",0.00950753688812256,1,-22.1
John
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
