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. V. -- 16:24:15.137561 IP6 2607:f238:2::11.12935 > 2001:888:20ee:94:123:270b:6c70:3d0d.ntp: NTPv3, Client, length 48 16:24:15.138049 IP6 2001:888:20ee:94:123:270b:6c70:3d0d.ntp > 2607:f238:2::11.12935: NTPv3, Server, length 48 16:24:17.140088 IP6 2607:f238:2::11.7463 > 2001:888:20ee:94:123:270b:6c70:3d0d.ntp: NTPv3, Client, length 48 16:24:17.140345 IP6 2001:888:20ee:94:123:270b:6c70:3d0d.ntp > 2607:f238:2::11.7463: NTPv3, Server, length 48 16:24:41.025464 IP6 2607:f238:2::11.37212 > 2001:888:20ee:94:123:270b:6c70:3d0d.ntp: NTPv3, Client, length 48 16:24:41.025633 IP6 2001:888:20ee:94:123:270b:6c70:3d0d.ntp > 2607:f238:2::11.37212: NTPv3, Server, length 48 16:25:06.974652 IP6 2607:f238:2::11.34313 > 2001:888:20ee:94:123:270b:6c70:3d0d.ntp: NTPv3, Client, length 48 16:25:06.975131 IP6 2001:888:20ee:94:123:270b:6c70:3d0d.ntp > 2607:f238:2::11.34313: NTPv3, Server, length 48 16:50:37.387717 IP6 2607:f238:2::11.14444 > 2001:888:20ee:94:123:270b:6c70:3d0d.ntp: NTPv3, Client, length 48 16:50:37.388327 IP6 2001:888:20ee:94:123:270b:6c70:3d0d.ntp > 2607:f238:2::11.14444: NTPv3, Server, length 48 16:50:39.389808 IP6 2607:f238:2::11.23716 > 2001:888:20ee:94:123:270b:6c70:3d0d.ntp: NTPv3, Client, length 48 16:50:39.389960 IP6 2001:888:20ee:94:123:270b:6c70:3d0d.ntp > 2607:f238:2::11.23716: NTPv3, Server, length 48 16:51:01.123773 IP6 2607:f238:2::11.42295 > 2001:888:20ee:94:123:270b:6c70:3d0d.ntp: NTPv3, Client, length 48 16:51:01.123969 IP6 2001:888:20ee:94:123:270b:6c70:3d0d.ntp > 2607:f238:2::11.42295: NTPv3, Server, length 48 16:51:13.675077 IP6 2607:f238:2::11.pconnectmgr > 2001:888:20ee:94:123:270b:6c70:3d0d.ntp: NTPv3, Client, length 48 16:51:13.675210 IP6 2001:888:20ee:94:123:270b:6c70:3d0d.ntp > 2607:f238:2::11.pconnectmgr: NTPv3, Server, length 48 16:51:15.677850 IP6 2607:f238:2::11.34486 > 2001:888:20ee:94:123:270b:6c70:3d0d.ntp: NTPv3, Client, length 48 16:51:15.677978 IP6 2001:888:20ee:94:123:270b:6c70:3d0d.ntp > 2607:f238:2::11.34486: NTPv3, Server, length 48 16:51:32.517299 IP6 2607:f238:2::11.34114 > 2001:888:20ee:94:123:270b:6c70:3d0d.ntp: NTPv3, Client, length 48 16:51:32.517437 IP6 2001:888:20ee:94:123:270b:6c70:3d0d.ntp > 2607:f238:2::11.34114: NTPv3, Server, length 48 16:51:46.733875 IP6 2607:f238:2::11.20973 > 2001:888:20ee:94:123:270b:6c70:3d0d.ntp: NTPv3, Client, length 48 16:51:46.734086 IP6 2001:888:20ee:94:123:270b:6c70:3d0d.ntp > 2607:f238:2::11.20973: NTPv3, Server, length 48 16:51:48.736625 IP6 2607:f238:2::11.imqbrokerd > 2001:888:20ee:94:123:270b:6c70:3d0d.ntp: NTPv3, Client, length 48 16:51:48.736837 IP6 2001:888:20ee:94:123:270b:6c70:3d0d.ntp > 2607:f238:2::11.imqbrokerd: NTPv3, Server, length 48 16:52:00.998867 IP6 2607:f238:2::11.43007 > 2001:888:20ee:94:123:270b:6c70:3d0d.ntp: NTPv3, Client, length 48 16:52:00.998960 IP6 2001:888:20ee:94:123:270b:6c70:3d0d.ntp > 2607:f238:2::11.43007: NTPv3, Server, length 48 16:52:15.155699 IP6 2607:f238:2::11.11334 > 2001:888:20ee:94:123:270b:6c70:3d0d.ntp: NTPv3, Client, length 48 16:52:15.155792 IP6 2001:888:20ee:94:123:270b:6c70:3d0d.ntp > 2607:f238:2::11.11334: NTPv3, Server, length 48 16:52:17.158475 IP6 2607:f238:2::11.33672 > 2001:888:20ee:94:123:270b:6c70:3d0d.ntp: NTPv3, Client, length 48 16:52:17.158582 IP6 2001:888:20ee:94:123:270b:6c70:3d0d.ntp > 2607:f238:2::11.33672: NTPv3, Server, length 48 16:52:33.307342 IP6 2607:f238:2::11.54582 > 2001:888:20ee:94:123:270b:6c70:3d0d.ntp: NTPv3, Client, length 48 16:52:33.307434 IP6 2001:888:20ee:94:123:270b:6c70:3d0d.ntp > 2607:f238:2::11.54582: NTPv3, Server, length 48 _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
