From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: passt.top; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: passt.top; dkim=pass (1024-bit key; unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=Y8v9EIzB; dkim-atps=neutral Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by passt.top (Postfix) with ESMTPS id CD7335A026E for ; Mon, 27 Jul 2026 18:48:50 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1785170929; 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=Bb1q8BtxLH8uH1wR/Pb0e8C+iFB0Npz10mlFm0vmBzA=; b=Y8v9EIzBKUpMiBXVV30Zia56qDh7x/40yiMzCHxS/7qLHA4G7jVJKd3lEOFZqhDfETYpRJ +ed8fqsmZm981TGUqvZgkVT6rkCat/YDf0LLVJuMypf2bYWVj4CEKFP5Sc8vBUHRZNH1tD cfDZgfgsf605sGH6tafsgZwxmi45iDY= Received: from mail-wr1-f71.google.com (mail-wr1-f71.google.com [209.85.221.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-96-JUhb2tr3PqWEEHz736XaHA-1; Mon, 27 Jul 2026 12:48:48 -0400 X-MC-Unique: JUhb2tr3PqWEEHz736XaHA-1 X-Mimecast-MFC-AGG-ID: JUhb2tr3PqWEEHz736XaHA_1785170927 Received: by mail-wr1-f71.google.com with SMTP id ffacd0b85a97d-47f83450a8eso2575144f8f.0 for ; Mon, 27 Jul 2026 09:48:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1785170927; x=1785775727; h=date:content-transfer-encoding:content-type:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to:content-type; bh=Bb1q8BtxLH8uH1wR/Pb0e8C+iFB0Npz10mlFm0vmBzA=; b=ksqGefLvtKd0Lt7Fl5QzR3fqPhb29CpW1qIekNJD3p9C96NrBK0Tlxrzj4GT1qezIO Fj/Wphn+TE5BGiy5a0UpyJkWI/2jgpRqpnMzocNsjfRuS585BjQZ5ZnvGVYlvi9012Tc p/EypNOUE4yCC6Ehh9iaoHPQBSczptgTNImMKYFGFMMfyB5pTbstSBOCMv63tGUzAigT 9T1Z3FuV3IQwUHgZ+2g8sf144kW3nmvay573qhqWrLREFXg7ONFVHGBlQe2UdDmi//u2 DA9uVdgEQwXutKBc5QjxaF38ZE2c436NvtsMnxDKMeMhJmNfacOl7DCS3u47kvoGkBAy GYUw== X-Gm-Message-State: AOJu0Yw6Ea0es+P/t9TEbVVc4eYl3pa7tOUIMXQ5I5OC1pWWCQenpUop YxnMBfusrSGC3mnxWQrNHMXC/z7SkK2FOhCDaidmMsnkcrkfabDN8nI0jv3liLQ8Wnt7SQMGA+O giyKQCtC0WlqQmycThh4o8ozgi18uTz/fbDNmMcpPkaxRogOWbQQt4Q== X-Gm-Gg: AR+sD10L/HsvhGYhdyZROffco9mJhS6FnawjEYDCFDQJc5+7szmqpKZ2TUHaJBfHsYt tNRpWxoZhnNNSTnp+LBzHsFcAmaA/iRSSRcQV2XspNLTVGfI73+orzdxe7b/C0LBC9AJ4UnsfFv Fe4t8PkDoYZIzR+iAvFR9GjIZZa74KH9ftiOST1ueVkukwFQt2rDa9bM/13Idc3plUADXpqLUTc AM2gxUOT6tzNn85WMv+d34xDQPhGMCLUzS8Y7e5mnVqX4l01qJye1Avssjfk39/+0XbvK5zSsIg Qo4XU9hlu4YAObVWfvLvlIL5Q0A8HZ0dasvGyujk8tiMTUnyW2HLd4ugy/PpVaycTRg1qiGDmOF 0ZGhmkbUeTx6sMCDidy9shb+CJfap X-Received: by 2002:a05:600c:4709:b0:495:71fc:3a64 with SMTP id 5b1f17b1804b1-496b56ff1fcmr114280665e9.25.1785170927200; Mon, 27 Jul 2026 09:48:47 -0700 (PDT) X-Received: by 2002:a05:600c:4709:b0:495:71fc:3a64 with SMTP id 5b1f17b1804b1-496b56ff1fcmr114280305e9.25.1785170926674; Mon, 27 Jul 2026 09:48:46 -0700 (PDT) Received: from maya.myfinge.rs (ifcgrfdd.trafficplex.cloud. [176.103.220.4]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-4957f9928fdsm261054955e9.1.2026.07.27.09.48.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 27 Jul 2026 09:48:46 -0700 (PDT) From: Stefano Brivio To: Yuxi Liu Subject: Re: [BUG] --map-guest-addr target resolved once at startup; host network change kills the mapping silently and permanently Message-ID: <20260727184841.7fc3dc30@elisabeth> In-Reply-To: References: Organization: Red Hat X-Mailer: Claws Mail 4.2.0 (GTK 3.24.49; x86_64-pc-linux-gnu) MIME-Version: 1.0 Date: Mon, 27 Jul 2026 18:48:45 +0200 (CEST) X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: BdeRD7197SuskHQFBuLmtPtvTBQV16d4A8-QqkCsGSs_1785170927 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-ID-Hash: A24TIG6UNS3A64QV25TX2LNNWHC4PT6U X-Message-ID-Hash: A24TIG6UNS3A64QV25TX2LNNWHC4PT6U X-MailFrom: sbrivio@redhat.com 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 CC: passt-dev@passt.top, David Gibson , Paul Holzinger , Jon Maloy X-Mailman-Version: 3.3.8 Precedence: list List-Id: Development discussion and patches for passt Archived-At: Archived-At: List-Archive: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Yuxi, thanks for the report. I think David and Paul already covered the main points here, but I have a couple of details: On Sat, 25 Jul 2026 09:28:14 -0700 Yuxi Liu wrote: > Expected > -------- > One of: > 1. pasta re-resolves the mapping target when the host's addresses > change, or This is the plan, essentially. For the moment: > 2. the mapped route fails loudly (RST) instead of silently, or ...we will reset the connection if our connect() attempt fails, or at least that should be the intention, and I'm fairly sure it works. So the route to the destination (via your default gateway, I suppose) is actually valid, packets are forwarded, but they just end up nowhere on your host, correct? If that's not the case, then it's something we should fix. > 3. the man page warns that the mapping dies permanently on host > network change. This would be a welcome change for the moment anyway, it might take months before we get to 1., so feel free to submit a patch for the man page if you have a moment. Note that there's a pending patch being reviewed for --map-guest-addr, at: https://archives.passt.top/passt-dev/20260727040946.105277-1-david@gibson.dropbear.id.au/#r so you would probably need to integrate your changes with it. At the same time the additional note could form its own paragraph at the end. I routinely fix up trivial conflicts while merging changes, so, if it's its own paragraph, you don't really need to take care of them. > Laptops are a mainstream platform for rootless podman. A silent, > permanent route death on every wifi change is a serious defect for > them. Absolutely. We have a ton of reports about those use cases, see: https://github.com/podman-container-tools/podman/discussions/22737#discussioncomment-9478727 as well. The implementation is in progress but by no means trivial. Let us know if you want to contribute to it, by the way. -- Stefano