<?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 Reverse Proxy (R80.40) - Limitations in Mobile</title>
    <link>https://community.checkpoint.com/t5/Mobile/Mobile-Access-Reverse-Proxy-R80-40-Limitations/m-p/142603#M768</link>
    <description>&lt;P&gt;Hello, Just want to share our experience implementing the MoB Reverse Proxy in R80.40.&lt;/P&gt;&lt;P&gt;Note: The &lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk110348&amp;amp;partition=Advanced&amp;amp;product=Mobile" target="_blank" rel="noopener"&gt;sk110348&lt;/A&gt; is a great article in conjunction with &lt;A href="https://sc1.checkpoint.com/documents/R80.40/WebAdminGuides/EN/CP_R80.40_MobileAccess_AdminGuide/Topics-MABG/Reverse-Proxy.htm?tocpath=_____17" target="_blank" rel="noopener"&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;MoB R80.40 admin Guide.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In R80.40 at least, found another limitation not explicitly noted in the SK at the time of this post:&lt;/P&gt;&lt;P&gt;It seems &lt;STRONG&gt;It is only possible to use the IP assigned to the Firewall.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;It is not possible to use another IP address that is available in the same Pub subnet.&lt;/P&gt;&lt;P&gt;Example: It is only possible to use the 0.0.0.2 IP (FW IP address)&lt;/P&gt;&lt;P&gt;/28&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;0.0.0.1 - GW NetworkService&lt;/LI&gt;&lt;LI&gt;0.0.0.2 - IP assigned to the Firewall / cluster.&lt;/LI&gt;&lt;LI&gt;0.0.0.3 - IP used for other NATs&lt;/LI&gt;&lt;LI&gt;0.0.0.4 - Free IP.&lt;/LI&gt;&lt;LI&gt;...&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;We have implemented KB, and we have tried to use the 3rd or 4th IP. But it did not work.&lt;/P&gt;&lt;P&gt;Only worked when we pointed the DNSs to the 2nd IP instead of 3 or 4.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
    <pubDate>Mon, 28 Feb 2022 10:30:35 GMT</pubDate>
    <dc:creator>taduo</dc:creator>
    <dc:date>2022-02-28T10:30:35Z</dc:date>
    <item>
      <title>Mobile Access Reverse Proxy (R80.40) - Limitations</title>
      <link>https://community.checkpoint.com/t5/Mobile/Mobile-Access-Reverse-Proxy-R80-40-Limitations/m-p/142603#M768</link>
      <description>&lt;P&gt;Hello, Just want to share our experience implementing the MoB Reverse Proxy in R80.40.&lt;/P&gt;&lt;P&gt;Note: The &lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk110348&amp;amp;partition=Advanced&amp;amp;product=Mobile" target="_blank" rel="noopener"&gt;sk110348&lt;/A&gt; is a great article in conjunction with &lt;A href="https://sc1.checkpoint.com/documents/R80.40/WebAdminGuides/EN/CP_R80.40_MobileAccess_AdminGuide/Topics-MABG/Reverse-Proxy.htm?tocpath=_____17" target="_blank" rel="noopener"&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;MoB R80.40 admin Guide.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In R80.40 at least, found another limitation not explicitly noted in the SK at the time of this post:&lt;/P&gt;&lt;P&gt;It seems &lt;STRONG&gt;It is only possible to use the IP assigned to the Firewall.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;It is not possible to use another IP address that is available in the same Pub subnet.&lt;/P&gt;&lt;P&gt;Example: It is only possible to use the 0.0.0.2 IP (FW IP address)&lt;/P&gt;&lt;P&gt;/28&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;0.0.0.1 - GW NetworkService&lt;/LI&gt;&lt;LI&gt;0.0.0.2 - IP assigned to the Firewall / cluster.&lt;/LI&gt;&lt;LI&gt;0.0.0.3 - IP used for other NATs&lt;/LI&gt;&lt;LI&gt;0.0.0.4 - Free IP.&lt;/LI&gt;&lt;LI&gt;...&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;We have implemented KB, and we have tried to use the 3rd or 4th IP. But it did not work.&lt;/P&gt;&lt;P&gt;Only worked when we pointed the DNSs to the 2nd IP instead of 3 or 4.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Mon, 28 Feb 2022 10:30:35 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Mobile/Mobile-Access-Reverse-Proxy-R80-40-Limitations/m-p/142603#M768</guid>
      <dc:creator>taduo</dc:creator>
      <dc:date>2022-02-28T10:30:35Z</dc:date>
    </item>
    <item>
      <title>Re: Mobile Access Reverse Proxy (R80.40) - Limitations</title>
      <link>https://community.checkpoint.com/t5/Mobile/Mobile-Access-Reverse-Proxy-R80-40-Limitations/m-p/142808#M769</link>
      <description>&lt;P&gt;I assume this is because the underlying MultiPortal infrastructure only works on the gateway IP and not others.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Mar 2022 15:21:26 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Mobile/Mobile-Access-Reverse-Proxy-R80-40-Limitations/m-p/142808#M769</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2022-03-02T15:21:26Z</dc:date>
    </item>
  </channel>
</rss>

