From: David Gibson <david@gibson.dropbear.id.au>
To: Jon Maloy <jmaloy@redhat.com>
Cc: sbrivio@redhat.com, dgibson@redhat.com, passt-dev@passt.top
Subject: Re: [PATCH v9 9/9] arp/ndp: send gratuitous ARP / unsolicitated NA when MAC cache entry added
Date: Mon, 29 Sep 2025 14:04:02 +1000 [thread overview]
Message-ID: <aNoFMp0SqkCKhw01@zatzit> (raw)
In-Reply-To: <68dc6be3-9dad-422f-8c4f-ab5bdb580b5b@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2316 bytes --]
On Fri, Sep 26, 2025 at 07:05:56PM -0400, Jon Maloy wrote:
>
>
> On 2025-09-25 20:55, David Gibson wrote:
> > On Thu, Sep 25, 2025 at 09:14:42AM -0400, Jon Maloy wrote:
> > >
> > >
> > > On 2025-09-25 02:36, David Gibson wrote:
> > > > On Wed, Sep 24, 2025 at 06:18:52PM -0400, Jon Maloy wrote:
> > > > >
> > > [...]
> > > > >
> > > > > I experimented a bit with this. My test program is a simple UDP
> > > > > client-server pair, exchanging first 3 UDP messages client->server, followed
> > > > > by
> > > > > 3 messages server->client.
> > > >
> > > > With the client on the guest, and server outside? How is the outside
> > > > machine arranged - is it a physically separate host? A bridged VM or
> > > > container on the same host? Something else?
> > >
> > > It is a physically separate host.
> > >
> > > >
> > > > > First, I changed the main() loop a bit, so that netlink events are
> > > > > handled before all other events, if any. (Basically, I added
> > > > > an extra loop before the main loop, only handling netlink events, before
> > > > > moving on to the main loop (where netlink events had been excluded.)
> > > > > This should secure absolute priority of netlink events before any other
> > > > > events. As you will see below, this made no difference to the scenarios
> > > > > I describe.
> > > >
> > > > Drat.
> > > > > 1: When starting the container, I notice that there is no subscription
> > > > > event in PASTA, even though I can see the entry for the remote host
> > > > > is present in the host's ARP table. There is never any event coming
> > > > > up even if I wait for 10+ minutes.
> > > >
> > > > Huh.... do we need to do something to ensure we get events for
> > > > existing entries in the host ARP table, not just ones that are added
> > > > or updated after we're running?
> > >
> > > It doesn't seem to be possible,
>
> It actually *is* possible, and I just implemented it. It doesn't solve all
> problems, but makes a huge difference. I will add it in v10.
Hooray! I thought there ought to be a way.
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-09-29 4:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 1:13 [PATCH v9 0/9] Use true MAC address of LAN local remote hosts Jon Maloy
2025-09-24 1:13 ` [PATCH v9 1/9] netlink: add subsciption on changes in NDP/ARP table Jon Maloy
2025-09-24 2:47 ` David Gibson
2025-09-24 3:34 ` David Gibson
2025-09-24 18:40 ` Jon Maloy
2025-09-25 6:42 ` David Gibson
2025-09-24 1:13 ` [PATCH v9 2/9] fwd: Add cache table for ARP/NDP contents Jon Maloy
2025-09-24 3:03 ` David Gibson
2025-09-24 18:54 ` Jon Maloy
2025-09-24 1:13 ` [PATCH v9 3/9] arp/ndp: respond with true MAC address of LAN local remote hosts Jon Maloy
2025-09-24 1:13 ` [PATCH v9 4/9] flow: add MAC address of LAN local remote hosts to flow Jon Maloy
2025-09-24 1:13 ` [PATCH v9 5/9] udp: forward external source MAC address through tap interface Jon Maloy
2025-09-24 1:13 ` [PATCH v9 6/9] tcp: " Jon Maloy
2025-09-24 1:13 ` [PATCH v9 7/9] tap: change signature of function tap_push_l2h() Jon Maloy
2025-09-24 1:13 ` [PATCH v9 8/9] icmp: let icmp use mac address from flowside structure Jon Maloy
2025-09-24 1:13 ` [PATCH v9 9/9] arp/ndp: send gratuitous ARP / unsolicitated NA when MAC cache entry added Jon Maloy
2025-09-24 3:22 ` David Gibson
2025-09-24 22:18 ` Jon Maloy
2025-09-24 23:32 ` Jon Maloy
2025-09-25 6:38 ` David Gibson
2025-09-25 12:48 ` Jon Maloy
2025-09-26 0:47 ` David Gibson
2025-09-26 22:59 ` Jon Maloy
2025-09-29 4:03 ` David Gibson
2025-09-25 6:36 ` David Gibson
2025-09-25 13:14 ` Jon Maloy
2025-09-26 0:55 ` David Gibson
2025-09-26 23:05 ` Jon Maloy
2025-09-29 4:04 ` David Gibson [this message]
2025-09-26 23:25 ` Jon Maloy
2025-09-27 19:32 ` Jon Maloy
2025-09-29 4:08 ` David Gibson
2025-09-29 22:23 ` Stefano Brivio
2025-09-30 0:15 ` 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=aNoFMp0SqkCKhw01@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=dgibson@redhat.com \
--cc=jmaloy@redhat.com \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.com \
/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).