[chrony-users] NTP bogus timestamps - Chrony on openSUSE 15.1

[ Thread Index | Date Index | More chrony.tuxfamily.org/chrony-users Archives ]


I was just looking at some NTP packets between my openSUSE desktop
system and my firewall, which has a NTP server.  I see the request
timestamps are all bogus values.

    Reference ID: NULL
    Reference Timestamp: Jan  1, 1970 00:00:00.000000000 UTC
    Origin Timestamp: Jan  1, 1970 00:00:00.000000000 UTC
    Receive Timestamp: Jan  1, 1970 00:00:00.000000000 UTC
    Transmit Timestamp: Jun 23, 1983 00:21:14.440064618 UTC

However, the reply from the server shows correct values.

    Reference ID: 132.246.11.238
    Reference Timestamp: Aug 20, 2019 15:46:02.939010883 UTC
    Origin Timestamp: Jun 23, 1983 00:21:14.440064618 UTC
    Receive Timestamp: Aug 20, 2019 16:02:07.892748690 UTC
    Transmit Timestamp: Aug 20, 2019 16:02:07.892798979 UTC

Why are the values from the client nonsense?

Proper NTP operation requires accurate time stamps in both directions,
to ensure accurate time.  For example, the transit time is used to
determine the local offset from the server.

The packets between my pfSense firewall and the public NTP server show
correct values.

    Reference ID: 132.246.11.238
    Reference Timestamp: Aug 20, 2019 16:21:22.937971724 UTC
    Origin Timestamp: Aug 20, 2019 16:23:07.952061086 UTC
    Receive Timestamp: Aug 20, 2019 16:23:07.971987723 UTC
    Transmit Timestamp: Aug 20, 2019 16:31:44.921310040 UTC

https://en.wikipedia.org/wiki/Network_Time_Protocol#Timestamps


-- 
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.


Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/