| Re: [chrony-dev] IPv6 link-local support |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] IPv6 link-local support
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Thu, 9 Jan 2020 14:42:00 +0100
- Cc: Per Nørgaard Christensen <per.christensen@xxxxxxxxx>, Lasse Klok Mikkelsen <Lasse.Klok@xxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1578577273; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9Z4MWC4KRlPZoNTha/8Ja/u4IUs/QotlXUb6Ozj53rc=; b=SJR43oNwVjkHT8OBGJ0jzn/CkFujE/fwSrtEMPhUHyy9qn+nteXntVlSZ7i4T7OosjbrUv 4U+j0v97OR3nb/msmn3IA2CY46qPQF3Jzmm5cN+iEnmOClcA0n9NyvrxEJxvrwcumXXFFo VFaDjrq3w0A776Qn0pnX4W1gU9uKU/U=
On Thu, Jan 09, 2020 at 11:58:48AM +0000, Rasmus Villemoes wrote:
> Now, is that a fundamental limitation, or is it something that might be
> supported? We have a number of clients that want to switch to chrony,
> but lack of IPv6LL is mostly a showstopper. I'm happy to try to dig into
> the code and help produce patches, but I will probably need a few
> pointers to get me started.
It should be possible to support it in chrony, but I suspect it would
require a lot of new code. I'm not sure if it's worth it. If it could
be implemented easily in few lines of code, I'd be happy to include
it.
I think there are quite a lot of places that would need to be extended
to work with the interface name or index in addition to the address.
This includes the client log, address filter, cmdmon protocol and
chronyc. It would require system specific code, e.g. to convert the
interface name to its index. Also, I'm not sure if we wouldn't need to
monitor changes in the networking configuration for performance
reasons, like ntpd does. Server support seems easier than client
support.
Could you describe your use case in more detail and why is it not
possible to enable ULA in the network? It doesn't seem to be a common
use case.
--
Miroslav Lichvar
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.