Using TRACE with ulogd2

Using TRACE with ulogd2

[Jan Engelhardt]

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?


Jan

Re: Using TRACE with ulogd2

[Eric Leblond]

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]

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.

BR,
-- 
Éric Leblond <eric@inl.fr>
INL, http://www.inl.fr/
NuFW, http://www.nufw.org

[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: Using TRACE with ulogd2

[Patrick McHardy]

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