From: GLAUME Vincent <vincent.glaume@cea.fr>
To: netfilter@vger.kernel.org
Subject: Using conntrack to create new expectation entry
Date: Fri, 11 Jun 2010 11:57:06 +0200 [thread overview]
Message-ID: <4C120872.4040308@cea.fr> (raw)
Hi there,
I'm currently trying to figure out how the whole libnetfilter_conntrack
works, and more precisely the expect part of the lib.
My aim is to be able to create new expectation entries with this lib in
an application that would inspect packets (either coming from a
pcap-based sniffer or from netfilter via the nfqueue mechanism) : thus
I'd like to allow connections related to the inspected (and already
allowed) connections.
My various tests make me think that to create such an expectation entry,
a kernel module related to the master connection is required: am I right?
For instance, the "expect_create" app in the libnetfilter_conntrack
"utils" subdirectory works fine, unless I modify the destination port of
the master conntrack structure... then it's no longer related to the FTP
conntrack mechanism...
Same thing happens when using the conntrack app. from the conntrack-tools.
So, I'd like to know how to do this the right way, without coding the
whole inspection thing in a kernel module (if this is possible). Is
there any generic tcp conntrack system that could help here?
As I'm not too sure to fully understand the whole mechanism of expected
connection creation, any hint is welcome!
I hope this is not too confused... Thanks,
--
V.
next reply other threads:[~2010-06-11 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 9:57 GLAUME Vincent [this message]
2010-06-13 23:24 ` Using conntrack to create new expectation entry Pablo Neira Ayuso
2010-06-14 8:15 ` GLAUME Vincent
-- strict thread matches above, loose matches on Subject: below --
2010-06-14 8:21 GLAUME Vincent
2010-06-14 19:57 ` Narendra Choyal
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=4C120872.4040308@cea.fr \
--to=vincent.glaume@cea.fr \
--cc=netfilter@vger.kernel.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.