From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top, jmaloy@redhat.com
Subject: Re: [PATCH v8 00/27] Unified flow table
Date: Fri, 19 Jul 2024 21:20:27 +0200 [thread overview]
Message-ID: <20240719212028.1e5bfdcc@elisabeth> (raw)
In-Reply-To: <20240718052653.3241585-1-david@gibson.dropbear.id.au>
On Thu, 18 Jul 2024 15:26:26 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:
> This is the seventh draft of an implementation of more general
> "connection" tracking, as described at:
> https://pad.passt.top/p/NewForwardingModel
>
> This series changes the TCP connection table and hash table into a
> more general flow table that can track other protocols as well. Each
> flow uniformly keeps track of all the relevant addresses and ports,
> which will allow for more robust control of NAT and port forwarding.
>
> ICMP and UDP are converted to use the new flow table.
>
> This is based on the recent series of UDP flow table preliminaries.
>
> Caveats:
> * We roughly double the size of a connection/flow entry
> * We don't yet record the local address of flows initiated from a
> socket, even in cases where it's bound to a specific address.
>
> Changes since v7:
> * Rebase
> * Fix unintended regression in forwarding logic (we weren't applying
> map_gw logic to DNS packets, if they didn't hit explicit DNS
> forwarding rules).
> * Remove return value from pif_sockaddr(), in turned out not to be
> very useful.
> * More robust discarding of datagrams received between bind() and
> connect() on UDP reply sockets.
> * Avoid the name 'fside' for variables which was confusing in some
> contexts
> * Assorted minor changes based on feedback.
Applied (!)
--
Stefano
next prev parent reply other threads:[~2024-07-19 19:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 5:26 [PATCH v8 00/27] Unified flow table David Gibson
2024-07-18 5:26 ` [PATCH v8 01/27] flow: Common address information for initiating side David Gibson
2024-07-18 5:26 ` [PATCH v8 02/27] flow: Common address information for target side David Gibson
2024-07-18 5:26 ` [PATCH v8 03/27] tcp, flow: Remove redundant information, repack connection structures David Gibson
2024-07-18 5:26 ` [PATCH v8 04/27] tcp: Obtain guest address from flowside David Gibson
2024-07-18 5:26 ` [PATCH v8 05/27] tcp: Manage outbound address via flow table David Gibson
2024-07-18 5:26 ` [PATCH v8 06/27] tcp: Simplify endpoint validation using flowside information David Gibson
2024-07-18 5:26 ` [PATCH v8 07/27] tcp_splice: Eliminate SPLICE_V6 flag David Gibson
2024-07-18 5:26 ` [PATCH v8 08/27] tcp, flow: Replace TCP specific hash function with general flow hash David Gibson
2024-07-18 5:26 ` [PATCH v8 09/27] flow, tcp: Generalise TCP hash table to general flow hash table David Gibson
2024-07-18 5:26 ` [PATCH v8 10/27] tcp: Re-use flow hash for initial sequence number generation David Gibson
2024-07-18 5:26 ` [PATCH v8 11/27] icmp: Remove redundant id field from flow table entry David Gibson
2024-07-18 5:26 ` [PATCH v8 12/27] icmp: Obtain destination addresses from the flowsides David Gibson
2024-07-18 5:26 ` [PATCH v8 13/27] icmp: Look up ping flows using flow hash David Gibson
2024-07-18 5:26 ` [PATCH v8 14/27] icmp: Eliminate icmp_id_map David Gibson
2024-07-18 5:26 ` [PATCH v8 15/27] flow: Helper to create sockets based on flowside David Gibson
2024-07-18 5:26 ` [PATCH v8 16/27] icmp: Manage outbound socket address via flow table David Gibson
2024-07-18 5:26 ` [PATCH v8 17/27] flow, tcp: Flow based NAT and port forwarding for TCP David Gibson
2024-07-18 5:26 ` [PATCH v8 18/27] flow, icmp: Use general flow forwarding rules for ICMP David Gibson
2024-07-18 5:26 ` [PATCH v8 19/27] fwd: Update flow forwarding logic for UDP David Gibson
2024-07-18 5:26 ` [PATCH v8 20/27] udp: Create flows for datagrams from originating sockets David Gibson
2024-07-18 5:26 ` [PATCH v8 21/27] udp: Handle "spliced" datagrams with per-flow sockets David Gibson
2024-07-18 5:26 ` [PATCH v8 22/27] udp: Remove obsolete splice tracking David Gibson
2024-07-18 5:26 ` [PATCH v8 23/27] udp: Find or create flows for datagrams from tap interface David Gibson
2024-07-18 5:26 ` [PATCH v8 24/27] udp: Direct datagrams from host to guest via flow table David Gibson
2024-07-18 5:26 ` [PATCH v8 25/27] udp: Remove obsolete socket tracking David Gibson
2024-07-18 5:26 ` [PATCH v8 26/27] udp: Remove rdelta port forwarding maps David Gibson
2024-07-18 5:26 ` [PATCH v8 27/27] udp: Rename UDP listening sockets David Gibson
2024-07-19 19:20 ` Stefano Brivio [this message]
2024-07-20 3:37 ` [PATCH v8 00/27] Unified flow table 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=20240719212028.1e5bfdcc@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=jmaloy@redhat.com \
--cc=passt-dev@passt.top \
/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).