From: Stefano Brivio <sbrivio@redhat.com>
To: Volker Diels-Grabsch <v@njh.eu>
Cc: passt-dev@passt.top, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] Send an initial ARP and NDP request to resolve the guest IP address
Date: Wed, 10 Sep 2025 16:01:55 +0200 [thread overview]
Message-ID: <20250910160155.0a11f81e@elisabeth> (raw)
In-Reply-To: <aMFUCM5Kkd1REm7J@6153f789-1cf1-4ca3-8cea-6fa7ae195a8b.njh.eu>
On Wed, 10 Sep 2025 12:33:44 +0200
Volker Diels-Grabsch <v@njh.eu> wrote:
> Dear Stefano,
>
> Thanks for your timely review. I agree with almost everything of it.
>
> Just a small clarification on this one:
>
> Stefano Brivio wrote:
> > > @@ -1503,11 +1510,12 @@ void tap_backend_init(struct ctx *c)
> > > case MODE_PASST:
> > > tap_sock_unix_init(c);
> > >
> > > - /* In passt mode, we don't know the guest's MAC address until it
> > > - * sends us packets. Use the broadcast address so that our
> > > - * first packets will reach it.
> > > + /* In passt mode, we don't know the guest's MAC address until
> > > + * it sends us packets (e.g. responds to our initial ARP or
> >
> > I don't think the response is an example, so I wouldn't use "e.g."
> > here, rather "i.e." / "that is", if that's the expected behaviour.
>
> The reason for using "e.g." is the following: There is still the
> "usual" case where the passt client (QEMU) was freshly started
> together with passt.
>
> In that case, it *will not* respond to neither our ARP nor NDP request,
> simply because it won't recognize the IPv4/6 addresses, because it
> doesn't yet have any. In that situation, we'll learn about the guest's
> MAC address only after it sends a DCHP request, or NDP, or similar to
> us, on its own initiative - not as a response to anything we might
> have sent.
>
> So I'd propose to either keep the "e.g." wording, or to extend the
> comment by enumerating all possible cases.
Ah, sorry, I see what you meant now. Of course, it makes sense.
> (Regarding the latter, I don't feel confident enough to be able to
> really enumerate them all. In addition to DCHP, NDP NS and DHCPv6, a
> sufficient strange client network stack might even broadcast nonsense
> packets to us, which we might not process further, but still learn the
> guest's MAC address from.)
I guess the version in v4 is more terse without any real loss of
generality or clarity.
--
Stefano
next prev parent reply other threads:[~2025-09-10 14:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 11:01 [PATCH] Send an initial ARP " Volker Diels-Grabsch
2025-09-08 4:00 ` David Gibson
2025-09-08 9:12 ` [PATCH v2] " Volker Diels-Grabsch
2025-09-08 9:22 ` Volker Diels-Grabsch
2025-09-09 2:52 ` David Gibson
2025-09-09 10:10 ` Volker Diels-Grabsch
2025-09-09 14:49 ` Volker Diels-Grabsch
2025-09-09 14:49 ` [PATCH] Send an initial ARP and NDP request to resolve the guest IP address Volker Diels-Grabsch
2025-09-10 3:32 ` David Gibson
2025-09-10 9:29 ` Stefano Brivio
2025-09-10 10:33 ` Volker Diels-Grabsch
2025-09-10 14:01 ` Stefano Brivio [this message]
2025-09-09 15:55 ` [PATCH v2] Send an initial ARP " Stefano Brivio
2025-09-10 3:33 ` David Gibson
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=20250910160155.0a11f81e@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=v@njh.eu \
/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).