<?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: Alias Interface Cloudguard in Cloud Firewall</title>
    <link>https://community.checkpoint.com/t5/Cloud-Firewall/Alias-Interface-Cloudguard/m-p/232944#M5054</link>
    <description>&lt;P&gt;This is adding this IP to topology since it's not directly related to the subnets.&lt;/P&gt;
&lt;P&gt;If you don't add it you'll need to put explicit rule in the access control rule base to avoid drops when accessing with this IP.&lt;/P&gt;</description>
    <pubDate>Sun, 17 Nov 2024 14:50:54 GMT</pubDate>
    <dc:creator>Amir_Senn</dc:creator>
    <dc:date>2024-11-17T14:50:54Z</dc:date>
    <item>
      <title>Alias Interface Cloudguard</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/Alias-Interface-Cloudguard/m-p/232943#M5053</link>
      <description>&lt;P&gt;I was trying to understand how Cross AZ Cluster with Transit Gateway works. I was reading the design guide and came across an alias interface. I was just trying to understand to what is the use case of external alias interface in the deployment.&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AZ-CLUSTER.png" style="width: 999px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/28475i116E652C8068277B/image-size/large?v=v2&amp;amp;px=999" role="button" title="AZ-CLUSTER.png" alt="AZ-CLUSTER.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 17 Nov 2024 14:21:55 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/Alias-Interface-Cloudguard/m-p/232943#M5053</guid>
      <dc:creator>sushantjoshi</dc:creator>
      <dc:date>2024-11-17T14:21:55Z</dc:date>
    </item>
    <item>
      <title>Re: Alias Interface Cloudguard</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/Alias-Interface-Cloudguard/m-p/232944#M5054</link>
      <description>&lt;P&gt;This is adding this IP to topology since it's not directly related to the subnets.&lt;/P&gt;
&lt;P&gt;If you don't add it you'll need to put explicit rule in the access control rule base to avoid drops when accessing with this IP.&lt;/P&gt;</description>
      <pubDate>Sun, 17 Nov 2024 14:50:54 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/Alias-Interface-Cloudguard/m-p/232944#M5054</guid>
      <dc:creator>Amir_Senn</dc:creator>
      <dc:date>2024-11-17T14:50:54Z</dc:date>
    </item>
    <item>
      <title>Re: Alias Interface Cloudguard</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/Alias-Interface-Cloudguard/m-p/232962#M5056</link>
      <description>&lt;P&gt;the alias is the 2nd IP address on the eth0 interface in each member.&lt;/P&gt;
&lt;P&gt;We attach the "VIP" Public&amp;nbsp; IP address to it and during failovers this IP detach and attach to the 2nd IP of the 2nd member and vice versa.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 18 Nov 2024 07:49:46 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/Alias-Interface-Cloudguard/m-p/232962#M5056</guid>
      <dc:creator>Nir_Shamir</dc:creator>
      <dc:date>2024-11-18T07:49:46Z</dc:date>
    </item>
  </channel>
</rss>

