From: Stefano Brivio <sbrivio@redhat.com>
To: Yuxi Liu <yuxi_liu@berkeley.edu>
Cc: passt-dev@passt.top, David Gibson <david@gibson.dropbear.id.au>,
Paul Holzinger <pholzing@redhat.com>,
Jon Maloy <jmaloy@redhat.com>
Subject: Re: [BUG] --map-guest-addr target resolved once at startup; host network change kills the mapping silently and permanently
Date: Mon, 27 Jul 2026 18:48:45 +0200 (CEST) [thread overview]
Message-ID: <20260727184841.7fc3dc30@elisabeth> (raw)
In-Reply-To: <CAOwiiiwebECFMPMqakdCe5-M8fHF3WGNu5hyEz3CRdwS+Lvwmw@mail.gmail.com>
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 <yuxi_liu@berkeley.edu> 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
prev parent reply other threads:[~2026-07-27 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 16:28 Yuxi Liu
2026-07-27 1:47 ` David Gibson
2026-07-27 9:55 ` Paul Holzinger
2026-07-27 16:48 ` Stefano Brivio [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260727184841.7fc3dc30@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=jmaloy@redhat.com \
--cc=passt-dev@passt.top \
--cc=pholzing@redhat.com \
--cc=yuxi_liu@berkeley.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).