<?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: Additional NAT rule 1 in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Additional-NAT-rule-1/m-p/161824#M28707</link>
    <description>&lt;P&gt;The log should point to the "link" to click on for it. As phoneboy asked, if you could provide a screenshot, it would help us.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
    <pubDate>Thu, 10 Nov 2022 21:57:14 GMT</pubDate>
    <dc:creator>the_rock</dc:creator>
    <dc:date>2022-11-10T21:57:14Z</dc:date>
    <item>
      <title>Additional NAT rule 1</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Additional-NAT-rule-1/m-p/161729#M28667</link>
      <description>&lt;P&gt;Please anyone can explain what is&amp;nbsp;&lt;SPAN&gt;Additional NAT rule 1?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;theoretically.&amp;nbsp; I have enabled bi-directional NAT in Global Properties.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Nov 2022 06:31:08 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Additional-NAT-rule-1/m-p/161729#M28667</guid>
      <dc:creator>m_bilal</dc:creator>
      <dc:date>2022-11-10T06:31:08Z</dc:date>
    </item>
    <item>
      <title>Re: Additional NAT rule 1</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Additional-NAT-rule-1/m-p/161818#M28706</link>
      <description>&lt;P&gt;Where exactly are you seeing this?&lt;BR /&gt;Please provide a screenshot.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Nov 2022 20:34:37 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Additional-NAT-rule-1/m-p/161818#M28706</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2022-11-10T20:34:37Z</dc:date>
    </item>
    <item>
      <title>Re: Additional NAT rule 1</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Additional-NAT-rule-1/m-p/161824#M28707</link>
      <description>&lt;P&gt;The log should point to the "link" to click on for it. As phoneboy asked, if you could provide a screenshot, it would help us.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Thu, 10 Nov 2022 21:57:14 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Additional-NAT-rule-1/m-p/161824#M28707</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2022-11-10T21:57:14Z</dc:date>
    </item>
    <item>
      <title>Re: Additional NAT rule 1</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Additional-NAT-rule-1/m-p/161924#M28763</link>
      <description>&lt;P&gt;"Additional NAT Rule" appearing in a log card indicates that a second NAT rule was matched for the same connection.&amp;nbsp; This is only possible if "bi-directional NAT" is set in the NAT Global Properties (it is set by default), and one automatically-generated NAT rule matches the source IP address of the packet, and another automatically-generated NAT rule matches the destination IP address on the packet.&amp;nbsp; In this case both source IP and destination IP for the connection are NATted simultaneously.&amp;nbsp; Most common NAT operations only change either source or destination but not both; this condition is an exception to that and certainly possible.&lt;/P&gt;
&lt;P&gt;Note that this can only happen for two automatically-generated rules; if a manual NAT rule is matched first, only that one NAT rule can be matched, and an additional NAT rule match is impossible.&amp;nbsp; It is also not possible to have an automatically-generated rule match one element of the packet (say source IP address) and a manual rule then match a destination IP address.&amp;nbsp; Only one manual NAT rule can be matched for a connection, period.&lt;/P&gt;</description>
      <pubDate>Sat, 12 Nov 2022 19:09:26 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Additional-NAT-rule-1/m-p/161924#M28763</guid>
      <dc:creator>Timothy_Hall</dc:creator>
      <dc:date>2022-11-12T19:09:26Z</dc:date>
    </item>
    <item>
      <title>Re: Additional NAT rule 1</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Additional-NAT-rule-1/m-p/161926#M28765</link>
      <description>&lt;P&gt;To excellent explanation from&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/597"&gt;@Timothy_Hall&lt;/a&gt;&amp;nbsp;, below is also great reference for this.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_SecurityManagement_AdminGuide/Topics-SECMG/NAT-Rules.htm" target="_blank"&gt;https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_SecurityManagement_AdminGuide/Topics-SECMG/NAT-Rules.htm&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 12 Nov 2022 20:10:40 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Additional-NAT-rule-1/m-p/161926#M28765</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2022-11-12T20:10:40Z</dc:date>
    </item>
  </channel>
</rss>

