Elijah,
I would add 'logging buffered debug' and see if you get any error messages
in the local log file. You check the local using 'show log'. You may see
traffic being blocked by an ACL.

Secondly version 6.2(2) does have the packet capture feature. It is too long
to go into but check the CCO on how to enable this. I have used it and it
works well. Basically you do the following:

1. Define an ACL to capture the traffic you are looking for, in your case
any traffic going to the syslog server.
2. Use the 'capture' comand assigning the ACL to an interface and starting
the capture.
3. Use the 'show capture' command to see the results.
Hope this helps,
Scott




 --- On Sun 01/26, Elijah Savage III  wrote:
From: Elijah Savage III [mailto: [EMAIL PROTECTED]]
To: [EMAIL PROTECTED]
Date: Sun, 26 Jan 2003 18:21:10 GMT
Subject: RE: Help with pix firewall logging [7:61902]

As a last resort I did reboot the pix also but still no logging, what am
I missing?

-----Original Message-----
From: Elijah Savage III 
Sent: Sunday, January 26, 2003 1:11 PM
To: [EMAIL PROTECTED]
Subject: Help with pix firewall logging [7:61902]

All,



I have a pix running 6.2 it is logging to a freebsd server on the local
network. It was logging at one time to syslog no problem but all of a
sudden it stopped and I can't get it working. Here is the logging config
I turned up logging to see if it would help and nothing. Yes I am sure
syslog is running on the box if I do a tcpdump on the freebsd server I
see nothing coming from the pix.



logging on

logging timestamp

logging trap warnings

logging history debugging

logging facility 23

logging host inside 192.168.11.254
_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=61959&t=61902
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to