<?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 Routing help in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/routing-help/m-p/662873#M1029977</link>
    <description>&lt;P&gt;we can't get onto any internet pages that start with 89.x.x.x because one of our remote office LAN's has been set up to use 89.x.x.x/8 so everything for that IP range is routed to that network through our PIX 515.  Is there anything we can do just for the moment to get on these pages, then we can fix this public LAN address to be a private address scheme?&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 09:14:19 GMT</pubDate>
    <dc:creator>whiteford</dc:creator>
    <dc:date>2019-03-11T09:14:19Z</dc:date>
    <item>
      <title>Routing help</title>
      <link>https://community.cisco.com/t5/network-security/routing-help/m-p/662873#M1029977</link>
      <description>&lt;P&gt;we can't get onto any internet pages that start with 89.x.x.x because one of our remote office LAN's has been set up to use 89.x.x.x/8 so everything for that IP range is routed to that network through our PIX 515.  Is there anything we can do just for the moment to get on these pages, then we can fix this public LAN address to be a private address scheme?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 09:14:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-help/m-p/662873#M1029977</guid>
      <dc:creator>whiteford</dc:creator>
      <dc:date>2019-03-11T09:14:19Z</dc:date>
    </item>
    <item>
      <title>Re: Routing help</title>
      <link>https://community.cisco.com/t5/network-security/routing-help/m-p/662874#M1029978</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi  ..   unfortunately  you need to re-address the remote site's LAN ..  to avoid these conflicts  .. internal networks should use a private addressing in the ranges.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;10.0.0.0 - 10.255.255.255&lt;/P&gt;&lt;P&gt;172.16.0.0 - 172.31.255.255&lt;/P&gt;&lt;P&gt;192.168.0.0 - 192.168.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope it helps  ..  please rate it if it does !!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 31 Dec 2006 04:55:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-help/m-p/662874#M1029978</guid>
      <dc:creator>Fernando_Meza</dc:creator>
      <dc:date>2006-12-31T04:55:48Z</dc:date>
    </item>
    <item>
      <title>Re: Routing help</title>
      <link>https://community.cisco.com/t5/network-security/routing-help/m-p/662875#M1029979</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Look at NAT Overlapping.&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/customer/tech/tk648/tk361/technologies_tech_note09186a0080094831.shtml" target="_blank"&gt;http://www.cisco.com/en/US/customer/tech/tk648/tk361/technologies_tech_note09186a0080094831.shtml&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 31 Dec 2006 16:06:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-help/m-p/662875#M1029979</guid>
      <dc:creator>h.parsons</dc:creator>
      <dc:date>2006-12-31T16:06:15Z</dc:date>
    </item>
  </channel>
</rss>

