From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Markus Kötter" <koetter@rrzn.uni-hannover.de>
Cc: netfilter-devel@vger.kernel.org, kaber@trash.net
Subject: Re: [RFC] nft trace
Date: Mon, 2 Mar 2015 01:20:04 +0100 [thread overview]
Message-ID: <20150302002004.GA9881@salvia> (raw)
In-Reply-To: <54F35515.5050807@rrzn.uni-hannover.de>
Cc'ing Patrick.
On Sun, Mar 01, 2015 at 07:06:13PM +0100, Markus Kötter wrote:
[...]
> I'd love a response regarding the odds of getting the nft trace
> functionality merged - I promise to continue working on it, clean
> things up, I'll take care it is optional and does not tie nft to
> libnetfilter_conntrack (e.g. for embedded platforms).
You can use libmnl, I think there's a example on the tree, so you
don't really need to rely on libnetfilter_log.
It would be good to have a netlink interface to configure nf_log, to
provide a replacement for the existing /proc interface and allow
further configurability (indicate the nfnetlink log group instead of
defaulting on zero). I agree the existing interface to configure the
prefered logging stub is not nice.
I think it's reasonable to have some tracing command intergrated into
nft, but we still have to discuss the text output layout. No
objections from my side if you want to get that rfc patch in better
shape and send us patches.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-03-02 0:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 18:06 [RFC] nft trace Markus Kötter
2015-03-02 0:10 ` nfnetlink_log and trace problems [was Re: [RFC] nft trace] Pablo Neira Ayuso
2015-03-02 0:20 ` Pablo Neira Ayuso [this message]
2015-03-02 7:33 ` [RFC] nft trace Markus Koetter
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=20150302002004.GA9881@salvia \
--to=pablo@netfilter.org \
--cc=kaber@trash.net \
--cc=koetter@rrzn.uni-hannover.de \
--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).