[opensuse] NTP bogus timestamps - 15.1
I was just looking at some NTP packets between my openSUSE desktop system and my firewall, which has a NTP server. I see the 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, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Forgot to mention, this system is running Chrony. On 2019-08-20 12:47 PM, James Knott wrote:
I was just looking at some NTP packets between my openSUSE desktop system and my firewall, which has a NTP server. I see the 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, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Tue, 20 Aug 2019, James Knott wrote:
Why are the values from the client nonsense?
Are you running a local ntpd or systemd-timesyncd? If the former, have you set the local reference clock source in /etc/ntp.conf? ==== /etc/ntp.conf ==== ## Undisciplined Local Clock. This is a fake driver intended for backup ## and when no outside source of synchronized time is available. server 127.127.1.0 fudge 127.127.1.0 stratum 15 ==== HTH, -dnh -- People disagree with me. I just ignore them. -- Linus Torvalds, regarding the use of C++ for the Linux kernel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-08-20 02:09 PM, David Haller wrote:
Hello,
On Tue, 20 Aug 2019, James Knott wrote:
Why are the values from the client nonsense? Are you running a local ntpd or systemd-timesyncd? If the former, have you set the local reference clock source in /etc/ntp.conf?
==== /etc/ntp.conf ==== ## Undisciplined Local Clock. This is a fake driver intended for backup ## and when no outside source of synchronized time is available. server 127.127.1.0 fudge 127.127.1.0 stratum 15
I'm not running an undisciplined server. I'm running Chrony and as far as I can tell, it's not being used as a server. Also, why would an undisciplined server be sending packets to a server? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
David Haller -
James Knott