<?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 Loopback - Hairpin NAT in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-Loopback-Hairpin-NAT/m-p/238201#M46226</link>
    <description>&lt;P&gt;Here's what a Hairpin NAT rule is supposed to look like:&amp;nbsp;&lt;A href="https://community.checkpoint.com/t5/Security-Gateways/Traffic-flow-in-between-C-to-S-via-Firewall-How/m-p/8466#M13082" target="_blank"&gt;https://community.checkpoint.com/t5/Security-Gateways/Traffic-flow-in-between-C-to-S-via-Firewall-How/m-p/8466#M13082&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 10 Jan 2025 17:21:04 GMT</pubDate>
    <dc:creator>PhoneBoy</dc:creator>
    <dc:date>2025-01-10T17:21:04Z</dc:date>
    <item>
      <title>NAT Loopback - Hairpin NAT</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-Loopback-Hairpin-NAT/m-p/238179#M46219</link>
      <description>&lt;P&gt;Good Day&lt;/P&gt;&lt;P&gt;We are trying to do allow hairpin NAT for our Mitel Voice system. We want our devices on the inside network to be able to reach the Mitel device, which is on the internal network, by its Public IP Address.&lt;/P&gt;&lt;P&gt;I have attached topology of the environment.&lt;/P&gt;&lt;P&gt;Tried sk110019 - not coming right&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jan 2025 15:37:12 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-Loopback-Hairpin-NAT/m-p/238179#M46219</guid>
      <dc:creator>ThabEugS</dc:creator>
      <dc:date>2025-01-10T15:37:12Z</dc:date>
    </item>
    <item>
      <title>Re: NAT Loopback - Hairpin NAT</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-Loopback-Hairpin-NAT/m-p/238182#M46220</link>
      <description>&lt;P&gt;Can you give an example of how you did the nat rule?&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jan 2025 15:48:38 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-Loopback-Hairpin-NAT/m-p/238182#M46220</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-01-10T15:48:38Z</dc:date>
    </item>
    <item>
      <title>Re: NAT Loopback - Hairpin NAT</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-Loopback-Hairpin-NAT/m-p/238201#M46226</link>
      <description>&lt;P&gt;Here's what a Hairpin NAT rule is supposed to look like:&amp;nbsp;&lt;A href="https://community.checkpoint.com/t5/Security-Gateways/Traffic-flow-in-between-C-to-S-via-Firewall-How/m-p/8466#M13082" target="_blank"&gt;https://community.checkpoint.com/t5/Security-Gateways/Traffic-flow-in-between-C-to-S-via-Firewall-How/m-p/8466#M13082&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jan 2025 17:21:04 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-Loopback-Hairpin-NAT/m-p/238201#M46226</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2025-01-10T17:21:04Z</dc:date>
    </item>
    <item>
      <title>Re: NAT Loopback - Hairpin NAT</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-Loopback-Hairpin-NAT/m-p/238203#M46228</link>
      <description>&lt;P&gt;Just to make sure I understand, do you want something on the 5.0/24 network to hit 5.5 via 161.30.141.1.12? Do you need to hide the client's IP addresses (or, more precisely, can you?)?&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jan 2025 18:02:51 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-Loopback-Hairpin-NAT/m-p/238203#M46228</guid>
      <dc:creator>Chillyjim</dc:creator>
      <dc:date>2025-01-10T18:02:51Z</dc:date>
    </item>
    <item>
      <title>Re: NAT Loopback - Hairpin NAT</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-Loopback-Hairpin-NAT/m-p/238263#M46233</link>
      <description>&lt;P&gt;What about the firewall rules ?&lt;/P&gt;</description>
      <pubDate>Sat, 11 Jan 2025 04:06:04 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-Loopback-Hairpin-NAT/m-p/238263#M46233</guid>
      <dc:creator>ThabEugS</dc:creator>
      <dc:date>2025-01-11T04:06:04Z</dc:date>
    </item>
    <item>
      <title>Re: NAT Loopback - Hairpin NAT</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-Loopback-Hairpin-NAT/m-p/238264#M46234</link>
      <description>&lt;P&gt;For regular fw rules, just make sure access is allowed.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Sat, 11 Jan 2025 04:28:25 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-Loopback-Hairpin-NAT/m-p/238264#M46234</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-01-11T04:28:25Z</dc:date>
    </item>
    <item>
      <title>Re: NAT Loopback - Hairpin NAT</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-Loopback-Hairpin-NAT/m-p/238265#M46235</link>
      <description>&lt;P&gt;For what is worth, though I know you said you followed the sk AI gave me in this example, but see below, hope it helps.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;************************************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV class="ai-chatbot-conversation-assistant-text css-1lxqfct"&gt;
