From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from maja (localhost.localdomain [127.0.0.1])
	by passt.top (Postfix) with ESMTP id 3F2065A0269
	for <passt-dev@passt.top>; Sat, 14 Nov 2026 05:53:25 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PATCH v4 2/2] conf, icmp, tcp,
 udp: Add options to bind to outbound address and interface
From: me@yueyinqiu.top
To: passt-dev@passt.top
Date: Sat, 14 Nov 2026 04:53:25 -0000
Message-ID: <179463200525.2887.15950519702333489150@maja>
In-Reply-To: <20230309020947.2609964-3-sbrivio@redhat.com>
References: <20230309020947.2609964-3-sbrivio@redhat.com>
User-Agent: HyperKitty on https://lists.passt.top/
Message-ID-Hash: HT2L5V2WIOMMEUF2VY2SKL3MUH3WMCTX
X-Message-ID-Hash: HT2L5V2WIOMMEUF2VY2SKL3MUH3WMCTX
X-MailFrom: me@yueyinqiu.top
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.8
Precedence: list
List-Id: Development discussion and patches for passt <passt-dev.passt.top>
Archived-At: <https://archives.passt.top/passt-dev/179463200525.2887.15950519702333489150@maja/>
Archived-At: <https://passt.top/hyperkitty/list/passt-dev@passt.top/message/HT2L5V2WIOMMEUF2VY2SKL3MUH3WMCTX/>
List-Archive: <https://archives.passt.top/passt-dev/>
List-Archive: <https://passt.top/hyperkitty/list/passt-dev@passt.top/>
List-Help: <mailto:passt-dev-request@passt.top?subject=help>
List-Owner: <mailto:passt-dev-owner@passt.top>
List-Post: <mailto:passt-dev@passt.top>
List-Subscribe: <mailto:passt-dev-join@passt.top>
List-Unsubscribe: <mailto:passt-dev-leave@passt.top>

Hi,

I ran into exactly the use case this series addresses: I run a rootless podman container that is itself a VPN client (Sangfor aTrust), on a host that also has a single-user tun (sing-box with auto_route). That tun captures all host egress via policy routing (ip rule), so pasta's outbound forwarding for my container gets hijacked -- the VPN tunnel ends up going through the host tun instead of directly out the physical NIC.

I noticed this series (v4) got a Reviewed-by from David but never seems to have been merged. Is it still the plan? What's it blocked on -- a rebase against the current tree? I'm happy to help if needed.

Thanks!