<?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 Mobile Access with NAT in the firewall in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Mobile-Access-with-NAT-in-the-firewall/m-p/75011#M5801</link>
    <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After reading so many post here, I decided to join the community and this is my first post.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm configuring a Mobile Access&amp;nbsp; from scratch. The MAP (Mobile Access Portal) is accessible through all interfaces. In the external interface we have private IP address configured, and so the ISP router (let's say 10.0.0.0/24. And .1 is the cluster floating IP, .1 and .2 are the gateway's IPs and .5 is the router). The router just forward all the traffic from a certain public IP address range (let's say 70.0.0.0/29).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would like the MAP be accessible through one of the public IPs (70.0.0.1 for example). I tried several NAT rules to translate the&amp;nbsp;70.0.0.1 to the floaing IP address of the cluster (10.0.0.1). Also I tried to use the dynamic Object "LocalMachine".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From the traffic captures that I performed, I see that:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;When I access to the floating IP address (&lt;A href="https://10.0.0.1/sslvpn" target="_blank"&gt;https://10.0.0.1/sslvpn&lt;/A&gt;), the portal is reachable.&lt;/LI&gt;&lt;LI&gt;When I access to the public IP address (&lt;A href="https://70.0.0.1/sslvpn" target="_blank"&gt;https://70.0.0.1/sslvpn&lt;/A&gt;), I see that the firewall is performing the NAT in the incoming traffic, but it is answering with RST packet to every SYN packet that it receive from this connection.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any help?&lt;/P&gt;</description>
    <pubDate>Wed, 12 Feb 2020 17:17:07 GMT</pubDate>
    <dc:creator>Enrique</dc:creator>
    <dc:date>2020-02-12T17:17:07Z</dc:date>
    <item>
      <title>Mobile Access with NAT in the firewall</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Mobile-Access-with-NAT-in-the-firewall/m-p/75011#M5801</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After reading so many post here, I decided to join the community and this is my first post.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm configuring a Mobile Access&amp;nbsp; from scratch. The MAP (Mobile Access Portal) is accessible through all interfaces. In the external interface we have private IP address configured, and so the ISP router (let's say 10.0.0.0/24. And .1 is the cluster floating IP, .1 and .2 are the gateway's IPs and .5 is the router). The router just forward all the traffic from a certain public IP address range (let's say 70.0.0.0/29).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would like the MAP be accessible through one of the public IPs (70.0.0.1 for example). I tried several NAT rules to translate the&amp;nbsp;70.0.0.1 to the floaing IP address of the cluster (10.0.0.1). Also I tried to use the dynamic Object "LocalMachine".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From the traffic captures that I performed, I see that:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;When I access to the floating IP address (&lt;A href="https://10.0.0.1/sslvpn" target="_blank"&gt;https://10.0.0.1/sslvpn&lt;/A&gt;), the portal is reachable.&lt;/LI&gt;&lt;LI&gt;When I access to the public IP address (&lt;A href="https://70.0.0.1/sslvpn" target="_blank"&gt;https://70.0.0.1/sslvpn&lt;/A&gt;), I see that the firewall is performing the NAT in the incoming traffic, but it is answering with RST packet to every SYN packet that it receive from this connection.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any help?&lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2020 17:17:07 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Mobile-Access-with-NAT-in-the-firewall/m-p/75011#M5801</guid>
      <dc:creator>Enrique</dc:creator>
      <dc:date>2020-02-12T17:17:07Z</dc:date>
    </item>
    <item>
      <title>Re: Mobile Access with NAT in the firewall</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Mobile-Access-with-NAT-in-the-firewall/m-p/75022#M5804</link>
      <description>How are clients behind the gateway reaching the internet? Is the router doing a hide-NAT? If yes, best would be to also let it do the inbound NAT!</description>
      <pubDate>Wed, 12 Feb 2020 18:46:36 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Mobile-Access-with-NAT-in-the-firewall/m-p/75022#M5804</guid>
      <dc:creator>Norbert_Bohusch</dc:creator>
      <dc:date>2020-02-12T18:46:36Z</dc:date>
    </item>
    <item>
      <title>Re: Mobile Access with NAT in the firewall</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Mobile-Access-with-NAT-in-the-firewall/m-p/77174#M5918</link>
      <description>Hello,&lt;BR /&gt;The ISP router is just "routing" the traffic to the firewall. It's the firewalls who are NATing all the traffic.&lt;BR /&gt;&lt;BR /&gt;I found a workaround by configuring the public IP address as loopback in the gateways. This allows the firewall to answer properly to the MAP or other VPNssl connection (VPN capsule or Mobile Client).</description>
      <pubDate>Wed, 04 Mar 2020 18:51:27 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Mobile-Access-with-NAT-in-the-firewall/m-p/77174#M5918</guid>
      <dc:creator>Enrique</dc:creator>
      <dc:date>2020-03-04T18:51:27Z</dc:date>
    </item>
  </channel>
</rss>

