<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: NAT problem - traffic from internet not reaching internal so in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338974#M345516</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In some cases where routing is the problem ICMP might act a bit differently than TCP connections for example.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ICMP might work and TCP not because of asymmetric routing. (especially when ASA is in the picture)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looking at your L3 Switch routing table I can only see ONE network adverticed with OSPF and its from the ASA. And since the ASA is the default gateway it wouldnt even need to advertice that network as the traffic would always come to the ASA with default route.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I am not sure where the OSPF is needed in this case since it seems to only run between the L3 switch and ASA. I would personally handle it with Static routing at both ASA and L3 switch since the OSPF doesnt really bring that much into the picture.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would only need static default route from L3 Switch towards ASA and ASA would need route for the LAN network towards its &lt;STRONG&gt;"inside"&lt;/STRONG&gt; interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It just somehow seems to me like something to do with routing but doesnt make sense especially when the ASA should be the only route out of your network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 05 Aug 2013 20:44:52 GMT</pubDate>
    <dc:creator>Jouni Forss</dc:creator>
    <dc:date>2013-08-05T20:44:52Z</dc:date>
    <item>
      <title>NAT problem - traffic from internet not reaching internal source.</title>
      <link>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338962#M345499</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have just added a 10.8.0.0 /16 network and I am having trouble figuring our why I cannot get trafiic back to devices on this network.&amp;nbsp; Traffic to/from our existing 172.16.0.0 networks works fine, but not the 10.8 network.&amp;nbsp; Ping requests are returned, but not internet traffic.&amp;nbsp; When I look at traffic I see these errors:&amp;nbsp; "&lt;/P&gt;&lt;P&gt;3&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Jul 31 2013&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;09:07:59&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;305006&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;10.8.0.10&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;56070&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;portmap translation creation failed for tcp src inside:74.125.225.128/80 dst inside:10.8.0.10/56070" and &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P&gt;3&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Jul 31 2013&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;09:09:33&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;305006&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;10.8.0.10&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;56071&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;portmap translation creation failed for tcp src inside:74.125.225.128/80 dst inside:10.8.0.10/56071"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, it appears that the traffic is returned, hits the inside interface, but is not being sent back to the proper device.&amp;nbsp; Can anyone see anything in this config that may be causing this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;ASA Version 8.2(2) &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;hostname ***-ASA5510&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;names&lt;/P&gt;&lt;P&gt;name 172.16.250.15 SBS&lt;/P&gt;&lt;P&gt;name 172.16.0.0 inside-nets&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/0&lt;/P&gt;&lt;P&gt; description Link to ***&lt;/P&gt;&lt;P&gt; nameif outside&lt;/P&gt;&lt;P&gt; security-level 0&lt;/P&gt;&lt;P&gt; ip address ***.***.***.*** 255.255.255.240 &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/1&lt;/P&gt;&lt;P&gt; nameif inside&lt;/P&gt;&lt;P&gt; security-level 100&lt;/P&gt;&lt;P&gt; ip address 172.16.20.1 255.255.255.248 &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/2&lt;/P&gt;&lt;P&gt; shutdown&lt;/P&gt;&lt;P&gt; nameif ***&lt;/P&gt;&lt;P&gt; security-level 0&lt;/P&gt;&lt;P&gt; ip address ***.***.***.*** 255.255.255.252 &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/3&lt;/P&gt;&lt;P&gt; nameif GuestWireless&lt;/P&gt;&lt;P&gt; security-level 0&lt;/P&gt;&lt;P&gt; ip address 172.16.30.1 255.255.255.0 &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Management0/0&lt;/P&gt;&lt;P&gt; nameif management&lt;/P&gt;&lt;P&gt; security-level 100&lt;/P&gt;&lt;P&gt; no ip address&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;banner exec Unauthorized Access is Prohibited.&lt;/P&gt;&lt;P&gt;banner login No Unauthorized Access.&amp;nbsp; All Access Attempts Will Be Logged.&lt;/P&gt;&lt;P&gt;banner motd&amp;nbsp; Authorized Access Only.&lt;/P&gt;&lt;P&gt;ftp mode passive&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;same-security-traffic permit inter-interface&lt;/P&gt;&lt;P&gt;same-security-traffic permit intra-interface&lt;/P&gt;&lt;P&gt;access-list outside_access_in extended deny ip 150.70.0.0 255.255.0.0 any &lt;/P&gt;&lt;P&gt;access-list outside_access_in remark ICMP type 11 for Windows Traceroute&lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit icmp any any time-exceeded &lt;/P&gt;&lt;P&gt;access-list outside_access_in remark ICMP type 3 for Cisco and Linux&lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit icmp any any unreachable &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp any host *.*.*.* eq 993 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp any host *.*.*.* eq imap4 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp any host *.*.*.* eq 4125 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp any host *.*.*.* eq https &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp any host *.*.*.* eq https &lt;/P&gt;&lt;P&gt;access-list remote-users_splitTunnelAcl standard permit inside-nets 255.255.0.0&amp;nbsp; &lt;/P&gt;&lt;P&gt;access-list inside_nat0_outbound extended permit ip inside-nets 255.255.0.0 172.16.100.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;pager lines 24&lt;/P&gt;&lt;P&gt;logging enable&lt;/P&gt;&lt;P&gt;logging timestamp&lt;/P&gt;&lt;P&gt;logging list Config_Changes level emergencies&lt;/P&gt;&lt;P&gt;logging list Config_Changes message 113019&lt;/P&gt;&lt;P&gt;logging list Config_Changes message 111007-111009&lt;/P&gt;&lt;P&gt;logging list Config_Changes message 113012&lt;/P&gt;&lt;P&gt;logging list vpn-log level debugging class vpnc&lt;/P&gt;&lt;P&gt;logging trap vpn-log&lt;/P&gt;&lt;P&gt;logging asdm notifications&lt;/P&gt;&lt;P&gt;logging facility 23&lt;/P&gt;&lt;P&gt;logging device-id hostname&lt;/P&gt;&lt;P&gt;logging host inside 172.16.250.41&lt;/P&gt;&lt;P&gt;logging debug-trace&lt;/P&gt;&lt;P&gt;logging permit-hostdown&lt;/P&gt;&lt;P&gt;mtu outside 1500&lt;/P&gt;&lt;P&gt;mtu inside 1500&lt;/P&gt;&lt;P&gt;mtu ISP2 1500&lt;/P&gt;&lt;P&gt;mtu GuestWireless 1500&lt;/P&gt;&lt;P&gt;mtu management 1500&lt;/P&gt;&lt;P&gt;ip local pool remote-user-pool 172.16.100.0-172.16.100.254 mask 255.255.255.0&lt;/P&gt;&lt;P&gt;icmp unreachable rate-limit 10 burst-size 5&lt;/P&gt;&lt;P&gt;asdm location inside-nets 255.255.0.0 inside&lt;/P&gt;&lt;P&gt;no asdm history enable&lt;/P&gt;&lt;P&gt;arp timeout 14400&lt;/P&gt;&lt;P&gt;global (outside) 101 interface&lt;/P&gt;&lt;P&gt;global (ISP2) 101 interface&lt;/P&gt;&lt;P&gt;nat (inside) 0 access-list inside_nat0_outbound&lt;/P&gt;&lt;P&gt;nat (inside) 101 0.0.0.0 0.0.0.0&lt;/P&gt;&lt;P&gt;nat (GuestWireless) 101 0.0.0.0 0.0.0.0&lt;/P&gt;&lt;P&gt;static (inside,outside) tcp interface smtp SBS smtp netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside,outside) tcp interface 4125 SBS 4125 netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside,outside) tcp interface https SBS https netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside,outside) tcp interface imap4 SBS imap4 netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside,outside) tcp interface 993 SBS 993 netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside,outside) tcp interface 6699 Untangle 6699 netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside,***) *.*.*.* SBS netmask 255.255.255.255 dns &lt;/P&gt;&lt;P&gt;static (inside,outside) [public IP] 172.16.170.10 netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;access-group outside_access_in in interface outside&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;router ospf 1&lt;/P&gt;&lt;P&gt; network 10.5.0.0 255.255.0.0 area 0&lt;/P&gt;&lt;P&gt; network 10.8.0.0 255.255.0.0 area 0&lt;/P&gt;&lt;P&gt; network inside-nets 255.255.0.0 area 0&lt;/P&gt;&lt;P&gt; log-adj-changes&lt;/P&gt;&lt;P&gt; default-information originate always&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;route outside 0.0.0.0 0.0.0.0 [Public IP] 1 track 1&lt;/P&gt;&lt;P&gt;route outside 172.16.240.159 255.255.255.255 *.*.*.* 1&lt;/P&gt;&lt;P&gt;timeout xlate 3:00:00&lt;/P&gt;&lt;P&gt;timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02&lt;/P&gt;&lt;P&gt;timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00&lt;/P&gt;&lt;P&gt;timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00&lt;/P&gt;&lt;P&gt;timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute&lt;/P&gt;&lt;P&gt;timeout tcp-proxy-reassembly 0:01:00&lt;/P&gt;&lt;P&gt;dynamic-access-policy-record DfltAccessPolicy&lt;/P&gt;&lt;P&gt;aaa-server SBS-RADIUS protocol radius&lt;/P&gt;&lt;P&gt; reactivation-mode depletion deadtime 1&lt;/P&gt;&lt;P&gt; max-failed-attempts 2&lt;/P&gt;&lt;P&gt;aaa-server SBS-RADIUS (inside) host SBS&lt;/P&gt;&lt;P&gt; key *&lt;/P&gt;&lt;P&gt; radius-common-pw *&lt;/P&gt;&lt;P&gt;aaa authentication ssh console SBS-RADIUS LOCAL&lt;/P&gt;&lt;P&gt;aaa authentication enable console SBS-RADIUS LOCAL&lt;/P&gt;&lt;P&gt;aaa authentication http console SBS-RADIUS LOCAL&lt;/P&gt;&lt;P&gt;aaa authorization exec authentication-server&lt;/P&gt;&lt;P&gt;http server enable&lt;/P&gt;&lt;P&gt;http inside-nets 255.255.0.0 inside&lt;/P&gt;&lt;P&gt;snmp-server host inside 172.16.250.135 community * version 2c&lt;/P&gt;&lt;P&gt;no snmp-server location&lt;/P&gt;&lt;P&gt;no snmp-server contact&lt;/P&gt;&lt;P&gt;snmp-server community *&lt;/P&gt;&lt;P&gt;snmp-server enable traps snmp authentication linkup linkdown coldstart&lt;/P&gt;&lt;P&gt;sla monitor 123&lt;/P&gt;&lt;P&gt; type echo protocol ipIcmpEcho *.*.*.* interface outside&lt;/P&gt;&lt;P&gt; num-packets 3&lt;/P&gt;&lt;P&gt; frequency 10&lt;/P&gt;&lt;P&gt;sla monitor schedule 123 life forever start-time now&lt;/P&gt;&lt;P&gt;crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac &lt;/P&gt;&lt;P&gt;crypto ipsec transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac &lt;/P&gt;&lt;P&gt;crypto ipsec transform-set ESP-DES-SHA esp-des esp-sha-hmac &lt;/P&gt;&lt;P&gt;crypto ipsec transform-set ESP-DES-MD5 esp-des esp-md5-hmac &lt;/P&gt;&lt;P&gt;crypto ipsec transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac &lt;/P&gt;&lt;P&gt;crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac &lt;/P&gt;&lt;P&gt;crypto ipsec transform-set ESP-AES-256-SHA esp-aes-256 esp-sha-hmac &lt;/P&gt;&lt;P&gt;crypto ipsec transform-set ESP-AES-128-SHA esp-aes esp-sha-hmac &lt;/P&gt;&lt;P&gt;crypto ipsec transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac &lt;/P&gt;&lt;P&gt;crypto ipsec transform-set ESP-AES-128-MD5 esp-aes esp-md5-hmac &lt;/P&gt;&lt;P&gt;crypto ipsec security-association lifetime seconds 28800&lt;/P&gt;&lt;P&gt;crypto ipsec security-association lifetime kilobytes 4608000&lt;/P&gt;&lt;P&gt;crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set pfs group1&lt;/P&gt;&lt;P&gt;crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA ESP-3DES-MD5 ESP-DES-SHA ESP-DES-MD5&lt;/P&gt;&lt;P&gt;crypto map outside_map 65535 ipsec-isakmp dynamic SYSTEM_DEFAULT_CRYPTO_MAP&lt;/P&gt;&lt;P&gt;crypto map outside_map interface outside&lt;/P&gt;&lt;P&gt;crypto isakmp enable outside&lt;/P&gt;&lt;P&gt;crypto isakmp policy 65535&lt;/P&gt;&lt;P&gt; authentication pre-share&lt;/P&gt;&lt;P&gt; encryption 3des&lt;/P&gt;&lt;P&gt; hash sha&lt;/P&gt;&lt;P&gt; group 2&lt;/P&gt;&lt;P&gt; lifetime 86400&lt;/P&gt;&lt;P&gt;no crypto isakmp nat-traversal&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;track 1 rtr 123 reachability&lt;/P&gt;&lt;P&gt;telnet timeout 5&lt;/P&gt;&lt;P&gt;ssh inside-nets 255.255.0.0 inside&lt;/P&gt;&lt;P&gt;ssh timeout 60&lt;/P&gt;&lt;P&gt;ssh version 2&lt;/P&gt;&lt;P&gt;console timeout 0&lt;/P&gt;&lt;P&gt;management-access inside&lt;/P&gt;&lt;P&gt;dhcpd address 172.16.30.100-172.16.30.200 GuestWireless&lt;/P&gt;&lt;P&gt;dhcpd dns *.*.*.* *.*.*.* interface GuestWireless&lt;/P&gt;&lt;P&gt;dhcpd option 3 ip 172.16.30.1 interface GuestWireless&lt;/P&gt;&lt;P&gt;dhcpd enable GuestWireless&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;threat-detection basic-threat&lt;/P&gt;&lt;P&gt;threat-detection statistics port&lt;/P&gt;&lt;P&gt;threat-detection statistics protocol&lt;/P&gt;&lt;P&gt;threat-detection statistics access-list&lt;/P&gt;&lt;P&gt;threat-detection statistics tcp-intercept rate-interval 30 burst-rate 400 average-rate 200&lt;/P&gt;&lt;P&gt;ntp server SBS&lt;/P&gt;&lt;P&gt;webvpn&lt;/P&gt;&lt;P&gt;group-policy remote-users internal&lt;/P&gt;&lt;P&gt;group-policy remote-users attributes&lt;/P&gt;&lt;P&gt; dns-server value 172.16.250.15&lt;/P&gt;&lt;P&gt; vpn-idle-timeout none&lt;/P&gt;&lt;P&gt; vpn-session-timeout none&lt;/P&gt;&lt;P&gt; vpn-tunnel-protocol IPSec &lt;/P&gt;&lt;P&gt; split-tunnel-policy tunnelspecified&lt;/P&gt;&lt;P&gt; split-tunnel-network-list value remote-users_splitTunnelAcl&lt;/P&gt;&lt;P&gt; default-domain value ***.local&lt;/P&gt;&lt;P&gt;tunnel-group remote-users type remote-access&lt;/P&gt;&lt;P&gt;tunnel-group remote-users general-attributes&lt;/P&gt;&lt;P&gt; address-pool remote-user-pool&lt;/P&gt;&lt;P&gt; authentication-server-group SBS-RADIUS&lt;/P&gt;&lt;P&gt; default-group-policy remote-users&lt;/P&gt;&lt;P&gt;tunnel-group remote-users ipsec-attributes&lt;/P&gt;&lt;P&gt; pre-shared-key ***&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;class-map inspection_default&lt;/P&gt;&lt;P&gt; match default-inspection-traffic&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;policy-map type inspect dns preset_dns_map&lt;/P&gt;&lt;P&gt; parameters&lt;/P&gt;&lt;P&gt;&amp;nbsp; message-length maximum client auto&lt;/P&gt;&lt;P&gt;&amp;nbsp; message-length maximum 512&lt;/P&gt;&lt;P&gt;policy-map global_policy&lt;/P&gt;&lt;P&gt; class inspection_default&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect dns preset_dns_map &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect ftp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect h323 h225 &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect h323 ras &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect ip-options &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect netbios &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect rsh &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect rtsp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect skinny&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect sqlnet &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect sunrpc &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect tftp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect sip&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect xdmcp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect icmp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect snmp &lt;/P&gt;&lt;P&gt; class class-default&lt;/P&gt;&lt;P&gt;&amp;nbsp; set connection decrement-ttl&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;service-policy global_policy global&lt;/P&gt;&lt;P&gt;prompt hostname context &lt;/P&gt;&lt;P&gt;call-home&lt;/P&gt;&lt;P&gt; profile CiscoTAC-1&lt;/P&gt;&lt;P&gt;&amp;nbsp; no active&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; destination address http &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://tools.cisco.com/its/service/oddce/services/DDCEService" target="_blank"&gt;https://tools.cisco.com/its/service/oddce/services/DDCEService&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; destination address email &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:callhome@cisco.com" target="_blank"&gt;callhome@cisco.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; destination transport-method http&lt;/P&gt;&lt;P&gt;&amp;nbsp; subscribe-to-alert-group diagnostic&lt;/P&gt;&lt;P&gt;&amp;nbsp; subscribe-to-alert-group environment&lt;/P&gt;&lt;P&gt;&amp;nbsp; subscribe-to-alert-group inventory periodic monthly&lt;/P&gt;&lt;P&gt;&amp;nbsp; subscribe-to-alert-group configuration periodic monthly&lt;/P&gt;&lt;P&gt;&amp;nbsp; subscribe-to-alert-group telemetry periodic daily&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 02:19:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338962#M345499</guid>
      <dc:creator>skoch1skoch</dc:creator>
      <dc:date>2019-03-12T02:19:25Z</dc:date>
    </item>
    <item>
      <title>NAT problem - traffic from internet not reaching internal source</title>
      <link>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338963#M345502</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there something wrong with the routing?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The logs indicate that its trying to create a Dynamic PAT for traffic from &lt;STRONG&gt;"inside"&lt;/STRONG&gt; to &lt;STRONG&gt;"inside".&lt;/STRONG&gt; The connections should be going to &lt;STRONG&gt;"outside"&lt;/STRONG&gt; I would imagine?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The reason you see the "portmap" log message is that the traffic is trying to head out through the &lt;STRONG&gt;"inside"&lt;/STRONG&gt; interface and &lt;STRONG&gt;"inside"&lt;/STRONG&gt; interface doesnt have any matching &lt;STRONG&gt;"global"&lt;/STRONG&gt; command. (Which it shouldnt have I imagine)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So why is the traffic heading to &lt;STRONG&gt;"inside"&lt;/STRONG&gt;?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you perhaps share the output of &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;show route&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jul 2013 14:48:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338963#M345502</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-07-31T14:48:52Z</dc:date>
    </item>
    <item>
      <title>Re: NAT problem - traffic from internet not reaching internal so</title>
      <link>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338964#M345504</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One thing that can cause the ASA to forward traffic to wrong place are "static" NAT configurations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But I would imagine that is not the case here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But I still wonder how/why the traffic is forwarded to &lt;STRONG&gt;"inside"&lt;/STRONG&gt; according to the above log messages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You do have static default route pointing out of the ASA so to my understanding that should be prefered for the public destination IP address shown in the logs no matter what routes the dynamic routing protocol might advertice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You seem to be using OSPF for the routing. I have never to this day used any dynamic routing protocol on the ASA. It has always been static routing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jul 2013 14:51:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338964#M345504</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-07-31T14:51:10Z</dc:date>
    </item>
    <item>
      <title>NAT problem - traffic from internet not reaching internal source</title>
      <link>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338965#M345506</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The routing from inside to inside is confusing me also.&amp;nbsp; Here is the routing table:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * - candidate default, U - per-user static route, o - ODR&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; P - periodic downloaded static route&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gateway of last resort is [ISP Gateway] to network 0.0.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; [Public Network] 255.255.255.240 is directly connected, outside&lt;/P&gt;&lt;P&gt;O&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.180.0 255.255.255.0 [110/11] via 172.16.20.2, 45:27:17, inside&lt;/P&gt;&lt;P&gt;O&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.170.0 255.255.255.0 [110/11] via 172.16.20.2, 45:27:17, inside&lt;/P&gt;&lt;P&gt;O&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.250.0 255.255.255.0 [110/11] via 172.16.20.2, 45:27:17, inside&lt;/P&gt;&lt;P&gt;O&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.251.0 255.255.255.0 [110/11] via 172.16.20.2, 45:27:17, inside&lt;/P&gt;&lt;P&gt;O&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.240.0 255.255.255.0 [110/11] via 172.16.20.2, 45:27:17, inside&lt;/P&gt;&lt;P&gt;O&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.230.0 255.255.255.0 [110/11] via 172.16.20.2, 45:27:17, inside&lt;/P&gt;&lt;P&gt;O&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.220.0 255.255.255.0 [110/11] via 172.16.20.2, 45:27:17, inside&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.30.0 255.255.255.0 is directly connected, GuestWireless&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.20.0 255.255.255.248 is directly connected, inside&lt;/P&gt;&lt;P&gt;S&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.240.159 255.255.255.255 [1/0] via [ISP Gateway], outside&lt;/P&gt;&lt;P&gt;O&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.99.0 255.255.255.0 [110/11] via 172.16.20.2, 45:27:17, inside&lt;/P&gt;&lt;P&gt;O&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.8.0.0 255.255.0.0 [110/11] via 172.16.20.2, 45:27:17, inside&lt;/P&gt;&lt;P&gt;O&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.5.0.0 255.255.0.0 [110/11] via 172.16.20.2, 45:27:17, inside&lt;/P&gt;&lt;P&gt;S*&amp;nbsp;&amp;nbsp; 0.0.0.0 0.0.0.0 [1/0] via [ISP Gateway], outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the help!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jul 2013 17:05:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338965#M345506</guid>
      <dc:creator>skoch1skoch</dc:creator>
      <dc:date>2013-07-31T17:05:22Z</dc:date>
    </item>
    <item>
      <title>NAT problem - traffic from internet not reaching internal source</title>
      <link>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338966#M345508</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you launch a packet tracer on the outside interface toward a host in the 10.8.0.0/16 network ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;packet-tracer input outside src-public_ip 1234 10.8.2.2 1234&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Aug 2013 20:36:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338966#M345508</guid>
      <dc:creator>turbo_engine26</dc:creator>
      <dc:date>2013-08-02T20:36:06Z</dc:date>
    </item>
    <item>
      <title>NAT problem - traffic from internet not reaching internal source</title>
      <link>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338967#M345509</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here's the output of the packet-tracer:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA5510# packet-tracer input outside tcp &lt;EM&gt;public_ip&lt;/EM&gt; 1234 10.8.2.2 12$&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 1&lt;/P&gt;&lt;P&gt;Type: ACCESS-LIST&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Implicit Rule&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;MAC Access list&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 2&lt;/P&gt;&lt;P&gt;Type: FLOW-LOOKUP&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;Found no matching flow, creating a new flow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 3&lt;/P&gt;&lt;P&gt;Type: ROUTE-LOOKUP&lt;/P&gt;&lt;P&gt;Subtype: input&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;in&amp;nbsp;&amp;nbsp; 10.8.0.0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 255.255.0.0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 4&lt;/P&gt;&lt;P&gt;Type: ACCESS-LIST&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: DROP&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Implicit Rule&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Result:&lt;/P&gt;&lt;P&gt;input-interface: outside&lt;/P&gt;&lt;P&gt;input-status: up&lt;/P&gt;&lt;P&gt;input-line-status: up&lt;/P&gt;&lt;P&gt;output-interface: inside&lt;/P&gt;&lt;P&gt;output-status: up&lt;/P&gt;&lt;P&gt;output-line-status: up&lt;/P&gt;&lt;P&gt;Action: drop&lt;/P&gt;&lt;P&gt;Drop-reason: (acl-drop) Flow is denied by configured rule&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;...so, it seems that an ACL is blocking the return traffic somehow.&amp;nbsp; I added these two statements to the ACL:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp any 10.8.0.0 255.255.0.0 eq 1234&lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit ip any 10.8.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I reran the packet-tracer and the connection was still blocked by an acl-drop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA5510(config)# packet-tracer input outside tcp &lt;EM&gt;public-ip&lt;/EM&gt; 1234 10.$&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 1&lt;/P&gt;&lt;P&gt;Type: FLOW-LOOKUP&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;Found no matching flow, creating a new flow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 2&lt;/P&gt;&lt;P&gt;Type: ROUTE-LOOKUP&lt;/P&gt;&lt;P&gt;Subtype: input&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;in&amp;nbsp;&amp;nbsp; 10.8.0.0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 255.255.0.0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 3&lt;/P&gt;&lt;P&gt;Type: ACCESS-LIST&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: DROP&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Implicit Rule&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Result:&lt;/P&gt;&lt;P&gt;input-interface: outside&lt;/P&gt;&lt;P&gt;input-status: up&lt;/P&gt;&lt;P&gt;input-line-status: up&lt;/P&gt;&lt;P&gt;output-interface: inside&lt;/P&gt;&lt;P&gt;output-status: up&lt;/P&gt;&lt;P&gt;output-line-status: up&lt;/P&gt;&lt;P&gt;Action: drop&lt;/P&gt;&lt;P&gt;Drop-reason: (acl-drop) Flow is denied by configured rule&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I cleared the ACL counter on the outside_access_in ACL and re-ran the packet-tracer:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA5510# clear access-list outside_access_in counters&lt;/P&gt;&lt;P&gt;ASA5510# show access-list&lt;/P&gt;&lt;P&gt;access-list cached ACL log flows: total 0, denied 0 (deny-flow-max 4096)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; alert-interval 300&lt;/P&gt;&lt;P&gt;access-list outside_access_in; 16 elements; name hash: 0x6892a938&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 1 extended deny ip 150.70.0.0 255.255.0.0 any (hitcnt=0) 0x247e4f19&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 2 remark ICMP type 11 for Windows Traceroute&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 3 extended permit icmp any any time-exceeded (hitcnt=0) 0x03690eb3&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 4 remark ICMP type 3 for Cisco and Linux&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 5 extended permit icmp any any unreachable (hitcnt=1) 0x5c2fa603&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 10 extended permit tcp any host &lt;EM&gt;public_ip &lt;/EM&gt;eq 993 (hitcnt=0) 0x445ffc7a&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 11 extended permit tcp any host &lt;EM&gt;public_ip &lt;/EM&gt;eq imap4 (hitcnt=0) 0xc10d6b17&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 12 extended permit tcp any host &lt;EM&gt;public_ip&lt;/EM&gt; eq 4125 (hitcnt=0) 0xf9904a7e&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 13 extended permit tcp any host &lt;EM&gt;public_ip &lt;/EM&gt;eq https (hitcnt=2) 0x933075d4&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 14 extended permit tcp any host &lt;EM&gt;public_ip &lt;/EM&gt;eq smtp (hitcnt=0) 0xbbbe8a1e&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 15 extended permit tcp any host &lt;EM&gt;public_ip &lt;/EM&gt;eq 6699 (hitcnt=0) 0x67c9552f&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 16 extended permit tcp any host &lt;EM&gt;public_ip &lt;/EM&gt;eq https (hitcnt=0) 0xda2d6a77&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 17 extended permit tcp any 10.8.0.0 255.255.0.0 eq 1234 (hitcnt=0) 0x88dd37e5&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 18 extended permit ip any 10.8.0.0 255.255.0.0 (hitcnt=0) 0xa9169af9&lt;/P&gt;&lt;P&gt;access-list remote-users_splitTunnelAcl; 1 elements; name hash: 0x19f43771&lt;/P&gt;&lt;P&gt;access-list remote-users_splitTunnelAcl line 1 standard permit inside-nets 255.255.0.0 (hitcnt=0) 0x9cd507cd&lt;/P&gt;&lt;P&gt;access-list inside_nat0_outbound; 5 elements; name hash: 0x467c8ce4&lt;/P&gt;&lt;P&gt;access-list inside_nat0_outbound line 1 extended permit ip 172.16.180.0 255.255.255.0 172.16.200.0 255.255.255.0 (hitcnt=0) 0xbc5b1ea5&lt;/P&gt;&lt;P&gt;access-list inside_nat0_outbound line 2 extended permit ip 172.16.180.0 255.255.255.0 172.16.210.0 255.255.255.0 (hitcnt=0) 0xbff6a7ce&lt;/P&gt;&lt;P&gt;access-list inside_nat0_outbound line 3 extended permit ip 172.16.180.0 255.255.255.0 172.16.190.0 255.255.255.0 (hitcnt=0) 0x19b50b54&lt;/P&gt;&lt;P&gt;access-list inside_nat0_outbound line 4 extended permit ip tascet-inside-nets 255.255.0.0 172.16.100.0 255.255.255.0 (hitcnt=0) 0xba71f6d5&lt;/P&gt;&lt;P&gt;access-list inside_nat0_outbound line 5 extended permit ip 172.16.180.0 255.255.255.0 172.16.240.0 255.255.255.0 (hitcnt=0) 0x00a7b064&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA5510# packet-tracer input outside tcp 66.170.26.242 1234 8.0.2.2 123$&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 1&lt;/P&gt;&lt;P&gt;Type: FLOW-LOOKUP&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;Found no matching flow, creating a new flow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 2&lt;/P&gt;&lt;P&gt;Type: ROUTE-LOOKUP&lt;/P&gt;&lt;P&gt;Subtype: input&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;in&amp;nbsp;&amp;nbsp; 0.0.0.0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0.0.0.0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 3&lt;/P&gt;&lt;P&gt;Type: ACCESS-LIST&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: DROP&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Implicit Rule&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Result:&lt;/P&gt;&lt;P&gt;input-interface: outside&lt;/P&gt;&lt;P&gt;input-status: up&lt;/P&gt;&lt;P&gt;input-line-status: up&lt;/P&gt;&lt;P&gt;output-interface: outside&lt;/P&gt;&lt;P&gt;output-status: up&lt;/P&gt;&lt;P&gt;output-line-status: up&lt;/P&gt;&lt;P&gt;Action: drop&lt;/P&gt;&lt;P&gt;Drop-reason: (acl-drop) Flow is denied by configured rule&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA5510# show access-list&lt;/P&gt;&lt;P&gt;access-list cached ACL log flows: total 0, denied 0 (deny-flow-max 4096)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; alert-interval 300&lt;/P&gt;&lt;P&gt;access-list outside_access_in; 16 elements; name hash: 0x6892a938&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 1 extended deny ip 150.70.0.0 255.255.0.0 any (hitcnt=0) 0x247e4f19&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 2 remark ICMP type 11 for Windows Traceroute&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 3 extended permit icmp any any time-exceeded (hitcnt=0) 0x03690eb3&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 4 remark ICMP type 3 for Cisco and Linux&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 5 extended permit icmp any any unreachable (hitcnt=1) 0x5c2fa603&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 10 extended permit tcp any host &lt;EM&gt;public_ip &lt;/EM&gt;eq 993 (hitcnt=0) 0x445ffc7a&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 11 extended permit tcp any host &lt;EM&gt;public_ip &lt;/EM&gt;eq imap4 (hitcnt=0) 0xc10d6b17&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 12 extended permit tcp any host &lt;EM&gt;public_ip &lt;/EM&gt;eq 4125 (hitcnt=0) 0xf9904a7e&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 13 extended permit tcp any host &lt;EM&gt;public_ip &lt;/EM&gt;eq https (hitcnt=2) 0x933075d4&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 14 extended permit tcp any host &lt;EM&gt;public_ip &lt;/EM&gt;eq smtp (hitcnt=0) 0xbbbe8a1e&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 15 extended permit tcp any host &lt;EM&gt;public_ip &lt;/EM&gt;eq 6699 (hitcnt=0) 0x67c9552f&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 16 extended permit tcp any host &lt;EM&gt;public_ip&lt;/EM&gt; eq https (hitcnt=0) 0xda2d6a77&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 17 extended permit tcp any 10.8.0.0 255.255.0.0 eq 1234 (hitcnt=0) 0x88dd37e5&lt;/P&gt;&lt;P&gt;access-list outside_access_in line 18 extended permit ip any 10.8.0.0 255.255.0.0 (hitcnt=0) 0xa9169af9&lt;/P&gt;&lt;P&gt;access-list remote-users_splitTunnelAcl; 1 elements; name hash: 0x19f43771&lt;/P&gt;&lt;P&gt;access-list remote-users_splitTunnelAcl line 1 standard permit inside-nets 255.255.0.0 (hitcnt=0) 0x9cd507cd&lt;/P&gt;&lt;P&gt;access-list inside_nat0_outbound; 5 elements; name hash: 0x467c8ce4&lt;/P&gt;&lt;P&gt;access-list inside_nat0_outbound line 1 extended permit ip 172.16.180.0 255.255.255.0 172.16.200.0 255.255.255.0 (hitcnt=0) 0xbc5b1ea5&lt;/P&gt;&lt;P&gt;access-list inside_nat0_outbound line 2 extended permit ip 172.16.180.0 255.255.255.0 172.16.210.0 255.255.255.0 (hitcnt=0) 0xbff6a7ce&lt;/P&gt;&lt;P&gt;access-list inside_nat0_outbound line 3 extended permit ip 172.16.180.0 255.255.255.0 172.16.190.0 255.255.255.0 (hitcnt=0) 0x19b50b54&lt;/P&gt;&lt;P&gt;access-list inside_nat0_outbound line 4 extended permit ip inside-nets 255.255.0.0 172.16.100.0 255.255.255.0 (hitcnt=0) 0xba71f6d5&lt;/P&gt;&lt;P&gt;access-list inside_nat0_outbound line 5 extended permit ip 172.16.180.0 255.255.255.0 172.16.240.0 255.255.255.0 (hitcnt=0) 0x00a7b064&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not seeing the ACL that is blocking traffic here - I'm baffled.&amp;nbsp; any ideas?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Aug 2013 17:39:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338967#M345509</guid>
      <dc:creator>skoch1skoch</dc:creator>
      <dc:date>2013-08-05T17:39:50Z</dc:date>
    </item>
    <item>
      <title>NAT problem - traffic from internet not reaching internal source</title>
      <link>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338968#M345510</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is not much point in trying to simulate a connection coming from the &lt;STRONG&gt;"outside"&lt;/STRONG&gt; to your &lt;STRONG&gt;"inside"&lt;/STRONG&gt; network with the private IP address as the destination as no such packet will ever reach your firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you try doing a &lt;STRONG&gt;"packet-tracer"&lt;/STRONG&gt; to simulate a new connection being formed from the new LAN Network&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;packet-tracer input inside tcp 10.8.2.2 12345 8.8.8.8 80&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And see if it gives us any information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The original log messages still seem really strange to me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Aug 2013 18:10:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338968#M345510</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-08-05T18:10:55Z</dc:date>
    </item>
    <item>
      <title>NAT problem - traffic from internet not reaching internal source</title>
      <link>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338969#M345511</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That seemed to work just fine:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA5510# packet-tracer input inside tcp 10.8.2.2 12345 8.8.8.8 80&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 1&lt;/P&gt;&lt;P&gt;Type: ACCESS-LIST&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Implicit Rule&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;MAC Access list&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 2&lt;/P&gt;&lt;P&gt;Type: FLOW-LOOKUP&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;Found no matching flow, creating a new flow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 3&lt;/P&gt;&lt;P&gt;Type: ROUTE-LOOKUP&lt;/P&gt;&lt;P&gt;Subtype: input&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;in&amp;nbsp;&amp;nbsp; 0.0.0.0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0.0.0.0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 4&lt;/P&gt;&lt;P&gt;Type: CONN-SETTINGS&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;class-map class-default&lt;/P&gt;&lt;P&gt; match any&lt;/P&gt;&lt;P&gt;policy-map global_policy&lt;/P&gt;&lt;P&gt; class class-default&lt;/P&gt;&lt;P&gt;&amp;nbsp; set connection decrement-ttl&lt;/P&gt;&lt;P&gt;service-policy global_policy global&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 5&lt;/P&gt;&lt;P&gt;Type: IP-OPTIONS&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 6&lt;/P&gt;&lt;P&gt;Type: NAT&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;nat (inside) 101 0.0.0.0 0.0.0.0&lt;/P&gt;&lt;P&gt;&amp;nbsp; match ip inside any outside any&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; dynamic translation to pool 101 (&lt;EM&gt;public_ip&lt;/EM&gt; [Interface PAT])&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; translate_hits = 964843, untranslate_hits = 39941&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;Dynamic translate 10.8.2.2/12345 to &lt;EM&gt;public_ip&lt;/EM&gt;/51088 using netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 7&lt;/P&gt;&lt;P&gt;Type: NAT&lt;/P&gt;&lt;P&gt;Subtype: host-limits&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;nat (inside) 101 0.0.0.0 0.0.0.0&lt;/P&gt;&lt;P&gt;&amp;nbsp; match ip inside any outside any&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; dynamic translation to pool 101 (&lt;EM&gt;public_ip&lt;/EM&gt; [Interface PAT])&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; translate_hits = 964843, untranslate_hits = 39941&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 8&lt;/P&gt;&lt;P&gt;Type: IP-OPTIONS&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 9&lt;/P&gt;&lt;P&gt;Type: FLOW-CREATION&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;New flow created with id 1300556, packet dispatched to next module&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Result:&lt;/P&gt;&lt;P&gt;input-interface: inside&lt;/P&gt;&lt;P&gt;input-status: up&lt;/P&gt;&lt;P&gt;input-line-status: up&lt;/P&gt;&lt;P&gt;output-interface: outside&lt;/P&gt;&lt;P&gt;output-status: up&lt;/P&gt;&lt;P&gt;output-line-status: up&lt;/P&gt;&lt;P&gt;Action: allow&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Aug 2013 18:50:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338969#M345511</guid>
      <dc:creator>skoch1skoch</dc:creator>
      <dc:date>2013-08-05T18:50:56Z</dc:date>
    </item>
    <item>
      <title>Re: NAT problem - traffic from internet not reaching internal so</title>
      <link>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338970#M345512</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest going through the whole path of the network from the host in the new network all the way to its default Internet gateway where its default route leads to and again back to the host from that Internet gateway viewing routing table on each step. I would imagine that are atleast some routers involved as you decided to use a routing protocol instead of static routing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am just wondering if this would have anything to do with you possibly having another Internet gateway in addition to the ASA and the traffic taking a "wrong turn" somewhere along the way in your network?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At first glance the log message would seem to point to a situation where a connection from the host might have gone to the Internet through some other Internet gateway (other than the ASA) and the return traffic has come back to the ASA from that Internet gateway before reaching the actual host.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Aug 2013 19:04:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338970#M345512</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-08-05T19:04:28Z</dc:date>
    </item>
    <item>
      <title>Re: NAT problem - traffic from internet not reaching internal so</title>
      <link>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338971#M345513</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've got layer 3 switches doing routing in my network.&amp;nbsp; The traffic from the 10.8.0.0 network is coming from the switch below.&amp;nbsp; The default route is to the inside interface of the firewall (172.16.20.1).&amp;nbsp; The ASA's routing table (shown above) then has a default gateway set to the ISP's gateway address.&amp;nbsp; Should the default gateway on the switch be set to the ISP's Gateway address?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edit:&amp;nbsp; There are no other paths out of the network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"switch1"#sh ip ro&lt;/P&gt;&lt;P&gt;Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; E1 - OSPF external type 1, E2 - OSPF external type 2&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ia - IS-IS inter area, * - candidate default, U - per-user static route&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; o - ODR, P - periodic downloaded static route&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gateway of last resort is 172.16.20.1 to network 0.0.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.0.0/16 is variably subnetted, 11 subnets, 3 masks&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.180.0/24 is directly connected, Vlan180&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.170.0/24 is directly connected, Vlan170&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.250.0/24 is directly connected, Vlan250&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.251.0/24 is directly connected, Vlan251&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.240.0/24 is directly connected, Vlan240&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.230.0/24 is directly connected, Vlan230&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.220.0/24 is directly connected, Vlan220&lt;/P&gt;&lt;P&gt;O&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.30.0/24 [110/11] via 172.16.20.1, 6d23h, GigabitEthernet1/0/48&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.20.0/29 is directly connected, GigabitEthernet1/0/48&lt;/P&gt;&lt;P&gt;S&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.240.159/32 [1/0] via 172.16.20.1&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 172.16.99.0/24 is directly connected, Vlan99&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.0.0.0/16 is subnetted, 2 subnets&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.8.0.0 is directly connected, Vlan108&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.5.0.0 is directly connected, Vlan105&lt;/P&gt;&lt;P&gt;S*&amp;nbsp;&amp;nbsp; 0.0.0.0/0 [1/0] via 172.16.20.1&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Aug 2013 19:16:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338971#M345513</guid>
      <dc:creator>skoch1skoch</dc:creator>
      <dc:date>2013-08-05T19:16:02Z</dc:date>
    </item>
    <item>
      <title>NAT problem - traffic from internet not reaching internal source</title>
      <link>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338972#M345514</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Routing seems correct. Default gateway should be pointing to the ASA &lt;STRONG&gt;"inside"&lt;/STRONG&gt; interface IP address like it is at the moment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't know why we would see the ASA at any point trying to create a translation from &lt;STRONG&gt;"inside"&lt;/STRONG&gt; to &lt;STRONG&gt;"inside"&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The most common reason I have seen for an ASA to forward traffic through wrong interface has been some NAT configuration but I cant see anything in your configuration that would point to such a problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can't remember ever running into such a situation myself so I dont even have that advantage when trying to see what this problem is about.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could always consider rebooting the ASA and see if it has any effect on the current problem (remember to save configuration if you device to do so)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other options would be to further try to get logs from connection attempts from a single host.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is also the option of trying to capture some traffic on the ASA if it would tell anything about the problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just dont see a reason why this network wouldnt work if all other networks behind &lt;STRONG&gt;"inside"&lt;/STRONG&gt; work at the moment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Aug 2013 20:00:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338972#M345514</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-08-05T20:00:36Z</dc:date>
    </item>
    <item>
      <title>Re: NAT problem - traffic from internet not reaching internal so</title>
      <link>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338973#M345515</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jouni,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Exactly right, all other inside networks (except the 10.5.0.0, which is also new) are routing and NATing just fine.&amp;nbsp; Also, I'm curious as to why ICMP traffic is routed properly to and from the 10.8.0.0 network, but not http or other tcp traffic.&amp;nbsp; I will bounce the ASA, but I'll have to wait until the evening.&amp;nbsp; Thanks for your help thus far.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Shane&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Aug 2013 20:08:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338973#M345515</guid>
      <dc:creator>skoch1skoch</dc:creator>
      <dc:date>2013-08-05T20:08:47Z</dc:date>
    </item>
    <item>
      <title>Re: NAT problem - traffic from internet not reaching internal so</title>
      <link>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338974#M345516</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In some cases where routing is the problem ICMP might act a bit differently than TCP connections for example.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ICMP might work and TCP not because of asymmetric routing. (especially when ASA is in the picture)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looking at your L3 Switch routing table I can only see ONE network adverticed with OSPF and its from the ASA. And since the ASA is the default gateway it wouldnt even need to advertice that network as the traffic would always come to the ASA with default route.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I am not sure where the OSPF is needed in this case since it seems to only run between the L3 switch and ASA. I would personally handle it with Static routing at both ASA and L3 switch since the OSPF doesnt really bring that much into the picture.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would only need static default route from L3 Switch towards ASA and ASA would need route for the LAN network towards its &lt;STRONG&gt;"inside"&lt;/STRONG&gt; interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It just somehow seems to me like something to do with routing but doesnt make sense especially when the ASA should be the only route out of your network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Aug 2013 20:44:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338974#M345516</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-08-05T20:44:52Z</dc:date>
    </item>
    <item>
      <title>Re: NAT problem - traffic from internet not reaching internal so</title>
      <link>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338975#M345517</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Shane,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is one obvious mistake in your OSPF configuration that may lead to this confusion. You are advertising networks that are not directly connected to your ASA. As shown, these networks are directly connected to the switch through Vlans 108 and 105. This means that the switch need to advertise them to the ASA not the vice-versa. After all, ASA want to reach these networks in order to serve them so they must get advertised by the switch. Remember the "network" command is used to define which networks the device knows to advertise them to other devices. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you just create static routes to these destinations with the switch as the default gateway and see what will happen?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Aug 2013 00:10:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338975#M345517</guid>
      <dc:creator>turbo_engine26</dc:creator>
      <dc:date>2013-08-06T00:10:55Z</dc:date>
    </item>
    <item>
      <title>NAT problem - traffic from internet not reaching internal source</title>
      <link>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338976#M345518</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also, i noticed that there is an object group defined called "inside-nets" in OSPF config. Is this the 172.16.0.0 major network behind the switch? ... When you said that there is no problem with traffic coming from/to 172.16.0.0, did you mean the 172.16 networks behind the switch OR the 172.16.30.0 and 172.16.20.0 that are directly connected to ASA? Did you try to initiate traffic from any of 172.16 networks that are behind the switch?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Aug 2013 00:27:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-problem-traffic-from-internet-not-reaching-internal-source/m-p/2338976#M345518</guid>
      <dc:creator>turbo_engine26</dc:creator>
      <dc:date>2013-08-06T00:27:52Z</dc:date>
    </item>
  </channel>
</rss>

