From: Patrick McHardy <kaber@trash.net>
To: Daniel <zyzhou1@gmail.com>
Cc: netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: How about issueing conntrack event in init_conntrack()?
Date: Thu, 15 Nov 2007 14:57:05 +0100 [thread overview]
Message-ID: <473C5031.3040504@trash.net> (raw)
In-Reply-To: <200711151738170572772@gmail.com>
Daniel wrote:
> hi, all
>
> We all know event IPCT_NEW is issued whenever conntrack is confirmed,
> then how about issueing a IPCT_INIT event in init_conntrack()?
> IPCT_INIT indicates that one IP is trying to create a connection, maybe
> we can catch these kind of events, do some analyzation work, and block
> the evil *attempting* packet(this will prevent conntrack being confirmed).
>
> Is this make any sense?
That wouldn't work since the connection is going to be confirmed
before you get a chance to do something. On SMP it might work,
but would be racy. In general ctnetlink events relate to the
conntrack table, so we don't want to send events for connections
that are not confirmed.
prev parent reply other threads:[~2007-11-15 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 9:38 How about issueing conntrack event in init_conntrack()? Daniel
2007-11-15 13:57 ` Patrick McHardy [this message]
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=473C5031.3040504@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=zyzhou1@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.