[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gauntlet-user
Subject:    Re: Gauntlet 4.0a
From:       Ekkehard Guembel <guembel () dvg-hannover ! de>
Date:       1997-10-24 22:13:26
[Download RAW message or body]

just guessing: did you make sure the resolver works fine? sounds a bit
like dns timeout problems, sometimes causing strange problems... to make
sure, temporarily comment the "bind" in /etc/host.conf
good luck =-)
Ekkehard



***original massage follows:***
Recently we did a fresh install on out firewall.

We did a clean install of BSD 3.0.  Installed Gauntlet Firewall 4.0a.
The system ran great at this point.

We tried to install our original trusted-networks file along with
static-routes, (trusted-networks)which had approximately 1000+ entries. 
The system came to a screaming halt when trying to update the
trusted-networks file thru gauntlet-admin utility.  It takes over 20
minutes just to boot the system.  The users see no degradation when
accessing the Internet, just operations on the firewall itself (console)
extremely slow! TIS is aware of the problem, I was just wondering if any
other companies have seen this and do they have a work around?  We found
a fix for ourselves, however it is not what we want to keep in place. 
One item we did notice is that the gauntlet software is now adding an
additional entry for each ip_address that we
add to the trusted-networks file. (#pat_????) What's up with this?
:-(
[...]

[prev in list] [next in list] [prev in thread] [next in thread]