Invalid pasta port specifier? #25748
-
To quote the pasta(1) manual:
And then, lower down:
So this, as far as I can tell, should be valid:
Is this a bug? I thought I'd check before opening a ticket. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Oops, yes, it's a documentation bug I indirectly introduced in https://passt.top/passt/commit/?id=3c6ae625101aee6ddf94e0fd85ce3a9c9067c3bf.
It's probably even quicker if you submit a patch ([email protected], no need to subscribe, the usual |
Beta Was this translation helpful? Give feedback.
Oops, yes, it's a documentation bug I indirectly introduced in https://passt.top/passt/commit/?id=3c6ae625101aee6ddf94e0fd85ce3a9c9067c3bf.
spec
for-T
(and-U
) is not (after that commit) as described for-t
(and-u
), because you can't bind to a particular address inside the namespace. These options are used for "spliced" forwarding over the loopback interface, so specifying an address there won't work.It's probably even quicker if you submit a patch ([email protected], no need to subscribe, the usual
git format-email
format) for the man page.