From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH 3/3] parser: allow both nat_flags and port specification in redirect
Date: Mon, 10 Nov 2014 18:22:49 +0100 [thread overview]
Message-ID: <20141110172249.GC28853@salvia> (raw)
In-Reply-To: <20141107113935.8480.16834.stgit@nfdev.cica.es>
On Fri, Nov 07, 2014 at 12:39:35PM +0100, Arturo Borrero Gonzalez wrote:
> This patch changes the parser to permit both nat_flags and port specification
> in the redirect expression.
>
> The resulting syntax is:
> % nft add rule nat prerouting redirect [port] [nat_flags]
>
> The port specification requires a bit of context regardin the transport
> protocol. Some examples:
> % nft add rule nat prerouting tcp dport 22 redirect :23
> % nft add rule add prerouting udp dport 53 redirect :5353
>
> The nat_flags argument is the last argument:
> % nft add rule nat prerouting tdp dport 80 redirect :8080 random
>
> The port specification can be a range:
> % nft add rule nat prerouting tcp dport 80 redirect :8080-8090 random
>
> While at it, the regression tests files are updated.
Applied, thanks.
next prev parent reply other threads:[~2014-11-10 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 11:39 [nft PATCH 1/3] tests/regression: masquerade: fix invalid syntax Arturo Borrero Gonzalez
2014-11-07 11:39 ` [nft PATCH 2/3] tests/regression: redirect: " Arturo Borrero Gonzalez
2014-11-10 17:22 ` Pablo Neira Ayuso
2014-11-07 11:39 ` [nft PATCH 3/3] parser: allow both nat_flags and port specification in redirect Arturo Borrero Gonzalez
2014-11-10 17:22 ` Pablo Neira Ayuso [this message]
2014-11-10 17:22 ` [nft PATCH 1/3] tests/regression: masquerade: fix invalid syntax Pablo Neira Ayuso
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=20141110172249.GC28853@salvia \
--to=pablo@netfilter.org \
--cc=arturo.borrero.glez@gmail.com \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).