From: Pablo Neira Ayuso <pablo@netfilter.org>
To: FaTe <gokuvsvegita@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] libxt_multiport: Add translation to nft
Date: Wed, 9 Mar 2016 13:32:38 +0100 [thread overview]
Message-ID: <20160309123238.GA30363@salvia> (raw)
In-Reply-To: <56DFC995.7090009@gmail.com>
On Wed, Mar 09, 2016 at 12:28:29PM +0530, FaTe wrote:
> Added translation for the match multiport.
>
> Example :
> $ iptables-translate -A INPUT -p tcp -m multiport --ports 3:4 -j ACCEPT
> nft add rule ip filter INPUT ip protocol tcp dport { 3-4 } tcp sport { 3-4 }
> counter accept
>
> $ iptables-translate -A INPUT -p tcp -m multiport --sports http,ssh,ftp -j
> ACCEPT
> nft add rule ip filter INPUT ip protocol tcp sport { 80,22,21 } counter accept
>
> $ iptables-translate -A INPUT -p tcp -m multiport --dports 1024:2048 -j ACCEPT
> nft add rule ip filter INPUT ip protocol tcp dport { 1024-2048 } counter accept
>
> $ iptables-translate -A input -p tcp -m multiport --dports 1024:2048,2049:3333
> -j ACCEPT
> nft add rule ip filter input ip protocol tcp dport { 1024-2048,2049-3333 }
> counter accept
This translation is not correct as it's been discussed in a different
thread.
next prev parent reply other threads:[~2016-03-09 12:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 21:21 [PATCHv3] extensions: libipt_icmp: Add translation to nft Laura Garcia Liebana
2016-03-08 10:53 ` Pablo Neira Ayuso
2016-03-09 6:58 ` [PATCH] libxt_multiport: " FaTe
2016-03-09 12:32 ` Pablo Neira Ayuso [this message]
2016-03-09 14:37 ` Piyush Pangtey
2016-03-09 14:39 ` [PATCH v2] " Piyush Pangtey
2016-03-09 17:30 ` Pablo Neira Ayuso
2016-03-10 12:50 ` [PATCH v3] " Piyush Pangtey
2016-03-10 18:31 ` Pablo Neira Ayuso
2016-03-09 7:05 ` Regarding libxt_multiport translation in nft FaTe
2016-03-09 10:06 ` Arturo Borrero Gonzalez
2016-03-09 14:34 ` Piyush Pangtey
2016-03-09 7:12 ` [PATCH] libip6t_hbh: Add translation to nft FaTe
2016-03-10 18:47 ` 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=20160309123238.GA30363@salvia \
--to=pablo@netfilter.org \
--cc=gokuvsvegita@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.