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/3] Properly preseve local addresses for UDP flows
Date: Thu, 10 Apr 2025 17:16:37 +1000 [thread overview]
Message-ID: <20250410071640.2310091-1-david@gibson.dropbear.id.au> (raw)
Add the pieces we need so that we'll reliably send replies from the
same local address that the originating datagram was delivered to.
Fixes bug 99, and will (I think) be necessary for a bunch more of the
flexible forwarding stuff we have in mind.
David Gibson (3):
udp: Use PKTINFO cmsgs to get destination address for received
datagrams
inany: Improve ASSERT message for bad socket family
udp, udp_flow: Track our specific address on socket interfaces
flow.c | 14 +++++++++++---
flow.h | 3 ++-
flow_table.h | 1 +
inany.h | 3 ++-
tcp.c | 2 +-
udp.c | 41 +++++++++++++++++++++++++++++++++++++----
udp_flow.c | 36 ++++++++++++++++++++++++++++++++----
udp_flow.h | 3 ++-
util.c | 8 ++++++--
util.h | 10 ++++++++++
10 files changed, 104 insertions(+), 17 deletions(-)
--
2.49.0
next reply other threads:[~2025-04-10 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 7:16 David Gibson [this message]
2025-04-10 7:16 ` [PATCH 1/3] udp: Use PKTINFO cmsgs to get destination address for received datagrams David Gibson
2025-04-10 7:16 ` [PATCH 2/3] inany: Improve ASSERT message for bad socket family David Gibson
2025-04-10 7:16 ` [PATCH 3/3] udp, udp_flow: Track our specific address on socket interfaces David Gibson
2025-04-11 5:03 ` [PATCH 0/3] Properly preseve local addresses for UDP flows Stefano Brivio
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=20250410071640.2310091-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).