<?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: Natting Proxy-Traffic to internal IP in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Natting-Proxy-Traffic-to-internal-IP/m-p/160592#M28331</link>
    <description>&lt;P&gt;Do you use WPAD / PAC file for your proxy configuration and are local domains excluded ?&lt;/P&gt;</description>
    <pubDate>Thu, 27 Oct 2022 15:31:03 GMT</pubDate>
    <dc:creator>Chris_Atkinson</dc:creator>
    <dc:date>2022-10-27T15:31:03Z</dc:date>
    <item>
      <title>Natting Proxy-Traffic to internal IP</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Natting-Proxy-Traffic-to-internal-IP/m-p/160570#M28326</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;we have the following problem, regarding HTTP-/HTTPS-Proxy on our CheckPoint ClusterXL R81.10:&lt;/P&gt;&lt;P&gt;The cluster is configured as a non-transparent http/https-proxy on one cluster-vip-ip port 8080.&amp;nbsp;We even host some websites on internal webservers, that are available via a external NAT on the cluster-xl, redirecting to internal webservers / reverse proxies:&lt;/P&gt;&lt;P&gt;External Client -----&amp;gt; www -----&amp;gt; public Cluster-IP -----&amp;gt; NAT to Webserver -----&amp;gt; Webserver&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now when our internal clients want to view a webpage, that is hosted on our internal servers, the page is not available.&lt;/P&gt;&lt;P&gt;So the process is:&lt;/P&gt;&lt;P&gt;1. Client resolves the dns-name of the webpage to the public ip.&lt;/P&gt;&lt;P&gt;2. Client opens a proxy-session with the checkpoint-cluster&lt;/P&gt;&lt;P&gt;At this point we want to have a NAT-Rule that redirects traffic, originally sent to our public Cluster-IP (original Dst) to our internal Webserver (translated Dst).&lt;/P&gt;&lt;P&gt;The standard NAT-Rule doesn´t work:&lt;/P&gt;&lt;P&gt;Internal Clients -----&amp;gt; public Cluster-IP:https -----&amp;gt; Original Src. -----&amp;gt; Internal Webserver&lt;/P&gt;&lt;P&gt;Is there a trick, so we can redirect http-/https-proxy-traffic to an internal server?&lt;/P&gt;&lt;P&gt;Thanks and best regards&lt;/P&gt;</description>
      <pubDate>Thu, 27 Oct 2022 11:28:12 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Natting-Proxy-Traffic-to-internal-IP/m-p/160570#M28326</guid>
      <dc:creator>Andre91</dc:creator>
      <dc:date>2022-10-27T11:28:12Z</dc:date>
    </item>
    <item>
      <title>Re: Natting Proxy-Traffic to internal IP</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Natting-Proxy-Traffic-to-internal-IP/m-p/160592#M28331</link>
      <description>&lt;P&gt;Do you use WPAD / PAC file for your proxy configuration and are local domains excluded ?&lt;/P&gt;</description>
      <pubDate>Thu, 27 Oct 2022 15:31:03 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Natting-Proxy-Traffic-to-internal-IP/m-p/160592#M28331</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2022-10-27T15:31:03Z</dc:date>
    </item>
    <item>
      <title>Re: Natting Proxy-Traffic to internal IP</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Natting-Proxy-Traffic-to-internal-IP/m-p/160683#M28369</link>
      <description>&lt;P&gt;I am assuming both the internal clients and your webserver are accessible through the same physical interface.&lt;BR /&gt;That means you basically need a hairpin NAT rule, something similar to what I described here:&amp;nbsp;&lt;A href="https://community.checkpoint.com/t5/Security-Gateways/Traffic-flow-in-between-C-to-S-via-Firewall-How/m-p/8465/thread-id/13081#M13082" target="_blank"&gt;https://community.checkpoint.com/t5/Security-Gateways/Traffic-flow-in-between-C-to-S-via-Firewall-How/m-p/8465/thread-id/13081#M13082&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Oct 2022 14:52:52 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Natting-Proxy-Traffic-to-internal-IP/m-p/160683#M28369</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2022-10-28T14:52:52Z</dc:date>
    </item>
    <item>
      <title>Re: Natting Proxy-Traffic to internal IP</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Natting-Proxy-Traffic-to-internal-IP/m-p/163336#M29149</link>
      <description>&lt;P&gt;Thanks for the tips, we excluded our domain-names in our PAC file. That works so far&lt;/P&gt;</description>
      <pubDate>Mon, 28 Nov 2022 11:34:27 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Natting-Proxy-Traffic-to-internal-IP/m-p/163336#M29149</guid>
      <dc:creator>Andre91</dc:creator>
      <dc:date>2022-11-28T11:34:27Z</dc:date>
    </item>
  </channel>
</rss>

