Problems configuring NAT on ASA (CML)

[gianlucaplatania]

Hello everyone, 

I'm building a topology on CML but I'm having problems configuring NAT on my ASA. I already discussed this a bit on the comment section of a previously solved question, but I felt the need of a new discussion.

I have a 5 switches topology, one of which is connected to the ASA that has another interface on the outside (towards my physical gateway). The asa can ping anything inside my network, and anything outside (i.e. Google) but I can't seem to ping the outside from my network. Here's the configuration. Any idea? I already tried to create a more specific object putting my networks one by one, but nothing changed. Here is a topology screen and the ASA configuration.

 

ASA Version 9.15(1)1
!
hostname ciscoasa
enable password ***** pbkdf2
service-module 0 keepalive-timeout 4
service-module 0 keepalive-counter 6
names
no mac-address auto

!
interface GigabitEthernet0/0
nameif inside
security-level 100
ip address 11.0.0.2 255.255.255.252
!
interface GigabitEthernet0/1
nameif outside
security-level 0
ip address 192.168.1.12 255.255.255.0
!
interface GigabitEthernet0/2
shutdown
no nameif
no security-level
no ip address
!
interface GigabitEthernet0/3
shutdown
no nameif
no security-level
no ip address
!
interface GigabitEthernet0/4
shutdown
no nameif
no security-level
no ip address
!
interface Management0/0
no management-only
shutdown
no nameif
no security-level
no ip address
!
ftp mode passive
object network obj_any
subnet 0.0.0.0 0.0.0.0
pager lines 23
mtu outside 1500
mtu inside 1500
no failover
no failover wait-disable
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
no arp permit-nonconnected
arp rate-limit 8192
!
object network obj_any
nat (inside,outside) dynamic interface
router ospf 1
router-id 12.12.12.12
network 11.0.0.0 255.255.255.252 area 0
log-adj-changes
default-information originate
!
route outside 0.0.0.0 0.0.0.0 192.168.1.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 sctp 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
timeout conn-holddown 0:00:15
timeout igp stale-route 0:01:10
user-identity default-domain LOCAL
aaa authentication login-history
no snmp-server location
no snmp-server contact
crypto ipsec security-association pmtu-aging infinite
crypto ca trustpoint _SmartCallHome_ServerCA
no validation-usage
crl configure
crypto ca trustpool policy
auto-import
crypto ca certificate chain _SmartCallHome_ServerCA
certificate ca 0509
308205b7 3082039f a0030201 02020205 09300d06 092a8648 86f70d01 01050500
3045310b 30090603 55040613 02424d31 19301706 0355040a 13105175 6f566164
6973204c 696d6974 6564311b 30190603 55040313 1251756f 56616469 7320526f
6f742043 41203230 1e170d30 36313132 34313832 3730305a 170d3331 31313234
31383233 33335a30 45310b30 09060355 04061302 424d3119 30170603 55040a13
1051756f 56616469 73204c69 6d697465 64311b30 19060355 04031312 51756f56
61646973 20526f6f 74204341 20323082 0222300d 06092a86 4886f70d 01010105
00038202 0f003082 020a0282 0201009a 18ca4b94 0d002daf 03298af0 0f81c8ae
4c19851d 089fab29 4485f32f 81ad321e 9046bfa3 86261a1e fe7e1c18 3a5c9c60
172a3a74 8333307d 615411cb edabe0e6 d2a27ef5 6b6f18b7 0a0b2dfd e93eef0a
c6b310e9 dcc24617 f85dfda4 daff9e49 5a9ce633 e62496f7 3fba5b2b 1c7a35c2
d667feab 66508b6d 28602bef d760c3c7 93bc8d36 91f37ff8 db1113c4 9c7776c1
aeb7026a 817aa945 83e205e6 b956c194 378f4871 6322ec17 6507958a 4bdf8fc6
5a0ae5b0 e35f5e6b 11ab0cf9 85eb44e9 f80473f2 e9fe5c98 8cf573af 6bb47ecd
d45c022b 4c39e1b2 95952d42 87d7d5b3 9043b76c 13f1dedd f6c4f889 3fd175f5
92c391d5 8a88d090 ecdc6dde 89c26571 968b0d03 fd9cbf5b 16ac92db eafe797c
adebaff7 16cbdbcd 252be51f fb9a9fe2 51cc3a53 0c48e60e bdc9b476 0652e611
13857263 0304e004 362b2019 02e874a7 1fb6c956 66f07525 dc67c10e 616088b3
3ed1a8fc a3da1db0 d1b12354 df44766d ed41d8c1 b222b653 1cdf351d dca1772a
31e42df5 e5e5dbc8 e0ffe580 d70b63a0 ff33a10f ba2c1515 ea97b3d2 a2b5bef2
8c961e1a 8f1d6ca4 6137b986 7333d797 969e237d 82a44c81 e2a1d1ba 675f9507
a32711ee 16107bbc 454a4cb2 04d2abef d5fd0c51 ce506a08 31f991da 0c8f645c
03c33a8b 203f6e8d 673d3ad6 fe7d5b88 c95efbcc 61dc8b33 77d34432 35096204
921610d8 9e2747fb 3b21e3f8 eb1d5b02 03010001 a381b030 81ad300f 0603551d
130101ff 04053003 0101ff30 0b060355 1d0f0404 03020106 301d0603 551d0e04
1604141a 8462bc48 4c332504 d4eed0f6 03c41946 d1946b30 6e060355 1d230467
30658014 1a8462bc 484c3325 04d4eed0 f603c419 46d1946b a149a447 3045310b
30090603 55040613 02424d31 19301706 0355040a 13105175 6f566164 6973204c
696d6974 6564311b 30190603 55040313 1251756f 56616469 7320526f 6f742043
41203282 02050930 0d06092a 864886f7 0d010105 05000382 0201003e 0a164d9f
065ba8ae 715d2f05 2f67e613 4583c436 f6f3c026 0c0db547 645df8b4 72c946a5
03182755 89787d76 ea963480 1720dce7 83f88dfc 07b8da5f 4d2e67b2 84fdd944
fc775081 e67cb4c9 0d0b7253 f8760707 4147960c fbe08226 93558cfe 221f6065
7c5fe726 b3f73290 9850d437 7155f692 2178f795 79faf82d 26876656 3077a637
78335210 58ae3f61 8ef26ab1 ef187e4a 5963ca8d a256d5a7 2fbc561f cf39c1e2
fb0aa815 2c7d4d7a 63c66c97 443cd26f c34a170a f890d257 a21951a5 2d9741da
074fa950 da908d94 46e13ef0 94fd1000 38f53be8 40e1b46e 561a20cc 6f588ded
2e458fd6 e9933fe7 b12cdf3a d6228cdc 84bb226f d0f8e4c6 39e90488 3cc3baeb
557a6d80 9924f56c 01fbf897 b0945beb fdd26ff1 77680d35 6423acb8 55a103d1
4d4219dc f8755956 a3f9a849 79f8af0e b911a07c b76aed34 d0b62662 381a870c
f8e8fd2e d3907f07 912a1dd6 7e5c8583 99b03808 3fe95ef9 3507e4c9 626e577f
a75095f7 bac89be6 8ea201c5 d666bf79 61f33c1c e1b9825c 5da0c3e9 d848bd19
a2111419 6eb2861b 683e4837 1a88b75d 965e9cc7 ef276208 e291195c d2f121dd
ba174282 97718153 31a99ff6 7d62bf72 e1a3931d cc8a265a 0938d0ce d70d8016
b478a53a 874c8d8a a5d54697 f22c10b9 bc5422c0 01506943 9ef4b2ef 6df8ecda
f1e3b1ef df918f54 2a0b25c1 2619c452 100565d5 8210eac2 31cd2e
quit
telnet timeout 5
ssh stricthostkeycheck
ssh timeout 5
ssh version 2
ssh key-exchange group dh-group14-sha256
console timeout 0
console serial
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
dynamic-access-policy-record DfltAccessPolicy
!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns migrated_dns_map_1
parameters
message-length maximum client auto
message-length maximum 512
no tcp-inspection
policy-map global_policy
class inspection_default
inspect dns migrated_dns_map_1
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 snmp
policy-map type inspect dns migrated_dns_map_2
parameters
message-length maximum client auto
message-length maximum 512
no tcp-inspection
!
service-policy global_policy global
prompt hostname context
no call-home reporting anonymous
call-home
profile License
destination address http https://tools.cisco.com/its/service/oddce/services/DDCEService
destination transport-method http
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:dd8ff72bf9a5d8c738c93a50f4b218e5

