<?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 2 ISP Connections in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/2-isp-connections/m-p/716026#M1005803</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am after configuring 2 ISP connections on my perimeter router; the connection from ISP A is to be dedicated for regular users internet access and for some servers' inbound access. On the other hand, connection from ISP B is dedicated for VIP users internet access and for VIP servers' inbound access. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a PIX FW running ver 6.3 behind the router. Now, as you know each ISP is giving a different public address range so what is the best configuration to control the traffic in the way I need ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have already tried to configure 2 connections b/ the router and the PIX, each is having the public range from different ISP, but since the PIX doesnt do source-based routing as in the router so I faced problems because always the traffic is routed to the default route which is in my case ISP A!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am thinking of configuring NATing for traffic intended for ISP B on the router itself on a loopback interface in the following manner: &lt;/P&gt;&lt;P&gt;-there is only one link b/ the router and the PIX which has ISP A public address&lt;/P&gt;&lt;P&gt;- A loopback on the router has ISP B public range.&lt;/P&gt;&lt;P&gt;- All the servers are on the same DMZ on the PIX&lt;/P&gt;&lt;P&gt;- Servers intended on ISP A will be NATed normally on the PIX iteself&lt;/P&gt;&lt;P&gt;- Servers and traffic intended for ISP B will be NATed 1st on the PIX and then on the router's loopback interface. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please give me your recommendations and advise whether there are other scenarios for achieving what I am after or whether there is a way to achieve this on the PIX.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Haitham&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 10:06:10 GMT</pubDate>
    <dc:creator>haithamnofal</dc:creator>
    <dc:date>2019-03-11T10:06:10Z</dc:date>
    <item>
      <title>2 ISP Connections</title>
      <link>https://community.cisco.com/t5/network-security/2-isp-connections/m-p/716026#M1005803</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am after configuring 2 ISP connections on my perimeter router; the connection from ISP A is to be dedicated for regular users internet access and for some servers' inbound access. On the other hand, connection from ISP B is dedicated for VIP users internet access and for VIP servers' inbound access. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a PIX FW running ver 6.3 behind the router. Now, as you know each ISP is giving a different public address range so what is the best configuration to control the traffic in the way I need ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have already tried to configure 2 connections b/ the router and the PIX, each is having the public range from different ISP, but since the PIX doesnt do source-based routing as in the router so I faced problems because always the traffic is routed to the default route which is in my case ISP A!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am thinking of configuring NATing for traffic intended for ISP B on the router itself on a loopback interface in the following manner: &lt;/P&gt;&lt;P&gt;-there is only one link b/ the router and the PIX which has ISP A public address&lt;/P&gt;&lt;P&gt;- A loopback on the router has ISP B public range.&lt;/P&gt;&lt;P&gt;- All the servers are on the same DMZ on the PIX&lt;/P&gt;&lt;P&gt;- Servers intended on ISP A will be NATed normally on the PIX iteself&lt;/P&gt;&lt;P&gt;- Servers and traffic intended for ISP B will be NATed 1st on the PIX and then on the router's loopback interface. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please give me your recommendations and advise whether there are other scenarios for achieving what I am after or whether there is a way to achieve this on the PIX.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Haitham&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 10:06:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/2-isp-connections/m-p/716026#M1005803</guid>
      <dc:creator>haithamnofal</dc:creator>
      <dc:date>2019-03-11T10:06:10Z</dc:date>
    </item>
    <item>
      <title>Re: 2 ISP Connections</title>
      <link>https://community.cisco.com/t5/network-security/2-isp-connections/m-p/716027#M1005804</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;I got what I want through the following; I just wanted to tell you how in case you needed to implement something similar in the future. Basically, do the following: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1- leave the connection between the PIX and the router to have the public range provided by ISP A &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2- Place the server you want it to have public IP from ISP B range on the PIX DMZ where you have your public servers &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3- Do static NAT for the server which needs to be accessible on ISP B's IP to have a public IP from ISP B range. Whil the rest of the servers will be NATted on ISP A address range. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4- Configure a route on the perimeter router for the ISP B public range to be routable through the PIX outside interface (which is part of ISP A public range). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have any questions, please don't hesitate to contact me. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, &lt;/P&gt;&lt;P&gt;Haitham &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Apr 2007 17:31:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/2-isp-connections/m-p/716027#M1005804</guid>
      <dc:creator>haithamnofal</dc:creator>
      <dc:date>2007-04-30T17:31:41Z</dc:date>
    </item>
  </channel>
</rss>

