topic Re: Unable to ping through ASA in Network Security

Unable to ping through ASA

nathanvicencio — Fri, 11 Oct 2019 20:50:05 GMT

I am currently trying to simply ping through my ASA from Router 1 at 10.10.0.1 to my Router 7 at a public ip address. But I am unable to ping through. I have set up nat and have applied the access rule permit ip any any, and have applied them to every into every interface on the ASA. But I am still unable to ping through.

Also router 1 can ping to inside interface of ASA at 10.10.0.2 and Router 7 can ping the outside interface of the ASA at the same public ip address.

ASA config:

show run
: Saved
:
: Serial Number: JMX2048Y0SR
: Hardware: ASA5505, 512 MB RAM, CPU Geode 500 MHz
:
ASA Version 9.1(6)
!
hostname TeamB-ASA-Outside-towards-ISP
enable password 8Ry2YjIyt7RRXU24 encrypted
names
!
interface Ethernet0/0
!
interface Ethernet0/1
switchport access vlan 2
!
interface Ethernet0/2
!
interface Ethernet0/3
shutdown
!
interface Ethernet0/4
shutdown
!
interface Ethernet0/5
<--- More ---> switchport access vlan 10
!
interface Ethernet0/6
shutdown
!
interface Ethernet0/7
shutdown
!
interface Vlan2
nameif outside
security-level 0
ip address Some public ip address 255.255.0.0
!
interface Vlan10
nameif inside
security-level 100
ip address 10.10.0.2 255.255.255.248
!
ftp mode passive
object network inside-net
subnet 100.2.0.0 255.255.0.0
access-list 101 extended permit ip any any
pager lines 24
mtu inside 1500
<--- More ---> mtu outside 1500
no failover
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
no arp permit-nonconnected
!
object network inside-net
nat (inside,outside) dynamic interface
access-group 101 in interface inside
access-group 101 out interface inside
access-group 101 in interface outside
access-group 101 out interface outside
route outside 0.0.0.0 0.0.0.0 PUBLIC IP ADDRES OF Router 7
timeout xlate 3:00:00
timeout pat-xlate 0:00:30
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
user-identity default-domain LOCAL
<--- More ---> no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart warmstart
crypto ipsec security-association pmtu-aging infinite
crypto ca trustpool policy
telnet timeout 5
ssh stricthostkeycheck
ssh timeout 5
ssh key-exchange group dh-group1-sha1
console timeout 0

threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
webvpn
anyconnect-essentials
!
class-map inspection_default
match default-inspection-traffic
class-map inspection_defualt
!
!
policy-map type inspect dns preset_dns_map
parameters
<--- More ---> message-length maximum client auto
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect ip-options
inspect netbios
inspect rsh
inspect rtsp
inspect skinny
inspect esmtp
inspect sqlnet
inspect sunrpc
inspect tftp
inspect sip
inspect xdmcp
inspect icmp
!
service-policy global_policy global
prompt hostname context
no call-home reporting anonymous
<--- More ---> call-home
profile CiscoTAC-1
no active
destination address http https://tools.cisco.com/its/service/oddce/services/DDCEService
destination address email callhome@cisco.com
destination transport-method http
subscribe-to-alert-group diagnostic
subscribe-to-alert-group environment
subscribe-to-alert-group inventory periodic monthly
subscribe-to-alert-group configuration periodic monthly
subscribe-to-alert-group telemetry periodic daily
Cryptochecksum:4ed7c2ab79f15f50a5709e66f0e008b4
: end

Re: Unable to ping through ASA

Marius Gunnerud — Fri, 11 Oct 2019 19:43:17 GMT

Your configuration looks correct for allowing ICMP from inside to outside. Though the NAT you posted is for subnet 100.2.0.0/24, not that it matters for this post. However if router 7 actually has a public IP and you just changed it in this post, then you need to add a NAT rule.

Otherwise, I would suggest doing a reboot of the ASA as it seems there might be some old settings hanging in a cache. Try the ping again after reboot.

Re: Unable to ping through ASA

nathanvicencio — Fri, 11 Oct 2019 19:51:02 GMT

