<?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: How can i create a SNAT Pool (Specific public IPs) with ISP redundancy in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-can-i-create-a-SNAT-Pool-Specific-public-IPs-with-ISP/m-p/61004#M4670</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Wing_Chow,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;if you are using ISP redundancy in LoadSharing mode both ISP links are used for outgoing connections.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Regarding the hide NAT, the default behaviour is to hide NAT the connection behind the outgoing interface.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;You must define an automatic hide NAT on the network- or host-object, select "hide behind gateway" and set your gateway with the ISP redundancy as install on target. You don't have to specify an IP-address&amp;nbsp; in the NAT configuration.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;And you can't use the automatic NAT-configuration on the gateway. Option "hide internal networks behind gateways" is not supported with ISP redundancy in LoadSharing mode.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;With this configuration outgoing packets via ISP-A are hide NATed behind the interface of ISP-A and&amp;nbsp;outgoing packets via ISP-B are hide NATed behind the interface of ISP-B.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Wolfgang&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 23 Aug 2019 06:41:52 GMT</pubDate>
    <dc:creator>Wolfgang</dc:creator>
    <dc:date>2019-08-23T06:41:52Z</dc:date>
    <item>
      <title>How can i create a SNAT Pool (Specific public IPs) with ISP redundancy</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-can-i-create-a-SNAT-Pool-Specific-public-IPs-with-ISP/m-p/61002#M4669</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I've been looking for SK to talk about how to configure a Hide NAT with specific Public IPs in ISP Redundancy. I mean how to can i create a outbound traffic with a Hide NAT pool (Specific IP for each ISP) not Gateway IP address.&lt;/P&gt;&lt;P&gt;I've been searching in history of GAIA OS from R76 to R80.30. I cannot see that this feature have been added.&lt;/P&gt;&lt;P&gt;For example:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="1.png" style="width: 758px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/2252i079F5AA6C5FAAB71/image-size/large?v=v2&amp;amp;px=999" role="button" title="1.png" alt="1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Email Servers: When we have a this scenario to load balanced a SMTP traffic, always need to respond from the same source for inbound and outbound. When we have a ISP Redundancy, the concepts to configure a ISP Redundancy are:&lt;/P&gt;&lt;P&gt;- To have redundance of services in most cases SMTP Traffic inbound and outbound for each ISP Public.&lt;/P&gt;&lt;P&gt;I know that Check Point is not a Load Balancer but at least need to have this feature because the only outbound load balancer is the Gateway IP Address.&lt;/P&gt;&lt;P&gt;Any information or SK or future feature in R80.40 and above, please let me know i will appreciate it.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Fri, 23 Aug 2019 04:57:37 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-can-i-create-a-SNAT-Pool-Specific-public-IPs-with-ISP/m-p/61002#M4669</guid>
      <dc:creator>Wing_Chow</dc:creator>
      <dc:date>2019-08-23T04:57:37Z</dc:date>
    </item>
    <item>
      <title>Re: How can i create a SNAT Pool (Specific public IPs) with ISP redundancy</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-can-i-create-a-SNAT-Pool-Specific-public-IPs-with-ISP/m-p/61004#M4670</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Wing_Chow,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;if you are using ISP redundancy in LoadSharing mode both ISP links are used for outgoing connections.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Regarding the hide NAT, the default behaviour is to hide NAT the connection behind the outgoing interface.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;You must define an automatic hide NAT on the network- or host-object, select "hide behind gateway" and set your gateway with the ISP redundancy as install on target. You don't have to specify an IP-address&amp;nbsp; in the NAT configuration.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;And you can't use the automatic NAT-configuration on the gateway. Option "hide internal networks behind gateways" is not supported with ISP redundancy in LoadSharing mode.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;With this configuration outgoing packets via ISP-A are hide NATed behind the interface of ISP-A and&amp;nbsp;outgoing packets via ISP-B are hide NATed behind the interface of ISP-B.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Wolfgang&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 23 Aug 2019 06:41:52 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-can-i-create-a-SNAT-Pool-Specific-public-IPs-with-ISP/m-p/61004#M4670</guid>
      <dc:creator>Wolfgang</dc:creator>
      <dc:date>2019-08-23T06:41:52Z</dc:date>
    </item>
    <item>
      <title>Re: How can i create a SNAT Pool (Specific public IPs) with ISP redundancy</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-can-i-create-a-SNAT-Pool-Specific-public-IPs-with-ISP/m-p/61045#M4676</link>
      <description>&lt;P&gt;Try this:&lt;/P&gt;&lt;P&gt;&lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk25152" target="_blank"&gt;https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk25152&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Static NAT fails for outgoing connections through gateway with ISP Redundancy in Load Sharing mode&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;It includes the use of dynamic objects to figure out which interface the connection goes through, but it should work...&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 23 Aug 2019 15:20:26 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-can-i-create-a-SNAT-Pool-Specific-public-IPs-with-ISP/m-p/61045#M4676</guid>
      <dc:creator>Eli_Faskha</dc:creator>
      <dc:date>2019-08-23T15:20:26Z</dc:date>
    </item>
    <item>
      <title>Re: How can i create a SNAT Pool (Specific public IPs) with ISP redundancy</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-can-i-create-a-SNAT-Pool-Specific-public-IPs-with-ISP/m-p/61058#M4677</link>
      <description>&lt;P&gt;Hi Eli_Faskha,&lt;/P&gt;&lt;P&gt;I have Tested for inbound and outbound and working good.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="1.png" style="width: 957px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/2261i0BAD8FBF7891AA58/image-size/large?v=v2&amp;amp;px=999" role="button" title="1.png" alt="1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks a lot.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Regards,&lt;/P&gt;</description>
      <pubDate>Fri, 23 Aug 2019 17:13:34 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-can-i-create-a-SNAT-Pool-Specific-public-IPs-with-ISP/m-p/61058#M4677</guid>
      <dc:creator>Wing_Chow</dc:creator>
      <dc:date>2019-08-23T17:13:34Z</dc:date>
    </item>
  </channel>
</rss>