&lt;P&gt;This is Check Point AI Assistant.&lt;/P&gt;
&lt;P&gt;To configure NAT Loopback (Hairpin NAT / NAT Reflection) on a Check Point Security Gateway, follow these steps:&lt;/P&gt;
&lt;H3&gt;Background&lt;/H3&gt;
&lt;P&gt;NAT Loopback allows internal clients to access an internal server using its public IP address. This is useful when internal clients need to access services using the same domain name or IP address as external clients.&lt;/P&gt;
&lt;H3&gt;Network Topology Example&lt;/H3&gt;
&lt;P&gt;Consider the following network topology:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Client #1&lt;/STRONG&gt;: Public IP 2.2.2.2&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Client #2&lt;/STRONG&gt;: Private IP 192.168.1.10&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Security Gateway&lt;/STRONG&gt;: Public IP 1.1.1.1, Private IP 192.168.1.1&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Web Server&lt;/STRONG&gt;: Private IP 192.168.1.2&lt;/LI&gt;
&lt;/UL&gt;
&lt;H3&gt;Steps to Configure NAT Loopback&lt;/H3&gt;
&lt;H4&gt;In SmartConsole R80 and Higher&lt;/H4&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Create Host Objects&lt;/STRONG&gt;:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Create host objects for Client #1, Client #2, Security Gateway, and Web Server with their respective IP addresses.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Configure NAT Rules&lt;/STRONG&gt;:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Open the NAT policy in SmartConsole.&lt;/LI&gt;
&lt;LI&gt;Add the following NAT rules:&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;TABLE&gt;
&lt;THEAD&gt;
&lt;TR&gt;
&lt;TH&gt;No.&lt;/TH&gt;
&lt;TH&gt;Original Source&lt;/TH&gt;
&lt;TH&gt;Original Destination&lt;/TH&gt;
&lt;TH&gt;Original Services&lt;/TH&gt;
&lt;TH&gt;Translated Source&lt;/TH&gt;
&lt;TH&gt;Translated Destination&lt;/TH&gt;
&lt;TH&gt;Translated Services&lt;/TH&gt;
&lt;TH&gt;Install On&lt;/TH&gt;
&lt;/TR&gt;
&lt;/THEAD&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD&gt;1&lt;/TD&gt;
&lt;TD&gt;Client #1's Public IP (2.2.2.2)&lt;/TD&gt;
&lt;TD&gt;Web Server's Public IP (1.1.1.1)&lt;/TD&gt;
&lt;TD&gt;http&lt;/TD&gt;
&lt;TD&gt;Client #1's Public IP (2.2.2.2)&lt;/TD&gt;
&lt;TD&gt;Web Server's Private IP (192.168.1.2)&lt;/TD&gt;
&lt;TD&gt;= Original&lt;/TD&gt;
&lt;TD&gt;Security Gateway&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;2&lt;/TD&gt;
&lt;TD&gt;Client #2's Private IP (192.168.1.10)&lt;/TD&gt;
&lt;TD&gt;Web Server's Public IP (1.1.1.1)&lt;/TD&gt;
&lt;TD&gt;http&lt;/TD&gt;
&lt;TD&gt;Security Gateway's Private IP (192.168.1.1)&lt;/TD&gt;
&lt;TD&gt;Web Server's Private IP (192.168.1.2)&lt;/TD&gt;
&lt;TD&gt;= Original&lt;/TD&gt;
&lt;TD&gt;Security Gateway&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;3&lt;/TD&gt;
&lt;TD&gt;Web Server's Private IP (192.168.1.2)&lt;/TD&gt;
&lt;TD&gt;* Any&lt;/TD&gt;
&lt;TD&gt;http&lt;/TD&gt;
&lt;TD&gt;Web Server's Public IP (1.1.1.1)&lt;/TD&gt;
&lt;TD&gt;= Original&lt;/TD&gt;
&lt;TD&gt;= Original&lt;/TD&gt;
&lt;TD&gt;Security Gateway&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;OL start="3"&gt;
&lt;LI&gt;&lt;STRONG&gt;Install Policy&lt;/STRONG&gt;:
&lt;UL&gt;
&lt;LI&gt;After configuring the NAT rules, install the policy on the Security Gateway.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;H4&gt;In SmartDashboard R77.X and Lower&lt;/H4&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Create Host Objects&lt;/STRONG&gt;:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Create host objects for Client #1, Client #2, Security Gateway, and Web Server with their respective IP addresses.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Configure NAT Rules&lt;/STRONG&gt;:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Open the NAT policy in SmartDashboard.&lt;/LI&gt;
&lt;LI&gt;Add the following NAT rules:&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;TABLE&gt;
&lt;THEAD&gt;
&lt;TR&gt;
&lt;TH&gt;No.&lt;/TH&gt;
&lt;TH&gt;Original Packet&lt;/TH&gt;
&lt;TH&gt;Translated Packet&lt;/TH&gt;
&lt;TH&gt;Install On&lt;/TH&gt;
&lt;/TR&gt;
&lt;/THEAD&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD&gt;1&lt;/TD&gt;
&lt;TD&gt;Source: Client #1's Public IP (2.2.2.2), Destination: Web Server's Public IP (1.1.1.1), Service: http&lt;/TD&gt;
&lt;TD&gt;Source: Client #1's Public IP (2.2.2.2), Destination: Web Server's Private IP (192.168.1.2), Service: = Original&lt;/TD&gt;
&lt;TD&gt;Security Gateway&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;2&lt;/TD&gt;
&lt;TD&gt;Source: Client #2's Private IP (192.168.1.10), Destination: Web Server's Public IP (1.1.1.1), Service: http&lt;/TD&gt;
&lt;TD&gt;Source: Client #2's Private IP (192.168.1.10), Destination: Web Server's Private IP (192.168.1.2), Service: = Original&lt;/TD&gt;
&lt;TD&gt;Security Gateway&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;3&lt;/TD&gt;
&lt;TD&gt;Source: Web Server's Private IP (192.168.1.2), Destination: Any, Service: http&lt;/TD&gt;
&lt;TD&gt;Source: Web Server's Public IP (1.1.1.1), Destination: = Original, Service: = Original&lt;/TD&gt;
&lt;TD&gt;Security Gateway&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;OL start="3"&gt;
&lt;LI&gt;&lt;STRONG&gt;Install Policy&lt;/STRONG&gt;:
&lt;UL&gt;
&lt;LI&gt;After configuring the NAT rules, install the policy on the Security Gateway.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;H3&gt;Important Notes&lt;/H3&gt;
&lt;UL&gt;
&lt;LI&gt;Ensure that the NAT rules are in the correct order.&lt;/LI&gt;
&lt;LI&gt;Verify the connectivity and functionality after applying the NAT rules.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;For more detailed information, you can refer to the Check Point support article&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://support.checkpoint.com/results/sk/sk110019" target="_blank" rel="noopener"&gt;sk110019&lt;/A&gt;.&lt;/P&gt;
&lt;/DIV&gt;
&lt;DIV class="ai-chatbot-references css-g9n3fs"&gt;
&lt;DIV class="css-131f8vm"&gt;Learn more:&lt;/DIV&gt;
&lt;DIV class="css-zs1iv6"&gt;
&lt;OL class="css-3yupri"&gt;
&lt;LI class="ai-chatbot-reference css-1onth16"&gt;&lt;A class="css-a3bjub" href="http://support.checkpoint.com/results/sk/sk110019" target="_blank" rel="noopener"&gt;sk110019 - How to configure NAT Loopback (Hairpin NAT / NAT Reflection) on Check Point Security Gateway&lt;/A&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Sat, 11 Jan 2025 04:53:39 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-Loopback-Hairpin-NAT/m-p/238265#M46235</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-01-11T04:53:39Z</dc:date>
    </item>
    <item>
      <title>Re: NAT Loopback - Hairpin NAT</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-Loopback-Hairpin-NAT/m-p/238895#M46341</link>
      <description>&lt;P&gt;That is what i am looking for.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jan 2025 10:22:59 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/NAT-Loopback-Hairpin-NAT/m-p/238895#M46341</guid>
      <dc:creator>ThabEugS</dc:creator>
      <dc:date>2025-01-17T10:22:59Z</dc:date>
    </item>
  </channel>
</rss>

