System information

Manual:System/Time
156
• kod-ABCD - Received "KoD" (Kiss-o'-Death) response. ABCD is the short "kiss code" text from the Reference
Identifier field.
• broadcast - Received proadcast message, but mode=unicast.
• non-broadcast - Received packed was server reply, but mode=broadcast.
• server-ip-mismatch - Received response from address that is not active-server.
• originate-timestamp-mismatch - Originate Timestamp field in the server response message is not the same as
the one included in the last request.
• roundtrip-too-long - request/response roundtrip exceeded 1 second.
Log messages
SNTP client can produce the following log messages. See article "log" on how to set up logging and how to inspect
logs.
• ntp,debug gradually adjust by OFFS
• ntp,debug instantly adjust by OFFS
• ntp,debug Wait for N seconds before sending next message
• ntp,debug Wait for N seconds before restarting
• ntp,debug,packet packet receive error, restarting
• ntp,debug,packet received PKT
• ntp,debug,packet ignoring received PKT
• ntp,debug,packet error sending to IP, restarting
• ntp,debug,packet sending to IP PKT
Explanation of log message fields
• OFFS - difference of two NTP timestamp values, in hexadecimal.
• PKT - dump of NTP packet. If packet is shorter than the minimum 48 bytes, it is dumped as a hexadecimal string.
Otherwise, packet is dumped as a list of field names and values, one per log line. Names of fields follow
RFC4330.
• IP - remote IP address.
NOTE: the above logging rules work only with the built-in SNTP client, the separate NTP package doesn't have any
logging facilities.
NTP client and server
To use NTP client and server, ntp package must be installed and enabled.
Client settings
Client configuration is located in /system ntp client.
• enabled (yes or no; default value: no)
• mode (One of broadcast, unicast, multicast or manycast.)
• primary-ntp, secondary-ntp (IP address)