From: "Neal P. Murphy" <neal.p.murphy@alum.wpi.edu>
To: netfilter@vger.kernel.org
Subject: Re: nft rule to redirect multiple ports using maps
Date: Fri, 9 Oct 2015 14:09:09 -0400 [thread overview]
Message-ID: <20151009140909.77221e5d@playground> (raw)
In-Reply-To: <20151009105621.GA2624@salvia>
On Fri, 9 Oct 2015 12:56:21 +0200
Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> On Thu, Oct 08, 2015 at 10:12:30PM +0200, Giorgio wrote:
> > <cmdline>:1:37-74: Error: transport protocol mapping is only valid after
> > transport protocol match
> That is telling that protocol context is missing, try with this:
>
> nft add rule nat prerouting ip protocol tcp \
> redirect to tcp dport map { 22 : 2222, 23 : 2323 }
The words, while technically correct, probably should convey more information. Perhaps something like:
"... Error: You must specify a transport protocol (TCP/UDP/etc.) before you can map it"
Neal
prev parent reply other threads:[~2015-10-09 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 20:12 nft rule to redirect multiple ports using maps Giorgio
2015-10-09 10:56 ` Pablo Neira Ayuso
2015-10-09 18:09 ` Neal P. Murphy [this message]
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=20151009140909.77221e5d@playground \
--to=neal.p.murphy@alum.wpi.edu \
--cc=netfilter@vger.kernel.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox