09-05-2002 07:48 AM - edited 03-09-2019 12:11 AM
I have the following at the top of my inbound access list
permit icmp any any
It's applied inbound in my outside interface, however, I still can't ping anything on the outside........
09-05-2002 08:05 AM
I am able to ping through my pix but I also have an access-list on the inside interface that looks like this:
permit icmp 1.1.1.0 255.255.255.0 any
This list permits ICMP packets from the inside networks to the outside. If I remember correctly, you must specifically permit ICMP to go from a higher security interface to a lower security interface.
Kevin
09-05-2002 08:06 AM
I am able to ping through my pix but I also have an access-list on the inside interface that looks like this:
permit icmp 1.1.1.0 255.255.255.0 any
This list permits ICMP packets from the inside networks to the outside. If I remember correctly, you must specifically permit ICMP to go from a higher security interface to a lower security interface.
Kevin
09-05-2002 10:32 AM
The key is that you have to allow the echo-reply into the outside interface.
These are the access-list statements I am using;
access-list acl_outside permit icmp any any echo-reply
access-list acl_outside permit icmp any any source-quench
access-list acl_outside permit icmp any any unreachable
access-list acl_outside permit icmp any any time-exceeded
Mike
09-18-2002 03:16 PM
The ASA algoritm from PIX does not treat ICMP protocol as "statefull". You have to open in both directions.
Only for a outside to inside "ping", open ICMP echo from outside and ICMP echo-reply from inside
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