<?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: ISP Redundancy: LAN via ISP‑1, WLAN via ISP‑2 in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-LAN-via-ISP-1-WLAN-via-ISP-2/m-p/261995#M51368</link>
    <description>&lt;P&gt;The best way to achieve your need is to use SD-WAN. SQ-WAN does all the magic, using both ISPs, sent traffic from network A via ISP A and traffic from network B via ISP B. And if one ISP is failing everything is sent via the other. It's simple to configure with SD-WAN policy.&lt;/P&gt;</description>
    <pubDate>Thu, 06 Nov 2025 13:37:17 GMT</pubDate>
    <dc:creator>Wolfgang</dc:creator>
    <dc:date>2025-11-06T13:37:17Z</dc:date>
    <item>
      <title>ISP Redundancy: LAN via ISP‑1, WLAN via ISP‑2</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-LAN-via-ISP-1-WLAN-via-ISP-2/m-p/261775#M51330</link>
      <description>&lt;P&gt;&lt;!--  StartFragment   --&gt;&lt;/P&gt;&lt;P&gt;Hi CheckMates,&lt;/P&gt;&lt;P&gt;I’m exploring a design where a Check Point gateway connects to two ISPs. The client’s requirement is:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;LAN subnets&lt;/STRONG&gt; should use &lt;STRONG&gt;ISP‑1&lt;/STRONG&gt; by default&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;WLAN subnets&lt;/STRONG&gt; should use &lt;STRONG&gt;ISP‑2&lt;/STRONG&gt; by default&lt;/LI&gt;&lt;LI&gt;Both ISPs should be &lt;STRONG&gt;active simultaneously&lt;/STRONG&gt; (Load Sharing, not HA)&lt;/LI&gt;&lt;LI&gt;If either ISP fails, traffic from both LAN and WLAN should &lt;STRONG&gt;fail over to the surviving ISP&lt;/STRONG&gt; automatically&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;From my understanding, this would involve:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Enabling &lt;STRONG&gt;ISP Redundancy in Load Sharing mode&lt;/STRONG&gt; to handle health monitoring and failover&lt;/LI&gt;&lt;LI&gt;Using &lt;STRONG&gt;NAT rules&lt;/STRONG&gt; so each subnet hides behind its “preferred” ISP’s external IP, but can also fall back to the other ISP if needed&lt;/LI&gt;&lt;LI&gt;Optionally applying &lt;STRONG&gt;Policy‑Based Routing (PBR)&lt;/STRONG&gt; to bias LAN traffic toward ISP‑1 and WLAN traffic toward ISP‑2 under normal conditions&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;!--  StartFragment   --&gt;&lt;/P&gt;&lt;P&gt;&lt;!--  StartFragment   --&gt;&lt;/P&gt;&lt;P&gt;Where I’m unsure:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Will NAT rules really switch cleanly during failover, or could I run into asymmetric routing?&lt;/LI&gt;&lt;LI&gt;Does PBR play nicely with ISP Redundancy, or could it “stick” to a dead ISP?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Has anyone here implemented something like this? I’d love to hear if this approach is solid, or if there’s a better way to achieve subnet‑specific ISP preference with automatic failover and zero human intervention.&lt;/P&gt;&lt;UL&gt;&lt;!--  EndFragment   --&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Nov 2025 15:17:24 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-LAN-via-ISP-1-WLAN-via-ISP-2/m-p/261775#M51330</guid>
      <dc:creator>DominusRex23</dc:creator>
      <dc:date>2025-11-04T15:17:24Z</dc:date>
    </item>
    <item>
      <title>Re: ISP Redundancy: LAN via ISP‑1, WLAN via ISP‑2</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-LAN-via-ISP-1-WLAN-via-ISP-2/m-p/261777#M51331</link>
      <description>&lt;P&gt;The fact you're talking about LAN/WLAN means you're discussing SMB appliances.&lt;BR /&gt;Generally ISPR and PBR aren't supported together:&amp;nbsp;&lt;A href="https://support.checkpoint.com/results/sk/sk167135" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk167135&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Nov 2025 15:28:21 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-LAN-via-ISP-1-WLAN-via-ISP-2/m-p/261777#M51331</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2025-11-04T15:28:21Z</dc:date>
    </item>
    <item>
      <title>Re: ISP Redundancy: LAN via ISP‑1, WLAN via ISP‑2</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-LAN-via-ISP-1-WLAN-via-ISP-2/m-p/261835#M51332</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/7"&gt;@PhoneBoy&lt;/a&gt;&amp;nbsp;&lt;!-- StartFragment  --&gt;&lt;/P&gt;&lt;P&gt;Thanks for pointing that out. I actually wasn’t aware of that SK, so I’ll definitely look into it. Just to clarify, this setup is on &lt;STRONG&gt;enterprise Gaia gateways&lt;/STRONG&gt;, not SMB appliances (I only used “&lt;STRONG&gt;LAN/WLAN&lt;/STRONG&gt;” to describe internal segmentation).&lt;/P&gt;&lt;P&gt;The client’s requirement is &lt;STRONG&gt;zero human intervention&lt;/STRONG&gt; in case of ISP failure, but they also want subnet‑specific steering (LAN → ISP‑1, WLAN → ISP‑2) under normal conditions. From what you’re saying, it sounds like ISP Redundancy and PBR can’t be combined, which raises the question:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;On enterprise gateways, is there a supported way to achieve both &lt;STRONG&gt;automatic failover&lt;/STRONG&gt; and &lt;STRONG&gt;subnet‑specific ISP preference&lt;/STRONG&gt; without relying on PBR? Or is it really an either/or trade‑off&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;!-- EndFragment  --&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Nov 2025 02:16:02 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-LAN-via-ISP-1-WLAN-via-ISP-2/m-p/261835#M51332</guid>
      <dc:creator>DominusRex23</dc:creator>
      <dc:date>2025-11-05T02:16:02Z</dc:date>
    </item>
    <item>
      <title>Re: ISP Redundancy: LAN via ISP‑1, WLAN via ISP‑2</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-LAN-via-ISP-1-WLAN-via-ISP-2/m-p/261837#M51334</link>
      <description>&lt;P&gt;You don't need ISP Redundancy for this, you can just use Multiple Default Routes with ECMP and PBR.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://sc1.checkpoint.com/documents/R81.20/WebAdminGuides/EN/CP_R81.20_Gaia_Advanced_Routing_AdminGuide/Content/Topics-GARG/Routing-Options-Equal-Cost-Multipath.htm" target="_blank"&gt;https://sc1.checkpoint.com/documents/R81.20/WebAdminGuides/EN/CP_R81.20_Gaia_Advanced_Routing_AdminGuide/Content/Topics-GARG/Routing-Options-Equal-Cost-Multipath.htm&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, I don't think you can define a different NAT for different ISP with this configuration.&lt;BR /&gt;&lt;A href="https://sc1.checkpoint.com/documents/Infinity_Portal/WebAdminGuides/EN/Quantum-SD-WAN-Admin-Guide/Content/Topics-SD-WAN/NAT-for-ISP.htm" target="_blank"&gt;You can do this with Quantum SD-WAN&lt;/A&gt;, though.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Nov 2025 03:26:25 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-LAN-via-ISP-1-WLAN-via-ISP-2/m-p/261837#M51334</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2025-11-05T03:26:25Z</dc:date>
    </item>
    <item>
      <title>Re: ISP Redundancy: LAN via ISP‑1, WLAN via ISP‑2</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-LAN-via-ISP-1-WLAN-via-ISP-2/m-p/261986#M51365</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can fix your issue with SKs without any manuel configuration when ISP link down.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For Hide Nat:&amp;nbsp;&lt;A href="https://support.checkpoint.com/results/sk/sk174197" target="_blank" rel="noopener"&gt;https://support.checkpoint.com/results/sk/sk174197&lt;/A&gt;&lt;/P&gt;&lt;P&gt;For Static Nat:&amp;nbsp;&lt;A href="https://support.checkpoint.com/results/sk/sk25152" target="_blank" rel="noopener"&gt;https://support.checkpoint.com/results/sk/sk25152&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Nov 2025 12:01:35 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-LAN-via-ISP-1-WLAN-via-ISP-2/m-p/261986#M51365</guid>
      <dc:creator>TurgutKaplanogl</dc:creator>
      <dc:date>2025-11-06T12:01:35Z</dc:date>
    </item>
    <item>
      <title>Re: ISP Redundancy: LAN via ISP‑1, WLAN via ISP‑2</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-LAN-via-ISP-1-WLAN-via-ISP-2/m-p/261995#M51368</link>
      <description>&lt;P&gt;The best way to achieve your need is to use SD-WAN. SQ-WAN does all the magic, using both ISPs, sent traffic from network A via ISP A and traffic from network B via ISP B. And if one ISP is failing everything is sent via the other. It's simple to configure with SD-WAN policy.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Nov 2025 13:37:17 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/ISP-Redundancy-LAN-via-ISP-1-WLAN-via-ISP-2/m-p/261995#M51368</guid>
      <dc:creator>Wolfgang</dc:creator>
      <dc:date>2025-11-06T13:37:17Z</dc:date>
    </item>
  </channel>
</rss>

