From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: connection tracking without iptables?
Date: Thu, 14 Oct 2004 14:57:58 -0400 [thread overview]
Message-ID: <20041014185758.GA4057@bender.817west.com> (raw)
In-Reply-To: <561dc326041014113163a6a9eb@mail.gmail.com>
On Thu, Oct 14, 2004 at 02:31:11PM -0400, Jiann-Ming Su wrote:
> On Thu, 30 Sep 2004 19:34:30 -0400, Jason Opperisano <opie@817west.com> wrote:
> >
> > egrep 'ESTABLISHED|ASSURED' /proc/net/ip_conntrack | wc -l
> >
>
> We're finding that any read operation on /proc/net/ip_conntrack really
> locks the system until that operation is completed. That is, it's
> almost as if the read prevents any writes, so the firewall locks up
> momentarily until the read is done. Is there a less system intensive
> way to read ip_conntrack? Or, is my observation completely wrong?
i'm not aware of any way that reading /proc/net/ip_conntrack would
prevent the system from creating new conntrack entries, but there's lots
of things that i'm not aware of...
you could try IPTState: http://iptstate.phildev.net/
i don't know if it'll help though, as i'm pretty sure it just reads in
/proc/net/ip_conntrack for its data, same as cat/grep/sed/awk/etc...
are you sure there isn't something else going on?
-j
--
Jason Opperisano <opie@817west.com>
next prev parent reply other threads:[~2004-10-14 18:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 18:19 connection tracking without iptables? Daniel Chemko
2004-09-30 18:26 ` Jason Opperisano
2004-09-30 23:04 ` Jiann-Ming Su
2004-09-30 23:34 ` Jason Opperisano
2004-10-14 18:31 ` Jiann-Ming Su
2004-10-14 18:57 ` Jason Opperisano [this message]
2004-10-15 5:16 ` Kiran Kumar Immidi
2004-10-16 12:30 ` Jose Maria Lopez
2004-10-25 20:48 ` Aleksandar Milivojevic
-- strict thread matches above, loose matches on Subject: below --
2004-09-30 23:20 Daniel Chemko
2004-09-29 21:22 Daniel Chemko
2004-09-30 2:24 ` Jiann-Ming Su
2004-09-29 20:50 Jiann-Ming Su
2004-09-29 20:57 ` Alexis
2004-09-29 21:01 ` Jason Opperisano
2004-09-29 21:37 ` Jose Maria Lopez
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=20041014185758.GA4057@bender.817west.com \
--to=opie@817west.com \
--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