<?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,I think we need to in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/nat-rule/m-p/2688393#M190993</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I think we need to understand more about your query to give you the exact answer.&lt;/P&gt;&lt;P&gt;NAT has changed a bit between ASA codes pre 8.2 and post 8.3.&lt;/P&gt;&lt;P&gt;Pre 8.2:-&lt;/P&gt;&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/security/asa/asa82/configuration/guide/config/nat_control.html&lt;/P&gt;&lt;P&gt;Post 8.4:-&lt;/P&gt;&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/security/asa/asa84/configuration/guide/asa_84_cli_config/nat_objects.html&lt;/P&gt;&lt;P&gt;Thi should work as a start for you.&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Vibhor Amrodia&lt;/P&gt;</description>
    <pubDate>Wed, 03 Jun 2015 16:02:36 GMT</pubDate>
    <dc:creator>Vibhor Amrodia</dc:creator>
    <dc:date>2015-06-03T16:02:36Z</dc:date>
    <item>
      <title>Nat Rule</title>
      <link>https://community.cisco.com/t5/network-security/nat-rule/m-p/2688392#M190991</link>
      <description>&lt;P&gt;How Nat rule works with Cisco ASA Configuration?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 06:02:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-rule/m-p/2688392#M190991</guid>
      <dc:creator>shubhamkulkarni39</dc:creator>
      <dc:date>2019-03-12T06:02:39Z</dc:date>
    </item>
    <item>
      <title>Hi,I think we need to</title>
      <link>https://community.cisco.com/t5/network-security/nat-rule/m-p/2688393#M190993</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I think we need to understand more about your query to give you the exact answer.&lt;/P&gt;&lt;P&gt;NAT has changed a bit between ASA codes pre 8.2 and post 8.3.&lt;/P&gt;&lt;P&gt;Pre 8.2:-&lt;/P&gt;&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/security/asa/asa82/configuration/guide/config/nat_control.html&lt;/P&gt;&lt;P&gt;Post 8.4:-&lt;/P&gt;&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/security/asa/asa84/configuration/guide/asa_84_cli_config/nat_objects.html&lt;/P&gt;&lt;P&gt;Thi should work as a start for you.&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Vibhor Amrodia&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jun 2015 16:02:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-rule/m-p/2688393#M190993</guid>
      <dc:creator>Vibhor Amrodia</dc:creator>
      <dc:date>2015-06-03T16:02:36Z</dc:date>
    </item>
    <item>
      <title>Hi Vibhor,I know the some</title>
      <link>https://community.cisco.com/t5/network-security/nat-rule/m-p/2688394#M190996</link>
      <description>&lt;P&gt;Hi Vibhor,&lt;/P&gt;&lt;P&gt;I know the some basics about Cisco ASA Nat,&lt;/P&gt;&lt;P&gt;My Query is all about ASA Nat Rule,&lt;/P&gt;&lt;P&gt;As Per Nat Rule, ASA first check Nat Excemption, Dynamic, Static,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;in My ASA Configuration: My Statements are Staic, Dynamic, Nat Excemption,&lt;/P&gt;&lt;P&gt;How Nat Rule works with Configuration Parameters?&lt;/P&gt;</description>
      <pubDate>Thu, 04 Jun 2015 10:22:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-rule/m-p/2688394#M190996</guid>
      <dc:creator>shubhamkulkarni39</dc:creator>
      <dc:date>2015-06-04T10:22:00Z</dc:date>
    </item>
    <item>
      <title>Hi,As you pointed out , you</title>
      <link>https://community.cisco.com/t5/network-security/nat-rule/m-p/2688395#M191000</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;As you pointed out , you are using the ASA 8.2 and before NAT syntax.&lt;/P&gt;&lt;P&gt;I think it would be better , if you can post the specific query which you have about the NAT statements.&lt;/P&gt;&lt;P&gt;It would help us reply accordingly.&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Vibhor Amrodia&lt;/P&gt;</description>
      <pubDate>Thu, 04 Jun 2015 10:30:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-rule/m-p/2688395#M191000</guid>
      <dc:creator>Vibhor Amrodia</dc:creator>
      <dc:date>2015-06-04T10:30:58Z</dc:date>
    </item>
    <item>
      <title>Could you Please Explain Me</title>
      <link>https://community.cisco.com/t5/network-security/nat-rule/m-p/2688396#M191002</link>
      <description>&lt;P&gt;Could you Please Explain Me these 4 steps:&lt;/P&gt;&lt;H2 class="p_H_Head1" style="font-size: 14.1680011749268px; color: rgb(51, 102, 102); font-weight: bold; font-family: Arial, Helvetica, sans-serif; margin: 14px 0em 7px -0.1in; line-height: normal;"&gt;oOrder of NAT Commands Used to Match Real Addresses&lt;/H2&gt;&lt;P&gt;&lt;A name="wp1079283" style="color: rgb(0, 0, 0); font-family: Arial, Helvetica, sans-serif; font-size: 12.8800001144409px; line-height: normal; background-color: rgb(255, 255, 255);"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P class="pB1_Body1" style="color: rgb(0, 0, 0); font-family: Arial, Helvetica, sans-serif; font-size: 12.2360000610352px; margin: 1px 0em 6px; line-height: normal;"&gt;The ASA matches real addresses to NAT commands in the following order:&lt;/P&gt;&lt;P&gt;&lt;A name="wp1079284" style="color: rgb(0, 0, 0); font-family: Arial, Helvetica, sans-serif; font-size: 12.8800001144409px; line-height: normal; background-color: rgb(255, 255, 255);"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P class="pNF_NumFirst" style="color: rgb(0, 0, 0); font-family: Arial, Helvetica, sans-serif; font-size: 12.2360000610352px; margin-right: 0em; margin-bottom: 7px; margin-left: 0.25in; text-indent: -0.25in; line-height: normal;"&gt;&lt;B&gt;1.&amp;nbsp;&lt;/B&gt;&lt;IMG alt="" border="0" height="2" src="http://www.cisco.com/c/dam/en/us/td/i/templates/blank.gif" width="10" /&gt;NAT exemption (&lt;B class="cBold"&gt;nat 0 access-list&lt;/B&gt;)—In order, until the first match. Identity NAT is not included in this category; it is included in the regular static NAT or regular NAT category. We do not recommend overlapping addresses in NAT exemption statements because unexpected results can occur.&lt;/P&gt;&lt;P&gt;&lt;A name="wp1079285" style="color: rgb(0, 0, 0); font-family: Arial, Helvetica, sans-serif; font-size: 12.8800001144409px; line-height: normal; background-color: rgb(255, 255, 255);"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P class="pNN_NumNext" style="color: rgb(0, 0, 0); font-family: Arial, Helvetica, sans-serif; font-size: 12.2360000610352px; margin-right: 0em; margin-bottom: 7px; margin-left: 0.25in; text-indent: -0.25in; line-height: normal;"&gt;&lt;B&gt;2.&amp;nbsp;&lt;/B&gt;&lt;IMG alt="" border="0" height="2" src="http://www.cisco.com/c/dam/en/us/td/i/templates/blank.gif" width="10" /&gt;Static NAT and Static PAT (regular and policy) (&lt;B class="cBold"&gt;static&lt;/B&gt;)—In order, until the first match. Static identity NAT is included in this category.&lt;/P&gt;&lt;P&gt;&lt;A name="wp1079286" style="color: rgb(0, 0, 0); font-family: Arial, Helvetica, sans-serif; font-size: 12.8800001144409px; line-height: normal; background-color: rgb(255, 255, 255);"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P class="pNN_NumNext" style="color: rgb(0, 0, 0); font-family: Arial, Helvetica, sans-serif; font-size: 12.2360000610352px; margin-right: 0em; margin-bottom: 7px; margin-left: 0.25in; text-indent: -0.25in; line-height: normal;"&gt;&lt;B&gt;3.&amp;nbsp;&lt;/B&gt;&lt;IMG alt="" border="0" height="2" src="http://www.cisco.com/c/dam/en/us/td/i/templates/blank.gif" width="10" /&gt;Policy dynamic NAT (&lt;B class="cBold"&gt;nat access-list&lt;/B&gt;)—In order, until the first match. Overlapping addresses are allowed.&lt;/P&gt;&lt;P&gt;&lt;A name="wp1079287" style="color: rgb(0, 0, 0); font-family: Arial, Helvetica, sans-serif; font-size: 12.8800001144409px; line-height: normal; background-color: rgb(255, 255, 255);"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P class="pNN_NumNext" style="color: rgb(0, 0, 0); font-family: Arial, Helvetica, sans-serif; font-size: 12.2360000610352px; margin-right: 0em; margin-bottom: 7px; margin-left: 0.25in; text-indent: -0.25in; line-height: normal;"&gt;&lt;B&gt;4.&amp;nbsp;&lt;/B&gt;&lt;IMG alt="" border="0" height="2" src="http://www.cisco.com/c/dam/en/us/td/i/templates/blank.gif" width="10" /&gt;Regular dynamic NAT (&lt;B class="cBold"&gt;nat&lt;/B&gt;)—Best match. Regular identity NAT is included in this category. The order of the NAT commands does not matter; the NAT&lt;B class="cBold"&gt;&amp;nbsp;&lt;/B&gt;statement that best matches the real address is used. For example, you can create a general statement to translate all addresses (0.0.0.0) on an interface. If you want to translate a subset of your network (10.1.1.1) to a different address, then you can create a statement to translate only 10.1.1.1. When 10.1.1.1 makes a connection, the specific statement for 10.1.1.1 is used because it matches the real address best. We do not recommend using overlapping statements; they use more memory and can slow the performance of the ASA.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Jun 2015 11:45:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-rule/m-p/2688396#M191002</guid>
      <dc:creator>shubhamkulkarni39</dc:creator>
      <dc:date>2015-06-04T11:45:25Z</dc:date>
    </item>
  </channel>
</rss>

