public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Jon Maloy <jmaloy@redhat.com>, passt-dev@passt.top
Subject: Re: Thoughts on interface modes / multiple guest addresses
Date: Thu, 18 Dec 2025 06:32:49 +0100	[thread overview]
Message-ID: <20251218063249.095e7614@elisabeth> (raw)
In-Reply-To: <aUN5OrwgRQ_3dHj5@zatzit>

On Thu, 18 Dec 2025 14:47:06 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:

> For multi-address support there are at least four things to consider:

For the bits related https://bugs.passt.top/show_bug.cgi?id=141, I
thought Jon was working on a proposal.

> (a) What goes in our internal list of addresses to give the guest?
> 
>     a.1. Everything listed with -a?

If anything is passed, yes, those, and just those (separately for IP
version), because the user is clearly overriding addresses (as
currently implemented and documented).

>     a.2. Everything on the host?

No, because you can't assume you can configure all those addresses on
a single interface. Adding multiple interfaces is something we could
consider later.

>     a.3. Everything on the host template interface?

Everything on the host template interface if available (as currently
documented).

>     a.4. A link local address we pick?

A link-local address if nothing else is available (as currently
documented). This will need to be permanent for the requirement we
already discussed months ago with Podman developers.

>     a.5. Some combination of the above.
> 
> Unlike routes (that I can see), I'm pretty sure there are use cases
> where we want both host-copied addresses (for transparency) and
> explicit addresses (for a stable way of communicating with the host).

Podman needs some anyway if we start with link-local addresses, to
keep DNS resolution working.

The rest just looks beyond the scope of
https://bugs.passt.top/show_bug.cgi?id=141 to me. I won't stand in the
way of this discussion, of course, but I won't participate either,
because I really don't see it as a priority at the moment.

-- 
Stefano


      reply	other threads:[~2025-12-18  5:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-16  5:53 David Gibson
2025-12-17  0:29 ` Stefano Brivio
2025-12-17  2:01   ` David Gibson
2025-12-17  5:00     ` David Gibson
2025-12-17 23:03       ` Stefano Brivio
2025-12-17 23:52         ` David Gibson
2025-12-17 20:01     ` Jon Maloy
2025-12-18  0:14       ` David Gibson
2025-12-17 23:22     ` Stefano Brivio
2025-12-18  3:47       ` David Gibson
2025-12-18  5:32         ` 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=20251218063249.095e7614@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=jmaloy@redhat.com \
    --cc=passt-dev@passt.top \
    /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).