From: Pablo Neira Ayuso <pablo@eurodev.net>
To: "Sébastien LAVEZE" <slaveze@gmail.com>
Cc: Harald Welte <laforge@netfilter.org>,
netfilter-devel@lists.netfilter.org
Subject: Re: Libnetfilter_conntrack problems
Date: Tue, 09 May 2006 17:12:14 +0200 [thread overview]
Message-ID: <4460B14E.90506@eurodev.net> (raw)
In-Reply-To: <ca021ab30605090806l791e6f3dl7354bd789df209ee@mail.gmail.com>
Hi,
Sébastien LAVEZE wrote:
>> > However the DESTROY events come a long time after the actual end of a
>> > connection by timeout...am I right ?
>>
>> not really. please be more specific. what is 'end of a connection by
>> timeout'? which specific timeout of which particular state are you
>> talking about?
>
>
> My problem is pretty strange...
> I got two processes, one has a callback registered to UPDATE events,
> the other one has a callback registered to DESTROY event
>
> I do get destroy events but not all the time, when i have tcp
> connections that go from ESTABLISHED state to FIN_WAIT and finally to
> TIME_WAIT ( i see the progression of these states with the process
> linked to UPDATE events ) But when the TIME_WAIT timer is over i do
> not get the DESTROY event...
Could you try to do the same thing with the conntrack tool and let us
know if the problem still persists?
to catch update events
# conntrack -E -e UPDATE
to catch destroy events
# conntrack -E -e DESTROY
--
Pablo
next prev parent reply other threads:[~2006-05-09 15:12 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
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 [this message]
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=4460B14E.90506@eurodev.net \
--to=pablo@eurodev.net \
--cc=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.