From: Harald Welte <laforge@netfilter.org>
To: "Sébastien LAVEZE" <slaveze@gmail.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Libnetfilter_conntrack problems
Date: Mon, 1 May 2006 14:53:53 -0300 [thread overview]
Message-ID: <20060501175353.GD5267@rama> (raw)
In-Reply-To: <ca021ab30604270455q5cf093c9s990558209bca3e1d@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
On Thu, Apr 27, 2006 at 01:55:13PM +0200, Sébastien LAVEZE wrote:
> but not for destroy ==> nfct_open(CONNTRACK,
> NF_NETLINK_CONNTRACK_DESTROY), i never get any event
are you sure? did you wait until the respective entries really timed
out from the conntrack table?
what does 'conntrack -E -e DESTROY' say? do you then see the events?
> 2) I also would like to work with ids, when i get a conntrack via a
> callback the id field is always set to zero, is it normal ?
IIRC, we dropped ID's recently. I'm a bit lagging behind, though.
--
- Harald Welte <laforge@netfilter.org> http://netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-05-01 17:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 11:55 Libnetfilter_conntrack problems Sébastien LAVEZE
2006-05-01 17:53 ` Harald Welte [this message]
2006-05-03 9:49 ` Sébastien LAVEZE
2006-05-03 11:15 ` Harald Welte
2006-05-09 15:06 ` Sébastien LAVEZE
2006-05-09 15:12 ` Pablo Neira Ayuso
2006-05-10 8:18 ` Sébastien LAVEZE
2006-05-10 13:00 ` Sébastien LAVEZE
2006-05-12 8:34 ` Sébastien LAVEZE
2006-05-12 8:42 ` Philip Craig
2006-05-12 9:01 ` Sébastien LAVEZE
2006-05-16 10:52 ` Pablo Neira Ayuso
2006-05-12 7:11 ` [PATCH] conntrack: Fix option parsing for ARM Philip Craig
2006-05-13 2:24 ` Patrick McHardy
2006-05-14 22:43 ` Pablo Neira Ayuso
2006-05-15 5:52 ` Patrick McHardy
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=20060501175353.GD5267@rama \
--to=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=slaveze@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 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.