> > All those timestamps in the far past and future? Does this look right?
> > I didn't even show you all the packets, but it is just an example.
>
> This is perfectly normal, it's random data that would be ignored by ntpd
> being converted to date/time by tcpdump.
Then why does my ntpd reply to those packets?
22:59:35.716438 IP (tos 0x0, ttl 56, id 53616, offset 0, flags [DF], proto
17, length: 76) pD9E77E91.dip.t-dialin.net.1071 >
535247CD.cable.casema.nl.ntp: NTPv4, length 48
Client, Leap indicator: (0), Stratum 0, poll 0s, precision 0
Root Delay: 0.000000, Root dispersion: 0.000000, Reference-ID:
(unspec)
Reference Timestamp: 0.000000000
Originator Timestamp: 0.000000000
Receive Timestamp: 0.000000000
Transmit Timestamp: 2898045451.504183851 (1991/11/02 05:37:31)
Originator - Receive Timestamp: 0.000000000
Originator - Transmit Timestamp: 2898045451.504183851
(1991/11/02 05:37:31)
22:59:35.716762 IP (tos 0x10, ttl 64, id 60231, offset 0, flags [DF], proto
17, length: 76) 535247CD.cable.casema.nl.ntp >
pD9E77E91.dip.t-dialin.net.1071: NTPv4, length 48
Server, Leap indicator: (0), Stratum 2, poll 0s, precision -20
Root Delay: 0.020019, Root dispersion: 0.038742, Reference-ID:
adsl.remco.org
Reference Timestamp: 3379787836.248038999 (2007/02/06 22:57:16)
Originator Timestamp: 2898045451.504183851 (1991/11/02 05:37:31)
Receive Timestamp: 3379787975.716652999 (2007/02/06 22:59:35)
Transmit Timestamp: 3379787975.716696999 (2007/02/06 22:59:35)
Originator - Receive Timestamp: +481742524.212469148
Originator - Transmit Timestamp: +481742524.212513148
Jos
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
