There are many articles out there about ICMP and PING. This article solely focuses on ICMP traffic passing through Adaptive Security Appliance. With the default configurations ASA will allow a host to ping the interface which is connected to. However, ping from an internal host to the internet would normally fail.
By default, traffic from the Higher Security Zone to (Inside) Lower Security Zone (Outside) is allowed without any Access Lists. Return traffic from Outside to Inside will be allowed through because the traffic was initiated from Inside.
For example, a client accessing a web page on the Internet. When a packet arrives in the Inside interface from the client, the packet is categorized into a flow based on five-tuple which contains the source IP, Source Port, Destination IP, Destination Port, and the Layer 4 protocol. ASA then maintains a state table to track these connections/flows. Based on this state table the return traffic from the web server is allowed through the firewall.
Back to ASA and Ping, ping is part of the ICMP protocol suite and handled differently compared to TCP/UDP. ASA doesn't track ICMP sessions/connections, making it stateless. Because ICMP packets do not themselves contain any connection information. Being stateless, ASA will let the ICMP echo request from Inside to Outside, but it will not allow the ICMP echo reply from Outside to Inside.
Cisco ASA can track ICMP sessions by enabling ICMP Inspection Engine. This results in an ICMP session being tracked, which in turn allows the ICMP reply packets to pass through from Outside to Inside. ICMP inspection can also dynamically allow time-exceeded and destination unreachable messages to pass through the Outside interface. (ICMP traffic has to be initiated from Inside to start with)
Below you will find the ICMP inspection configuration.
So now when the client tries and ping the web server, the ICMP echo-request packet is allowed through. ASA now starts to track this ICMP session.
Finally, when the web server sends echo-reply, ASA determines that this packet is part of an existing session and allows the packet through.
ICMP Inspection is disabled. Ping from VPC4 to VPC5 would fail.
ASA will let the echo request passes through the ASA however, ICMP reply from VPC5 to VPC4 is denied.
I'm building multiple IPSec VPNs over cellular networks using a Cradlepoint IBR650 on either end. On the head end is the 867VAE-K9 behind one of these Cradlepoints terminating one end of every tunnel and each other end is another Cradlepoint termina...
Trying to determine how to properly configure FQDNs in access lists on an ASA5525 to always resolve for HTTPS from an internal network server VM application reaching out to them regardless of what ip address changes occur to each domain name over time. Af...
Could you please provide support on the following questions: · I have two VAs deployed, both on the same network in a single site. We have a second site so need to know if it is possible to move one of those VAs to the new site. It will be in a different ...
I recently purchased a pair of ASA 5550's to upgrade my home network since I have a Gig line but the 3900 I've been using as my boundary firewall throttles filtered traffic at about 150Mbps. I *thought* the 5550s would be very similar to routers--they are...
I have a firepower 1010 I am trying to configure for a customer. It is going in place of a router that is there now. internal ip for example on firepower is 192.168.1.10 and this is the default gateway for all computers then we have another ro...