<?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 Re: Creating a NAT exemption between an ASA and a Cisco router in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4944309#M1105215</link>
    <description>&lt;P&gt;If you use tunnel then you don't need any NONAT in Asa and in router except NONAT for tunnel head which is&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Nonat host&amp;nbsp;&lt;SPAN&gt;10.12.200.166 host&amp;nbsp;10.12.200.x&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Because traffic will pass encapsulation inside tunnel head.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 19 Oct 2023 14:27:47 GMT</pubDate>
    <dc:creator>MHM Cisco World</dc:creator>
    <dc:date>2023-10-19T14:27:47Z</dc:date>
    <item>
      <title>Creating a NAT exemption between an ASA and a Cisco router</title>
      <link>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4943282#M1105189</link>
      <description>&lt;P&gt;Forum,&lt;/P&gt;&lt;P&gt;I have been tasked with creating a NAT exemption for one of our vlans/networks.&lt;/P&gt;&lt;P&gt;I know we used to use a "NONAT" rule back in the legacy pix days.. yes i am dating myself a bit.&lt;/P&gt;&lt;P&gt;I am not sure how to tackle this on our ASA which is a model 5516 running version&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Oct 2023 20:34:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4943282#M1105189</guid>
      <dc:creator>KMNRuser</dc:creator>
      <dc:date>2023-10-18T20:34:46Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a NAT exemption between an ASA and a Cisco router</title>
      <link>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4943284#M1105190</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1049471"&gt;@KMNRuser&lt;/a&gt; ASA NAT exemption rule example:-&lt;/P&gt;
