<?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 traffic in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ipsec-tunnel-traffic/m-p/204560#M1061002</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The setup shown in figure 01.gif won't work simply because traffic received by the PIX on an interface is not sent out over the same. If however you place PIX 2 and PIX 3 on differnt interfaces on PIX central... the issue boils down to passing encrypted traffic through the PIX. For that see the doc Configuring an IPSec Tunnel through a Firewall with NAT at &lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/tech/tk648/tk367/technologies_configuration_example09186a008009486e.shtml" target="_blank"&gt;http://www.cisco.com/en/US/tech/tk648/tk367/technologies_configuration_example09186a008009486e.shtml&lt;/A&gt;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 03 Feb 2003 21:00:26 GMT</pubDate>
    <dc:creator>mchin345</dc:creator>
    <dc:date>2003-02-03T21:00:26Z</dc:date>
    <item>
      <title>IPSEC tunnel traffic</title>
      <link>https://community.cisco.com/t5/network-security/ipsec-tunnel-traffic/m-p/204559#M1061001</link>
      <description>&lt;P&gt;Is it possible to configure the following:&lt;/P&gt;&lt;P&gt;networkA(watchguard firewall) --ipsec--&amp;gt;networkB(pix)--ipsec--&amp;gt;networkC(pix)  &lt;/P&gt;&lt;P&gt;where connection atempts from networkA to networkC are translated to networkB addresses first so that connections are transparent to networkC?&lt;/P&gt;&lt;P&gt;need to connect networkA to networkC through networkB.  no changes can be made to networkC.&lt;/P&gt;&lt;P&gt;currently traffic from networkA to networkC results in:  402103: identity doesn't match negotiated identity on networkB pix.&lt;/P&gt;&lt;P&gt;for ex: using &lt;A class="jive-link-custom" href="http://www.cisco.com/warp/customer/110/pixhubspoke-01.gif" target="_blank"&gt;http://www.cisco.com/warp/customer/110/pixhubspoke-01.gif&lt;/A&gt;  , how to make traffic go from pix2 to pix3 through pixCentral.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:31:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ipsec-tunnel-traffic/m-p/204559#M1061001</guid>
      <dc:creator>b.s</dc:creator>
      <dc:date>2020-02-21T06:31:40Z</dc:date>
    </item>
    <item>
      <title>Re: IPSEC tunnel traffic</title>
      <link>https://community.cisco.com/t5/network-security/ipsec-tunnel-traffic/m-p/204560#M1061002</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The setup shown in figure 01.gif won't work simply because traffic received by the PIX on an interface is not sent out over the same. If however you place PIX 2 and PIX 3 on differnt interfaces on PIX central... the issue boils down to passing encrypted traffic through the PIX. For that see the doc Configuring an IPSec Tunnel through a Firewall with NAT at &lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/tech/tk648/tk367/technologies_configuration_example09186a008009486e.shtml" target="_blank"&gt;http://www.cisco.com/en/US/tech/tk648/tk367/technologies_configuration_example09186a008009486e.shtml&lt;/A&gt;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Feb 2003 21:00:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ipsec-tunnel-traffic/m-p/204560#M1061002</guid>
      <dc:creator>mchin345</dc:creator>
      <dc:date>2003-02-03T21:00:26Z</dc:date>
    </item>
  </channel>
</rss>

