| Re: [chrony-users] Chrony Client Support for different ports to the same server? |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Chrony Client Support for different ports to the same server?
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 28 Jan 2025 08:35:00 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1738049709; 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=xitQf4nsQa/xLtZ+tgSvwNV1UuqUvmv+bC6kJJ1TU2M=; b=i8qlKG3hOnGCnQd/SMtrP8ncQRNVknSMC8qbgkeh/8Sze3/cOFT4YTEYYLz89BsD4vv5Kd h913rBWbf1OjdCCHzlTeHIlzNnqJcM0wZhrRVj2lH+hQ+z49XmiRQTWXGaU6tvkRgnK+T9 nanIem16zT3lQdPspzVRqonpiCDNgs8=
On Mon, Jan 27, 2025 at 06:28:42PM -0500, Derek Atkins wrote:
> I was able to get it working using NAT from a localhost address out to the
> server. I'm working on integrating that approach into the code.
Note that in the case when both ports work this effectively doubles
the weight of the single server in the source selection algorithm.
If it was serving incorrect time and there two other sources (4 IP
addresses in total), chronyd would not be able to reject it and fail
to synchronize.
If you don't use any other sources, it shouldn't be a problem.
--
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.