<?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: NATing with Duplicate Subnets in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/nating-with-duplicate-subnets/m-p/675105#M1054733</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check this link for more info:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/tech/tk583/tk372/technologies_configuration_example09186a00800b07ed.shtml" target="_blank"&gt;http://www.cisco.com/en/US/tech/tk583/tk372/technologies_configuration_example09186a00800b07ed.shtml&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 13 Oct 2006 12:23:23 GMT</pubDate>
    <dc:creator>drolemc</dc:creator>
    <dc:date>2006-10-13T12:23:23Z</dc:date>
    <item>
      <title>NATing with Duplicate Subnets</title>
      <link>https://community.cisco.com/t5/network-security/nating-with-duplicate-subnets/m-p/675104#M1054727</link>
      <description>&lt;P&gt;I have an issue where I need to set up a site to site VPN with a partner company through a PIX.  The partner company has a site to site tunnel with a vendor that is a duplicate subnet to ours (10.0.0.0/16).  Can anyone point me in the right direction as to performing a NAT on a PIX to change my subnet to the partner to look like 10.241.21.0/24?  Thanks in advance for any and all help provided.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 09:13:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nating-with-duplicate-subnets/m-p/675104#M1054727</guid>
      <dc:creator>tkowalski</dc:creator>
      <dc:date>2020-02-21T09:13:26Z</dc:date>
    </item>
    <item>
      <title>Re: NATing with Duplicate Subnets</title>
      <link>https://community.cisco.com/t5/network-security/nating-with-duplicate-subnets/m-p/675105#M1054733</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check this link for more info:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/tech/tk583/tk372/technologies_configuration_example09186a00800b07ed.shtml" target="_blank"&gt;http://www.cisco.com/en/US/tech/tk583/tk372/technologies_configuration_example09186a00800b07ed.shtml&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Oct 2006 12:23:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nating-with-duplicate-subnets/m-p/675105#M1054733</guid>
      <dc:creator>drolemc</dc:creator>
      <dc:date>2006-10-13T12:23:23Z</dc:date>
    </item>
    <item>
      <title>Re: NATing with Duplicate Subnets</title>
      <link>https://community.cisco.com/t5/network-security/nating-with-duplicate-subnets/m-p/675106#M1054736</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the input.  I have seen that article and it does not apply to my situation.  There is also an article regarding a PIX and a 3000 concentrator that is very close, but not quite what I am looking for.  See this article also...&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/tech/tk583/tk372/technologies_configuration_example09186a00800949f1.shtml" target="_blank"&gt;http://www.cisco.com/en/US/customer/tech/tk583/tk372/technologies_configuration_example09186a00800949f1.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again for the input....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Oct 2006 13:14:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nating-with-duplicate-subnets/m-p/675106#M1054736</guid>
      <dc:creator>tkowalski</dc:creator>
      <dc:date>2006-10-13T13:14:57Z</dc:date>
    </item>
  </channel>
</rss>

