- Products
- Learn
- Local User Groups
- Partners
-
More
Celebrate the New Year
With CheckMates!
Value of Security
Vendor Self-Awareness
Join Us for CPX 360
23-24 February 2021
Important certificate update to CloudGuard Controller, CME,
and Azure HA Security Gateways
How to Remediate Endpoint & VPN
Issues (in versions E81.10 or earlier)
Mobile Security
Buyer's Guide Out Now
Important! R80 and R80.10
End Of Support around the corner (May 2021)
Our Perimeter Firewall-Cluster is connected to the Internet via Provider 1 using Provider-Assigned Public IP Addresses.
In the future, we will use our own PI-Range to connect to the Internet via BGP-attached Provider2 and Provider3.
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?
PhoneBoy
A network diagram would be really helpful here with a little more information about what you want routed through which ISP.
That said, ISP Redundancy only supports two ISPs, so maybe you want to use Policy-Based Routing here.
Thanks Dameon
PBR is probably the way to go. Are there any numbers on how big the performance impcat is when using PBR?
About CheckMates
Learn Check Point
Advanced Learning
WELCOME TO THE FUTURE OF CYBER SECURITY