08-08-2018 12:17 PM - edited 02-21-2020 08:04 AM
Hello,
I am using an ASA on the Firepower 2110. I was trying to traffic flow between interfaces and configured one interface E1/5 with ip address 10.1.215.115/24; security-level 100 and another interface E1/6 with ip address 10.1.253.115/25; security-level 100). I allowed icmp from any to each interface. I created an ACL to allow icmp to each interface. I attahced two laptops to each interface( laptop215: 10.1.215.100/24- GW: 10.1.215.115 and laptop253: 10.1.253.100/24- GW: 10.1.253.115).
From laptop215, I can ping it's GW (10.1.215.115 just fine. From laptop253, I can also ping it's GW: 10.1.253.115 just fine.
On the ASA, I can ping each interface just fine, but the issue I am facing is that when I try to ping from laptop215 to interface E1/6 - 10.1.253.115, it fails. The same thing happens when I try to ping from laptop253 to interface E1/5 - 10.1.215.115.
I can't figure out why I can't ping from each host (laptop) to the other interface or laptop. Why can't I ping from one host 10.1.253.100 to interface 10.1.251.115 or host 10.1.215.100 to 10.1.253.115?
Any assistance would be greatly appreciated.
Best, ~zK
08-08-2018 12:34 PM
08-08-2018 02:08 PM
08-08-2018 02:27 PM
Ok, packet-trace confirms it should be allowed.
If I understand you correctly you are attempting to ping an interface of the ASA that you are not connected to (as in the interface connected to the other laptop). Try configuring the management-access command, reference here.
If you cannot ping the laptops, do they have a local firewall enabled?
HTH
08-08-2018 02:42 PM - edited 08-08-2018 02:45 PM
That's correct. I am trying to ping from one laptop that's directly connected to one interface (10.1.251.x) to another on the ASA (10.1.253.x) and vice versa. Win FW is disabled on both laptops. The issue is when I try to ping from laptop 10.1.253.100 to ASA interface 10.1.251.115, ping fails!
I attached the ASA intfs configs and test results.
Thanks..
08-08-2018 02:47 PM - edited 08-08-2018 02:51 PM
Ok, but did you enable the management-access command like I previously suggested?
08-08-2018 03:05 PM - edited 08-08-2018 11:39 PM
Yes. I did!
08-10-2018 03:35 PM
I ended up rebooting the ASA and it worked.
Thanks for your assistance.
08-10-2018 04:33 PM - edited 08-10-2018 04:34 PM
I have noticed a few areas lately when working with the Cisco ASA firewalls that a reboot or "clear conn" has fixed the odd issue(s). In the latest case I was running 9.9(2). Glad it worked out for you.
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