All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Guiton <emmanuel@netlab.hut.fi>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: How do I use ip_conntrack_destroyed?
Date: Fri, 05 Dec 2003 16:57:59 +0200	[thread overview]
Message-ID: <3FD09CF7.1090402@netlab.hut.fi> (raw)
In-Reply-To: 3FCF4E6A.8070202@balabit.hu

KOVACS Krisztian wrote:

>   This was the case for an older version of nfnetlink. With 
> nfnetlink-ctnetlink 0.13 you should use
>
> static struct notifier_block my_notifier = {
>     my_notifier_function,
>     NULL,
>     0
> };
>
>   For more info see that patch, it actually _uses_ notifiers to be 
> able to catch conntrack entry related events. Note that this interface 
> is much more universal, for example you can catch events when a 
> conntrack entry is modified, etc. Good luck :)
>

About this patch, I cannot install it. I started over from a clean linux 
2.4.22 kernel and applied the patches. First I used ./runme base and 
applied everything I could. then I used ./runme extra and in the extra 
patches I only tried to apply the nfnetlinc patch (thus I did not 
install the two conflicting patches - ctstat and netfilter-docbook). 
Still, it does not work. Is there any other required/conflicted patch 
that I am not aware of?


             Emmanuel

PS: for information, the output of pom:


Testing... nfnetlink-ctnetlink-0.13.patch NOT APPLIED (4 missing files)
The extra/nfnetlink-ctnetlink-0.13 patch:
   Author: Harald Welte <laforge@gnumonks.org>, Jay Schulist 
<jschlst@samba.org>,
   Patrick McHardy <kaber@trash.net>
   Status: Under development, but stabilizing now.
  
   Add recent work by patrick (notifiers, event messages to userspace.
  
-----------------------------------------------------------------
Do you want to apply this patch [N/y/t/f/a/r/b/w/q/?] y
Patch extra/nfnetlink-ctnetlink-0.13.patch conflicts with 
extra/netfilter-docbook.patch...
netfilter-docbook.patch NOT APPLIED (33 rejects out of 33 hunks)
Patch extra/nfnetlink-ctnetlink-0.13.patch conflicts with 
extra/ctstat.patch...
ctstat.patch NOT APPLIED (15 rejects out of 15 hunks)
Testing patch extra/nfnetlink-ctnetlink-0.13.patch...
   Placed new Config.in line
   Placed new Config.in line
   Placed new Makefile line
   Placed new ip_conntrack.h line
   Placed new ip_conntrack.h line
   Placed new ip_conntrack.h line
   Placed new ip_conntrack.h line
   Placed new ip_conntrack.h line
   Placed new ip_conntrack.h line
   Placed new ip_conntrack.h line
   Placed new ip_conntrack.h line
Failed to patch copy of /usr/src/linux-2.4.22
TEST FAILED: patch NOT applied.

  parent reply	other threads:[~2003-12-05 14:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03 12:05 How do I use ip_conntrack_destroyed? Emmanuel Guiton
2003-12-03 14:10 ` KOVACS Krisztian
2003-12-03 21:57 ` Henrik Nordstrom
2003-12-04  7:58   ` KOVACS Krisztian
2003-12-04 14:14     ` Emmanuel Guiton
2003-12-04 15:10       ` KOVACS Krisztian
2003-12-04 15:32         ` Emmanuel Guiton
2003-12-05 14:57         ` Emmanuel Guiton [this message]
2003-12-05 15:56           ` How do I use ip_conntrack_destroyed? [previous message erratum] Emmanuel Guiton
  -- strict thread matches above, loose matches on Subject: below --
2003-12-03 10:17 How do I use ip_conntrack_destroyed? Emmanuel Guiton

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=3FD09CF7.1090402@netlab.hut.fi \
    --to=emmanuel@netlab.hut.fi \
    --cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.