Actually, the issue is the number of messages going to the console.  We have trimmed the syslog activity, but we have pass-through filters setup.  They are set to nolog and priority 0, but the console is so busy we can not read anything on it (moving too fast).  Any thoughts on how to trim the console activity?
 
Thanks,
-Vaugn
----- Original Message -----
Sent: Thursday, December 06, 2001 10:28 AM
Subject: RE: Logging Woes

Sounds like you may be logging all the NAT open and closed tunnel messages.  If you go into "remote logging" you can turn of "tunnel opens" and "tunnel closes" in the NAT section.  Also, you can turn off reporting of WWW messages.

Rick Woloss
Network Administrator
|D|S|T|   INNOVIS TM
connecting people through technology
work    (916) 941-4262
mobile (916) 296-7465
[EMAIL PROTECTED]

-----Original Message-----
From: Vaughn Thurman - Swift Systems Inc [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 05, 2001 3:32 PM
To: [EMAIL PROTECTED]
Subject: Logging Woes

Hi All,
    I'm new to gnat box, so forgive me if this is an oft repeated thread...
 
I am logging a lot of activity on the console and would prefer to only show denies or errors etc.  I have set logging to no in all of the accept filters but still there is a lot of data being generated.  Any suggestions?  We are trying to build a customer friendly config and that's the main thing we have left to resolve.  Thanks in advance!
-Vaughn


Notice: This e-mail and any attachments are intended only for the individual or company to which it is addressed and may contain information which is privileged, confidential and prohibited from disclosure or unauthorized use under applicable law. If you are not the intended recipient of this e-mail, you are hereby notified that any use, dissemination, or copying of this e-mail or the information contained in this e-mail is strictly prohibited by the sender. If you have received this transmission in error, please return the material received to the sender and delete all copies from your system. Thank you.

Reply via email to