<?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 525 NAT in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-525-nat/m-p/596573#M498409</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's actually pretty common.  What you need to do is explore the policy nat features introduced in PIX OS 6.2.  &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/sw/secursw/ps2120/products_configuration_guide_chapter09186a0080172786.html#wp1113601" target="_blank"&gt;http://www.cisco.com/en/US/customer/products/sw/secursw/ps2120/products_configuration_guide_chapter09186a0080172786.html#wp1113601&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH Pls Rate!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 Aug 2006 17:13:02 GMT</pubDate>
    <dc:creator>mmorris11</dc:creator>
    <dc:date>2006-08-14T17:13:02Z</dc:date>
    <item>
      <title>PIX 525 NAT</title>
      <link>https://community.cisco.com/t5/network-security/pix-525-nat/m-p/596572#M498408</link>
      <description>&lt;P&gt;I have a weird situation that I could use some help with.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a customer that is using an RFC 1918 range internally. One the remote end of an IPSEC VPN a vendor is using in part some of the same block. I need to be able to NAT two system to new address for bi-directional communication. I also need to be able to let those two original system to be able to access the internet as needed being globally translated to the address already in that pool/interface on the original customer PIX.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 09:06:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-525-nat/m-p/596572#M498408</guid>
      <dc:creator>enforcers</dc:creator>
      <dc:date>2020-02-21T09:06:42Z</dc:date>
    </item>
    <item>
      <title>Re: PIX 525 NAT</title>
      <link>https://community.cisco.com/t5/network-security/pix-525-nat/m-p/596573#M498409</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's actually pretty common.  What you need to do is explore the policy nat features introduced in PIX OS 6.2.  &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/sw/secursw/ps2120/products_configuration_guide_chapter09186a0080172786.html#wp1113601" target="_blank"&gt;http://www.cisco.com/en/US/customer/products/sw/secursw/ps2120/products_configuration_guide_chapter09186a0080172786.html#wp1113601&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH Pls Rate!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Aug 2006 17:13:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-525-nat/m-p/596573#M498409</guid>
      <dc:creator>mmorris11</dc:creator>
      <dc:date>2006-08-14T17:13:02Z</dc:date>
    </item>
  </channel>
</rss>