So router 7 does indeed have a public ip address and what is this Nat rule that you suggested?

Also I did indeed restart the ASA and i still cannot ping through. Do you have any other ideas? I've been trying to trouble shoot this problem for a while now.

Re: Unable to ping through ASA

Marius Gunnerud — Fri, 11 Oct 2019 19:57:58 GMT

Currently your NAT configuration, that you have posted, is this:

object network inside-net
subnet 100.2.0.0 255.255.0.0
nat (inside,outside) dynamic interface

So to allow 10.10.0.1 to ping router 7 which has a public IP you would need to add a NAT statement for that IP or subnet:

object network inside-net2

subnet 10.10.0.0 255.255.255.248

nat (inside,outside) dynamic interface

Re: Unable to ping through ASA

nathanvicencio — Fri, 11 Oct 2019 20:32:14 GMT

So, We do have access to a public ip address so i changed the outside ASA and router 7 ports to the correct public ip addresses. so the original NAT statement was correct i just had the Ip addresses wrong. But now that they are fixed

Here is the updated config with the correct public ip addresses on the outside interface of the asa.

I am also still unable to ping through the ASA

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2019.10.11 15:29:09 =~=~=~=~=~=~=~=~=~=~=~=
show run
: Saved
:
: Serial Number: JMX2048Y0SR

: Hardware: ASA5505, 512 MB RAM, CPU Geode 500 MHz
:
ASA Version 9.1(6)
!
hostname TeamB-ASA-Outside-towards-ISP
enable password 8Ry2YjIyt7RRXU24 encrypted
names
!
interface Ethernet0/0
!
interface Ethernet0/1
switchport access vlan 2
!
interface Ethernet0/2
!
interface Ethernet0/3
shutdown
!
interface Ethernet0/4
shutdown
!
interface Ethernet0/5
<--- More ---> switchport access vlan 10
!
interface Ethernet0/6
shutdown
!
interface Ethernet0/7
shutdown
!
interface Vlan2
nameif outside
security-level 0
ip address THE PUBLIC IP ADDRESS
!
interface Vlan10
nameif inside
security-level 100
ip address 10.10.0.2 255.255.255.248
!
ftp mode passive
object network inside-net
subnet 100.2.0.0 255.255.0.0
access-list 101 extended permit ip any any
pager lines 24
mtu outside 1500
<--- More ---> mtu inside 1500
no failover
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
no arp permit-nonconnected
!
object network inside-net
nat (inside,outside) dynamic interface
access-group 101 in interface outside
access-group 101 out interface outside
access-group 101 in interface inside
access-group 101 out interface inside
route outside 0.0.0.0 0.0.0.0 100.2.0.254 1
timeout xlate 3:00:00
timeout pat-xlate 0:00:30
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
user-identity default-domain LOCAL
<--- More ---> no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart warmstart
crypto ipsec security-association pmtu-aging infinite
crypto ca trustpool policy
telnet timeout 5
ssh stricthostkeycheck
ssh timeout 5
ssh key-exchange group dh-group1-sha1
console timeout 0

Re: Unable to ping through ASA

bhargavdesai — Sat, 12 Oct 2019 03:40:02 GMT

Can you post the packet-tracer output.

Packet-tracer input inside icmp SOURCE-IP 8 0 DESTINATION-IP detailed.

HTH
### RATE ALL HELPFUL RESPONSES ###

Re: Unable to ping through ASA

Marius Gunnerud — Sat, 12 Oct 2019 22:45:18 GMT

you still have an incorrect NAT statement for 10.10.0.1 to be able to ping R7.

object network inside-net
subnet 100.2.0.0 255.255.0.0 <-- This subnet does not match the IP you are trying to ping R7 from. If your default route is correct then this is you public subnet

nat (inside,outside) dynamic interface

interface Vlan10
nameif inside
security-level 100
ip address 10.10.0.2 255.255.255.248 <-- You need NAT for this subnet

You neet to configure NAT for the inside network subnet. The NAT statment you have provided in the configuration is for the 100.2.0.0/16 subnet, you need to configure NAT for 10.10.0.0/29 subnet as I have mentioned in my previous post.