From: Jon Maloy <jmaloy@redhat.com>
To: passt-dev@passt.top, sbrivio@redhat.com, lvivier@redhat.com,
dgibson@redhat.com, jmaloy@redhat.com
Subject: [PATCH v6 0/4] Reconstruct ICMP headers for failed UDP connect
Date: Mon, 24 Feb 2025 14:24:43 -0500 [thread overview]
Message-ID: <20250224192447.3758771-1-jmaloy@redhat.com> (raw)
Reconstruct incoming ICMP headers for failed UDP connect and forward back
to local peer.
v2: - Added patch breaking out udp header creation from function
tap_udp4_send().
- Updated the ICMP creation by using the new function.
- Added logics to find correct flow, depending on origin.
- All done after feedback from David Gibson.
v3: - More changes after feedback from David Gibson.
v4: - Even more changes after feedback from D. Gibson
v5: - Added corresponding patches for IPv6
v6: - Fixed some small nits after comments from D. Gibson.
Jon Maloy (4):
tap: break out building of udp header from tap_udp4_send function
udp: create and send ICMPv4 to local peer when applicable
tap: break out building of udp header from tap_udp6_send function
udp: create and send ICMPv6 to local peer when applicable
tap.c | 86 +++++++++++++++++++++++++----------
tap.h | 15 ++++++
udp.c | 121 ++++++++++++++++++++++++++++++++++++++++++++-----
udp_internal.h | 2 +-
udp_vu.c | 4 +-
5 files changed, 189 insertions(+), 39 deletions(-)
--
2.48.1
next reply other threads:[~2025-02-24 19:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 19:24 Jon Maloy [this message]
2025-02-24 19:24 ` [PATCH v6 1/4] tap: break out building of udp header from tap_udp4_send function Jon Maloy
2025-02-24 19:24 ` [PATCH v6 2/4] udp: create and send ICMPv4 to local peer when applicable Jon Maloy
2025-02-24 19:24 ` [PATCH v6 3/4] tap: break out building of udp header from tap_udp6_send function Jon Maloy
2025-02-24 19:24 ` [PATCH v6 4/4] udp: create and send ICMPv6 to local peer when applicable Jon Maloy
2025-02-25 14:19 ` Stefano Brivio
2025-02-26 20:28 ` Jon Maloy
2025-02-26 20:36 ` 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=20250224192447.3758771-1-jmaloy@redhat.com \
--to=jmaloy@redhat.com \
--cc=dgibson@redhat.com \
--cc=lvivier@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).