<?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: How to deal with 2 Providers in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-deal-with-2-Providers/m-p/10718#M684</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A network diagram would be really helpful here with a little more information about what you want routed through which ISP.&lt;/P&gt;&lt;P&gt;That said, ISP Redundancy only supports two ISPs, so maybe you want to use Policy-Based Routing here.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 30 Nov 2018 21:41:18 GMT</pubDate>
    <dc:creator>PhoneBoy</dc:creator>
    <dc:date>2018-11-30T21:41:18Z</dc:date>
    <item>
      <title>How to deal with 2 Providers</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-deal-with-2-Providers/m-p/10717#M683</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Our Perimeter Firewall-Cluster is connected to the Internet via Provider 1 using Provider-Assigned Public IP Addresses.&lt;/P&gt;&lt;P&gt;In the future, we will use our own PI-Range to connect to the Internet via BGP-attached Provider2 and Provider3.&lt;/P&gt;&lt;P&gt;The migration phase will last 2 years. During that time, the Firewall Cluster must be able to handle both the "old" PA-Range and the "new" PI-Range. Basically, the Firewall should provide Source based Routing for the packets leaving its external linterfaces. How good will fit the ISP-redundancy feature here. Arer there any other options to achieve our goal?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Nov 2018 10:16:43 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-deal-with-2-Providers/m-p/10717#M683</guid>
      <dc:creator>peter_schumache</dc:creator>
      <dc:date>2018-11-29T10:16:43Z</dc:date>
    </item>
    <item>
      <title>Re: How to deal with 2 Providers</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-deal-with-2-Providers/m-p/10718#M684</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A network diagram would be really helpful here with a little more information about what you want routed through which ISP.&lt;/P&gt;&lt;P&gt;That said, ISP Redundancy only supports two ISPs, so maybe you want to use Policy-Based Routing here.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Nov 2018 21:41:18 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-deal-with-2-Providers/m-p/10718#M684</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2018-11-30T21:41:18Z</dc:date>
    </item>
    <item>
      <title>Re: How to deal with 2 Providers</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-deal-with-2-Providers/m-p/10719#M685</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Dameon&lt;/P&gt;&lt;P&gt;PBR is probably the way to go. Are there any numbers on how big the performance impcat is when using PBR?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Dec 2018 15:39:31 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-deal-with-2-Providers/m-p/10719#M685</guid>
      <dc:creator>peter_schumache</dc:creator>
      <dc:date>2018-12-03T15:39:31Z</dc:date>
    </item>
  </channel>
</rss>

