<?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 can be a different subnet IP address from real interface in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Alias-can-be-a-different-subnet-IP-address-from-real-interface/m-p/146551#M23279</link>
    <description>&lt;P&gt;ok, thanks&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 20 Apr 2022 07:31:52 GMT</pubDate>
    <dc:creator>Baasanjargal_Ts</dc:creator>
    <dc:date>2022-04-20T07:31:52Z</dc:date>
    <item>
      <title>Alias can be a different subnet IP address from real interface</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Alias-can-be-a-different-subnet-IP-address-from-real-interface/m-p/146252#M23204</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ISP gave another subnet public IP addresses. Can I set this new subnet IP on the existing WAN interface as an Alias? Usage of this new additional subnet is for static NAT on a host. If yes, how to configure default gateway address of this new subnetting?&lt;/P&gt;</description>
      <pubDate>Thu, 14 Apr 2022 06:22:32 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Alias-can-be-a-different-subnet-IP-address-from-real-interface/m-p/146252#M23204</guid>
      <dc:creator>Baasanjargal_Ts</dc:creator>
      <dc:date>2022-04-14T06:22:32Z</dc:date>
    </item>
    <item>
      <title>Re: Alias can be a different subnet IP address from real interface</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Alias-can-be-a-different-subnet-IP-address-from-real-interface/m-p/146334#M23205</link>
      <description>&lt;P&gt;It is enough for the ISP to route this subnet to your existing WAN IP as a next-hop and then you can configure the NAT. No alias interface is required here.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Apr 2022 01:22:11 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Alias-can-be-a-different-subnet-IP-address-from-real-interface/m-p/146334#M23205</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2022-04-15T01:22:11Z</dc:date>
    </item>
    <item>
      <title>Re: Alias can be a different subnet IP address from real interface</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Alias-can-be-a-different-subnet-IP-address-from-real-interface/m-p/146551#M23279</link>
      <description>&lt;P&gt;ok, thanks&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Apr 2022 07:31:52 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Alias-can-be-a-different-subnet-IP-address-from-real-interface/m-p/146551#M23279</guid>
      <dc:creator>Baasanjargal_Ts</dc:creator>
      <dc:date>2022-04-20T07:31:52Z</dc:date>
    </item>
  </channel>
</rss>