&lt;PRE&gt;object network INSIDE&lt;BR /&gt;&amp;nbsp;subnet 192.168.10.0 255.255.255.0&lt;BR /&gt;object network REMOTE&lt;BR /&gt;&amp;nbsp;subnet 10.1.1.0 255.255.255.0&lt;BR /&gt;nat (INSIDE,OUTSIDE) source static INSIDE INSIDE destination static REMOTE REMOTE &lt;/PRE&gt;
&lt;P&gt;amend object and nameif's to fit your needs. &lt;/P&gt;</description>
      <pubDate>Wed, 18 Oct 2023 20:38:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4943284#M1105190</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2023-10-18T20:38:40Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a NAT exemption between an ASA and a Cisco router</title>
      <link>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4944304#M1105213</link>
      <description>&lt;P&gt;Rob,&lt;/P&gt;&lt;P&gt;Thanks for&amp;nbsp; your response.&lt;/P&gt;&lt;P&gt;I am wondering about the router side.&lt;/P&gt;&lt;P&gt;I am thinking it would be on the router side where i also need to make a configuration that would keep that network from being translated.&lt;/P&gt;&lt;P&gt;The network in question is&amp;nbsp;10.200.1.49 255.255.255.240.&amp;nbsp; The configuration on the router for the tunnel back to the Firewall is:&lt;/P&gt;&lt;P&gt;interface Tunnel11&lt;BR /&gt;ip address 10.12.200.166 255.255.255.252&lt;BR /&gt;tunnel source Loopback0&lt;BR /&gt;tunnel mode ipsec ipv4&lt;BR /&gt;tunnel destination 10.2.4.100&lt;BR /&gt;tunnel protection ipsec profile SCADA_PRI&lt;/P&gt;&lt;P&gt;and the only NAT statement i see on the router at all is:&lt;/P&gt;&lt;P&gt;"ip nat inside source list Overload interface GigabitEthernet0/0/0 overload"&lt;/P&gt;&lt;P&gt;I am not sure how to write the statement to exclude the network from the NAT.&lt;/P&gt;&lt;P&gt;Thanks again,&lt;/P&gt;&lt;P&gt;KMNRUser&lt;/P&gt;</description>
      <pubDate>Thu, 19 Oct 2023 14:21:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4944304#M1105213</guid>
      <dc:creator>KMNRuser</dc:creator>
      <dc:date>2023-10-19T14:21:16Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a NAT exemption between an ASA and a Cisco router</title>
      <link>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4944306#M1105214</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1049471"&gt;@KMNRuser&lt;/a&gt; on the router side, configure the NAT ACL with a new ACE to deny traffic between the local networks and the remote VPN networks. This traffic will not be subjected to NAT translation. This ACE &lt;U&gt;must be above&lt;/U&gt; the existing ACE that identifies (permits) traffic to be translated.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Oct 2023 14:23:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4944306#M1105214</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2023-10-19T14:23:59Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a NAT exemption between an ASA and a Cisco router</title>
      <link>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4944309#M1105215</link>
      <description>&lt;P&gt;If you use tunnel then you don't need any NONAT in Asa and in router except NONAT for tunnel head which is&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Nonat host&amp;nbsp;&lt;SPAN&gt;10.12.200.166 host&amp;nbsp;10.12.200.x&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Because traffic will pass encapsulation inside tunnel head.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Oct 2023 14:27:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4944309#M1105215</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-10-19T14:27:47Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a NAT exemption between an ASA and a Cisco router</title>
      <link>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4944340#M1105217</link>
      <description>&lt;P&gt;Rob,&lt;/P&gt;&lt;P&gt;Your response makes sense, but for the life of me I am unable to find the existing NAT ACL on the router.&lt;/P&gt;&lt;P&gt;That being said, there are several ACL's on the router.&amp;nbsp; But none jump out with a description of NAT..&lt;/P&gt;&lt;P&gt;I know there has to be one as we have a working tunnel..&lt;/P&gt;&lt;P&gt;Here are the ACL's on the box:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ip access-list standard Member-Routes&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;10 permit 192.168.150.62&lt;/P&gt;&lt;P&gt;&amp;nbsp;20 permit 10.200.1.48 0.0.0.15&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ip access-list standard R_Access&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;10 permit 65.222.174.0 0.0.0.255&lt;/P&gt;&lt;P&gt;&amp;nbsp;20 permit 65.222.216.216 0.0.0.7&lt;/P&gt;&lt;P&gt;&amp;nbsp;30 permit 65.199.14.16 0.0.0.15&lt;/P&gt;&lt;P&gt;&amp;nbsp;40 permit 209.10.79.64 0.0.0.63&lt;/P&gt;&lt;P&gt;&amp;nbsp;50 permit 24.101.151.16 0.0.0.7&lt;/P&gt;&lt;P&gt;&amp;nbsp;60 permit 24.101.151.24 0.0.0.7&lt;/P&gt;&lt;P&gt;&amp;nbsp;70 permit 192.168.1.0 0.0.0.255&lt;/P&gt;&lt;P&gt;&amp;nbsp;80 deny&amp;nbsp;&amp;nbsp; any&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ip access-list extended CAP-FILTER&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;10 permit ip host 10.200.1.51 host 10.12.3.101&lt;/P&gt;&lt;P&gt;&amp;nbsp;20 permit ip host 10.12.3.101 host 10.200.1.51&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ip access-list extended CAP-FILTER2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;10 permit ip host 192.168.150.62 host 10.2.4.100&lt;/P&gt;&lt;P&gt;&amp;nbsp;20 permit ip host 10.2.4.100 host 192.168.150.62&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ip access-list extended Overload&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;10 permit ip 10.200.1.48 0.0.0.15 any&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ip access-list extended 100&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;10 permit ip 172.17.10.4 0.0.0.3 172.17.10.0 0.0.0.3&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ip access-list extended 110&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;10 permit ip 10.200.1.48 0.0.0.15 192.168.1.0 0.0.0.255&lt;/P&gt;&lt;P&gt;&amp;nbsp;20 permit ip 10.200.1.48 0.0.0.15 10.1.1.0 0.0.0.255&lt;/P&gt;&lt;P&gt;&amp;nbsp;30 permit ip 10.200.1.48 0.0.0.15 192.168.3.0 0.0.0.255&lt;/P&gt;&lt;P&gt;&amp;nbsp;40 permit ip 10.200.1.48 0.0.0.15 192.168.7.0 0.0.0.255&lt;/P&gt;&lt;P&gt;&amp;nbsp;50 permit ip 10.200.1.48 0.0.0.15 10.254.254.0 0.0.0.255&lt;/P&gt;&lt;P&gt;&amp;nbsp;60 permit ip 10.200.1.48 0.0.0.15 192.168.176.0 0.0.0.255&lt;/P&gt;&lt;P&gt;&amp;nbsp;70 permit ip host 192.168.150.62 192.168.1.0 0.0.0.255&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ip access-list extended 120&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;10 permit ip 10.200.1.48 0.0.0.15 10.2.1.0 0.0.0.255&lt;/P&gt;&lt;P&gt;&amp;nbsp;20 permit ip 10.200.1.48 0.0.0.15 10.2.3.0 0.0.0.255&lt;/P&gt;&lt;P&gt;&amp;nbsp;30 permit ip 10.200.1.48 0.0.0.15 10.2.251.0 0.0.0.255&lt;/P&gt;&lt;P&gt;&amp;nbsp;40 permit ip host 192.168.150.62 10.2.1.0 0.0.0.255&lt;/P&gt;&lt;P&gt;&amp;nbsp;50 permit ip host 192.168.150.62 host 10.2.4.100&lt;/P&gt;&lt;P&gt;&amp;nbsp;60 permit ip host 192.168.150.62 host 10.12.254.146&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ip access-list extended 130&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;10 permit ip host 192.168.150.62 10.11.3.0 0.0.0.255&lt;/P&gt;&lt;P&gt;&amp;nbsp;20 permit ip 10.200.1.48 0.0.0.15 10.11.3.0 0.0.0.255&lt;/P&gt;&lt;P&gt;&amp;nbsp;30 permit ip 10.200.1.48 0.0.0.15 10.13.3.0 0.0.0.255&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ip access-list extended 140&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;10 permit ip host 10.200.1.51 host 10.12.3.101&lt;/P&gt;&lt;P&gt;&amp;nbsp;20 permit ip host 10.200.1.51 host 10.12.3.102&lt;/P&gt;&lt;P&gt;&amp;nbsp;30 permit ip host 10.200.1.51 host 10.12.11.104&lt;/P&gt;&lt;P&gt;&amp;nbsp;40 permit ip host 10.200.1.52 host 10.12.3.101&lt;/P&gt;&lt;P&gt;&amp;nbsp;50 permit ip host 10.200.1.52 host 10.12.3.102&lt;/P&gt;&lt;P&gt;&amp;nbsp;60 permit ip host 10.200.1.52 host 10.12.11.104&lt;/P&gt;&lt;P&gt;&amp;nbsp;70 permit ip host 10.200.1.49 host 10.12.3.101&lt;/P&gt;&lt;P&gt;&amp;nbsp;80 permit ip host 10.200.1.49 host 10.12.3.102&lt;/P&gt;&lt;P&gt;&amp;nbsp;90 permit ip host 10.200.1.49 host 10.12.11.104&lt;/P&gt;&lt;P&gt;Could it be one of these?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Oct 2023 15:11:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4944340#M1105217</guid>
      <dc:creator>KMNRuser</dc:creator>
      <dc:date>2023-10-19T15:11:27Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a NAT exemption between an ASA and a Cisco router</title>
      <link>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4944346#M1105218</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1049471"&gt;@KMNRuser&lt;/a&gt; it looks to be called &lt;STRONG&gt;Overload&lt;/STRONG&gt;. So an an ACE number #5 to deny the traffic from local networks and remote networks.&lt;/P&gt;
