[3715] in linux-net channel archive

home help back first fref pref prev next nref lref last post

Re: firewalling/bridging and proc tables

daemon@ATHENA.MIT.EDU (Carsten Paeth)
Tue Jul 16 05:53:35 1996

To: paul@matthews.com (Paul Matthews)
Date: 	Sun, 14 Jul 1996 23:29:38 +0200 (MET DST)
From: "Carsten Paeth" <calle@calle.in-berlin.de>
Cc: devel@vrml.k12.la.us, linux-kernel@vger.rutgers.edu,
        linux-net@vger.rutgers.edu
In-Reply-To: <199607132124.RAA04974@gw1.matthews.com> from "Paul Matthews" at Jul 13, 96 05:24:45 pm

> 
> System Development writes:
> 
>  > Also, why do certain utilities that rely on the data obtained from the
>  > /proc filesystem seem to hang up when I try to get a listing?  Like,
>  > route and in particular ipfwadm -F -l or ipfwadm -M -l.  
> 
> I have run Linux-2.0.0, 2.0.3, and now 2.0.6, and I do not experience
> any Hanging. Have you upgraded to the latest procps?
> 
> Regards,
> 
> -- 
> Paul Matthews
> McLean, VA
> e-mail: paul@matthews.com
> 

The tools are using DNS to provide names on output.
The 'hang' is not related to the proc filesystem, but to DNS.
My tip: Setup a local named as secondary for all zones you are
using with ipfwadm or route (especially the ...in-addr.arpa zones)

calle
-- 
calle@calle.in-berlin.de


home help back first fref pref prev next nref lref last post