| Re: [chrony-dev] Re: chrony 3.4+ on multihomed machines forces wrong interface |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] Re: chrony 3.4+ on multihomed machines forces wrong interface
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 28 Apr 2020 14:06:16 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1588075581; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=MFs6sRRtYUTesb9GitQn9z7tV6yGcfIaM1tKboTjrI4=; b=E1zRQ2GNhxuCuQQOrTM/pASTLrOwmGk9cUOHb/wCHgETSjzF7+dAhkLiPZ04AN7BtPGpkt 4SjO1MlWPnL7hnrdzjMdNPufsY5yTnNANOd8j7eRN5hAVDsQ+OZyEQaiS+X9xYWJJiAmbb ruvFipzA5dHySwde9J/Ve8eoXhWJ8Ic=
On Tue, Apr 28, 2020 at 01:01:59PM +0200, Arkadiusz Miśkiewicz wrote:
> On 28/04/2020 12:23, Miroslav Lichvar wrote:
> > On Tue, Apr 28, 2020 at 11:57:31AM +0200, Arkadiusz Miśkiewicz wrote:
> >> Anyway forcing interface index looks to be wrong (bypasses routing
> >> table) solution to problem which that commit tried to fix.
> >
> > Do you have a suggestion for a different fix?
>
> What was the original problem that
> 5fc7674e366fa1bfda162bdaba57243cff0a55a7 tried to fix?
A server with multiple interfaces in a local network. I wasn't able to
find sysctl settings that would make chronyd consistently respond from
the same interface that received the request.
> That would mean implementing "ip route get A from B" variant
> (RTM_GETROUTE) and checking if that route is thru gateway (as I
> understand accuracy you mention makes sense in local lan only, when
> there are multiple interfaces to the same network) and if it is using
> gateway and interfaces don't match then avoid forcing interface.
>
> Ugly.
Yes. I don't like the idea of tracking interfaces and networks in
chronyd. I wish there was an option to only hint the interface in
sendmsg() and ignore it if there is no route.
--
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.