<?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: ASA outside to inside in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-outside-to-inside/m-p/1418798#M712939</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;To answer my own question, it works and access list entry was not needed.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;cheers&lt;/SPAN&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 23 Apr 2010 04:17:24 GMT</pubDate>
    <dc:creator>satendrak</dc:creator>
    <dc:date>2010-04-23T04:17:24Z</dc:date>
    <item>
      <title>ASA outside to inside</title>
      <link>https://community.cisco.com/t5/network-security/asa-outside-to-inside/m-p/1418797#M712906</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a requirement to setup a IPSEC tunnel to allow access to remote users to a subnet on inside. The same subnet is already in use elsewhere on the inside network. My vpn tunnel terminates on the ASA (7.2) on the outside interface. I want to NAT the source address of this traffic before it goes to inside.&lt;/P&gt;&lt;P&gt;My ASA is:&lt;/P&gt;&lt;P&gt;192.168.198.138/28 (outside)|ASA|(inside) 192.168.198.36/28&lt;/P&gt;&lt;P&gt;The traffic coming from the tunnel is 10.2.0.0/22 going to 10.172.152.64/27. My tunnel is up and running. How can I NAT/PAT this traffic?&lt;/P&gt;&lt;P&gt;Is this possible:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (outside) 5 access-list Site_A_VPN_IN outside &lt;BR /&gt;global (inside) 5 10.58.200.31&lt;/P&gt;&lt;P&gt;access-list Site_A_VPN_IN extended permit ip 10.2.0.0 255.255.252.0 10.172.152.64 255.255.255.224&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do I need to allow this on the ACL for the outside interface?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help would be appreciate.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Stan.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 17:36:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-outside-to-inside/m-p/1418797#M712906</guid>
      <dc:creator>satendrak</dc:creator>
      <dc:date>2019-03-11T17:36:28Z</dc:date>
    </item>
    <item>
      <title>Re: ASA outside to inside</title>
      <link>https://community.cisco.com/t5/network-security/asa-outside-to-inside/m-p/1418798#M712939</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;To answer my own question, it works and access list entry was not needed.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;cheers&lt;/SPAN&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Apr 2010 04:17:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-outside-to-inside/m-p/1418798#M712939</guid>
      <dc:creator>satendrak</dc:creator>
      <dc:date>2010-04-23T04:17:24Z</dc:date>
    </item>
  </channel>
</rss>

