From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
Netfilter Developer Mailing List
<netfilter-devel@lists.netfilter.org>
Subject: Re: xt_connlimit kernel 20070620
Date: Wed, 20 Jun 2007 14:47:57 +0200 [thread overview]
Message-ID: <467921FD.8000909@trash.net> (raw)
In-Reply-To: <46791704.4090609@netfilter.org>
Pablo Neira Ayuso wrote:
> Jan Engelhardt wrote:
>
>> UDP does not have a transition from ESTABLISHED -> TIME_WAIT, to begin
>> with.
>
>
> But the event API has the DESTROY transition. There are three kind of
> events: NEW, UPDATE and DESTROY. Just wait for DESTROY events to release
> the entry from the hashtable.
Thats not a bad idea, but I always considered the notifier chains
overkill just for ctnetlink and thought about replacing them by
simple hooks. Adding another user for them would need some good
justification, also since it quite heavily adds to the overhead
for packet processing.
next prev parent reply other threads:[~2007-06-20 12:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 22:41 xt_connlimit kernel 20070620 Jan Engelhardt
2007-06-19 22:41 ` xt_connlimit iptables 20070620 Jan Engelhardt
2007-06-19 22:45 ` xt_connlimit kernel 20070620 Jan Engelhardt
2007-06-20 9:47 ` Pablo Neira Ayuso
2007-06-20 10:29 ` Jan Engelhardt
2007-06-20 11:07 ` Pablo Neira Ayuso
2007-06-20 11:32 ` Jan Engelhardt
2007-06-20 12:01 ` Pablo Neira Ayuso
2007-06-20 12:35 ` Jan Engelhardt
2007-06-20 12:47 ` Patrick McHardy [this message]
2007-06-20 12:56 ` Jan Engelhardt
2007-06-21 15:39 ` Pablo Neira Ayuso
2007-06-21 15:44 ` Patrick McHardy
2007-06-21 15:50 ` Pablo Neira Ayuso
2007-06-21 15:51 ` 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=467921FD.8000909@trash.net \
--to=kaber@trash.net \
--cc=jengelh@computergmbh.de \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@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.