| Re: [chrony-dev] Chrony behind load balancer doing DSR |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] Chrony behind load balancer doing DSR
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Thu, 28 Apr 2022 09:11:48 +0200
- Authentication-results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1651129913; 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=hopLZf26ZeAOMyelQjLwA5925vEjx/qruV2B0bSC3rw=; b=LludJF7thik09avg69agYWZRkmB1CRz/VhVWxDaKMQLgsvszBlFRTcuufRBfoeE6qpAGai TQxuUgzkgpjJoyDr4IY+d7KoA16pXSaFy5hsAwd6otqlfL4aoNPOXmICLM0g/5q5m6RFzq JLm8pG5QPNACAhNrGT7MV5nVHOCYCMQ=
On Wed, Apr 27, 2022 at 02:59:42PM -0400, Bryan Seitz wrote:
> Chrony devs,
>
> We’d like to migrate to a load balancer using direct server return with Chrony. The VIP address is assigned to the LO interface and we are using an IPIP tunnel. The problem is that Chrony receives the packet on the tunl0 (pip) interface and sends the reply (DSR with real client IP destination) back out the tunl0 interface. The packet needs to go out eth0 since that is how things are routed properly. ISC Kea has an option to do this however I cannot find an equivalent with Chrony. Is there a solution or is it possible to add similar functionality to Chrony?
What version of chrony are you using?
In 4.0 there was this change:
* Don't set interface for NTP responses to allow asymmetric routing
which was intended for cases like you describe.
--
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.