<?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 Static vs. NONAT in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/static-vs-nonat/m-p/1404570#M737815</link>
    <description>&lt;P&gt;What is the functional difference between the two for the following scenrio&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,dmz) 1.1.1.1 1.1.1.1 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vs&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;nat (inside) 0 1.1.1.1 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Those accomplish the same thing. Is there something I'm missing?&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 17:04:57 GMT</pubDate>
    <dc:creator>merryllem</dc:creator>
    <dc:date>2019-03-11T17:04:57Z</dc:date>
    <item>
      <title>Static vs. NONAT</title>
      <link>https://community.cisco.com/t5/network-security/static-vs-nonat/m-p/1404570#M737815</link>
      <description>&lt;P&gt;What is the functional difference between the two for the following scenrio&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,dmz) 1.1.1.1 1.1.1.1 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vs&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;nat (inside) 0 1.1.1.1 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Those accomplish the same thing. Is there something I'm missing?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 17:04:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-vs-nonat/m-p/1404570#M737815</guid>
      <dc:creator>merryllem</dc:creator>
      <dc:date>2019-03-11T17:04:57Z</dc:date>
    </item>
    <item>
      <title>Re: Static vs. NONAT</title>
      <link>https://community.cisco.com/t5/network-security/static-vs-nonat/m-p/1404571#M737817</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Technically speaking the NAT statement actually does NAT. Granted it NATs to its own address, but it does NAT. With NAT0 is does not NAT at all.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;Please let Cisco know that these forums are valuable to you!&lt;BR /&gt;&lt;A class="jive-link-wiki-small" href="https://community.cisco.com/docs/DOC-6212"&gt;https://supportforums.cisco.com/docs/DOC-6212&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Feb 2010 19:49:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-vs-nonat/m-p/1404571#M737817</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2010-02-03T19:49:29Z</dc:date>
    </item>
    <item>
      <title>Re: Static vs. NONAT</title>
      <link>https://community.cisco.com/t5/network-security/static-vs-nonat/m-p/1404572#M737819</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;static (inside,dmz) 1.1.1.1 1.1.1.1 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is only between inside and dmz&lt;/P&gt;&lt;P&gt;This is bi-directional meaning, in addition to the hosts on the inside, hosts in the DMZ can initiate traffic also provided ACLs allow.&lt;/P&gt;&lt;P&gt;This is called identity static&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vs&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;nat (inside) 0 1.1.1.1 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This can only be sourced from the inside interface going anywhere. This is called nat exemption.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Feb 2010 21:15:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-vs-nonat/m-p/1404572#M737819</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2010-02-03T21:15:56Z</dc:date>
    </item>
  </channel>
</rss>