[balaji.bandi]

what network not able to reach ?  when you do trace to 8.8.8.8 what hop it stops ? ASA ?

From ASA can you show ip route ? 

interface GigabitEthernet0/0
nameif inside
security-level 100
ip address 11.0.0.2 255.255.255.252 <<-- is this subnet correct - it got only 2 usable Addresses here

I would rather go with controlled ( add the network in object group ) 

object network obj_any
subnet 11.0.0.0 255.255.255.252     <-- in this case thie IP 11.0.0.1 with gateway 11.0.0.2 shoud be able to reach internet
nat (inside,outside) dynamic interface

[gianlucaplatania]

Hey thanks for answering

this is my show route:

Gateway of last resort is 192.168.1.254 to network 0.0.0.0

S* 0.0.0.0 0.0.0.0 [1/0] via 192.168.1.254, outside
O 10.0.0.0 255.255.255.0 [110/12] via 11.0.0.1, 00:00:09, inside
O 10.0.1.0 255.255.255.252 [110/11] via 11.0.0.1, 00:00:39, inside
O 10.0.1.4 255.255.255.252 [110/12] via 11.0.0.1, 00:00:39, inside
O 10.0.2.0 255.255.255.252 [110/12] via 11.0.0.1, 00:00:29, inside
O 10.0.2.4 255.255.255.252 [110/11] via 11.0.0.1, 00:00:39, inside
C 11.0.0.0 255.255.255.252 is directly connected, inside
L 11.0.0.2 255.255.255.255 is directly connected, inside

