<?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: NAT in S2S VPN deployment. in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-in-S2S-VPN-deployment/m-p/185089#M34032</link>
    <description>&lt;P&gt;Yes, it is possible to setup groups in the NAT rule base for your hide NAT. I use this feature quite often.&lt;/P&gt;&lt;P&gt;You can absolutely put those 3 servers into a group and specify hide behind&amp;nbsp;&lt;SPAN&gt;172.26.15.254 when talking to the other remote network.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 28 Jun 2023 19:35:47 GMT</pubDate>
    <dc:creator>CaseyB</dc:creator>
    <dc:date>2023-06-28T19:35:47Z</dc:date>
    <item>
      <title>NAT in S2S VPN deployment.</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-in-S2S-VPN-deployment/m-p/185064#M34026</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;A query, I have a S2S IPsec VPN against a third party, in which, on our side we have the need that "the remote peer" does not know us with the real IPs of our servers.&lt;/P&gt;
&lt;P&gt;These are our Real IPs:&lt;BR /&gt;10.7.12.124&lt;BR /&gt;10.7.106.114 &lt;BR /&gt;192.168.216.50&lt;/P&gt;
&lt;P&gt;Destination IP of the remote peer:&lt;BR /&gt;69.20.50.41&lt;/P&gt;
&lt;P&gt;These 3 IPs, must "present" themselves to the remote peer, with the NAT IP -&amp;gt; 172.26.15.254&lt;/P&gt;
&lt;P&gt;Checkpoint requires that in this case, 3 Hide NAT type rules are created for each of the real IPs, right?&lt;/P&gt;
&lt;P&gt;It is not possible to work it in only one NAT rule?&lt;/P&gt;
&lt;P&gt;Cheers. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2023 16:25:27 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-in-S2S-VPN-deployment/m-p/185064#M34026</guid>
      <dc:creator>Matlu</dc:creator>
      <dc:date>2023-06-28T16:25:27Z</dc:date>
    </item>
    <item>
      <title>Re: NAT in S2S VPN deployment.</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-in-S2S-VPN-deployment/m-p/185065#M34027</link>
      <description>&lt;P&gt;Hey bro,&lt;/P&gt;
&lt;P&gt;Make sure NAT is enabled inside vpn community and if its static nat rules, then they may need to be separate.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2023 16:39:14 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-in-S2S-VPN-deployment/m-p/185065#M34027</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2023-06-28T16:39:14Z</dc:date>
    </item>
    <item>
      <title>Re: NAT in S2S VPN deployment.</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-in-S2S-VPN-deployment/m-p/185067#M34028</link>
      <description>&lt;P&gt;Buddy&lt;BR /&gt;&lt;BR /&gt;The TAC told me that in order for Checkpoint, to take my manual NAT rules into account, I have to disable the checkbox of the option that you see in the following image. &lt;span class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;😄&lt;/span&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="VPN1.png" style="width: 737px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/21557i2849BC8A00BA7BF5/image-size/large?v=v2&amp;amp;px=999" role="button" title="VPN1.png" alt="VPN1.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;For now, my manual NAT works fine, but it is configured as a 1 - 1 NAT.&lt;BR /&gt;And what I want is that on my side, there are 3 servers with different IPs, that can reach the other side of the VPN, with a single NAT IP.&lt;/P&gt;
&lt;P&gt;Is it possible to make a Hide NAT, using as origin a "group object" and putting there, all the IPs that I want to leave my side ????&lt;/P&gt;
&lt;P&gt;Greetings.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2023 16:49:23 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-in-S2S-VPN-deployment/m-p/185067#M34028</guid>
      <dc:creator>Matlu</dc:creator>
      <dc:date>2023-06-28T16:49:23Z</dc:date>
    </item>
    <item>
      <title>Re: NAT in S2S VPN deployment.</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-in-S2S-VPN-deployment/m-p/185068#M34029</link>
      <description>&lt;P&gt;Sorry, my bad, I believe TAC is correct. Also, as per below, makes sense&lt;/P&gt;
&lt;P&gt;&lt;A href="https://sc1.checkpoint.com/documents/R81.20/SmartConsole_OLH/EN/Topics-OLH/dL_YCs4YOk8Belcgyiq0Lg2.htm?cshid=dL_YCs4YOk8Belcgyiq0Lg2" target="_blank"&gt;VPN Communities - Advanced (checkpoint.com)&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Btw, if its hide NAT rule, then group should work.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2023 16:59:39 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-in-S2S-VPN-deployment/m-p/185068#M34029</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2023-06-28T16:59:39Z</dc:date>
    </item>
    <item>
      <title>Re: NAT in S2S VPN deployment.</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-in-S2S-VPN-deployment/m-p/185089#M34032</link>
      <description>&lt;P&gt;Yes, it is possible to setup groups in the NAT rule base for your hide NAT. I use this feature quite often.&lt;/P&gt;&lt;P&gt;You can absolutely put those 3 servers into a group and specify hide behind&amp;nbsp;&lt;SPAN&gt;172.26.15.254 when talking to the other remote network.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2023 19:35:47 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-in-S2S-VPN-deployment/m-p/185089#M34032</guid>
      <dc:creator>CaseyB</dc:creator>
      <dc:date>2023-06-28T19:35:47Z</dc:date>
    </item>
    <item>
      <title>Re: NAT in S2S VPN deployment.</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-in-S2S-VPN-deployment/m-p/185090#M34033</link>
      <description>&lt;P&gt;100% that works, agree.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2023 19:37:19 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-in-S2S-VPN-deployment/m-p/185090#M34033</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2023-06-28T19:37:19Z</dc:date>
    </item>
    <item>
      <title>Re: NAT in S2S VPN deployment.</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-in-S2S-VPN-deployment/m-p/185092#M34034</link>
      <description>&lt;P&gt;Thanks for the support, guys.&lt;/P&gt;
&lt;P&gt;Cheers. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2023 20:01:09 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-in-S2S-VPN-deployment/m-p/185092#M34034</guid>
      <dc:creator>Matlu</dc:creator>
      <dc:date>2023-06-28T20:01:09Z</dc:date>
    </item>
    <item>
      <title>Re: NAT in S2S VPN deployment.</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-in-S2S-VPN-deployment/m-p/185093#M34035</link>
      <description>&lt;P&gt;FYBFOC = for you bro, free of charge &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2023 20:09:39 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-in-S2S-VPN-deployment/m-p/185093#M34035</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2023-06-28T20:09:39Z</dc:date>
    </item>
  </channel>
</rss>

