netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Eric Leblond <eric@inl.fr>
Cc: Jan Engelhardt <jengelh@medozas.de>,
	Netfilter Developer Mailing List
	<netfilter-devel@vger.kernel.org>,
	sean.donner@gmail.com
Subject: Re: Using TRACE with ulogd2
Date: Mon, 12 Jan 2009 06:17:04 +0100	[thread overview]
Message-ID: <496AD250.9020400@trash.net> (raw)
In-Reply-To: <1231238052.15452.32.camel@khasse.inl.fr>

Eric Leblond wrote:
> Hi,
> 
> Le mardi 06 janvier 2009 à 11:28 +0100, Jan Engelhardt a écrit :
>> Hi,
>>
>>
>> from discussions on IRC and after looking at the kernel's code, I got 
>> the impression that xt_TRACE's output can currently not be fed into 
>> ulogd2, as xt_NFLOG does not make itself available for NF Core logging 
>> through nf_log_packet() as it does not register with nf_log.c's
>> nf_log_register().
>> Could you consider adding this?
> 
> In fact, it should work but it can be a little tricky. You need to
> declare a stack starting with a NFLOG input plugin. This plugin has to
> listen to event on nflog group 0:
> 
> stack=log1:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU
> 
> [log1]
> group=0
> 
> Under that condition, you should receive messages from TRACE.

Indeed, I've used it like that and it works fine.
--
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

      reply	other threads:[~2009-01-12  5:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06 10:28 Using TRACE with ulogd2 Jan Engelhardt
2009-01-06 10:34 ` Eric Leblond
2009-01-12  5:17   ` Patrick McHardy [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=496AD250.9020400@trash.net \
    --to=kaber@trash.net \
    --cc=eric@inl.fr \
    --cc=jengelh@medozas.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=sean.donner@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 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).