<?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: Redundant tunnels with Wireguard Connector in SASE and Remote Access</title>
    <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Redundant-tunnels-with-Wireguard-Connector/m-p/244822#M1131</link>
    <description>&lt;P&gt;Actually, it won't let me create another connector with the same address space behind it.&lt;/P&gt;
&lt;P&gt;What I had in mind was 1 connector with 2 tunnels to the gateways, reducing 2 points of failure to only 1. It seems it is not possible.&lt;/P&gt;
&lt;P&gt;Some customers don't want to change to IPSec because of costs and they find it complicated, but it is the right way to go.&lt;/P&gt;
&lt;P&gt;Anyway, thank you for your input. I just wanted to confirm.&lt;/P&gt;</description>
    <pubDate>Wed, 26 Mar 2025 12:52:45 GMT</pubDate>
    <dc:creator>Pedro_Espindola</dc:creator>
    <dc:date>2025-03-26T12:52:45Z</dc:date>
    <item>
      <title>Redundant tunnels with Wireguard Connector</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Redundant-tunnels-with-Wireguard-Connector/m-p/243206#M1117</link>
      <description>&lt;P&gt;If I have a SASE network with 2 gateways, is there any way to create redundant tunnels when using Wireguard Connector so that if one gateway becomes unavailable the other takes over or is that available only with IPSec?&lt;/P&gt;</description>
      <pubDate>Thu, 06 Mar 2025 23:34:40 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Redundant-tunnels-with-Wireguard-Connector/m-p/243206#M1117</guid>
      <dc:creator>Pedro_Espindola</dc:creator>
      <dc:date>2025-03-06T23:34:40Z</dc:date>
    </item>
    <item>
      <title>Re: Redundant tunnels with Wireguard Connector</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Redundant-tunnels-with-Wireguard-Connector/m-p/244116#M1119</link>
      <description>&lt;P&gt;My understanding is that you can install multiple Wireguard connectors for the same site/network, which would provide redundancy and scalability.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Mar 2025 22:53:42 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Redundant-tunnels-with-Wireguard-Connector/m-p/244116#M1119</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2025-03-18T22:53:42Z</dc:date>
    </item>
    <item>
      <title>Re: Redundant tunnels with Wireguard Connector</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Redundant-tunnels-with-Wireguard-Connector/m-p/244822#M1131</link>
      <description>&lt;P&gt;Actually, it won't let me create another connector with the same address space behind it.&lt;/P&gt;
&lt;P&gt;What I had in mind was 1 connector with 2 tunnels to the gateways, reducing 2 points of failure to only 1. It seems it is not possible.&lt;/P&gt;
&lt;P&gt;Some customers don't want to change to IPSec because of costs and they find it complicated, but it is the right way to go.&lt;/P&gt;
&lt;P&gt;Anyway, thank you for your input. I just wanted to confirm.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Mar 2025 12:52:45 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Redundant-tunnels-with-Wireguard-Connector/m-p/244822#M1131</guid>
      <dc:creator>Pedro_Espindola</dc:creator>
      <dc:date>2025-03-26T12:52:45Z</dc:date>
    </item>
  </channel>
</rss>

