<?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 Thanks for your help. Mike in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/nat-clairifcation-for-vpn/m-p/2692411#M191543</link>
    <description>&lt;P&gt;Thanks for your help.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;</description>
    <pubDate>Fri, 15 May 2015 14:12:43 GMT</pubDate>
    <dc:creator>burleyman</dc:creator>
    <dc:date>2015-05-15T14:12:43Z</dc:date>
    <item>
      <title>NAT clairifcation for VPN</title>
      <link>https://community.cisco.com/t5/network-security/nat-clairifcation-for-vpn/m-p/2692406#M191531</link>
      <description>&lt;P&gt;Please correct me if I am wrong.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For site-2-site VPN's and client VPN access into the private LAN and from the private LAN to the VPN clients and sites, I do not need to configure No NAT with the newer 9.x ASA software.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The older (Pre 8.3) No NAT for this would have been....&lt;/P&gt;&lt;P&gt;access-list 100 extended permit ip 10.10.1.0 255.255.255.0 192.168.10.0 255.255.255.0&lt;/P&gt;&lt;P&gt;nat (inside) 0 access-list 100&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now with ASA 9.x, or more accurately 8.3 and newer... I would not need to configure anything for NAT with this......correct.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mike&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:56:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-clairifcation-for-vpn/m-p/2692406#M191531</guid>
      <dc:creator>burleyman</dc:creator>
      <dc:date>2019-03-12T05:56:40Z</dc:date>
    </item>
    <item>
      <title>It depends. If you still have</title>
      <link>https://community.cisco.com/t5/network-security/nat-clairifcation-for-vpn/m-p/2692407#M191535</link>
      <description>&lt;P&gt;It depends. If you still have NAT from your LAN to the outside network (typically you have), then you also have to configure NAT exemption on ASA v8.3+.&lt;/P&gt;&lt;P&gt;It's done with twice-NAT in Section 1 of the NAT rules.&lt;/P&gt;</description>
      <pubDate>Thu, 14 May 2015 21:13:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-clairifcation-for-vpn/m-p/2692407#M191535</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2015-05-14T21:13:40Z</dc:date>
    </item>
    <item>
      <title>That is what I thought but I</title>
      <link>https://community.cisco.com/t5/network-security/nat-clairifcation-for-vpn/m-p/2692408#M191538</link>
      <description>&lt;P&gt;That is what I thought but I had someone telling me I did not, but I think he was confused.&lt;/P&gt;&lt;P&gt;So if I have a subnet of 10.10.10.0/24 for Site A and a subnet of 172.16.100.0/24 for Site B I would configure this in Sites A ASA&lt;/P&gt;&lt;P&gt;object network NET-10.10.10.0_24&lt;BR /&gt;&amp;nbsp;subnet 10.10.10.0 255.255.255.0&lt;/P&gt;&lt;P&gt;object network NET-172.16.100.0_24&lt;BR /&gt;&amp;nbsp;subnet 172.16.100.0 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;nat (inside,outside) source static NET-10.10.10.0_24 NET-10.10.10.0_24 destination static NET-172.16.100.0_24 NET-172.16.100.0_24&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;</description>
      <pubDate>Fri, 15 May 2015 13:27:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-clairifcation-for-vpn/m-p/2692408#M191538</guid>
      <dc:creator>burleyman</dc:creator>
      <dc:date>2015-05-15T13:27:22Z</dc:date>
    </item>
    <item>
      <title>Yes, that's the way to</title>
      <link>https://community.cisco.com/t5/network-security/nat-clairifcation-for-vpn/m-p/2692409#M191539</link>
      <description>&lt;P&gt;Yes, that's the way to configure it. But also add the keyword "no-proxy-arp route-lookup" to the end of the NAT-satement as it can avoid problems in many situations. And if there are other nat-statements in section one, you probably want to have it at the beginning:&lt;/P&gt;

&lt;PRE&gt;
nat (inside,outside) 1 source static NET-10.10.10.0_24 NET-10.10.10.0_24 destination static NET-172.16.100.0_24 NET-172.16.100.0_24 no-proxy-arp route-lookup&lt;/PRE&gt;</description>
      <pubDate>Fri, 15 May 2015 13:41:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-clairifcation-for-vpn/m-p/2692409#M191539</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2015-05-15T13:41:07Z</dc:date>
    </item>
    <item>
      <title>MikeYes, that is a NAT</title>
      <link>https://community.cisco.com/t5/network-security/nat-clairifcation-for-vpn/m-p/2692410#M191541</link>
      <description>&lt;P&gt;-&lt;/P&gt;</description>
      <pubDate>Fri, 15 May 2015 13:42:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-clairifcation-for-vpn/m-p/2692410#M191541</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2015-05-15T13:42:45Z</dc:date>
    </item>
    <item>
      <title>Thanks for your help. Mike</title>
      <link>https://community.cisco.com/t5/network-security/nat-clairifcation-for-vpn/m-p/2692411#M191543</link>
      <description>&lt;P&gt;Thanks for your help.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;</description>
      <pubDate>Fri, 15 May 2015 14:12:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-clairifcation-for-vpn/m-p/2692411#M191543</guid>
      <dc:creator>burleyman</dc:creator>
      <dc:date>2015-05-15T14:12:43Z</dc:date>
    </item>
  </channel>
</rss>