&lt;P&gt;"ip nat inside source list &lt;STRONG&gt;Overload&lt;/STRONG&gt; interface GigabitEthernet0/0/0 overload&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;ip access-list extended Overload&lt;BR /&gt;&lt;/STRONG&gt;&amp;nbsp;10 permit ip 10.200.1.48 0.0.0.15 any&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Oct 2023 15:16:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4944346#M1105218</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2023-10-19T15:16:30Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a NAT exemption between an ASA and a Cisco router</title>
      <link>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4945155#M1105262</link>
      <description>&lt;P&gt;I went to command line on the router in question.&amp;nbsp; Is this router IOS apparently there is not a "nonat" command..&lt;/P&gt;&lt;P&gt;ODEC-Cheriton-RTR# conf t&lt;BR /&gt;Enter configuration commands, one per line. End with CNTL/Z.&lt;BR /&gt;ODEC-Cheriton-RTR(config)#nonat ?&lt;BR /&gt;% Unrecognized command&lt;BR /&gt;ODEC-Cheriton-RTR(config)#nonat ?&lt;BR /&gt;% Unrecognized command&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;perhaps I am missing what you are trying to indicate?..thx&lt;/P&gt;</description>
      <pubDate>Fri, 20 Oct 2023 17:52:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4945155#M1105262</guid>
      <dc:creator>KMNRuser</dc:creator>
      <dc:date>2023-10-20T17:52:29Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a NAT exemption between an ASA and a Cisco router</title>
      <link>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4945156#M1105263</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1049471"&gt;@KMNRuser&lt;/a&gt; there is no "nonat" command, you define what to nat using a "pemit" in the NAT ACL and you define what not to nat using a "deny" in the NAT ACL on the router, which is above the permit ACE.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Oct 2023 17:56:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4945156#M1105263</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2023-10-20T17:56:47Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a NAT exemption between an ASA and a Cisco router</title>
      <link>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4945158#M1105264</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/97036"&gt;@Rob Ingram&lt;/a&gt;&amp;nbsp;answer you.&lt;/P&gt;
&lt;P&gt;There is no command nonat.&lt;/P&gt;
&lt;P&gt;I write my post to explain for which you need nonat in router and asa.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Oct 2023 18:00:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/creating-a-nat-exemption-between-an-asa-and-a-cisco-router/m-p/4945158#M1105264</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-10-20T18:00:24Z</dc:date>
    </item>
  </channel>
</rss>

