<?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: PIX 535 NAT problem in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-535-nat-problem/m-p/527838#M498800</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have never actually tried such a setup, but I believe you could solve your problem by using an acl with your NAT 0 (NAT exemption vs current identity NAT).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list nonat deny ip host 140.32.x.10 152.10.32.4 255.255.255.254&lt;/P&gt;&lt;P&gt;access-list nonat permit ip any any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;no nat (inside) 0 0.0.0.0 0.0.0.0&lt;/P&gt;&lt;P&gt;nat (inside) 0 access-list nonat&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 31 Jul 2006 09:07:44 GMT</pubDate>
    <dc:creator>granberg</dc:creator>
    <dc:date>2006-07-31T09:07:44Z</dc:date>
    <item>
      <title>PIX 535 NAT problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-535-nat-problem/m-p/527837#M498798</link>
      <description>&lt;P&gt;Hello, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry but I'm having a problem with my PIX 535.  I have a PIX 535 with 4 interfaces... inside, DMZ1, DMZ2, and outside. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;inside 140.32.1.x&lt;/P&gt;&lt;P&gt;dmz 192.168.1.0 &lt;/P&gt;&lt;P&gt;outside 140.32.1.x &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have this is in my config and everything works fine:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside) 0 0.0.0.0 0.0.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My problem is this.  I &lt;/P&gt;&lt;P&gt;need to NAT some traffic from my inside interface and then dump it into my VPN tunnel.  The rest of the inside traffic should not be NAT'd and go out to the Internet.  I could do this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list JPS-Web permit host 140.32.x.10 152.10.32.4 255.255.255.254&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;global (outside) 5 140.32.x.30&lt;/P&gt;&lt;P&gt;nat (inside) 5 access-list JPS-Web &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is...won't the NAT 0 override everything I'm trying to do???  I just need the one IP NAT'd when it tries to go to the two Web servers.  It then would go into an IPSEC tunnel and come out at a remote site.  The rest of my inside traffic needs to go out un-NAT'd.  I don't want to break all my user's Internet access just so a couple of users can get to the remote Web servers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Help!!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 09:04:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-535-nat-problem/m-p/527837#M498798</guid>
      <dc:creator>chrismoore63</dc:creator>
      <dc:date>2020-02-21T09:04:45Z</dc:date>
    </item>
    <item>
      <title>Re: PIX 535 NAT problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-535-nat-problem/m-p/527838#M498800</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have never actually tried such a setup, but I believe you could solve your problem by using an acl with your NAT 0 (NAT exemption vs current identity NAT).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list nonat deny ip host 140.32.x.10 152.10.32.4 255.255.255.254&lt;/P&gt;&lt;P&gt;access-list nonat permit ip any any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;no nat (inside) 0 0.0.0.0 0.0.0.0&lt;/P&gt;&lt;P&gt;nat (inside) 0 access-list nonat&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Jul 2006 09:07:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-535-nat-problem/m-p/527838#M498800</guid>
      <dc:creator>granberg</dc:creator>
      <dc:date>2006-07-31T09:07:44Z</dc:date>
    </item>
    <item>
      <title>Re: PIX 535 NAT problem</title>
      <link>https://community.cisco.com/t5/network-security/pix-535-nat-problem/m-p/527839#M498802</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here is a link to explain NAT/STATIC order of operation. Hope it helps... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/customer/products/ps6120/products_configuration_guide_chapter09186a008063b1fa.html#wp1042696" target="_blank"&gt;http://www.cisco.com/en/US/customer/products/ps6120/products_configuration_guide_chapter09186a008063b1fa.html#wp1042696&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Bostjan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Jul 2006 13:05:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-535-nat-problem/m-p/527839#M498802</guid>
      <dc:creator>bfele</dc:creator>
      <dc:date>2006-07-31T13:05:17Z</dc:date>
    </item>
  </channel>
</rss>

