<?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: VPN tunnels S2S and remote access using  IPSec VPN - Link Selection with Natted Ip address in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VPN-tunnels-S2S-and-remote-access-using-IPSec-VPN-Link-Selection/m-p/184693#M33931</link>
    <description>&lt;P&gt;Your main ip address is a private ip or a public one? It is the IP configured on remote peers side?&lt;/P&gt;</description>
    <pubDate>Sat, 24 Jun 2023 07:27:44 GMT</pubDate>
    <dc:creator>CheckPointerXL</dc:creator>
    <dc:date>2023-06-24T07:27:44Z</dc:date>
    <item>
      <title>VPN tunnels S2S and remote access using  IPSec VPN - Link Selection with Natted Ip address</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VPN-tunnels-S2S-and-remote-access-using-IPSec-VPN-Link-Selection/m-p/184269#M33861</link>
      <description>&lt;P&gt;&lt;SPAN&gt;we already have a working CP cluster VPN tunnels S2S and remote access using&amp;nbsp;&amp;nbsp;IPSec VPN - Link Selection (Alway use this ip adress --- the 1er ISP public ip address, that is used as the a static NAT on Peplink load balancer).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Now we are trying to implement a new VPN tunnels on the second link (ISP2) while ensuring the continuity of existing tunnels over ISP1.&lt;/P&gt;&lt;P&gt;Our primary goal is to incorporate the new VPN tunnels on ISP2 while keeping the existing tunnels on ISP1 operational. We should focus on maintaining connectivity and ensuring a smooth transition to use&amp;nbsp; the both links ISP1 for the existing tunnels and ISP2 for the new ones .&lt;/P&gt;&lt;P&gt;we already tied a ISP redundancy that goes to failure, we even created support tickets with Checkpoint support, the last one is "&lt;SPAN&gt;6-0003628640"&lt;/SPAN&gt; with no success .&lt;/P&gt;&lt;P&gt;This is very challenging for us since the customer was happy with the solution till this issue raises and other technologies like Fortigate and Palo Alto are arround.&lt;/P&gt;&lt;P&gt;any suggestion or workarround from you checkpoint gurus that can help will be appreciated.&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jun 2023 09:59:19 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VPN-tunnels-S2S-and-remote-access-using-IPSec-VPN-Link-Selection/m-p/184269#M33861</guid>
      <dc:creator>abdelmajid_lakb</dc:creator>
      <dc:date>2023-06-19T09:59:19Z</dc:date>
    </item>
    <item>
      <title>Re: VPN tunnels S2S and remote access using  IPSec VPN - Link Selection with Natted Ip address</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VPN-tunnels-S2S-and-remote-access-using-IPSec-VPN-Link-Selection/m-p/184281#M33862</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Your S2S tunnels, are these with Check Point devices managed by the same SMS, or with 3th party devices ?&lt;/P&gt;&lt;P&gt;If it is a 3th party, this device will not know about the link selection for remote peers (Always use this address, statically NATed IP ) and can use your ISP2 IP address. You will have to put a host route to ISP2 for the public IP of the new S2S VPN.&lt;/P&gt;&lt;P&gt;For Check Point managed devices, ISP redundancy should be able to failover the VPN to ISP2 if there is a failure, but I don't think it is possible to point al new peers to ISP2 while all others have ISP1. ( Maybe changing the ISP redundancy settings and only pushing them to the new peers will work, but not optimal ).&amp;nbsp;&lt;/P&gt;&lt;P&gt;What issues did you get with ISP redundancy ? ( we also got a lot of issues, but is is a bit stable now, only drops once a week )&lt;/P&gt;&lt;P&gt;Maybe Check Point SDWAN is a solution for you ?&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jun 2023 14:52:08 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VPN-tunnels-S2S-and-remote-access-using-IPSec-VPN-Link-Selection/m-p/184281#M33862</guid>
      <dc:creator>K_R_V</dc:creator>
      <dc:date>2023-06-19T14:52:08Z</dc:date>
    </item>
    <item>
      <title>Re: VPN tunnels S2S and remote access using  IPSec VPN - Link Selection with Natted Ip address</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VPN-tunnels-S2S-and-remote-access-using-IPSec-VPN-Link-Selection/m-p/184693#M33931</link>
      <description>&lt;P&gt;Your main ip address is a private ip or a public one? It is the IP configured on remote peers side?&lt;/P&gt;</description>
      <pubDate>Sat, 24 Jun 2023 07:27:44 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VPN-tunnels-S2S-and-remote-access-using-IPSec-VPN-Link-Selection/m-p/184693#M33931</guid>
      <dc:creator>CheckPointerXL</dc:creator>
      <dc:date>2023-06-24T07:27:44Z</dc:date>
    </item>
  </channel>
</rss>

