From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiann-Ming Su Subject: Re: connection tracking without iptables? Date: Thu, 14 Oct 2004 14:31:11 -0400 Sender: netfilter-bounces@lists.netfilter.org Message-ID: <561dc326041014113163a6a9eb@mail.gmail.com> References: <7C9884991ADAE0479C14F10C858BCDF591E37C@alderaan.smgtec.com> <561dc326040930160476d839c7@mail.gmail.com> <1096587270.22962.24.camel@wolfpack.ljm.dom> Reply-To: Jiann-Ming Su Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1096587270.22962.24.camel@wolfpack.ljm.dom> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: netfilter-bounces@lists.netfilter.org Content-Type: text/plain; charset="us-ascii" To: netfilter@lists.netfilter.org On Thu, 30 Sep 2004 19:34:30 -0400, Jason Opperisano 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? -- Jiann-Ming Su "I have to decide between two equally frightening options. If I wanted to do that, I'd vote." --Duckman