<?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 Routing to remote subnet in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783470#M964992</link>
    <description>&lt;P&gt;Working with a Pix 535 ver 6.3(5)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The pix is the default gateway for the entire subnet 192.168.160.0 255.255.240.0. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have since added a VMware environment that I have put into the 172.17.0.0 space for a number of reasons. The VMware subnet is accessible via 192.168.162.87 (I am doing the layer 3 switching &amp;amp; inter VLAN routing on a switch at this address). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can get everything to work by adding a static route in the PCs I am working on, but I want to accomplish this in the pix. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[Pix: 192.168.160.1 (inside)]----&amp;gt;[Cisco 6500]---&amp;gt;[VMware Switch: 192.168.162.87]-----&amp;gt;172.17.0.0/24 network. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can I do something like this?&lt;/P&gt;&lt;P&gt;Ip address VMware 172.17.0.1 255.255.255.0&lt;/P&gt;&lt;P&gt;Static (inside, VMware) 192.168.160.1 172.17.0.1 255.255.255.255&lt;/P&gt;&lt;P&gt;Route VMware 172.17.0.0 255.255.255.0 192.168.162.87 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;edit: I should mention that the VMnetwork is not directly connected. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 10:58:16 GMT</pubDate>
    <dc:creator>bill.morton</dc:creator>
    <dc:date>2019-03-11T10:58:16Z</dc:date>
    <item>
      <title>Pix Routing to remote subnet</title>
      <link>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783470#M964992</link>
      <description>&lt;P&gt;Working with a Pix 535 ver 6.3(5)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The pix is the default gateway for the entire subnet 192.168.160.0 255.255.240.0. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have since added a VMware environment that I have put into the 172.17.0.0 space for a number of reasons. The VMware subnet is accessible via 192.168.162.87 (I am doing the layer 3 switching &amp;amp; inter VLAN routing on a switch at this address). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can get everything to work by adding a static route in the PCs I am working on, but I want to accomplish this in the pix. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[Pix: 192.168.160.1 (inside)]----&amp;gt;[Cisco 6500]---&amp;gt;[VMware Switch: 192.168.162.87]-----&amp;gt;172.17.0.0/24 network. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can I do something like this?&lt;/P&gt;&lt;P&gt;Ip address VMware 172.17.0.1 255.255.255.0&lt;/P&gt;&lt;P&gt;Static (inside, VMware) 192.168.160.1 172.17.0.1 255.255.255.255&lt;/P&gt;&lt;P&gt;Route VMware 172.17.0.0 255.255.255.0 192.168.162.87 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;edit: I should mention that the VMnetwork is not directly connected. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 10:58:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783470#M964992</guid>
      <dc:creator>bill.morton</dc:creator>
      <dc:date>2019-03-11T10:58:16Z</dc:date>
    </item>
    <item>
      <title>Re: Pix Routing to remote subnet</title>
      <link>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783471#M964995</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Bill &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just to confirm, if a client on the 192.168.160.x subnet wanted to communicate with the 172.17.0.0 subnet does the traffic go from the client to the pix inside interface, back out the inside interface to the VMware switch and then to the subnet. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If so this will not work with pix ver 6.x as you cannot send traffic back out the same interface it came in on to it's destination.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You have 2 choices if you don't want to add static routes to PC's&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Upgrade pix to v7.x where you can send traffic back out same interface. It's called hairpinning. Be aware that v7.x config is quite different from v6.x&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) Migrate the default gateway of your 192.168.160.x clients to the L3 switch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would go with 2. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Aug 2007 15:47:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783471#M964995</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2007-08-15T15:47:36Z</dc:date>
    </item>
    <item>
      <title>Re: Pix Routing to remote subnet</title>
      <link>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783472#M964997</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That is exactly what would happen, traffic would go in/out the same interface on the pix. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'll give the default gateway a shot, though I do have a 515 running v7 around. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Aug 2007 16:07:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783472#M964997</guid>
      <dc:creator>bill.morton</dc:creator>
      <dc:date>2007-08-15T16:07:30Z</dc:date>
    </item>
    <item>
      <title>Re: Pix Routing to remote subnet</title>
      <link>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783473#M964999</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok, getting close but I am having a mental blcok here. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can ping my 172.17 hosts from outside (192.168.*.*)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My 172.17 hosts can ping each other.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My 172.17 hosts can ping the L3 switch gateway 192.168.162.87&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My L3 Switch can ping the rest of the network 192.168.*.*&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My 172.17 hosts can not ping the rest of the 192.168.*.* network. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[172.17.0.*]---&amp;gt;[Cisco 3750 192.168.162.87]---&amp;gt;192.168.160.* /20&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cisco 3750 config: (the hosts I am trying to ping from are on Vlan 4 [management] &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ok, too long for a full post, but:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;      &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Aug 2007 16:33:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783473#M964999</guid>
      <dc:creator>bill.morton</dc:creator>
      <dc:date>2007-08-15T16:33:00Z</dc:date>
    </item>
    <item>
      <title>Re: Pix Routing to remote subnet</title>
      <link>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783474#M965001</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;VMCisco3750_0#sh vlan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VLAN Name                             Status    Ports&lt;/P&gt;&lt;P&gt;---- -------------------------------- --------- -------------------------------&lt;/P&gt;&lt;P&gt;1    default                          active    Gi1/0/21, Gi1/0/22, Gi1/0/23&lt;/P&gt;&lt;P&gt;                                                Gi1/0/24&lt;/P&gt;&lt;P&gt;2    iSCSI                            active    Gi1/0/1, Gi1/0/2, Gi1/0/3&lt;/P&gt;&lt;P&gt;                                                Gi1/0/4, Gi1/0/5, Gi1/0/6&lt;/P&gt;&lt;P&gt;                                                Gi1/0/7, Gi1/0/8, Gi1/0/9&lt;/P&gt;&lt;P&gt;                                                Gi1/0/10, Gi1/0/11, Gi1/0/12&lt;/P&gt;&lt;P&gt;3    VMotion                          active    Gi1/0/13, Gi1/0/14&lt;/P&gt;&lt;P&gt;4    Management                       active    Gi1/0/15, Gi1/0/16, Gi1/0/17&lt;/P&gt;&lt;P&gt;                                                Gi1/0/18, Gi1/0/19, Gi1/0/20&lt;/P&gt;&lt;P&gt;1002 fddi-default                     act/unsup&lt;/P&gt;&lt;P&gt;1003 token-ring-default               act/unsup&lt;/P&gt;&lt;P&gt;1004 fddinet-default                  act/unsup&lt;/P&gt;&lt;P&gt;1005 trnet-default                    act/unsup&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VLAN Type  SAID       MTU   Parent RingNo BridgeNo Stp  BrdgMode Trans1 Trans2&lt;/P&gt;&lt;P&gt;---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------&lt;/P&gt;&lt;P&gt;1    enet  100001     1500  -      -      -        -    -        0      0&lt;/P&gt;&lt;P&gt;2    enet  100002     9000  -      -      -        -    -        0      0&lt;/P&gt;&lt;P&gt;3    enet  100003     1500  -      -      -        -    -        0      0&lt;/P&gt;&lt;P&gt;4    enet  100004     1500  -      -      -        -    -        0      0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VLAN Type  SAID       MTU   Parent RingNo BridgeNo Stp  BrdgMode Trans1 Trans2&lt;/P&gt;&lt;P&gt;---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------&lt;/P&gt;&lt;P&gt;1002 fddi  101002     1500  -      -      -        -    -        0      0&lt;/P&gt;&lt;P&gt;1003 tr    101003     1500  -      -      -        -    -        0      0&lt;/P&gt;&lt;P&gt;1004 fdnet 101004     1500  -      -      -        ieee -        0      0&lt;/P&gt;&lt;P&gt;1005 trnet 101005     1500  -      -      -        ibm  -        0      0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Remote SPAN VLANs&lt;/P&gt;&lt;P&gt;------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Primary Secondary Type              Ports&lt;/P&gt;&lt;P&gt;------- --------- ----------------- ------------------------------------------&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VMCisco3750_0#&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Aug 2007 16:33:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783474#M965001</guid>
      <dc:creator>bill.morton</dc:creator>
      <dc:date>2007-08-15T16:33:11Z</dc:date>
    </item>
    <item>
      <title>Re: Pix Routing to remote subnet</title>
      <link>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783475#M965004</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;VMCisco3750_0#sh ip int brief&lt;/P&gt;&lt;P&gt;Interface              IP-Address      OK? Method Status                Protocol&lt;/P&gt;&lt;P&gt;Vlan1                  192.168.162.87  YES NVRAM  up                    up&lt;/P&gt;&lt;P&gt;Vlan2                  unassigned      YES manual up                    up&lt;/P&gt;&lt;P&gt;Vlan3                  unassigned      YES manual up                    up&lt;/P&gt;&lt;P&gt;Vlan4                  172.17.0.97     YES NVRAM  up                    up&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/1   unassigned      YES unset  up                    up&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/2   unassigned      YES unset  down                  down&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/3   unassigned      YES unset  up                    up&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/4   unassigned      YES unset  down                  down&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/5   unassigned      YES unset  up                    up&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/6   unassigned      YES unset  down                  down&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/7   unassigned      YES unset  up                    up&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/8   unassigned      YES unset  up                    up&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/9   unassigned      YES unset  up                    up&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/10  unassigned      YES unset  up                    up&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/11  unassigned      YES unset  up                    up&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/12  unassigned      YES unset  down                  down&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/13  unassigned      YES unset  up                    up&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/14  unassigned      YES unset  up                    up&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/15  unassigned      YES unset  up                    up&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/16  unassigned      YES unset  up                    up&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/17  unassigned      YES unset  down                  down&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/18  unassigned      YES unset  up                    up&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/19  unassigned      YES unset  down                  down&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/20  unassigned      YES unset  down                  down&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/21  unassigned      YES unset  up                    up&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/22  unassigned      YES unset  up                    up&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/23  unassigned      YES unset  administratively down down&lt;/P&gt;&lt;P&gt;GigabitEthernet1/0/24  unassigned      YES unset  up                    up&lt;/P&gt;&lt;P&gt;VMCisco3750_0#sh ip route&lt;/P&gt;&lt;P&gt;Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP&lt;/P&gt;&lt;P&gt;       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area&lt;/P&gt;&lt;P&gt;       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2&lt;/P&gt;&lt;P&gt;       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP&lt;/P&gt;&lt;P&gt;       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2&lt;/P&gt;&lt;P&gt;       ia - IS-IS inter area, * - candidate default, U - per-user static route&lt;/P&gt;&lt;P&gt;       o - ODR, P - periodic downloaded static route&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gateway of last resort is 192.168.160.1 to network 0.0.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;     172.17.0.0/27 is subnetted, 1 subnets&lt;/P&gt;&lt;P&gt;C       172.17.0.96 is directly connected, Vlan4&lt;/P&gt;&lt;P&gt;S*   0.0.0.0/0 [1/0] via 192.168.160.1&lt;/P&gt;&lt;P&gt;C    192.168.160.0/20 is directly connected, Vlan1&lt;/P&gt;&lt;P&gt;VMCisco3750_0#&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Aug 2007 16:33:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783475#M965004</guid>
      <dc:creator>bill.morton</dc:creator>
      <dc:date>2007-08-15T16:33:46Z</dc:date>
    </item>
    <item>
      <title>Re: Pix Routing to remote subnet</title>
      <link>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783476#M965005</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As Jon said your default gateway for subnet 192.168.160.0 should the L3 switch and then have a default route in the L3 switch pointing to the PIX. You are going to need a route in the PIX for the 172.17.0.0 subnet pointing to the L3 switch.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Aug 2007 17:32:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783476#M965005</guid>
      <dc:creator>rigoberto.cintron</dc:creator>
      <dc:date>2007-08-15T17:32:46Z</dc:date>
    </item>
    <item>
      <title>Re: Pix Routing to remote subnet</title>
      <link>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783477#M965006</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think would run into the same problem that Jon mentioned earlier with packets entering and leaving the same interface which 6.3(5) wont allow. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Aug 2007 17:50:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783477#M965006</guid>
      <dc:creator>bill.morton</dc:creator>
      <dc:date>2007-08-15T17:50:47Z</dc:date>
    </item>
    <item>
      <title>Re: Pix Routing to remote subnet</title>
      <link>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783478#M965007</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Bill &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You wouldn't as long as every network internally routed off your L3 switch. And then on your L3 switch you have a default route pointing to the pix. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The idea is that you only go to the pix inside interface when you want to go out through the pix not to get to another internal subnet. For routing internally use the L3 switch. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Aug 2007 17:57:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783478#M965007</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2007-08-15T17:57:39Z</dc:date>
    </item>
    <item>
      <title>Re: Pix Routing to remote subnet</title>
      <link>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783479#M965008</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Alright, I see where you are going; I'll have to think this one out a bit. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think the best option for my environment would be to directly connect the 172.17 network to the PIX, so I?ll see if I have any open interfaces to work with. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for all the help!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Aug 2007 18:14:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783479#M965008</guid>
      <dc:creator>bill.morton</dc:creator>
      <dc:date>2007-08-15T18:14:46Z</dc:date>
    </item>
    <item>
      <title>Re: Pix Routing to remote subnet</title>
      <link>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783480#M965009</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you need to Firewall the 172.17 subnet independently from the 192.168.160 subnet then conecting it to another interface in the PIX it's the way to go. If you don't need to firewall that subnet independently then the best way to do it is route with the L3 switch. Remember that the PIX it's not a router and it's slower than a L3 switch. If you need high speed connection between those subnets the PIX will just make it slower.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Aug 2007 19:29:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-routing-to-remote-subnet/m-p/783480#M965009</guid>
      <dc:creator>rigoberto.cintron</dc:creator>
      <dc:date>2007-08-15T19:29:13Z</dc:date>
    </item>
  </channel>
</rss>

