Re: Thoughts on interface modes / multiple guest addresses

On Wed, 17 Dec 2025 13:01:36 +1100 David Gibson wrote:

On Wed, Dec 17, 2025 at 01:29:36AM +0100, Stefano Brivio wrote:

...

On Tue, 16 Dec 2025 16:53:49 +1100 David Gibson wrote:

...

Hi Jon,

As discussed on the call yesterday, I've written up my thoughts on what a bunch of the address semantics should be. Turns out I'd already done some of this at: https://pad.passt.top/p/InterfaceMode

Two general comments:

1. local mode is already implemented, and some things such as the interface name ("tap0") are already defined, see man page and 'pasta -- pasta --config-net ip a'

Yes, I'm aware. The two modes have the "normal" and "local" local to indicate the existing modes they're more similar to (neither is identical to current behaviour). Another point I left out is that this is intended as an endpoint to aim at. Getting there I expect to involve extra stuff for compatiblity along the way.

...

2. I think it's more relevant to define the basics of how one switches between the existing local mode and a mode where we copy addresses and routes (as they become available on the host), rather than defining every single detail of these modes.

Oh.. right. I guess I did't make this clear: these are modes set by the command line (details TBD), we never switch between them at runtime. They kind of have to be, because which mode we're in affects how we respond to runtime changes.

...

In these terms, I think it would actually be helpful to *avoid* seeing them as separate modes. If there's no host connectivity, we'll start in local mode, and switch to the other mode as we get addresses and routes configured... just to switch back to the previous mode if we lose them.

The whole point of all-interface mode (better name suggestions welcome) is that the guest's routing configuration *doesn't* change, even if the host's does.

If that's what you mean, I think we're talking about two rather different things. At the moment, local mode is used if a given IP version doesn't have a configured address on the host, in that specific moment. This is what the netlink monitor needs to make independent of the timing. But if the user wants to specify addresses, or routes, we certainly don't want to override them. So we would rather have an "override" or "manual" mode (same as we already have now) as opposed to a "template" or "automatic" mode where we copy (at runtime, with a monitor) addresses and routes. It's actually rather simple to implement a netlink monitor on top of this, and that's for sure what we need to implement because it's rather broken in Podman and rootlesskit and it has been for a while. I think that's the priority and what Jon was about to do rather than spending now months to revise addressing and all possible defaults and command line options. I mean, feel free to do that of course but I think it needs to be implemented in parallel at that point.

Advantages: * The host can have whatever source-dependent, multi-path, bizarro routing configuration, changing as often as it likes and we (and the guest) don't care. Guest routes to the host, host routes onward from there. * We have a consistent (link local) way of addressing the host regardless of what changes happen on the host side * We have the freedom to allocate link-local addresses if we want them for any purpose Disadvantages: * No access to external peers via link-local address * Guest's routing setup is visibly different from the host's (so less L3 transparent)

I actually think that's a more useful and robust way of operating for most use cases and we should eventually make it the default.

Making things look like they're on the host is a very fundamental feature that many users appreciate and use. I haven't reviewed the rest in detail but forcing users to specify a new option to go back to a convenient default they had for years now doesn't sound like a good idea.

One-interface mode is for the use cases where those disadvantages are fatal.

There is another possible option here: present multiple interfaces in the guest, one for each host interface. I'm not including it, since it's basically equivalent to having multiple pasta instances in one-interface mode. To implement this, we'd basically have to implement one-interface mode first.

...

So does it really help to have "modes" instead of just considering what addresses and routes are we going to delete, and when? Because that's what we'll need to do anyway (and that's what I think defines the design).

I haven't seen a way to define coherent semantics that cover all the use cases without introducing two modes. The overlapping constraints here are:

The two modes could be what we roughly have now: -a / -g imply that we don't copy addresses / routes, and we don't source them for DHCP / SLAAC / DHCPv6 either. The netlink monitor could simply be enabled when the user doesn't override things.

* With passt or !--config-net, we can't fully control the guest's networking config. We both can't set things with arbitrary precision, and we don't have a way of forcing an update when things change.

What is the problem with that? Nobody reported any issue with it. It's actually expected.

* If we're dealing with multiple host interfaces - either concurrently or to a lesser extent over time, then there's no way to coherently map host-side link-local addresses to the guest.

Also never reported as an issue as far as I know.

...

I see that this is not an explicit use case in Jon's list (which I still have to review), but it's one of the most two fundamental ones I think (that, and Podman Quadlets), also nicely described by a user at:

https://github.com/containers/podman/discussions/22737#discussioncomment-947...

Ah, yes, that is another case. I think it would work out equivalent to one-interface mode attached to a dummy0 interface on the host. So, it should be fairly easy to implement in terms of one-interface mode, just pretending a dummy0 existed even if it doesn't.

That's pretty much the most important / most frequently reported case, not just another case. But anyway, there's no need for dummy0 or suchlike, we can just keep what we use as "local mode" (which wouldn't be a mode anymore, rather a temporary state). -- Stefano