<?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: Multiple Inside Translation to one Global Range in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/multiple-inside-translation-to-one-global-range/m-p/2237093#M346864</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 personally like to do the typical Dynamic NAT in this way&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;object-group network DEFAULT-NAT-SOURCE&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object 10.1.1.0 255.255.255.0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object 192.168.1.0 255.255.255.0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object 172.16.1.0 255.255.255.0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;object network NAT-POOL&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; range 32.16.1.1 32.16.1.50&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;nat (inside,outside) after-auto source dynamic DEFAULT-NAT-SOURCE NAT-POOL&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or you can change the NAT configuration format a bit and change it to&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;nat (any,outside) after-auto source dynamic DEFAULT-NAT-SOURCE NAT-POOL&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only difference with the 2 above &lt;STRONG&gt;"nat"&lt;/STRONG&gt; commands is that the other works only for network behind &lt;STRONG&gt;"inside"&lt;/STRONG&gt; interface. The other one could be used for &lt;STRONG&gt;"any"&lt;/STRONG&gt; interface on the ASA. So if you have multiple networks you wanted to add to the NAT configuration then you would simply add them to the &lt;STRONG&gt;"object-group"&lt;/STRONG&gt; we used. The names of the objects can naturally be anything you like.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please do remember to mark the reply as the correct answer if it answered your question.&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, 08 Jul 2013 13:50:31 GMT</pubDate>
    <dc:creator>Jouni Forss</dc:creator>
    <dc:date>2013-07-08T13:50:31Z</dc:date>
    <item>
      <title>Multiple Inside Translation to one Global Range</title>
      <link>https://community.cisco.com/t5/network-security/multiple-inside-translation-to-one-global-range/m-p/2237092#M346863</link>
      <description>&lt;P&gt;I need assistance with this configuration.&amp;nbsp; In the pre 8.3 version of the ASA IOS, I could do this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside) 1 10.1.1.0 255.255.255.0&lt;/P&gt;&lt;P&gt;nat (inside) 1 192.168.1.0 255.255.255.0&lt;/P&gt;&lt;P&gt;nat (inside) 1 172.16.1.0 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Global (outside) 1 32.16.1.1 - 32.16.1.50&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can't seem to replicate a similar configuration in ASA 8.4.&amp;nbsp;&amp;nbsp;&amp;nbsp; Can someone please help me with that?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 02:08:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-inside-translation-to-one-global-range/m-p/2237092#M346863</guid>
      <dc:creator>ty.masse</dc:creator>
      <dc:date>2019-03-12T02:08:40Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple Inside Translation to one Global Range</title>
      <link>https://community.cisco.com/t5/network-security/multiple-inside-translation-to-one-global-range/m-p/2237093#M346864</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 personally like to do the typical Dynamic NAT in this way&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;object-group network DEFAULT-NAT-SOURCE&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object 10.1.1.0 255.255.255.0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object 192.168.1.0 255.255.255.0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object 172.16.1.0 255.255.255.0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;object network NAT-POOL&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; range 32.16.1.1 32.16.1.50&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;nat (inside,outside) after-auto source dynamic DEFAULT-NAT-SOURCE NAT-POOL&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or you can change the NAT configuration format a bit and change it to&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;nat (any,outside) after-auto source dynamic DEFAULT-NAT-SOURCE NAT-POOL&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only difference with the 2 above &lt;STRONG&gt;"nat"&lt;/STRONG&gt; commands is that the other works only for network behind &lt;STRONG&gt;"inside"&lt;/STRONG&gt; interface. The other one could be used for &lt;STRONG&gt;"any"&lt;/STRONG&gt; interface on the ASA. So if you have multiple networks you wanted to add to the NAT configuration then you would simply add them to the &lt;STRONG&gt;"object-group"&lt;/STRONG&gt; we used. The names of the objects can naturally be anything you like.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please do remember to mark the reply as the correct answer if it answered your question.&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, 08 Jul 2013 13:50:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-inside-translation-to-one-global-range/m-p/2237093#M346864</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-07-08T13:50:31Z</dc:date>
    </item>
    <item>
      <title>Multiple Inside Translation to one Global Range</title>
      <link>https://community.cisco.com/t5/network-security/multiple-inside-translation-to-one-global-range/m-p/2237094#M346865</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;You can always check out a NAT 8.3+ document I made on the forums. It has some basic information about the new NAT format.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-wiki-small" href="https://community.cisco.com/docs/DOC-31116"&gt;https://supportforums.cisco.com/docs/DOC-31116&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Though naturally feel free to ask questions here if you have something other configurations you havent been able to migrate to the new format.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&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>Mon, 08 Jul 2013 13:57:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/multiple-inside-translation-to-one-global-range/m-p/2237094#M346865</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-07-08T13:57:31Z</dc:date>
    </item>
  </channel>
</rss>

