<?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: Routing problem Cisco PIX? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/routing-problem-cisco-pix/m-p/1454292#M726604</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Geir&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think you can overcome this by creating a subnet (/27) specific route for your AIX servers so that your packets doesn't go back to inside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regds&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 12 May 2010 12:48:27 GMT</pubDate>
    <dc:creator>spremkumar</dc:creator>
    <dc:date>2010-05-12T12:48:27Z</dc:date>
    <item>
      <title>Routing problem Cisco PIX?</title>
      <link>https://community.cisco.com/t5/network-security/routing-problem-cisco-pix/m-p/1454291#M726594</link>
      <description>&lt;P&gt;I have a PIX 515E running 8.0.4.&lt;/P&gt;&lt;P&gt;It's configured with an outside2 interface with security level 4 (here I have an AIX-server, 10.174.253.24/27), and DMZ with security level 10 (here I have a windows-server with 192.168.102.13/24).&amp;nbsp; Inside inteface of the PIX has 10.174.102.86/24.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From the server in the outside2 net, I can ping the PIX outside2 interface . Nice!&lt;/P&gt;&lt;P&gt;But when pinging from the outside2 AIX-server 10.174.253.24 to the 192.168.102.13, it doesn't work.&amp;nbsp; The PIX sends the reply packet out on the inside interface, instead og directly back out on the outside2 interface. Why?&lt;/P&gt;&lt;P&gt;The pix has a route that says:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;route inside 10.174.0.0 255.255.0.0 10.174.0.1 1&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is in the same range as the outside2 interface, but shouldn't it use the directly connected instead of the routing information?&lt;/P&gt;&lt;P&gt;Br&lt;/P&gt;&lt;P&gt;Geir&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 17:44:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-problem-cisco-pix/m-p/1454291#M726594</guid>
      <dc:creator>pd.politiet.no</dc:creator>
      <dc:date>2019-03-11T17:44:12Z</dc:date>
    </item>
    <item>
      <title>Re: Routing problem Cisco PIX?</title>
      <link>https://community.cisco.com/t5/network-security/routing-problem-cisco-pix/m-p/1454292#M726604</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Geir&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think you can overcome this by creating a subnet (/27) specific route for your AIX servers so that your packets doesn't go back to inside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regds&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 May 2010 12:48:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-problem-cisco-pix/m-p/1454292#M726604</guid>
      <dc:creator>spremkumar</dc:creator>
      <dc:date>2010-05-12T12:48:27Z</dc:date>
    </item>
    <item>
      <title>Re: Routing problem Cisco PIX?</title>
      <link>https://community.cisco.com/t5/network-security/routing-problem-cisco-pix/m-p/1454293#M726619</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry, checked it was correct, but it isn't.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is that the ouside interface is local to the PIX, as for the DMZ-interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I ping from a AIX server sitting on the outside interface, to a windows server in the dmz interface.&amp;nbsp; The request goes to the windows server, which then replies.&amp;nbsp; But the return reply is by the pix sent out on the inside interface.&lt;/P&gt;&lt;P&gt;The only thing I can say is thath the pic has an route to the inside, 10.174.0.0/16, and that the subnet of the outside interface of the pix is 10.174.253.0/27.&amp;nbsp; So a spesific route cannot be entered.&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;Br&lt;/P&gt;&lt;P&gt;Geir&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 May 2010 09:21:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-problem-cisco-pix/m-p/1454293#M726619</guid>
      <dc:creator>pd.politiet.no</dc:creator>
      <dc:date>2010-05-14T09:21:27Z</dc:date>
    </item>
    <item>
      <title>Re: Routing problem Cisco PIX?</title>
      <link>https://community.cisco.com/t5/network-security/routing-problem-cisco-pix/m-p/1454294#M726642</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, you can add the following route:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;route outside2 10.174.253.0 255.255.255.224 &lt;NEXT-HOP-ON-OUTSIDE2-IP&gt;&lt;/NEXT-HOP-ON-OUTSIDE2-IP&gt;&lt;/STRONG&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>Fri, 14 May 2010 09:29:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-problem-cisco-pix/m-p/1454294#M726642</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2010-05-14T09:29:57Z</dc:date>
    </item>
    <item>
      <title>Re: Routing problem Cisco PIX?</title>
      <link>https://community.cisco.com/t5/network-security/routing-problem-cisco-pix/m-p/1454295#M726678</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Next hop is directly connected to the outside2 interface.&lt;/P&gt;&lt;P&gt;When adding the route I get:&lt;/P&gt;&lt;P&gt;ERROR: Cannot add route, connected route exists&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Therefore I cannot do this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It must be something with the route to inside with the 10.174.0.0/16 route statement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Geir&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 May 2010 10:18:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-problem-cisco-pix/m-p/1454295#M726678</guid>
      <dc:creator>pd.politiet.no</dc:creator>
      <dc:date>2010-05-14T10:18:00Z</dc:date>
    </item>
    <item>
      <title>Re: Routing problem Cisco PIX?</title>
      <link>https://community.cisco.com/t5/network-security/routing-problem-cisco-pix/m-p/1454296#M726707</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If it's directly connected subnet to the outside2 interface, then it should take precedence over the static route towards the inside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assuming that you have NAT exemption configured on your DMZ interface? Something like this:&lt;/P&gt;&lt;P&gt;access-list dmz-nonat permit ip 192.168.102.0 255.255.255.0 10.174.253.0 255.255.255.224&lt;/P&gt;&lt;P&gt;nat (dmz) 0 access-list dmz-nonat&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"clear xlate" if you haven't had the above configured after the changes.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 May 2010 10:47:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-problem-cisco-pix/m-p/1454296#M726707</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2010-05-14T10:47:57Z</dc:date>
    </item>
  </channel>
</rss>

