<?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: Same network via different interfaces in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-same-network-via-different-interfaces/m-p/492713#M528985</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Lee,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There should not be much an issue as pix will take more specific route. But you should take care that there is not static statement for the entire subnet pointing to inside. if there is one you need to remove that and use nat will access-list instead and eliminating that IP address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Arun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 02 Jan 2006 04:25:38 GMT</pubDate>
    <dc:creator>arunsing</dc:creator>
    <dc:date>2006-01-02T04:25:38Z</dc:date>
    <item>
      <title>PIX: Same network via different interfaces</title>
      <link>https://community.cisco.com/t5/network-security/pix-same-network-via-different-interfaces/m-p/492711#M528980</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a pix that has a route to a network on my inside interface, but there is one host within that network range that is on an outside interface. How can I have a route to a network on my inside interface and still be able to connect to the host on my outside interface? Host routes are not an option becuase the host address lives on both sides. Both sides need to communicate with each other.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas???&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lee&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:37:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-same-network-via-different-interfaces/m-p/492711#M528980</guid>
      <dc:creator>lxcollin1</dc:creator>
      <dc:date>2020-02-21T08:37:11Z</dc:date>
    </item>
    <item>
      <title>Re: PIX: Same network via different interfaces</title>
      <link>https://community.cisco.com/t5/network-security/pix-same-network-via-different-interfaces/m-p/492712#M528983</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;the easiest option would be changing the outside hosts IP address.&lt;/P&gt;&lt;P&gt;In case this is not an option you need to configure NAT with a NAT IP assigned inside for the outside host and an outside IP for the inside host(s).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Host inside and outside to communicate: 10.1.1.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip nat inside source static 10.1.1.1 192.168.1.1&lt;/P&gt;&lt;P&gt;ip nat outside source static 10.1.1.1 192.168.2.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Host inside should ping 192.168.2.1 and connect to Host outside, who will respond to 192.168.1.1.&lt;/P&gt;&lt;P&gt;IP routing needs to be setup for 192.168.1.1 und 192.168.2.1 respectively.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Martin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 01 Jan 2006 19:51:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-same-network-via-different-interfaces/m-p/492712#M528983</guid>
      <dc:creator>mheusinger</dc:creator>
      <dc:date>2006-01-01T19:51:00Z</dc:date>
    </item>
    <item>
      <title>Re: PIX: Same network via different interfaces</title>
      <link>https://community.cisco.com/t5/network-security/pix-same-network-via-different-interfaces/m-p/492713#M528985</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Lee,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There should not be much an issue as pix will take more specific route. But you should take care that there is not static statement for the entire subnet pointing to inside. if there is one you need to remove that and use nat will access-list instead and eliminating that IP address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Arun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Jan 2006 04:25:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-same-network-via-different-interfaces/m-p/492713#M528985</guid>
      <dc:creator>arunsing</dc:creator>
      <dc:date>2006-01-02T04:25:38Z</dc:date>
    </item>
    <item>
      <title>Re: PIX: Same network via different interfaces</title>
      <link>https://community.cisco.com/t5/network-security/pix-same-network-via-different-interfaces/m-p/492714#M528987</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;totally agree with arun.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;e.g.&lt;/P&gt;&lt;P&gt;pix# sh route&lt;/P&gt;&lt;P&gt;        outside 192.168.2.154 255.255.255.255 192.168.1.1 1 OTHER static&lt;/P&gt;&lt;P&gt;        outside 192.168.2.157 255.255.255.255 192.168.1.1 1 OTHER static&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;pix# sh ip&lt;/P&gt;&lt;P&gt;System IP Addresses:&lt;/P&gt;&lt;P&gt;	ip address dmz1 192.168.2.155 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the pix has 192.168.2.x subnet directly connected with interface dmz1, however, the static routes are still effective. in fact, this sample is being cut/paste from a production box.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Jan 2006 22:44:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-same-network-via-different-interfaces/m-p/492714#M528987</guid>
      <dc:creator>jackko</dc:creator>
      <dc:date>2006-01-02T22:44:49Z</dc:date>
    </item>
  </channel>
</rss>

