From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Liping Zhang <zlpnobody@163.com>
Cc: netfilter-devel@vger.kernel.org,
Liping Zhang <liping.zhang@spreadtrum.com>
Subject: Re: [PATCH nft] src: support ct l3proto/protocol without direction syntax
Date: Mon, 17 Oct 2016 18:28:16 +0200 [thread overview]
Message-ID: <20161017162816.GA15107@salvia> (raw)
In-Reply-To: <1474554892-50927-1-git-send-email-zlpnobody@163.com>
On Thu, Sep 22, 2016 at 10:34:52PM +0800, Liping Zhang wrote:
> From: Liping Zhang <liping.zhang@spreadtrum.com>
>
> Acctually, ct l3proto and ct protocol are unrelated to direction, so
> it's unnecessary that we must specify dir if we want to use them.
>
> Now add support that we can match ct l3proto/protocol without direction:
> # nft add rule filter input ct l3proto ipv4
> # nft add rule filter output ct protocol 17
>
> Note: existing syntax is still preserved, so "ct reply l3proto ipv6"
> is still fine.
Applied, thanks.
Sorry, it seems I accidentally left this patch behind.
prev parent reply other threads:[~2016-10-17 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 14:34 [PATCH nft] src: support ct l3proto/protocol without direction syntax Liping Zhang
2016-10-17 16:28 ` Pablo Neira Ayuso [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=20161017162816.GA15107@salvia \
--to=pablo@netfilter.org \
--cc=liping.zhang@spreadtrum.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=zlpnobody@163.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 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).