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 v3 11/14] flow, fwd: Consult rules table when forwarding a new flow from socket
Date: Thu,  8 Jan 2026 13:29:45 +1100	[thread overview]
Message-ID: <20260108022948.2657573-12-david@gibson.dropbear.id.au> (raw)
In-Reply-To: <20260108022948.2657573-1-david@gibson.dropbear.id.au>

We now have a formal array of forwarding rules.  However, we don't actually
consult it when we forward a new flow.  Instead we rely on (a) implicit
information (we wouldn't be here if there wasn't a listening socket for the
rule) and (b) the legacy delta[] data structure.

Start addressing this, by searching for a matching forwarding rule when
attempting to forward a new flow.  For now this is incomplete:
 * We only do this for socket-initiated flows
 * We make a potentially costly linear lookup
 * We don't actually use the matching rule for anything yet

We'll address each of those in later patches.

Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
---
 flow.c | 43 ++++++++++++++++++++++++++++++++++---------
 fwd.c  | 33 +++++++++++++++++++++++++++++++++
 fwd.h  |  2 ++
 3 files changed, 69 insertions(+), 9 deletions(-)

diff --git a/flow.c b/flow.c
index 4f534865..045e9712 100644
--- a/flow.c
+++ b/flow.c
@@ -489,7 +489,7 @@ struct flowside *flow_initiate_sa(union flow *flow, uint8_t pif,
 struct flowside *flow_target(const struct ctx *c, union flow *flow,
 			     uint8_t proto)
 {
-	char estr[INANY_ADDRSTRLEN], fstr[INANY_ADDRSTRLEN];
+	char estr[INANY_ADDRSTRLEN], ostr[INANY_ADDRSTRLEN];
 	struct flow_common *f = &flow->f;
 	const struct flowside *ini = &f->side[INISIDE];
 	struct flowside *tgt = &f->side[TGTSIDE];
@@ -500,6 +500,30 @@ struct flowside *flow_target(const struct ctx *c, union flow *flow,
 	ASSERT(f->pif[INISIDE] != PIF_NONE && f->pif[TGTSIDE] == PIF_NONE);
 	ASSERT(flow->f.state == FLOW_STATE_INI);
 
+	if (pif_is_socket(f->pif[INISIDE])) {
+		const struct fwd_ports *fwd;
+
+		if (f->pif[INISIDE] == PIF_HOST && proto == IPPROTO_TCP)
+			fwd = &c->tcp.fwd_in;
+		else if (f->pif[INISIDE] == PIF_HOST && proto == IPPROTO_UDP)
+			fwd = &c->udp.fwd_in;
+		else if (f->pif[INISIDE] == PIF_SPLICE && proto == IPPROTO_TCP)
+			fwd = &c->tcp.fwd_out;
+		else if (f->pif[INISIDE] == PIF_SPLICE && proto == IPPROTO_UDP)
+			fwd = &c->udp.fwd_out;
+		else
+			goto nofwd;
+
+		if (!fwd_rule_search(fwd, ini)) {
+			/* This shouldn't happen, because if there's no rule for
+			 * it we should have no listening socket that would let
+			 * us get here
+			 */
+			flow_dbg(flow, "Unexpected missing forward rule");
+			goto nofwd;
+		}
+	}
+
 	switch (f->pif[INISIDE]) {
 	case PIF_TAP:
 		memcpy(f->tap_omac, MAC_UNDEF, ETH_ALEN);
@@ -514,22 +538,23 @@ struct flowside *flow_target(const struct ctx *c, union flow *flow,
 		tgtpif = fwd_nat_from_host(c, proto, ini, tgt);
 		fwd_neigh_mac_get(c, &tgt->oaddr, f->tap_omac);
 		break;
-
 	default:
-		flow_err(flow, "No rules to forward %s [%s]:%hu -> [%s]:%hu",
-			 pif_name(f->pif[INISIDE]),
-			 inany_ntop(&ini->eaddr, estr, sizeof(estr)),
-			 ini->eport,
-			 inany_ntop(&ini->oaddr, fstr, sizeof(fstr)),
-			 ini->oport);
+		goto nofwd;
 	}
 
 	if (tgtpif == PIF_NONE)
-		return NULL;
+		goto nofwd;
 
 	f->pif[TGTSIDE] = tgtpif;
 	flow_set_state(f, FLOW_STATE_TGT);
 	return tgt;
+
+nofwd:
+	flow_err(flow, "No rules to forward %s %s [%s]:%hu -> [%s]:%hu",
+		 pif_name(f->pif[INISIDE]), ipproto_name(proto),
+		 inany_ntop(&ini->eaddr, estr, sizeof(estr)), ini->eport,
+		 inany_ntop(&ini->oaddr, ostr, sizeof(ostr)), ini->oport);
+	return NULL;
 }
 
 /**
diff --git a/fwd.c b/fwd.c
index 3f088fd2..633ba5db 100644
--- a/fwd.c
+++ b/fwd.c
@@ -409,6 +409,39 @@ void fwd_rule_add(struct fwd_ports *fwd, uint8_t flags,
 	}
 }
 
+/**
+ * fwd_rule_match() - Does a prospective flow match a given forwarding rule
+ * @rule:	Forwarding rule
+ * @ini:	Initiating side flow information
+ *
+ * Returns: true if the rule applies to the flow, false otherwise
+ */
+static bool fwd_rule_match(const struct fwd_rule *rule,
+			   const struct flowside *ini)
+{
+	return inany_matches(&ini->oaddr, fwd_rule_addr(rule)) &&
+		ini->oport >= rule->first && ini->oport <= rule->last;
+}
+
+/**
+ * fwd_rule_search() - Find a rule which matches a prospective flow
+ * @fwd:	Forwarding table
+ * @ini:	Initiating side flow information
+ *
+ * Returns: first matching rule, or NULL if there is none
+ */
+const struct fwd_rule *fwd_rule_search(const struct fwd_ports *fwd,
+				       const struct flowside *ini)
+{
+	unsigned i;
+
+	for (i = 0; i < fwd->count; i++) {
+		if (fwd_rule_match(&fwd->rules[i], ini))
+			return &fwd->rules[i];
+	}
+	return NULL;
+}
+
 /**
  * fwd_rules_print() - Print forwarding rules for debugging
  * @fwd:	Table to print
diff --git a/fwd.h b/fwd.h
index f84e7c01..a10bdbb4 100644
--- a/fwd.h
+++ b/fwd.h
@@ -103,6 +103,8 @@ struct fwd_ports {
 void fwd_rule_add(struct fwd_ports *fwd, uint8_t flags,
 		  const union inany_addr *addr, const char *ifname,
 		  in_port_t first, in_port_t last, in_port_t to);
+const struct fwd_rule *fwd_rule_search(const struct fwd_ports *fwd,
+				       const struct flowside *ini);
 void fwd_rules_print(const struct fwd_ports *fwd);
 
 void fwd_scan_ports_init(struct ctx *c);
-- 
2.52.0


  parent reply	other threads:[~2026-01-08  2:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08  2:29 [PATCH v3 00/14] Introduce forwarding table David Gibson
2026-01-08  2:29 ` [PATCH v3 01/14] inany: Extend inany_ntop() to treat NULL as a fully unspecified address David Gibson
2026-01-08 13:16   ` Laurent Vivier
2026-01-08  2:29 ` [PATCH v3 02/14] conf, fwd: Keep a table of our port forwarding configuration David Gibson
2026-01-08  2:29 ` [PATCH v3 03/14] conf: Accurately record ifname and address for outbound forwards David Gibson
2026-01-08  2:29 ` [PATCH v3 04/14] conf, fwd: Record "auto" port forwards in forwarding table David Gibson
2026-01-08  2:29 ` [PATCH v3 05/14] fwd: Make space to store listening sockets in forward table David Gibson
2026-01-08  2:29 ` [PATCH v3 06/14] ip: Add ipproto_name() function David Gibson
2026-01-08 13:22   ` Laurent Vivier
2026-01-08 23:12     ` David Gibson
2026-01-08  2:29 ` [PATCH v3 07/14] fwd, tcp, udp: Set up listening sockets based on forward table David Gibson
2026-01-08  2:29 ` [PATCH v3 08/14] tcp, udp: Remove old auto-forwarding socket arrays David Gibson
2026-01-08  2:29 ` [PATCH v3 09/14] conf, fwd: Check forwarding table for conflicting rules David Gibson
2026-01-08  2:29 ` [PATCH v3 10/14] fwd: Generate auto-forward exclusions from socket fd tables David Gibson
2026-01-08  2:29 ` David Gibson [this message]
2026-01-08  2:29 ` [PATCH v3 12/14] fwd: Remap ports based directly on forwarding rule David Gibson
2026-01-08  2:29 ` [PATCH v3 13/14] fwd, tcp, udp: Add forwarding rule to listening socket epoll references David Gibson
2026-01-08  2:29 ` [PATCH v3 14/14] flow, fwd: Optimise forwarding rule lookup using epoll ref when possible 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=20260108022948.2657573-12-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).