From: KOVACS Krisztian <hidden@balabit.hu>
To: netfilter-failover@lists.netfilter.org
Cc: netfilter-devel <netfilter-devel@lists.netfilter.org>,
Ramsurrun Visham <vishamr@gmail.com>
Subject: Re: [nf-failover] Conntrack schema!!
Date: Tue, 18 Jul 2006 15:22:39 +0200 [thread overview]
Message-ID: <200607181522.40035@nienna> (raw)
In-Reply-To: <802220ef0607180609v6c362c56h401cb9c8d7b53647@mail.gmail.com>
Hi,
On Tuesday 18 July 2006 15.09, Ramsurrun Visham wrote:
> I would like to know if there's a document that explains the different
> parts of the conntrack system (the different functions involved, the
> entry points for packets..etc).
I'm afraid you're asking this on the wrong list. You should ask Netfilter
development-related questions on the netfilter-devel (-at-)
lists.netfilter.org mailing list.
BTW, I'd recommend Pablo's recent article available here:
http://people.netfilter.org/pablo/docs/login.pdf
This provides a quite nice overview of the conntrack system in general.
Once you know the key data structures and Netfilter concepts reading the
source code is much easier.
--
Regards,
Krisztian Kovacs
parent reply other threads:[~2006-07-18 13:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <802220ef0607180609v6c362c56h401cb9c8d7b53647@mail.gmail.com>]
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=200607181522.40035@nienna \
--to=hidden@balabit.hu \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter-failover@lists.netfilter.org \
--cc=vishamr@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.