<?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 PIX, as a router on a stick, inside int redirect ?? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-as-a-router-on-a-stick-inside-int-redirect/m-p/743240#M1021929</link>
    <description>&lt;P&gt;Not sure why the customer wants this but they want to use the inside int of a PIX as a default gateway for users on one inside network, 192.168.x.x to redirect to another inside network 10.x.x.x, I.e. router on a stick kind of deal.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't think the PIX can do this. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, it does take a static route:&lt;/P&gt;&lt;P&gt;inside 192.16.20.0 255.255.255.0 10.4.2.31 1 OTHER static&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;...again both networks are on the inside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this even possible?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;m.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 10:32:45 GMT</pubDate>
    <dc:creator>mprescher</dc:creator>
    <dc:date>2019-03-11T10:32:45Z</dc:date>
    <item>
      <title>PIX, as a router on a stick, inside int redirect ??</title>
      <link>https://community.cisco.com/t5/network-security/pix-as-a-router-on-a-stick-inside-int-redirect/m-p/743240#M1021929</link>
      <description>&lt;P&gt;Not sure why the customer wants this but they want to use the inside int of a PIX as a default gateway for users on one inside network, 192.168.x.x to redirect to another inside network 10.x.x.x, I.e. router on a stick kind of deal.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't think the PIX can do this. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, it does take a static route:&lt;/P&gt;&lt;P&gt;inside 192.16.20.0 255.255.255.0 10.4.2.31 1 OTHER static&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;...again both networks are on the inside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this even possible?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;m.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 10:32:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-as-a-router-on-a-stick-inside-int-redirect/m-p/743240#M1021929</guid>
      <dc:creator>mprescher</dc:creator>
      <dc:date>2019-03-11T10:32:45Z</dc:date>
    </item>
    <item>
      <title>Re: PIX, as a router on a stick, inside int redirect ??</title>
      <link>https://community.cisco.com/t5/network-security/pix-as-a-router-on-a-stick-inside-int-redirect/m-p/743241#M1021931</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you probably need to use hairpinning for this...available in 7.x PIX OS&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00805734ae.shtml#ra-sol-2" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00805734ae.shtml#ra-sol-2&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you have a spare interface, maybe you could just use that, and route traffic between these networks through the pix.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jun 2007 19:35:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-as-a-router-on-a-stick-inside-int-redirect/m-p/743241#M1021931</guid>
      <dc:creator>srue</dc:creator>
      <dc:date>2007-06-19T19:35:00Z</dc:date>
    </item>
    <item>
      <title>Re: PIX, as a router on a stick, inside int redirect ??</title>
      <link>https://community.cisco.com/t5/network-security/pix-as-a-router-on-a-stick-inside-int-redirect/m-p/743242#M1021932</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes it is possible only with version 7.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jun 2007 19:35:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-as-a-router-on-a-stick-inside-int-redirect/m-p/743242#M1021932</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2007-06-19T19:35:42Z</dc:date>
    </item>
    <item>
      <title>Re: PIX, as a router on a stick, inside int redirect ??</title>
      <link>https://community.cisco.com/t5/network-security/pix-as-a-router-on-a-stick-inside-int-redirect/m-p/743243#M1021934</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;In addition to what's been suggested, depending on the topology of the inside networks and the model of your pix you can use 802.1q trunking on the pix inside interface and create logical interfaces, so you can assign one to the 192.168.x.x network and one to the 10.x.x.x network. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jun 2007 20:34:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-as-a-router-on-a-stick-inside-int-redirect/m-p/743243#M1021934</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2007-06-19T20:34:27Z</dc:date>
    </item>
    <item>
      <title>Re: PIX, as a router on a stick, inside int redirect ??</title>
      <link>https://community.cisco.com/t5/network-security/pix-as-a-router-on-a-stick-inside-int-redirect/m-p/743244#M1021936</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jon, &lt;/P&gt;&lt;P&gt;i thought of that also.   Do you know if hairpinning needs enabled in that situation?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jun 2007 23:04:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-as-a-router-on-a-stick-inside-int-redirect/m-p/743244#M1021936</guid>
      <dc:creator>srue</dc:creator>
      <dc:date>2007-06-19T23:04:23Z</dc:date>
    </item>
    <item>
      <title>Re: PIX, as a router on a stick, inside int redirect ??</title>
      <link>https://community.cisco.com/t5/network-security/pix-as-a-router-on-a-stick-inside-int-redirect/m-p/743245#M1021940</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I guess I could pick apart this vpn hairpinning technique but this case would not involve vpn's, address pools or other vpn related constructs. After further experimentation, the inside interface route back to the inside second network seems to work, though I get the 802.1q suggestion as a possible alternative solution.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Jun 2007 00:39:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-as-a-router-on-a-stick-inside-int-redirect/m-p/743245#M1021940</guid>
      <dc:creator>mprescher</dc:creator>
      <dc:date>2007-06-20T00:39:31Z</dc:date>
    </item>
    <item>
      <title>Re: PIX, as a router on a stick, inside int redirect ??</title>
      <link>https://community.cisco.com/t5/network-security/pix-as-a-router-on-a-stick-inside-int-redirect/m-p/743246#M1021942</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here's another hairpinning example.&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/products/ps6120/products_configuration_example09186a00807968d1.shtml#solution2" target="_blank"&gt;http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00807968d1.shtml#solution2&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Jun 2007 00:59:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-as-a-router-on-a-stick-inside-int-redirect/m-p/743246#M1021942</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2007-06-20T00:59:32Z</dc:date>
    </item>
    <item>
      <title>Re: PIX, as a router on a stick, inside int redirect ??</title>
      <link>https://community.cisco.com/t5/network-security/pix-as-a-router-on-a-stick-inside-int-redirect/m-p/743247#M1021944</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Steven&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interesting question. As far as i know i the pix treats each logical interface as a separate interface to which you can apply access-lists etc. so i'm pretty sure you would not need hairpinning in this case. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Course, i'm going to have to test it sometime now that you've brought it up &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 23 Jun 2007 14:55:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-as-a-router-on-a-stick-inside-int-redirect/m-p/743247#M1021944</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2007-06-23T14:55:05Z</dc:date>
    </item>
    <item>
      <title>Re: PIX, as a router on a stick, inside int redirect ??</title>
      <link>https://community.cisco.com/t5/network-security/pix-as-a-router-on-a-stick-inside-int-redirect/m-p/743248#M1021945</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Using 801.q trunking you would not need hairpinning. The PIX would treat each VLAN as a sep interface. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 23 Jun 2007 15:00:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-as-a-router-on-a-stick-inside-int-redirect/m-p/743248#M1021945</guid>
      <dc:creator>JBDanford2002</dc:creator>
      <dc:date>2007-06-23T15:00:31Z</dc:date>
    </item>
  </channel>
</rss>

