<?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: PIX routing possibility in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-routing-possibility/m-p/489749#M530145</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To route this correctly, you would need a route for each remote network:&lt;/P&gt;&lt;P&gt;route inside 192.168.19.0 255.255.255.0 192.168.18.1&lt;/P&gt;&lt;P&gt;route inside 192.168.20.0 255.255.255.0 192.168.18.1&lt;/P&gt;&lt;P&gt;route inside 192.168.21.0 255.255.255.0 192.168.18.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and a default route for the Internet:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;route outside 0.0.0.0 0.0.0.0 (ISP Gateway IP address)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the rest of the PIX config is correct, this should work.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 30 Nov 2005 23:21:35 GMT</pubDate>
    <dc:creator>rsmith</dc:creator>
    <dc:date>2005-11-30T23:21:35Z</dc:date>
    <item>
      <title>PIX routing possibility</title>
      <link>https://community.cisco.com/t5/network-security/pix-routing-possibility/m-p/489748#M530143</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a client with the attached Network topolog file. He wants to &lt;/P&gt;&lt;P&gt;install his PIX firewall in the position showed in the topology file&amp;#133;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;His request is to route the internal traffic between his branches and internet using his PIX firewall&amp;#133;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Actually I did not know if it's possible to route his traffic from B1,  B2 &lt;/P&gt;&lt;P&gt;and B3 to internet and back to the mail VPN device at HQ by PIX Or no..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can any one of you help me to make his network work properly and can any &lt;/P&gt;&lt;P&gt;traffic to the internet from any Branch go smoothly and get back to his &lt;/P&gt;&lt;P&gt;source IP???&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried to make something like route inside 192.168.0.0 255.255.0.0 &lt;/P&gt;&lt;P&gt;192.168.18.1 1 with no hope&amp;#133; please help me to fix this issue if possible&amp;#133;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&amp;#133;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,,,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Magdy Hossein&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:33:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-routing-possibility/m-p/489748#M530143</guid>
      <dc:creator>mastechnology</dc:creator>
      <dc:date>2020-02-21T08:33:34Z</dc:date>
    </item>
    <item>
      <title>Re: PIX routing possibility</title>
      <link>https://community.cisco.com/t5/network-security/pix-routing-possibility/m-p/489749#M530145</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To route this correctly, you would need a route for each remote network:&lt;/P&gt;&lt;P&gt;route inside 192.168.19.0 255.255.255.0 192.168.18.1&lt;/P&gt;&lt;P&gt;route inside 192.168.20.0 255.255.255.0 192.168.18.1&lt;/P&gt;&lt;P&gt;route inside 192.168.21.0 255.255.255.0 192.168.18.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and a default route for the Internet:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;route outside 0.0.0.0 0.0.0.0 (ISP Gateway IP address)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the rest of the PIX config is correct, this should work.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Nov 2005 23:21:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-routing-possibility/m-p/489749#M530145</guid>
      <dc:creator>rsmith</dc:creator>
      <dc:date>2005-11-30T23:21:35Z</dc:date>
    </item>
  </channel>
</rss>

