<?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 Checkpoint Remote Access to IPSec VPN in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Checkpoint-Remote-Access-to-IPSec-VPN/m-p/198998#M33254</link>
    <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;We have a situation where the Checkpoint Endpoint(Remote Access) VPN users to connect to peer behind the IPSec site to site VPN tunnel.&lt;/P&gt;&lt;P&gt;So Traffic is from Remote Access VPN User &amp;gt; Firewall &amp;gt; IPSec Tunnel &amp;gt; Peer Device.&lt;/P&gt;&lt;P&gt;But the problem here is Remote Access VPN users will get their route table updated only when we add the subnet in the Enc domain our end Under Network Management &amp;gt; VPN Domain. Only when we add the subnet or IP the RA VPN users will get their route table updated.&lt;/P&gt;&lt;P&gt;As the Peer is already behind an IPSec tunnel it is part of Peer end enc domain which we cant add in our enc domain. So i planned as below but it did not work.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Used a dummy IP which is not in the routing Table.&lt;/P&gt;&lt;P&gt;Remote Access VPN Subnet &amp;gt; 10.10.10.0/24&lt;/P&gt;&lt;P&gt;Dummy IP: 172.18.1.1&lt;/P&gt;&lt;P&gt;Peer End Enc Domain: 192.168.1.0/24&lt;/P&gt;&lt;P&gt;Peer End IP that need to be access from RA VPN: 192.168.1.32&lt;/P&gt;&lt;P&gt;Added Dummy IP 172.18.1.1 in our Encryption Domain.&lt;/P&gt;&lt;P&gt;So User route table is updated with 172.18.1.1 and it is reaching our Firewall as well.&lt;/P&gt;&lt;P&gt;I can see the traffic hitting the right NAT rule as below.&lt;/P&gt;&lt;P&gt;Src: RA VPN: 10.10.10.0./24&lt;/P&gt;&lt;P&gt;Dst: 172.18.1.1&lt;/P&gt;&lt;P&gt;Svc: Any&lt;/P&gt;&lt;P&gt;Translated:&lt;/P&gt;&lt;P&gt;Src: Original&lt;/P&gt;&lt;P&gt;Dst: 192.168.1.32&lt;/P&gt;&lt;P&gt;Svc: Original&lt;/P&gt;&lt;P&gt;But the traffic doesn't seem to be working. As per the peer they are not seeing any logs from our end reaching there.&lt;/P&gt;&lt;P&gt;Please suggest any better way to achieve this or please let me know if i am doing anything wrong here.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sanjay S&lt;/P&gt;</description>
    <pubDate>Mon, 27 Nov 2023 12:26:28 GMT</pubDate>
    <dc:creator>Sanjay_S</dc:creator>
    <dc:date>2023-11-27T12:26:28Z</dc:date>
    <item>
      <title>Checkpoint Remote Access to IPSec VPN</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Checkpoint-Remote-Access-to-IPSec-VPN/m-p/198998#M33254</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;We have a situation where the Checkpoint Endpoint(Remote Access) VPN users to connect to peer behind the IPSec site to site VPN tunnel.&lt;/P&gt;&lt;P&gt;So Traffic is from Remote Access VPN User &amp;gt; Firewall &amp;gt; IPSec Tunnel &amp;gt; Peer Device.&lt;/P&gt;&lt;P&gt;But the problem here is Remote Access VPN users will get their route table updated only when we add the subnet in the Enc domain our end Under Network Management &amp;gt; VPN Domain. Only when we add the subnet or IP the RA VPN users will get their route table updated.&lt;/P&gt;&lt;P&gt;As the Peer is already behind an IPSec tunnel it is part of Peer end enc domain which we cant add in our enc domain. So i planned as below but it did not work.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Used a dummy IP which is not in the routing Table.&lt;/P&gt;&lt;P&gt;Remote Access VPN Subnet &amp;gt; 10.10.10.0/24&lt;/P&gt;&lt;P&gt;Dummy IP: 172.18.1.1&lt;/P&gt;&lt;P&gt;Peer End Enc Domain: 192.168.1.0/24&lt;/P&gt;&lt;P&gt;Peer End IP that need to be access from RA VPN: 192.168.1.32&lt;/P&gt;&lt;P&gt;Added Dummy IP 172.18.1.1 in our Encryption Domain.&lt;/P&gt;&lt;P&gt;So User route table is updated with 172.18.1.1 and it is reaching our Firewall as well.&lt;/P&gt;&lt;P&gt;I can see the traffic hitting the right NAT rule as below.&lt;/P&gt;&lt;P&gt;Src: RA VPN: 10.10.10.0./24&lt;/P&gt;&lt;P&gt;Dst: 172.18.1.1&lt;/P&gt;&lt;P&gt;Svc: Any&lt;/P&gt;&lt;P&gt;Translated:&lt;/P&gt;&lt;P&gt;Src: Original&lt;/P&gt;&lt;P&gt;Dst: 192.168.1.32&lt;/P&gt;&lt;P&gt;Svc: Original&lt;/P&gt;&lt;P&gt;But the traffic doesn't seem to be working. As per the peer they are not seeing any logs from our end reaching there.&lt;/P&gt;&lt;P&gt;Please suggest any better way to achieve this or please let me know if i am doing anything wrong here.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sanjay S&lt;/P&gt;</description>
      <pubDate>Mon, 27 Nov 2023 12:26:28 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Checkpoint-Remote-Access-to-IPSec-VPN/m-p/198998#M33254</guid>
      <dc:creator>Sanjay_S</dc:creator>
      <dc:date>2023-11-27T12:26:28Z</dc:date>
    </item>
    <item>
      <title>Re: Checkpoint Remote Access to IPSec VPN</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Checkpoint-Remote-Access-to-IPSec-VPN/m-p/199006#M33256</link>
      <description>&lt;P&gt;Are the Office Mode Pool addresses added to the Encryption domain ?&lt;/P&gt;</description>
      <pubDate>Mon, 27 Nov 2023 13:30:33 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Checkpoint-Remote-Access-to-IPSec-VPN/m-p/199006#M33256</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2023-11-27T13:30:33Z</dc:date>
    </item>
    <item>
      <title>Re: Checkpoint Remote Access to IPSec VPN</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Checkpoint-Remote-Access-to-IPSec-VPN/m-p/199051#M33257</link>
      <description>&lt;P&gt;Modify the RemoteAccess Encryption Domain in the Gateway object:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="PhoneBoy_0-1701100923503.png" style="width: 400px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/23441i1032CC3CBEC44749/image-size/medium?v=v2&amp;amp;px=400" role="button" title="PhoneBoy_0-1701100923503.png" alt="PhoneBoy_0-1701100923503.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The object referred to here should be a group object that includes both your local IP addresses (i.e. your local encryption domain) and the remote IP addresses you wish to be accessible (i.e. the remote encryption domain).&lt;/P&gt;</description>
      <pubDate>Mon, 27 Nov 2023 16:02:32 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Checkpoint-Remote-Access-to-IPSec-VPN/m-p/199051#M33257</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2023-11-27T16:02:32Z</dc:date>
    </item>
    <item>
      <title>Re: Checkpoint Remote Access to IPSec VPN</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Checkpoint-Remote-Access-to-IPSec-VPN/m-p/199263#M33269</link>
      <description>&lt;P&gt;Yup we are using pool IP addresses in the ENC domain.&lt;/P&gt;</description>
      <pubDate>Wed, 29 Nov 2023 14:02:58 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Checkpoint-Remote-Access-to-IPSec-VPN/m-p/199263#M33269</guid>
      <dc:creator>Sanjay_S</dc:creator>
      <dc:date>2023-11-29T14:02:58Z</dc:date>
    </item>
  </channel>
</rss>

