From: Ted Kaczmarek <tedkaz@optonline.net>
To: Alistair Tonner <Alistair@nerdnet.ca>
Cc: netfilter@lists.netfilter.org
Subject: Re: ip_conntrack_max vs ip_conntrack
Date: Tue, 28 Sep 2004 08:53:38 -0400 [thread overview]
Message-ID: <1096376018.16424.95.camel@inyoureyes.linsolutions.com> (raw)
In-Reply-To: <200409280831.31267.Alistair@nerdnet.ca>
*
On Tue, 2004-09-28 at 08:31, Alistair Tonner wrote:
> On September 28, 2004 03:59 am, Mohamed Eldesoky wrote:
> > But still,
> > The /proc/net/ip_conntrack should contain all connections tracked by
> > that firewall (ie, passing through the firewall), am I right ??
> >
>
> This list is all actively tracked connections, all not yet completed, but
> possibly tracked connections (called expectations) that the netfilter code is
> watching for. You need to pay attention to the state of the connection, but
> you've got the right idea.
>
> I can't recall all the states off the top of my head, but they are fairly
> clearly labelled.
>
> Alistair Tonner.
>
> << SNIPPAGE>>
>
Iptstate is nice for this.
Ted
next prev parent reply other threads:[~2004-09-28 12:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 22:34 ip_conntrack_max vs ip_conntrack Michal Ludvig
2004-09-24 22:49 ` Stephen J Smoogen
2004-09-30 9:59 ` Michal Ludvig
2004-09-28 7:59 ` Mohamed Eldesoky
2004-09-28 12:31 ` Alistair Tonner
2004-09-28 12:53 ` Ted Kaczmarek [this message]
2004-09-28 14:27 ` Jose Maria Lopez
2004-09-28 14:48 ` Mohamed Eldesoky
2004-09-28 15:19 ` Alistair Tonner
2004-09-30 11:30 ` Mohamed Eldesoky
-- strict thread matches above, loose matches on Subject: below --
2004-09-27 17:52 Jiann-Ming Su
2004-09-27 18:04 ` Jason Opperisano
2004-09-27 18:57 ` Jose Maria Lopez
2004-09-30 22:48 ` Jiann-Ming Su
2004-09-30 23:03 ` Jason Opperisano
2004-10-19 17:21 ` Jiann-Ming Su
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=1096376018.16424.95.camel@inyoureyes.linsolutions.com \
--to=tedkaz@optonline.net \
--cc=Alistair@nerdnet.ca \
--cc=netfilter@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox