<?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: IPsec Tunnel PIX issues in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ipsec-tunnel-pix-issues/m-p/1482826#M667686</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You would need to create mirror image crypto ACL on the PIX and Fortigate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Based on the network diagram, I assume that from the PIX end, your traffic would be from 10.41.0.0/16, hence that would be the interesting traffic for your crypto ACL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, looks like you have overlapping networks between your Fortigate LAN and PIX LAN as both falls under the 10.0.0.0 network. If your Fortigate LAN /8? If it is, then it's overlapping. You would need to NAT the traffic so it's not overlapping because routing will not work when it's overlapping subnets. If your Fortigate LAN is /24, then it's OK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is a sample configuration for overlapping subnet for your reference:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a0080b37d0b.shtml"&gt;http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a0080b37d0b.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 21 Jul 2010 21:15:18 GMT</pubDate>
    <dc:creator>Jennifer Halim</dc:creator>
    <dc:date>2010-07-21T21:15:18Z</dc:date>
    <item>
      <title>IPsec Tunnel PIX issues</title>
      <link>https://community.cisco.com/t5/network-security/ipsec-tunnel-pix-issues/m-p/1482824#M667633</link>
      <description>&lt;P&gt;Can anyone provide me soln for the below&lt;/P&gt;&lt;P&gt;My goal is to create an ipsec tunnel between my pix and fortigate(other vendor)&lt;BR /&gt;I am facing a lot of issues&lt;/P&gt;&lt;P&gt;Site A network looks like this&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;---10.41.x.x/16---switch(192.168.1.1/30)----(192.168.1.2)pix--122.x.x.x----internet&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Site B look like this&lt;/P&gt;&lt;P&gt;10.x.x.x/8----fortigate---116.x.x.x---internet&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Before establishing tunnel i tried to ping the pix outside address from my fortigate and pinging fine&lt;BR /&gt;{As public ip its fine and reachable}&lt;/P&gt;&lt;P&gt;But after i create ipsec tunnel from fortigate its not pinging my pix firewall outside ip! what might be the issue? and its not even pinging directly connected gateway ip&lt;/P&gt;&lt;P&gt;one more i need to know is while creating cryptomap on pix,which network i have to define&lt;/P&gt;&lt;P&gt;192.168.x.x or 10.41.x.x ?&lt;/P&gt;&lt;P&gt;Do i need to create any static route ? for internal subnet reachability? if so how ?&lt;/P&gt;&lt;P&gt;can some one explain in detail to address these issues ?&lt;/P&gt;&lt;P&gt;Seeking help from experts&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Pramod&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 18:14:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ipsec-tunnel-pix-issues/m-p/1482824#M667633</guid>
      <dc:creator>pramod</dc:creator>
      <dc:date>2019-03-11T18:14:15Z</dc:date>
    </item>
    <item>
      <title>Re: IPsec Tunnel PIX issues</title>
      <link>https://community.cisco.com/t5/network-security/ipsec-tunnel-pix-issues/m-p/1482825#M667670</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The interesting traffic should be between your 10.41.x.x on site A and the 10.x.x.x on site B( if those indeed are your networks). Is that what has been defined on the PIX and fortigate?&lt;/P&gt;&lt;P&gt;Also th route to be added on the PIX should be&lt;/P&gt;&lt;P&gt;route inside 10.41.x.x 255.255.0.0 192.168.1.1&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Jul 2010 11:37:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ipsec-tunnel-pix-issues/m-p/1482825#M667670</guid>
      <dc:creator>rahgovin</dc:creator>
      <dc:date>2010-07-21T11:37:58Z</dc:date>
    </item>
    <item>
      <title>Re: IPsec Tunnel PIX issues</title>
      <link>https://community.cisco.com/t5/network-security/ipsec-tunnel-pix-issues/m-p/1482826#M667686</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You would need to create mirror image crypto ACL on the PIX and Fortigate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Based on the network diagram, I assume that from the PIX end, your traffic would be from 10.41.0.0/16, hence that would be the interesting traffic for your crypto ACL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, looks like you have overlapping networks between your Fortigate LAN and PIX LAN as both falls under the 10.0.0.0 network. If your Fortigate LAN /8? If it is, then it's overlapping. You would need to NAT the traffic so it's not overlapping because routing will not work when it's overlapping subnets. If your Fortigate LAN is /24, then it's OK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is a sample configuration for overlapping subnet for your reference:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a0080b37d0b.shtml"&gt;http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a0080b37d0b.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Jul 2010 21:15:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ipsec-tunnel-pix-issues/m-p/1482826#M667686</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2010-07-21T21:15:18Z</dc:date>
    </item>
  </channel>
</rss>

