<?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: NAT question... in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/nat-question/m-p/2270258#M346558</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess you already asked something like this on the previous thread.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you situation is still so that NO HOSTS need to be NATed through the firewall then you can simply LEAVE OUT ALL NAT configurations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Generally when people need to exempt hosts from NAT they usually only have certain destination networks for which this should apply. (VPN connections). So you usually define destination parameters for the NAT configuration also.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then you might naturally have public subnets behind the firewall that dont need NAT. As long as no other NAT rule matches these public subnets as a source then you can simply leave out all NAT configuration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From what I tested I wouldnt probably suggest the above NAT configuration even though I mentioned it in the other thread. It might possibly even cause problems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest the other format which basically is that you define the source networks behind that interface under an &lt;STRONG&gt;"object-group network"&lt;/STRONG&gt; and then configure the NAT rule&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;object-group network NETWORKS&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object &lt;NETWORK&gt; &lt;MASK&gt;&lt;/MASK&gt;&lt;/NETWORK&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object &lt;NETWORK&gt; &lt;MASK&gt;&lt;/MASK&gt;&lt;/NETWORK&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;nat (interface,any) source static NETWORKS NETWORKS&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pretty hard to say more than that when dont have exact picture of the situation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 Jul 2013 18:50:23 GMT</pubDate>
    <dc:creator>Jouni Forss</dc:creator>
    <dc:date>2013-07-11T18:50:23Z</dc:date>
    <item>
      <title>NAT question...</title>
      <link>https://community.cisco.com/t5/network-security/nat-question/m-p/2270257#M346557</link>
      <description>&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Quick question, if i want to do NAT exception for &lt;STRONG&gt;ALL ip traffic&lt;/STRONG&gt; on an interface in version 8.4(2). what should i do?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;just want to double check it... would it work or should i use another method: &lt;STRONG&gt;nat (&lt;EM&gt;interface&lt;/EM&gt;,any) source static any any&lt;/STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Thanks,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Soroush.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 02:11:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-question/m-p/2270257#M346557</guid>
      <dc:creator>smehrnia</dc:creator>
      <dc:date>2019-03-12T02:11:08Z</dc:date>
    </item>
    <item>
      <title>Re: NAT question...</title>
      <link>https://community.cisco.com/t5/network-security/nat-question/m-p/2270258#M346558</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess you already asked something like this on the previous thread.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you situation is still so that NO HOSTS need to be NATed through the firewall then you can simply LEAVE OUT ALL NAT configurations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Generally when people need to exempt hosts from NAT they usually only have certain destination networks for which this should apply. (VPN connections). So you usually define destination parameters for the NAT configuration also.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then you might naturally have public subnets behind the firewall that dont need NAT. As long as no other NAT rule matches these public subnets as a source then you can simply leave out all NAT configuration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From what I tested I wouldnt probably suggest the above NAT configuration even though I mentioned it in the other thread. It might possibly even cause problems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest the other format which basically is that you define the source networks behind that interface under an &lt;STRONG&gt;"object-group network"&lt;/STRONG&gt; and then configure the NAT rule&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;object-group network NETWORKS&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object &lt;NETWORK&gt; &lt;MASK&gt;&lt;/MASK&gt;&lt;/NETWORK&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; network-object &lt;NETWORK&gt; &lt;MASK&gt;&lt;/MASK&gt;&lt;/NETWORK&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;nat (interface,any) source static NETWORKS NETWORKS&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pretty hard to say more than that when dont have exact picture of the situation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Jul 2013 18:50:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-question/m-p/2270258#M346558</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-07-11T18:50:23Z</dc:date>
    </item>
  </channel>
</rss>

