From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v2 15/23] doc: Rework man page description of port specifiers
Date: Thu, 16 Apr 2026 11:34:10 +1000 [thread overview]
Message-ID: <aeA8kqsUbuhw4zuL@zatzit> (raw)
In-Reply-To: <20260416000437.3115b822@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 4647 bytes --]
On Thu, Apr 16, 2026 at 12:04:38AM +0200, Stefano Brivio wrote:
> On Fri, 10 Apr 2026 11:03:01 +1000
> David Gibson <david@gibson.dropbear.id.au> wrote:
>
> > Currently the man page describes the internal syntax of port specifiers
> > in prose, which isn't particularly easy to follow. Rework it to use
> > more syntax "diagrams" to show how it works. This will also allow us to
> > more easily update the manual page for some coming changes in syntax.
> >
> > usage() output is updated similarly, though more briefly.
> >
> > Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> > ---
> > conf.c | 10 +++++-----
> > passt.1 | 32 ++++++++++++++++++++++----------
> > 2 files changed, 27 insertions(+), 15 deletions(-)
> >
> > diff --git a/conf.c b/conf.c
> > index c3655824..5d6517c3 100644
> > --- a/conf.c
> > +++ b/conf.c
> > @@ -1041,11 +1041,11 @@ static void usage(const char *name, FILE *f, int status)
> > " 'none': don't forward any ports\n"
> > " 'all': forward all unbound, non-ephemeral ports\n"
> > "%s"
> > - " a comma-separated list, optionally ranged with '-'\n"
> > - " and optional target ports after ':', with optional\n"
> > - " address specification suffixed by '/' and optional\n"
> > - " interface prefixed by '%%'. Ranges can be reduced by\n"
> > - " excluding ports or ranges prefixed by '~'\n"
> > + " [ADDR[%%IFACE]/]PORTS: forward specific ports\n"
> > + " PORTS is a comma-separated list of ports, optionally\n"
> > + " ranged with '-' and optional target ports after ':'.\n"
> > + " Ranges can be reduced by excluding ports or ranges\n"
> > + " prefixed by '~'\n"
> > " Examples:\n"
> > " -t 22 Forward local port 22 to 22 on %s\n"
> > " -t 22:23 Forward local port 22 to 23 on %s\n"
> > diff --git a/passt.1 b/passt.1
> > index 7da4fe5f..d329f8f0 100644
> > --- a/passt.1
> > +++ b/passt.1
> > @@ -447,16 +447,28 @@ periodically derived (every second) from listening sockets reported by
> > \fI/proc/net/tcp\fR and \fI/proc/net/tcp6\fR, see \fBproc\fR(5).
> >
> > .TP
> > -.BR ports
> > -A comma-separated list of ports, optionally ranged with \fI-\fR, and,
> > -optionally, with target ports after \fI:\fR, if they differ. Specific addresses
> > -can be bound as well, separated by \fI/\fR, and also, since Linux 5.7, limited
> > -to specific interfaces, prefixed by \fI%\fR. Within given ranges, selected ports
> > -and ranges can be excluded by an additional specification prefixed by \fI~\fR.
> > -
> > -Specifying excluded ranges only implies that all other ports are forwarded. In
> > -this case, no failures are reported for unavailable ports, unless no ports could
> > -be forwarded at all.
> > +[\fIaddress\fR[\fB%\fR\fIinterface\fR]\fB/\fR]\fIports\fR ...
> > +Specific ports to forward. Optionally, a specific listening address
> > +and interface name (since Linux 5.7) can be specified. \fIports\fR is
> > +a comma-separated list of entries which may be any of:
> > +.RS
> > +.TP
> > +\fIfirst\fR[\fB-\fR\fIlast\fR][\fB:\fR\fItofirst\fR[\fB-\fR\fItolast\fR]]
> > +Include range. Forward port numbers between \fIfirst\fR and \fIlast\fR
> > +(inclusive) to ports between \fItofirst\fR and \fItolast\fR. If
> > +\fItofirst\fR and \fItolast\fR are omitted, assume the same as
> > +\fIfirst\fR and \fIlast\fR. If \fIlast\fR is omitted, assume the same
> > +as \fIfirst\fR.
> > +
> > +.TP
> > +\fB~\fR\fIfirst\fR[\fB-\fR\fIlast\fR]
> > +Exclude range. Exclude port numbers between \fIfirst\fR and
> > +\fIlast\fR from. This takes precedences over include ranges.
>
> ..."from the set of all non-ephemeral ports permitted by current
> capabilities"?
>
> Or simply drop " from", because it should be clear from the paragraph
> below?
Uh, yeah, not entirely sure what I was going for there. I've changed
this to
\fB~\fR\fIfirst\fR[\fB-\fR\fIlast\fR]
Exclude range. Don't forward port numbers between \fIfirst\fR and
\fIlast\fR. This takes precedences over include ranges.
>
> > +.RE
> > +
> > +Specifying excluded ranges only implies that all other non-ephemeral
> > +ports are forwarded. In this case, no failures are reported for
> > +unavailable ports, unless no ports could be forwarded at all.
> >
> > Examples:
> > .RS
>
> --
> Stefano
>
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-04-16 1:47 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 1:02 [PATCH v2 00/23] Rework forwarding option parsing David Gibson
2026-04-10 1:02 ` [PATCH v2 01/23] conf: Split parsing of port specifiers from the rest of -[tuTU] parsing David Gibson
2026-04-10 1:02 ` [PATCH v2 02/23] conf: Simplify handling of default forwarding mode David Gibson
2026-04-10 1:02 ` [PATCH v2 03/23] conf: Move first pass handling of -[TU] next to handling of -[tu] David Gibson
2026-04-10 1:02 ` [PATCH v2 04/23] doc: Consolidate -[tu] option descriptions for passt and pasta David Gibson
2026-04-10 1:02 ` [PATCH v2 05/23] conf: Permit -[tTuU] all in pasta mode David Gibson
2026-04-10 1:02 ` [PATCH v2 06/23] fwd: Better split forwarding rule specification from associated sockets David Gibson
2026-04-10 1:02 ` [PATCH v2 07/23] fwd_rule: Move forwarding rule formatting David Gibson
2026-04-10 1:02 ` [PATCH v2 08/23] conf: Pass protocol explicitly to conf_ports_range_except() David Gibson
2026-04-10 1:02 ` [PATCH v2 09/23] fwd: Split rule building from rule adding David Gibson
2026-04-10 1:02 ` [PATCH v2 10/23] fwd_rule: Move rule conflict checking from fwd_rule_add() to caller David Gibson
2026-04-15 22:04 ` Stefano Brivio
2026-04-16 1:19 ` David Gibson
2026-04-10 1:02 ` [PATCH v2 11/23] fwd: Improve error handling in fwd_rule_add() David Gibson
2026-04-15 22:04 ` Stefano Brivio
2026-04-16 1:21 ` David Gibson
2026-04-10 1:02 ` [PATCH v2 12/23] conf: Don't be strict about exclusivity of forwarding mode David Gibson
2026-04-10 1:02 ` [PATCH v2 13/23] conf: Rework stepping through chunks of port specifiers David Gibson
2026-04-10 1:03 ` [PATCH v2 14/23] conf: Rework checking for garbage after a range David Gibson
2026-04-10 1:03 ` [PATCH v2 15/23] doc: Rework man page description of port specifiers David Gibson
2026-04-15 22:04 ` Stefano Brivio
2026-04-16 1:34 ` David Gibson [this message]
2026-04-10 1:03 ` [PATCH v2 16/23] conf: Move "all" handling to port specifier David Gibson
2026-04-15 22:04 ` Stefano Brivio
2026-04-16 1:37 ` David Gibson
2026-04-10 1:03 ` [PATCH v2 17/23] conf: Allow user-specified auto-scanned port forwarding ranges David Gibson
2026-04-15 22:04 ` Stefano Brivio
2026-04-16 1:44 ` David Gibson
2026-04-10 1:03 ` [PATCH v2 18/23] conf: Move SO_BINDTODEVICE workaround to conf_ports() David Gibson
2026-04-10 1:03 ` [PATCH v2 19/23] conf: Don't pass raw commandline argument to conf_ports_spec() David Gibson
2026-04-10 1:03 ` [PATCH v2 20/23] fwd, conf: Add capabilities bits to each forwarding table David Gibson
2026-04-10 1:03 ` [PATCH v2 21/23] conf, fwd: Stricter rule checking in fwd_rule_add() David Gibson
2026-04-15 22:04 ` Stefano Brivio
2026-04-16 1:46 ` David Gibson
2026-04-10 1:03 ` [PATCH v2 22/23] fwd_rule: Move ephemeral port probing to fwd_rule.c David Gibson
2026-04-10 1:03 ` [PATCH v2 23/23] fwd, conf: Move rule parsing code to fwd_rule.[ch] David Gibson
2026-04-15 22:05 ` [PATCH v2 00/23] Rework forwarding option parsing 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=aeA8kqsUbuhw4zuL@zatzit \
--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).