From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 16/18] conf: Allow user-specified auto-scanned port forwarding ranges
Date: Wed, 08 Apr 2026 23:40:42 +0200 (CEST) [thread overview]
Message-ID: <20260408234041.636a01af@elisabeth> (raw)
In-Reply-To: <20260407031630.2457081-17-david@gibson.dropbear.id.au>
On Tue, 7 Apr 2026 13:16:28 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:
> The forwarding table now allows for arbitrary port ranges to be marked as
> FWD_SCAN, meaning we don't open sockets for every port, but only those we
> scan as listening on the target side. However, there's currently no way
> to create such rules, except -[tTuU] auto which always scans every port
> with an unspecified listening address and interface.
>
> Allow user-specified "auto" ranges by moving the parsing of the "auto"
> keyword from conf_ports(), to conf_ports_spec() as part of the port
> specified. "auto" can be combined freely with other port ranges, e.g.
> -t 127.0.0.1/auto
> -u %lo/5000-7000,auto
> -T auto,12345
> -U auto,~1-9000
>
> Note that any address and interface given only affects where the automatic
> forwards listen, not what addresses we consider when scanning. That is,
> if the target side is listening on *any* address, we will create a forward
> on the specified address.
>
> Link: https://bugs.passt.top/show_bug.cgi?id=180
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> conf.c | 66 ++++++++++++++++++++++++++++++++++++++++++----------------
> 1 file changed, 48 insertions(+), 18 deletions(-)
>
> diff --git a/conf.c b/conf.c
> index fcc75d25..86c30c7f 100644
> --- a/conf.c
> +++ b/conf.c
> @@ -13,6 +13,7 @@
> */
>
> #include <arpa/inet.h>
> +#include <ctype.h>
> #include <errno.h>
> #include <fcntl.h>
> #include <getopt.h>
> @@ -112,6 +113,28 @@ static int parse_port_range(const char *s, const char **endptr,
> return 0;
> }
>
> +/**
> + * parse_keyword() - Parse a literal keyword
Here, "parse" sounds overly generic. If I understand this correctly,
it's a strstr() / memmem() implementation with the added 'endptr'
functionality, so maybe... "Find the end of a substring"?
> + * @s: String to parse
> + * @endptr: Update to the character after the keyword
> + * @kw: Keyword to accept
> + *
> + * Return: 0, if @s starts with @kw, -EINVAL if it does not
> + */
> +static int parse_keyword(const char *s, const char **endptr, const char *kw)
> +{
> + size_t len = strlen(kw);
> +
> + if (strlen(s) < len)
> + return -EINVAL;
> +
> + if (memcmp(s, kw, len))
> + return -EINVAL;
> +
> + *endptr = s + len;
> + return 0;
> +}
> +
> /**
> * conf_ports_range_except() - Set up forwarding for a range of ports minus a
> * bitmap of exclusions
> @@ -249,6 +272,7 @@ static void conf_ports_spec(const struct ctx *c,
> uint8_t exclude[PORT_BITMAP_SIZE] = { 0 };
> bool exclude_only = true;
> const char *p, *ep;
> + uint8_t flags = 0;
> unsigned i;
>
> if (!strcmp(spec, "all")) {
> @@ -256,15 +280,32 @@ static void conf_ports_spec(const struct ctx *c,
> spec = "";
> }
>
> - /* Mark all exclusions first, they might be given after base ranges */
> + /* Parse excluded ranges and "auto" in the first pass */
> for_each_chunk(p, ep, spec, ",") {
> struct port_range xrange;
>
> - if (*p != '~') {
> - /* Not an exclude range, parse later */
> + if (isdigit(*p)) {
> + /* Include range, parse later */
> exclude_only = false;
> continue;
> }
> +
> + if (parse_keyword(p, &p, "auto") == 0) {
> + if (p != ep) /* Garbage after the keyword */
> + goto bad;
> +
> + if (c->mode != MODE_PASTA) {
> + die(
> +"'auto' port forwarding is only allowed for pasta");
> + }
> +
> + flags |= FWD_SCAN;
> + continue;
> + }
> +
> + /* Should be an exclude range */
> + if (*p != '~')
> + goto bad;
> p++;
>
> if (parse_port_range(p, &p, &xrange))
> @@ -283,7 +324,7 @@ static void conf_ports_spec(const struct ctx *c,
> conf_ports_range_except(c, optname, optarg, fwd,
> proto, addr, ifname,
> 1, NUM_PORTS - 1, exclude,
> - 1, FWD_WEAK);
> + 1, flags | FWD_WEAK);
> return;
> }
>
> @@ -291,8 +332,8 @@ static void conf_ports_spec(const struct ctx *c,
> for_each_chunk(p, ep, spec, ",") {
> struct port_range orig_range, mapped_range;
>
> - if (*p == '~')
> - /* Exclude range, already parsed */
> + if (!isdigit(*p))
> + /* Already parsed */
> continue;
>
> if (parse_port_range(p, &p, &orig_range))
> @@ -320,7 +361,7 @@ static void conf_ports_spec(const struct ctx *c,
> proto, addr, ifname,
> orig_range.first, orig_range.last,
> exclude,
> - mapped_range.first, 0);
> + mapped_range.first, flags);
> }
>
> return;
> @@ -366,17 +407,6 @@ static void conf_ports(const struct ctx *c, char optname, const char *optarg,
> if (proto == IPPROTO_UDP && c->no_udp)
> die("UDP port forwarding requested but UDP is disabled");
>
> - if (!strcmp(optarg, "auto")) {
> - if (c->mode != MODE_PASTA)
> - die("'auto' port forwarding is only allowed for pasta");
> -
> - conf_ports_range_except(c, optname, optarg, fwd,
> - proto, NULL, NULL,
> - 1, NUM_PORTS - 1, NULL, 1, FWD_SCAN);
> -
> - return;
> - }
> -
> strncpy(buf, optarg, sizeof(buf) - 1);
>
> if ((spec = strchr(buf, '/'))) {
The rest of the series looks good to me!
--
Stefano
next prev parent reply other threads:[~2026-04-08 21:40 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 3:16 [PATCH 00/18] Rework forwarding option parsing David Gibson
2026-04-07 3:16 ` [PATCH 01/18] conf: Split parsing of port specifiers from the rest of -[tuTU] parsing David Gibson
2026-04-07 3:16 ` [PATCH 02/18] conf: Simplify handling of default forwarding mode David Gibson
2026-04-07 23:14 ` Stefano Brivio
2026-04-08 1:10 ` David Gibson
2026-04-07 3:16 ` [PATCH 03/18] conf: Move first pass handling of -[TU] next to handling of -[tu] David Gibson
2026-04-07 3:16 ` [PATCH 04/18] doc: Consolidate -[tu] option descriptions for passt and pasta David Gibson
2026-04-07 23:14 ` Stefano Brivio
2026-04-08 1:23 ` David Gibson
2026-04-07 3:16 ` [PATCH 05/18] conf: Permit -[tTuU] all in pasta mode David Gibson
2026-04-07 3:16 ` [PATCH 06/18] fwd: Better split forwarding rule specification from associated sockets David Gibson
2026-04-07 23:14 ` Stefano Brivio
2026-04-08 1:30 ` David Gibson
2026-04-08 21:39 ` Stefano Brivio
2026-04-09 0:47 ` David Gibson
2026-04-07 3:16 ` [PATCH 07/18] fwd_rule: Move forwarding rule formatting David Gibson
2026-04-07 3:16 ` [PATCH 08/18] conf: Pass protocol explicitly to conf_ports_range_except() David Gibson
2026-04-07 3:16 ` [PATCH 09/18] fwd: Split rule building from rule adding David Gibson
2026-04-07 3:16 ` [PATCH 10/18] fwd_rule: Move rule conflict checking from fwd_rule_add() to caller David Gibson
2026-04-07 23:14 ` Stefano Brivio
2026-04-08 1:37 ` David Gibson
2026-04-08 4:42 ` David Gibson
2026-04-07 3:16 ` [PATCH 11/18] fwd: Improve error handling in fwd_rule_add() David Gibson
2026-04-08 21:40 ` Stefano Brivio
2026-04-09 0:10 ` David Gibson
2026-04-07 3:16 ` [PATCH 12/18] conf: Don't be strict about exclusivity of forwarding mode David Gibson
2026-04-08 21:40 ` Stefano Brivio
2026-04-09 0:12 ` David Gibson
2026-04-07 3:16 ` [PATCH 13/18] conf: Rework stepping through chunks of port specifiers David Gibson
2026-04-08 21:40 ` Stefano Brivio
2026-04-09 0:13 ` David Gibson
2026-04-07 3:16 ` [PATCH 14/18] conf: Rework checking for garbage after a range David Gibson
2026-04-08 21:40 ` Stefano Brivio
2026-04-09 0:15 ` David Gibson
2026-04-07 3:16 ` [PATCH 15/18] conf: Move "all" handling to port specifier David Gibson
2026-04-08 21:40 ` Stefano Brivio
2026-04-07 3:16 ` [PATCH 16/18] conf: Allow user-specified auto-scanned port forwarding ranges David Gibson
2026-04-08 21:40 ` Stefano Brivio [this message]
2026-04-07 3:16 ` [PATCH 17/18] conf: Move SO_BINDTODEVICE workaround to conf_ports() David Gibson
2026-04-07 3:16 ` [PATCH 18/18] conf: Don't pass raw commandline argument to conf_ports_spec() 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=20260408234041.636a01af@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--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).