Hey, Piloria ... it's you! I didn't notice first time. It's been a busy day.
Anyway, firstly debugging needs to be turned on ..
pix(config)# logging on
If you want to see the logs on the console, direct them there using ..
pix(config)# logging console <level>
The level depends on how much info you want to see. You can also direct logging to your SSH or telnet session with the command "terminal monitor".
Other options are:
pixfirewall(config)# logging console
Usage: [no] logging on
[no] logging timestamp
[no] logging standby
[no] logging host [<in_if>] <l_ip> [tcp|udp/port#] [format {emblem}]
[no] logging console <level>
[no] logging buffered <level>
[no] logging monitor <level>
[no] logging history <level>
[no] logging trap <level>
[no] logging message <syslog_id> level <level>
[no] logging facility <fac>
[no] logging device-id hostname | ipaddress <if_name>
| string <text>
logging queue <queue_size>
show logging [{message [<syslog_id>|all]} | level | disabled]
Best practice would be to direct the logs to a syslog server and sort them there. I have to say, having worked with both Firewall-1 and Pix, Firewall-1 has by far the best logging. Still, I do like working with the Pix!
Chris.
**********************
Chris Andrew, CCNA, CCSA
chris@iproute.co.uk
**********************