<?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 Why CISCO ASA does NATing by default and not ROUTing ? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/why-cisco-asa-does-nating-by-default-and-not-routing/m-p/1751678#M533418</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Peter,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would need the nat command only if you have nat-control enabled on the ASA, if it is no nat-control, you would just need an access-list to go from your dmz to inside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can check this by:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;show run nat-control&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It will tell you whether it is enabled or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Varun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 16 Aug 2011 15:39:40 GMT</pubDate>
    <dc:creator>varrao</dc:creator>
    <dc:date>2011-08-16T15:39:40Z</dc:date>
    <item>
      <title>Why CISCO ASA does NATing by default and not ROUTing ?</title>
      <link>https://community.cisco.com/t5/network-security/why-cisco-asa-does-nating-by-default-and-not-routing/m-p/1751677#M533417</link>
      <description>&lt;P&gt;Hello, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;my question may sound stupid, but please explain to me the following behavior.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CISCO ASA 5505&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interfaces: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OUTSIDE - 194.50.90.221&amp;nbsp;&amp;nbsp; 255.255.255.0 / security level 0&lt;/P&gt;&lt;P&gt;DMZ - 192.168.12.254&amp;nbsp;&amp;nbsp; 255.255.255.0 / security level 25&lt;/P&gt;&lt;P&gt;INSIDE - 192.168.0.6&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 255.255.255.0 / security level 50&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, if I want to ping from the DMZ to INSIDE, I get an error message "no translation group found for icmp src DMZ: ...... dst: INSIDE...."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I fixed is by adding "NAT 0" onto the INSIDE interface so that packets originating from "INSIDE" that are destined for "DMZ" do not get NAT'd.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now my question is, becasue these are all directly connected networks, how come the firewall does not route the packets, but tries to NAT them instead... ???&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 21:12:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/why-cisco-asa-does-nating-by-default-and-not-routing/m-p/1751677#M533417</guid>
      <dc:creator>Peter Nemec</dc:creator>
      <dc:date>2019-03-11T21:12:28Z</dc:date>
    </item>
    <item>
      <title>Why CISCO ASA does NATing by default and not ROUTing ?</title>
      <link>https://community.cisco.com/t5/network-security/why-cisco-asa-does-nating-by-default-and-not-routing/m-p/1751678#M533418</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Peter,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would need the nat command only if you have nat-control enabled on the ASA, if it is no nat-control, you would just need an access-list to go from your dmz to inside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can check this by:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;show run nat-control&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It will tell you whether it is enabled or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Varun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Aug 2011 15:39:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/why-cisco-asa-does-nating-by-default-and-not-routing/m-p/1751678#M533418</guid>
      <dc:creator>varrao</dc:creator>
      <dc:date>2011-08-16T15:39:40Z</dc:date>
    </item>
    <item>
      <title>Why CISCO ASA does NATing by default and not ROUTing ?</title>
      <link>https://community.cisco.com/t5/network-security/why-cisco-asa-does-nating-by-default-and-not-routing/m-p/1751679#M533419</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A firewall is a security device. It's role is to separate trusted and untrusted networks. Part of that separation is controlled by the security level. You can't go from a less secure network to a more secure network without you specifically granting access (both NAT and ACL).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Aug 2011 15:41:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/why-cisco-asa-does-nating-by-default-and-not-routing/m-p/1751679#M533419</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2011-08-16T15:41:13Z</dc:date>
    </item>
    <item>
      <title>Why CISCO ASA does NATing by default and not ROUTing ?</title>
      <link>https://community.cisco.com/t5/network-security/why-cisco-asa-does-nating-by-default-and-not-routing/m-p/1751680#M533420</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks guys, makes sense now &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;&lt;/P&gt;&lt;P&gt;This was just one of the thinks I wanted to have clarified &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;&lt;/P&gt;&lt;P&gt;yes it is a firewall and not a router &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;By the way, I am still a bit confused, because I tried to run the "show run nat-control" and it shows "no nat-control"...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes I previously added access-lists to allow ICMP traffic flowing from lower sec level to higher sec level, but wont work without having NAT 0 specified in INSIDE interface...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But yeah, makes sense that because this is a firewall and no router, by default, It's supposed to provide the least-permissive conditions for traffic to flow through its interfaces...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Aug 2011 16:54:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/why-cisco-asa-does-nating-by-default-and-not-routing/m-p/1751680#M533420</guid>
      <dc:creator>Peter Nemec</dc:creator>
      <dc:date>2011-08-16T16:54:54Z</dc:date>
    </item>
    <item>
      <title>Why CISCO ASA does NATing by default and not ROUTing ?</title>
      <link>https://community.cisco.com/t5/network-security/why-cisco-asa-does-nating-by-default-and-not-routing/m-p/1751681#M533421</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Peter,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kindly go through the doc, if you have qany queries, feel free to drop in:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/nat_control.html"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/nat_control.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Varun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Aug 2011 17:45:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/why-cisco-asa-does-nating-by-default-and-not-routing/m-p/1751681#M533421</guid>
      <dc:creator>varrao</dc:creator>
      <dc:date>2011-08-16T17:45:46Z</dc:date>
    </item>
    <item>
      <title>Why CISCO ASA does NATing by default and not ROUTing ?</title>
      <link>https://community.cisco.com/t5/network-security/why-cisco-asa-does-nating-by-default-and-not-routing/m-p/1751682#M533422</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks all again, I have read the last article, makes sense, cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Aug 2011 08:48:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/why-cisco-asa-does-nating-by-default-and-not-routing/m-p/1751682#M533422</guid>
      <dc:creator>Peter Nemec</dc:creator>
      <dc:date>2011-08-17T08:48:30Z</dc:date>
    </item>
    <item>
      <title>Why CISCO ASA does NATing by default and not ROUTing ?</title>
      <link>https://community.cisco.com/t5/network-security/why-cisco-asa-does-nating-by-default-and-not-routing/m-p/1751683#M533423</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sure Peter &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; , you can mark the thread as answered if your queries are resolved.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Varun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Aug 2011 09:03:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/why-cisco-asa-does-nating-by-default-and-not-routing/m-p/1751683#M533423</guid>
      <dc:creator>varrao</dc:creator>
      <dc:date>2011-08-17T09:03:57Z</dc:date>
    </item>
  </channel>
</rss>

