<?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 Hi CF, in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-nat-command/m-p/2785519#M174034</link>
    <description>&lt;P&gt;Hi CF,&lt;/P&gt;
&lt;P&gt;Little correction to what Mike has mentioned. There are two kind of nat which are used wit nat(...) 0. When you see &amp;nbsp;nat 0 with access-list, then it is called 'nat exempt' for which there is no xlate created on ASA and it has the highest preference in the nat order.&lt;/P&gt;
&lt;P&gt;Another flavor is when you have nat 0 without an access-list which is called as 'identity nat'. This identity means nat to itself. For this nat, xlate entry is created . Please use the link below to understand the same :&lt;/P&gt;
&lt;P&gt;https://learningnetwork.cisco.com/thread/22575&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Rest of the your understanding is correct as you have explained for dynamic nat.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Hope it helps.&lt;/P&gt;
&lt;P&gt;Regards.&lt;/P&gt;
&lt;P&gt;Akshay Rastogi&lt;/P&gt;
&lt;P&gt;Remember to rate helpful posts.&lt;/P&gt;</description>
    <pubDate>Wed, 16 Dec 2015 11:09:42 GMT</pubDate>
    <dc:creator>Akshay Rastogi</dc:creator>
    <dc:date>2015-12-16T11:09:42Z</dc:date>
    <item>
      <title>ASA Nat command</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-command/m-p/2785517#M174032</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I am a newbie to the Cisco ASA world. So I am finding it difficult to understand certain configuration especially the ones configured in older versions.&lt;/P&gt;
&lt;P&gt;Can you please help me to understand the meaning of these commands:&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;global (outside) 13 interface&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;nat (inside) 0 access-list 10&lt;/EM&gt;&amp;nbsp; --&amp;gt; My assumption is ACL 10 entries are exempted from NATing since its in Nat rule position 0&lt;BR /&gt;&lt;EM&gt;nat (inside) 13 0.0.0.0 0.0.0.0&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;nat (dmz) 0 access-list 12&lt;/EM&gt; --&amp;gt; My assumption is ACL 12 entries are exempted from NATing since its in Nat rule position 0&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;My assumption about the other two statements is they are connected each other(They both share rule position 13). So any IP that hits the internal interface will be NATed with the interface IP of external interface. Am I right?&lt;/P&gt;
&lt;P&gt;CF&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 07:02:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-command/m-p/2785517#M174032</guid>
      <dc:creator>Cisco Freak</dc:creator>
      <dc:date>2019-03-12T07:02:08Z</dc:date>
    </item>
    <item>
      <title>Short answer, yes. you are</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-command/m-p/2785518#M174033</link>
      <description>&lt;P&gt;Short answer, yes. you are correct.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ACL 12 can have a source/dest and from that source/des comming from the DMZ interface the traffic is not going to be natted.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Same logic for the other one.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;There are some rules in regards to the order of operation. Nat0 IS only beaten if there is an existing NAT session going on (existing xlate), the rest of the order goes as follows&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Existing Xlate (sh xlate)&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Nat0&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Static NAT -----First match on the list (sh run static)&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Static PAT (port forward)---First match on the list &lt;STRONG&gt;&lt;/STRONG&gt;&lt;SPAN&gt;(sh run static)&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Regular NAT (Nat and global commands)----Best match (most specific)&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Cheers&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Mike.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Dec 2015 05:55:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-command/m-p/2785518#M174033</guid>
      <dc:creator>Maykol Rojas</dc:creator>
      <dc:date>2015-12-15T05:55:33Z</dc:date>
    </item>
    <item>
      <title>Hi CF,</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-command/m-p/2785519#M174034</link>
      <description>&lt;P&gt;Hi CF,&lt;/P&gt;
&lt;P&gt;Little correction to what Mike has mentioned. There are two kind of nat which are used wit nat(...) 0. When you see &amp;nbsp;nat 0 with access-list, then it is called 'nat exempt' for which there is no xlate created on ASA and it has the highest preference in the nat order.&lt;/P&gt;
&lt;P&gt;Another flavor is when you have nat 0 without an access-list which is called as 'identity nat'. This identity means nat to itself. For this nat, xlate entry is created . Please use the link below to understand the same :&lt;/P&gt;
&lt;P&gt;https://learningnetwork.cisco.com/thread/22575&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Rest of the your understanding is correct as you have explained for dynamic nat.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Hope it helps.&lt;/P&gt;
&lt;P&gt;Regards.&lt;/P&gt;
&lt;P&gt;Akshay Rastogi&lt;/P&gt;
&lt;P&gt;Remember to rate helpful posts.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Dec 2015 11:09:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-command/m-p/2785519#M174034</guid>
      <dc:creator>Akshay Rastogi</dc:creator>
      <dc:date>2015-12-16T11:09:42Z</dc:date>
    </item>
  </channel>
</rss>

