<?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 Simple NAT question in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/simple-nat-question/m-p/2135250#M393948</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would use this type of NAT (Identity NAT) when you want to traffic from your inside interface to flow through to your outside interface without changing the address. An example scenario would be a private MPLS cloud with separate clients. Each client has a unique address space so NATing is not necessary. Using Identity NAT is the solution because it provides us with the privacy of only allowing inside hosts to initiate communication with outside hosts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is when your outside its a private range as well, if it is public you use regular PAT with the outside interface or any public IP:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object network ALL_ZEROS&lt;/P&gt;&lt;P&gt;subnet 0.0.0.0 0.0.0.0&lt;/P&gt;&lt;P&gt;nat (inside,outside) dynamic interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On very specific/rare circumstances you want to use this NAT. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Juan Lombana&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate helpful posts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 19 Dec 2012 13:57:43 GMT</pubDate>
    <dc:creator>julomban</dc:creator>
    <dc:date>2012-12-19T13:57:43Z</dc:date>
    <item>
      <title>Simple NAT question</title>
      <link>https://community.cisco.com/t5/network-security/simple-nat-question/m-p/2135249#M393945</link>
      <description>&lt;P&gt;Will someone please explain what this NAT rules does?&amp;nbsp; I'm confused by what happens to the packet when you use "dynamic" and a host that is 0.0.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object network obj-0.0.0.0 &lt;/P&gt;&lt;P&gt; host 0.0.0.0&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;object network ALL_ZEROS&lt;/P&gt;&lt;P&gt; subnet 0.0.0.0 0.0.0.0&lt;/P&gt;&lt;P&gt; nat (inside,outside) dynamic obj-0.0.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 00:39:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/simple-nat-question/m-p/2135249#M393945</guid>
      <dc:creator>anowell</dc:creator>
      <dc:date>2019-03-12T00:39:03Z</dc:date>
    </item>
    <item>
      <title>Simple NAT question</title>
      <link>https://community.cisco.com/t5/network-security/simple-nat-question/m-p/2135250#M393948</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would use this type of NAT (Identity NAT) when you want to traffic from your inside interface to flow through to your outside interface without changing the address. An example scenario would be a private MPLS cloud with separate clients. Each client has a unique address space so NATing is not necessary. Using Identity NAT is the solution because it provides us with the privacy of only allowing inside hosts to initiate communication with outside hosts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is when your outside its a private range as well, if it is public you use regular PAT with the outside interface or any public IP:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object network ALL_ZEROS&lt;/P&gt;&lt;P&gt;subnet 0.0.0.0 0.0.0.0&lt;/P&gt;&lt;P&gt;nat (inside,outside) dynamic interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On very specific/rare circumstances you want to use this NAT. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Juan Lombana&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate helpful posts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Dec 2012 13:57:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/simple-nat-question/m-p/2135250#M393948</guid>
      <dc:creator>julomban</dc:creator>
      <dc:date>2012-12-19T13:57:43Z</dc:date>
    </item>
  </channel>
</rss>

