| Re: [chrony-users] NTP to Chrony migration issue with NTP authentication with symmetric keys |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] NTP to Chrony migration issue with NTP authentication with symmetric keys
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 7 Nov 2023 12:49:47 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1699357791; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=gRWKpXMXc/xTWLOY8g5MSmyzw4vJ34Txr1f4xKvxSBQ=; b=aJhLA4i7BI4B2rAaYnn0jW2V07sLgvJqTu5lQp2cL8ymBKJlL4D6zK4s+aNSv+f8NowSSs TX3A+niUTjmfCovdPn8QTPDPP0xPr1FZ/nMChfhpIAQ5tQJqkarPsd2B4D3bVVXYmJuSCZ XGSPyHVoMwLzC6JogEdaSXIYUwoOq+A=
On Mon, Nov 06, 2023 at 10:55:12AM -0600, Michael Krell wrote:
> I've modified the value in the chrony.keys file to include "HEX:";
> retesting "chronyd -dd", now the output does not show the
> "(NCR_ProcessRxUnknown)" log message. There is still a "Receive timeout"
An occasional receive timeout could be due to the rate limiting
enabled on the server (restrict kod limited).
Do you see any valid packets received in ntpdata? Which NTP tests are
failing?
If not, please capture an exchange with tcpdump and post the output
here.
--
Miroslav Lichvar
--
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.