| [chrony-users] Checking chrony daemon status via NTP3 protocol |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: "chrony-users@xxxxxxxxxxxxxxxxxxxx" <chrony-users@xxxxxxxxxxxxxxxxxxxx>
- Subject: [chrony-users] Checking chrony daemon status via NTP3 protocol
- From: SALA MASSIMO <MASSIMO.SALA@xxxxxxxxx>
- Date: Tue, 26 May 2020 17:49:15 +0000
- Accept-language: it-IT, en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ats-bg.it; dmarc=pass action=none header.from=ats-bg.it; dkim=pass header.d=ats-bg.it; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=EtvkXISvc1Iyzyzgc3nIeKLcW4fEwZny2Bd+0+9cuJE=; b=KFy5+QaHh4i1ChyZDWYMCjnmEevNV603fcoaa4YtUK5mM3mlrIrEmE2/Ol4O0+cwWsAl8skRAHeTOHHNQQad6WKG/L5pGe3L8PVW4cA2Yy2v/ZC+NFxxkCthhlQSn3/sCgAuW7VBGRlKCkFASWpj0xWMgjoWjK/geKHj4E97aDr9yGS00sH5gZVvt8BikFl/akV7MZstYLqsQJW3tXL1Yj0PJSlsReH7LQrgc58aq+hDW2S3MMwWzZZw+/GeTpNqvt/a7+wyuf4fGUEonBdP/WijyRib3tUQ+g6QxeoaJAu3ESA5iWUFoeEQpC6DDud0eagMXve3FveB59uwbIjUmA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=F+taHciChOQfJHUrOCW14TFM3Jc5V9684UFA6loqL9arq3UeI+/kcT2R0IctJkpLHi9uFzU44SNjfclbzkmv6VXoMSDSmUN1oiv9e0AJaHTyUPhqqMqPFqq85T3RC/R0TiDUiQmhGxDOAzCgp168qBGfZeCCpzU5kpMJ/yqFTgtsWajdT/w0o8AYNyeOidDezfr1INqCyx81yqbe1oRwAcK0fmhztMoOnTlH7r9UkpYrkbGw9zhFeV8/657AeukyiUv/3WAjYwInxgEOWbUseWsqirxG656iapkI+ptkhRMKrTdyi0umJs5kjxKB0754NrHwyZn45wTCoIQjsKayXQ==
- Authentication-results: chrony.tuxfamily.org; dkim=none (message not signed) header.d=none;chrony.tuxfamily.org; dmarc=none action=none header.from=ats-bg.it;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=atsbg.onmicrosoft.com; s=selector2-atsbg-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=EtvkXISvc1Iyzyzgc3nIeKLcW4fEwZny2Bd+0+9cuJE=; b=fO7QtyJZWyPsu4l6gayfJZDjBJqhbZIYdplGokApm03cajSk0kFsqPDaeDZ1XkcUKNxHgGK37wtTIlJGXAm++N0MjryiVu4mLN7nmyHnsh9UnsRzo4kxsoydQ29R9Fwit7AElo+W7OQAqqKy3UaLcA0wpWyXKI0LA6OzE03de68=
- Thread-index: AQHWM4WSHA1aL6NS4UGHHVN07eDCPA==
- Thread-topic: Checking chrony daemon status via NTP3 protocol
Hi
I apologize in advace if my question is trivial.
The daemon is stopped (ver 3.5).
I start it and send a NTP3 CLIENT query, to localhost port 123/udp:
NTP_VERSION << 3 | NTP_MODE_CLIENT
The first answer has the status 0xdc : the bit NTP_LEAP_NOTSYNC is set.
Good: the daemon is starting and looking for the Ntp servers.
I query again the daemon, and in the following replies from the server:
* the status is OK : 0x1c
* the server time (reference timestamp, at offset 16 of the Udp packet payload) is incorrect.
The time values are random, below the UNIX_EPOCH (Ntp time 2208988800, 1/1/1970).
After a few queries, the server time changes to a sane value.
Why does chronyd report random time values, without NTP_LEAP_NOTSYNC ?
1) is this compliant to RFC 1305 ?
2) is there any other info in the response payload I have to check ?
Best regards, Massimo
[ATS logo]
Le informazioni contenute in questo messaggio e nei suoi allegati sono ad esclusivo beneficio del corretto destinatario e sono da considerarsi confidenziali e riservate. Qualora abbiate ricevuto il messaggio per errore, siete pregati di darne immediata notizia al mittente e di provvedere alla sua cancellazione. La rivelazione del contenuto di corrispondenza destinata ad altri e ricevuta per errore è perseguibile penalmente e può costituire un trattamento illecito di dati personali.
This e-mail and any attachment is confidential and only for use of the intended recipient. If you are not the intended recipient, you are hereby notified that any disclosure of this communication is strictly prohibited. If you have received this communication in error, please notify the sender, and then delete this message from your system.
Prima di stampare, pensa all’ambiente.