From: Florian Westphal <fw@strlen.de>
To: Liping Zhang <zlpnobody@163.com>
Cc: pablo@netfilter.org, netfilter-devel@vger.kernel.org,
Liping Zhang <liping.zhang@spreadtrum.com>
Subject: Re: [PATCH nf-next 4/4] netfilter: nft_meta: add explicitly nf_logger_find_get call
Date: Wed, 8 Jun 2016 14:59:32 +0200 [thread overview]
Message-ID: <20160608125932.GA29699@breakpoint.cc> (raw)
In-Reply-To: <1465389800-27842-5-git-send-email-zlpnobody@163.com>
Liping Zhang <zlpnobody@163.com> wrote:
> From: Liping Zhang <liping.zhang@spreadtrum.com>
>
> Like xt_TRACE do, we should request related nf_log module appropriately.
> Otherwise, if the nf_log_ipv4 kernel module is not installed, and the
> user add the following nft rule:
> # nft add rule filter input nftrace set 1
>
> There will be no trace log generated until we install nf_log_ipv4 module
> manually.
With nftables we have a new infrastructure in place that emits trace info via
nfnetlink.
So loading nf_log_ipX isn't needed anymore in nft.
next prev parent reply other threads:[~2016-06-08 12:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 12:43 [PATCH nf-next 0/4] netfilter: request related nf_log module when we add TRACE rule Liping Zhang
2016-06-08 12:43 ` [PATCH nf-next 1/4] netfilter: nf_log: handle NFPROTO_INET properly in nf_logger_[find_get|put] Liping Zhang
2016-06-23 11:22 ` Pablo Neira Ayuso
2016-06-23 11:23 ` Pablo Neira Ayuso
2016-06-08 12:43 ` [PATCH nf-next 2/4] netfilter: nft_log: no need to deal with NFPROTO_INET family Liping Zhang
2016-06-08 12:43 ` [PATCH nf-next 3/4] netfilter: xt_TRACE: add explicitly nf_logger_find_get call Liping Zhang
2016-06-08 13:00 ` Florian Westphal
2016-06-23 17:26 ` Pablo Neira Ayuso
2016-06-08 12:43 ` [PATCH nf-next 4/4] netfilter: nft_meta: " Liping Zhang
2016-06-08 12:59 ` Florian Westphal [this message]
2016-06-14 12:35 ` Liping Zhang
2016-06-23 17:33 ` 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=20160608125932.GA29699@breakpoint.cc \
--to=fw@strlen.de \
--cc=liping.zhang@spreadtrum.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).