<?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 VPN encryption domain using private range in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/vpn-encryption-domain-using-private-range/m-p/3951881#M900719</link>
    <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm setting up a VPN with a 3rd party who have suggested the use of 172.16.8.0/26 as the encryption domain on my side of the tunnel (happy to do this to avoid wasting public IP's). There side of the encryption domain is 70.0.0.x/27. I am planning on using the 192.168.1.0/24 range for my internal network. A requirement from the 3rd party is that there are 11 IP's configured as static NAT. My question is how would I implement this config so the static NAT's are in place and that the rest of the interesting traffic uses PAT? Also, can I actually NAT private to private and if so where does my public IP (213.0.0.x) come into the equation?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have added what I believe is correct but i'm obviously not entirely sure :-&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;access-list internet_1_cryptomap line 1 extended permit ip host 192.168.1.0 70.0.0.1 255.255.255.224&lt;/P&gt;&lt;P&gt;nat (inside,outside) source static 192.168.1.0 172.16.8.0 destination static 70.0.0.0&amp;nbsp;70.0.0.0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 17:39:19 GMT</pubDate>
    <dc:creator>Sunny Banks</dc:creator>
    <dc:date>2020-02-21T17:39:19Z</dc:date>
    <item>
      <title>VPN encryption domain using private range</title>
      <link>https://community.cisco.com/t5/network-security/vpn-encryption-domain-using-private-range/m-p/3951881#M900719</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm setting up a VPN with a 3rd party who have suggested the use of 172.16.8.0/26 as the encryption domain on my side of the tunnel (happy to do this to avoid wasting public IP's). There side of the encryption domain is 70.0.0.x/27. I am planning on using the 192.168.1.0/24 range for my internal network. A requirement from the 3rd party is that there are 11 IP's configured as static NAT. My question is how would I implement this config so the static NAT's are in place and that the rest of the interesting traffic uses PAT? Also, can I actually NAT private to private and if so where does my public IP (213.0.0.x) come into the equation?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have added what I believe is correct but i'm obviously not entirely sure :-&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;access-list internet_1_cryptomap line 1 extended permit ip host 192.168.1.0 70.0.0.1 255.255.255.224&lt;/P&gt;&lt;P&gt;nat (inside,outside) source static 192.168.1.0 172.16.8.0 destination static 70.0.0.0&amp;nbsp;70.0.0.0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 17:39:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-encryption-domain-using-private-range/m-p/3951881#M900719</guid>
      <dc:creator>Sunny Banks</dc:creator>
      <dc:date>2020-02-21T17:39:19Z</dc:date>
    </item>
    <item>
      <title>Re: VPN encryption domain using private range</title>
      <link>https://community.cisco.com/t5/network-security/vpn-encryption-domain-using-private-range/m-p/3952197#M900721</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;The nat is correct because you're translating your original subnet to a xlated subnet and keep as is the destination.&lt;BR /&gt;However your acl should mention the xlated subnet to the destination subnet and here you're referring to the original source subnet.</description>
      <pubDate>Sun, 03 Nov 2019 03:38:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-encryption-domain-using-private-range/m-p/3952197#M900721</guid>
      <dc:creator>Francesco Molino</dc:creator>
      <dc:date>2019-11-03T03:38:39Z</dc:date>
    </item>
    <item>
      <title>Re: VPN encryption domain using private range</title>
      <link>https://community.cisco.com/t5/network-security/vpn-encryption-domain-using-private-range/m-p/3952787#M900723</link>
      <description>&lt;P&gt;Francisco,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for the prompt reply. So something like this :-&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;access-list internet_1_cryptomap line 1 extended permit 172.16.8.0 255.255.255.192 70.0.0.0 255.255.255.224&lt;/P&gt;&lt;P&gt;nat (inside,outside) source static 192.168.1.0 172.16.8.0 destination static 70.0.0.0&amp;nbsp;70.0.0.0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, if i'm trying to configure some static 1-to-1 NAT's (and leave the rest for PAT) would this be correct :-&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;nat (inside,outside) source static 192.168.1.1 172.16.8.1 destination static 70.0.0.0&amp;nbsp;70.0.0.0&lt;/P&gt;&lt;P&gt;nat (inside,outside) source static 192.168.1.2 172.16.8.2 destination static 70.0.0.0&amp;nbsp;70.0.0.0&lt;/P&gt;&lt;P&gt;nat (inside,outside) source static 192.168.1.3 172.16.8.3 destination static 70.0.0.0&amp;nbsp;70.0.0.0&lt;/P&gt;&lt;P&gt;nat (inside,outside) source static 192.168.1.4 172.16.8.4 destination static 70.0.0.0&amp;nbsp;70.0.0.0&lt;/P&gt;&lt;P&gt;.................&lt;/P&gt;&lt;P&gt;nat (inside,outside) source static 192.168.1.10 172.16.8.10 destination static 70.0.0.0&amp;nbsp;70.0.0.0&lt;/P&gt;&lt;P&gt;nat (inside,outside) source static 192.168.1.0 172.16.8.0 destination static 70.0.0.0&amp;nbsp;70.0.0.0 &amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;PAT for the rest&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance. Your help is greatly appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Nov 2019 16:31:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-encryption-domain-using-private-range/m-p/3952787#M900723</guid>
      <dc:creator>Sunny Banks</dc:creator>
      <dc:date>2019-11-04T16:31:40Z</dc:date>
    </item>
    <item>
      <title>Re: VPN encryption domain using private range</title>
      <link>https://community.cisco.com/t5/network-security/vpn-encryption-domain-using-private-range/m-p/3953125#M900725</link>
      <description>This should work.</description>
      <pubDate>Tue, 05 Nov 2019 04:21:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-encryption-domain-using-private-range/m-p/3953125#M900725</guid>
      <dc:creator>Francesco Molino</dc:creator>
      <dc:date>2019-11-05T04:21:15Z</dc:date>
    </item>
  </channel>
</rss>

