public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Laine Stump <laine@redhat.com>
To: passt-dev@passt.top
Subject: [PATCH] Correct port ranges in --tcp-ports examples
Date: Fri,  6 Jan 2023 15:08:36 -0500	[thread overview]
Message-ID: <20230106200836.117368-1-laine@redhat.com> (raw)

The proper syntax is:

   ${start}-${end}:${dststart}-${dstend}

not

   ${start}-${end}-${dststart}:${dstend}

Signed-off-by: Laine Stump <laine@redhat.com>
---
 passt.1 | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/passt.1 b/passt.1
index 528763b..0dad878 100644
--- a/passt.1
+++ b/passt.1
@@ -349,7 +349,7 @@ Forward local ports 22 and 25 to ports 22 and 25 on the guest
 -t 22-80
 Forward local ports 22 to 80 to corresponding ports on the guest
 .TP
--t 22-80-32:90
+-t 22-80:32-90
 Forward local ports 22 to 80 to corresponding ports on the guest plus 10
 .TP
 -t 192.0.2.1/22
@@ -361,7 +361,7 @@ Forward local port 22, bound to 192.0.2.1 and interface eth0, to port 22
 -t 2000-5000,~3000-3010
 Forward local ports 2000 to 5000, but not 3000 to 3010
 .TP
--t 192.0.2.1/20-30,~25
+-t 192.0.2.1/20-26:24-30,~25-29
 Forward local ports 20 to 24, and 26 to 30, bound to 192.0.2.1
 .TP
 -t ~20000-20010
@@ -427,7 +427,7 @@ Forward local ports 22 and 25 to ports 22 and 25 in the target namespace
 -t 22-80
 Forward local ports 22 to 80 to corresponding ports in the target namespace
 .TP
--t 22-80-32:90
+-t 22-80:32-90
 Forward local ports 22 to 80 to corresponding ports plus 10 in the target
 namespace
 .TP
@@ -440,7 +440,7 @@ Forward local port 22, bound to 192.0.2.1 and interface eth0, to port 22
 -t 2000-5000,~3000-3010
 Forward local ports 2000 to 5000, but not 3000 to 3010
 .TP
--t 192.0.2.1/20-30,~25
+-t 192.0.2.1/20-26:24-30,~25-29
 Forward local ports 20 to 24, and 26 to 30, bound to 192.0.2.1
 .TP
 -t ~20000-20010
-- 
@@ -349,7 +349,7 @@ Forward local ports 22 and 25 to ports 22 and 25 on the guest
 -t 22-80
 Forward local ports 22 to 80 to corresponding ports on the guest
 .TP
--t 22-80-32:90
+-t 22-80:32-90
 Forward local ports 22 to 80 to corresponding ports on the guest plus 10
 .TP
 -t 192.0.2.1/22
@@ -361,7 +361,7 @@ Forward local port 22, bound to 192.0.2.1 and interface eth0, to port 22
 -t 2000-5000,~3000-3010
 Forward local ports 2000 to 5000, but not 3000 to 3010
 .TP
--t 192.0.2.1/20-30,~25
+-t 192.0.2.1/20-26:24-30,~25-29
 Forward local ports 20 to 24, and 26 to 30, bound to 192.0.2.1
 .TP
 -t ~20000-20010
@@ -427,7 +427,7 @@ Forward local ports 22 and 25 to ports 22 and 25 in the target namespace
 -t 22-80
 Forward local ports 22 to 80 to corresponding ports in the target namespace
 .TP
--t 22-80-32:90
+-t 22-80:32-90
 Forward local ports 22 to 80 to corresponding ports plus 10 in the target
 namespace
 .TP
@@ -440,7 +440,7 @@ Forward local port 22, bound to 192.0.2.1 and interface eth0, to port 22
 -t 2000-5000,~3000-3010
 Forward local ports 2000 to 5000, but not 3000 to 3010
 .TP
--t 192.0.2.1/20-30,~25
+-t 192.0.2.1/20-26:24-30,~25-29
 Forward local ports 20 to 24, and 26 to 30, bound to 192.0.2.1
 .TP
 -t ~20000-20010
-- 
2.38.1


             reply	other threads:[~2023-01-06 20:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06 20:08 Laine Stump [this message]
2023-01-09  2:33 ` [PATCH] Correct port ranges in --tcp-ports examples 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=20230106200836.117368-1-laine@redhat.com \
    --to=laine@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).