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>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 12/18] conf: Don't be strict about exclusivity of forwarding mode
Date: Thu, 9 Apr 2026 18:30:39 +1000	[thread overview]
Message-ID: <addjr77665buaRDp@zatzit> (raw)
In-Reply-To: <20260409094043.16d67825@elisabeth>

[-- Attachment #1: Type: text/plain, Size: 2462 bytes --]

On Thu, Apr 09, 2026 at 09:40:44AM +0200, Stefano Brivio wrote:
> On Thu, 9 Apr 2026 10:12:07 +1000
> David Gibson <david@gibson.dropbear.id.au> wrote:
> 
> > On Wed, Apr 08, 2026 at 11:40:16PM +0200, Stefano Brivio wrote:
> > > On Tue,  7 Apr 2026 13:16:24 +1000
> > > David Gibson <david@gibson.dropbear.id.au> wrote:
> > >   
> > > > Currently as well as building the forwarding tables, conf() maintains a
> > > > "forwarding mode" value for each protocol and direction.  This prevents,
> > > > for example "-t all" and "-t 40000" being given on the same command line.
> > > > 
> > > > This restriction predates the forwarding table and is no longer really
> > > > necessary.  Remove the restriction, instead doing our best to apply all the
> > > > given options simultaneously.
> > > > 
> > > >  * Many combinations previously disallowed will still be disallowed because
> > > >    of conflicts between the specific generated rules, e.g.
> > > >         -t all -t 8888
> > > >    (because -t all already listens on port 8888)
> > > >  * Some new combinations are now allowed and will work, e.g.
> > > >         -t all -t 40000
> > > >    because 'all' excludes ephemeral ports (which includes 40000 on default
> > > >    Linux configurations).  
> > > 
> > > This is slightly confusing though:
> > > 
> > > $ ./pasta -t auto -t 31337
> > > Forwarding configuration conflict: TCP [*]:31337  =>  31337  versus TCP [*]:1-32767  =>  1-32767  (best effort) (auto-scan)  
> > 
> > You mean because the single port rule is redundant, but doesn't do
> > something different, so not strictly speaking conflicting?
> 
> Right, yes. One might want to say something like "map all ports
> automatically, but 31337 always", and that's not (much?) more
> conflicting than "-t all -t 8888"... maybe.

Yeah, maybe.  I'm inclined to leave this kind of refinement until
later, though - if people actually hit it in practice.  There's a
pretty easy workaround, since you can do:
	$ pasta -t auto,~31337 -t 31337

> > > but I don't see a practical way to "fix" it for the moment being, and
> > > overall I'd say the new behaviour is better than the original one, so I
> > > don't really care.  
> > 
> > Ok.
> 
> -- 
> 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 --]

  reply	other threads:[~2026-04-09  8:30 UTC|newest]

Thread overview: 46+ 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-09  7:40           ` Stefano Brivio
2026-04-09  8:26             ` 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-09  7:40       ` Stefano Brivio
2026-04-09  8:30         ` David Gibson [this message]
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-09  7:40       ` Stefano Brivio
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-09  2:50     ` David Gibson
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
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=addjr77665buaRDp@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).