O 172.16.0.0 255.255.255.248 [110/11] via 11.0.0.1, 00:00:09, inside
C 192.168.1.0 255.255.255.0 is directly connected, outside
L 192.168.1.12 255.255.255.255 is directly connected, outside

---------------------------------------------------------------------------

ip address 11.0.0.2 255.255.255.252 is correct, that's the ptp between the switch and the ASA.

---------------------------------------------------------------------------

Adding that piece of configuration didn't change the situation. The switch with 11.0.0.1 isn't able to ping 8.8.8.8

[balaji.bandi · Accepted solution]

Can you post-show ip route on the connected not (not from ASA)

also for testing add the below lines to ASA :

access-list bb_acl extended permit ip any any
access-group bb_acl in interface outside

Try to ping from connected inside device ?

[gianlucaplatania]

Well it works, but I'm wondering why do I need an access list allowing traffic from the outside interface considering that it should be already allowed? Could you explain what's the reason of this? 

[balaji.bandi]

I do not see in your config there is an access-list to allow traffic? (do you ? since big config i may be missed - so i suggested that way).

Since you did not even see x-late or show nat translation interface inside (0) so the packet not even reaching to NAT

here is ASA traffic flow to understand :

https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/113396-asa-packet-flow-00.html

if you do packet tracer 

packet-tracer input inside tcp 11.0.0.1 12345 8.8.8.8 - you see DROP in ACL.

[gianlucaplatania]

Thank you so much! I'd say I might close this thread

[paul driver · Accepted solution]

Hello
As by default icmp inspection is not enabled on the firewall as it is a stateless connection as such it will be blocked when an echo reply is attempted from the lower fw interface (outside) towards the higher fw interface (inside)

So to allow this you could append acl as previously suggested or you could enable inspection for icmp within the global policy-map for the fw as shown below:

policy-map global_policy
class inspection_default
inspect icmp

[gianlucaplatania]

Thank you this was enlightning! I marked it as a correct answer as well so that everyone can take advantage of this discussion.