libconntrack usage

libconntrack usage

[Eric Leblond]

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

Hi,

INL has develop a daemon (nutrackd) which use the libconntrack. It opens
event handler for DESTROY event and to register the callback it uses :
	nfct_register_callback(cth, update_handler, NULL);
and this work well, our handler is called.

But is still display [DESTROY] on stdout after each message.

By doing :
    nfct_unregister_callback(cth);
    nfct_register_callback(cth, update_handler, NULL);
we manage to suppress the useless message.

Is this a bug or a feature ?

BR,
-- 
Eric Leblond <eric@inl.fr>
INL

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: libconntrack usage

[Pablo Neira Ayuso]

Hi Eric,

Eric Leblond wrote:
> INL has develop a daemon (nutrackd) which use the libconntrack. It opens
> event handler for DESTROY event and to register the callback it uses :
> 	nfct_register_callback(cth, update_handler, NULL);
> and this work well, our handler is called.
> 
> But is still display [DESTROY] on stdout after each message.
> 
> By doing :
>     nfct_unregister_callback(cth);
>     nfct_register_callback(cth, update_handler, NULL);
> we manage to suppress the useless message.
> 
> Is this a bug or a feature ?

Curiously I noticed that some hours ago, I fixed in the last SVN commit
together with some changes. That will fix your problem. Check out a
working copy from SVN.

BTW, nfct_event_display_handler doesn't exist anymore, now you have to
use nfct_conntrack_display_handler instead.

cheers.

-- 
Pablo