public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>, passt-dev@passt.top
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 0/5] RFC: Fix bug 209
Date: Fri, 10 Jul 2026 16:56:06 +1000	[thread overview]
Message-ID: <20260710065611.530947-1-david@gibson.dropbear.id.au> (raw)

Here are a handful of changes to forwarding ant multicast handling,
that fix bug 209.  It also gets us closer to correct multicast
handling, though we're certainly not there yet - multicast things
currently only really work at all because IP_MULTICAST_ALL defaults to
on, and for the common protocols the host is likely to be already a
group member.

RFC, because a tmux change has broken the tests for me, and I wanted
to send this out before I sort out how to fix that.  I have run the
subset of tests covered by "make bats", which includes the podman
tests.

David Gibson (5):
  fwd: Clarify semantics of --host-lo-to-ns-lo
  udp: Validate that we have a unicast source address
  fwd: Rework default address logic for inbound flows
  fwd: Reorder DNAPT and SNAT steps in fwd_nat_from_host()
  fwd: Don't rewrite inbound multicast destinations

 conf.c     |  2 ++
 fwd.c      | 61 ++++++++++++++++++++++++++++++++++--------------------
 passt.1    |  9 ++++----
 udp_flow.c |  2 +-
 4 files changed, 46 insertions(+), 28 deletions(-)

-- 
2.55.0


             reply	other threads:[~2026-07-10  6:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10  6:56 David Gibson [this message]
2026-07-10  6:56 ` [PATCH 1/5] fwd: Clarify semantics of --host-lo-to-ns-lo David Gibson
2026-07-10  6:56 ` [PATCH 2/5] udp: Validate that we have a unicast source address David Gibson
2026-07-10  6:56 ` [PATCH 3/5] fwd: Rework default address logic for inbound flows David Gibson
2026-07-10  6:56 ` [PATCH 4/5] fwd: Reorder DNAPT and SNAT steps in fwd_nat_from_host() David Gibson
2026-07-10  6:56 ` [PATCH 5/5] fwd: Don't rewrite inbound multicast destinations 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=20260710065611.530947-1-david@gibson.dropbear.id.au \
    --to=david@gibson.dropbear.id.au \
    --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).