From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: Shivani Bhardwaj <shivanib134@gmail.com>,
Netfilter Development Mailing list
<netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH] extensions: libxt_sctp: Add translation to nft
Date: Wed, 2 Mar 2016 16:10:05 +0100 [thread overview]
Message-ID: <20160302151005.GA5844@salvia> (raw)
In-Reply-To: <alpine.LSU.2.20.1603021539140.17720@nerf40.vanv.qr>
On Wed, Mar 02, 2016 at 03:47:32PM +0100, Jan Engelhardt wrote:
>
> On Wednesday 2016-03-02 15:14, Shivani Bhardwaj wrote:
> >>
> >> This crazy thing seems to be valid:
> >>
> >> iptables -I INPUT -p sctp -m sctp
>
> This is how all protocols are loaded. It can be readily seen
> in a iptables-save dump. One tests the L3 header field, the other
> loads the module for further options to do tests on L4 fields.
>
> >>
> >> and this will be translated as:
> >>
> >> nft add rule filter INPUT ip protocol sctp sctp
>
> that seems correct, does it not?
That translation is not correct in nft:
# nft add rule filter INPUT ip protocol sctp sctp
<cmdline>:1:44-44: Error: syntax error, unexpected end of file,
expecting checksum or sport or dport or vtag
add rule filter INPUT ip protocol sctp sctp
next prev parent reply other threads:[~2016-03-02 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 20:40 [PATCH] extensions: libxt_sctp: Add translation to nft Shivani Bhardwaj
2016-03-02 11:48 ` Pablo Neira Ayuso
2016-03-02 11:54 ` Pablo Neira Ayuso
2016-03-02 14:14 ` Shivani Bhardwaj
2016-03-02 14:47 ` Jan Engelhardt
2016-03-02 15:10 ` Pablo Neira Ayuso [this message]
2016-03-02 15:20 ` 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=20160302151005.GA5844@salvia \
--to=pablo@netfilter.org \
--cc=jengelh@inai.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=shivanib134@gmail.com \
/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.