| Re: [chrony-users] help with bindacqaddress | 
[ Thread Index | 
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
] 
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
 
- Subject: Re: [chrony-users] help with bindacqaddress
 
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
 
- Date: Tue, 26 May 2020 09:42:03 +0200
 
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;	s=mimecast20190719; t=1590478929;	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=H3gT+rhFy7RWw3gpBRL3oJ6d4ARO/2p8WUbVdpl8QJs=;	b=SeEWIf8sKPQVrhA4bH9Cg/SuF7JWHqEp7wV4UXCVLfjf01q4XHz4YCncD9aWipnKGN3nBF	ISK3d7w3gn9nlQRuUlkwwrx1J6VkkRgeGQpzCYliHDUXceap1TNroyUl7bgEw5zeeyMAKL	sKRYTIvQGPnkxAL2Qm/iRS04dMqrj40=
 
On Mon, May 25, 2020 at 11:24:41AM -0400, Giacomo Comes wrote:
> with chrony the equivalent command should be:
>   bindacqaddress <ip>
> and while this works with a network interface with static
> ip address, it is troublesome with DHCP.
> ( I need to change chrony.conf and and restart chronyd every
> time the ip address changes).
> Am I missing something?
No, there is currently no way to specify the interface for NTP
requests.
> Could bindacqaddress be changed to
> have as argument also the network interface name instead of 
> the ip address?
It could, at least in theory. The trouble is with portability. I'm not
sure how to bind a socket to a specific interface on non-Linux
systems. There is a possibility of getting addresses of all
interfaces, but I suspect that would be too expensive to do with each
request. ntpd is continuously tracking all interfaces. That's complex,
requires a lot of OS-specific code, and not really acceptable for
chrony.
As a workaround, maybe you could use policy routing (ip rule) to 
select the interface for NTP packets?
-- 
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.