Re: 答复: [chrony-users ] about NTP services on multiple network interfaces.
Miroslav Lichvar <[email protected]>
| Newsgroups | gmane.comp.time.chrony.user |
|---|---|
| Message-ID | <Ytj/2vQyYTmByIkC@localhost> |
On Thu, Jul 21, 2022 at 01:54:12AM +0000, chengyechun wrote: > Thank you for your reply； > This is my expression problem. When I use chrony as the server, add bindaddress 0.0.0.0 to listen to all IPv4 addresses. This is fine. However, if a cluster needs time synchronization and a machine is used as the ingress of the cluster, it is a server inside the cluster and uses an IP address. If it is a client outside the cluster, can it use another IP address? This means that the IP addresses of the received and sent packets are different. It's still not very clear to me what's the issue. Are you trying to restrict access, or are some clients not working if bindaddress is 0.0.0.0? As a server, chronyd follows bindaddress. As a client, it follows bindacqaddress. They can be different. The default of 0.0.0.0 means it listens on all addresses the host has. If you change it to a specific address, it will not listen on other addresses. As a server, it should always respond with the same address as it received the request. NTP clients will not normally accept a response from a different address than they sent request to, but bindaddress shouldn't change anything about that. -- Miroslav Lichvar -- To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "unsubscribe" in the subject. For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "help" in the subject. Trouble? Email [email protected]