07-13-2006 12:07 AM - edited 02-21-2020 01:02 AM
I loved the debug packet cmd in ver 6.3 and used it *every* time there was an issue or a question of whether it was the FW's 'fault' - generally wasn't and I could show traffic hitting the pix on one side, leaving it on another with required NATing or not and often thereby prove by lack of return traffic that the issue was downstream.
Ver 7.x does not have this debug packet cmd ... what can I use in it's place. So far ASA is looking like a backwards step, but only for this reason.
Thanks for any help,
Mike
Solved! Go to Solution.
07-13-2006 01:12 AM
Hi,
See the capture command in the docs - and as of 7.2 see also the packet-tracer command - should give you all the tools you need.
HTH
Andrew.
07-13-2006 05:08 AM
Cisco have dropped the debug packet command for PIX from v7, however instead you can use the capture command to set up packet sniffing on the PIX itself. It is best used with an ACL to specify traffic. The basic syntax is:
capture
show capture
07-13-2006 01:12 AM
Hi,
See the capture command in the docs - and as of 7.2 see also the packet-tracer command - should give you all the tools you need.
HTH
Andrew.
07-18-2006 07:21 AM
thanks also for the info
Regards,
Mike
07-13-2006 05:08 AM
Cisco have dropped the debug packet command for PIX from v7, however instead you can use the capture command to set up packet sniffing on the PIX itself. It is best used with an ACL to specify traffic. The basic syntax is:
capture
show capture
07-18-2006 07:21 AM
thanks for the info .... I shall go forth and capture (doesn't sound as cool as debug)
Regards,
Mike
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide