<?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: Combine VLAN and physical interface, which already has an assigned IP in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32431#M6803</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV class=""&gt;&lt;P&gt;&lt;STRONG&gt;Check Point updated &lt;A class="" href="http://supportcontent.checkpoint.com/solutions?id=sk88700" rel="nofollow"&gt;sk88700&lt;/A&gt;: &lt;A href="http://supportcontent.checkpoint.com/solutions?id=sk88700" rel="nofollow"&gt;Creating VLAN interfaces on a physical interface, which already has an assigned IP address&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It is &lt;STRONG&gt;mandatory &lt;/STRONG&gt;to remove an IP address from a physical interface &lt;STRONG&gt;BEFORE &lt;/STRONG&gt;creating VLAN interfaces on it and it is not supported to add an IP address to that physical interfaces &lt;STRONG&gt;AFTER&lt;/STRONG&gt; creating a VLAN interface on it.&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 29 Aug 2018 08:41:09 GMT</pubDate>
    <dc:creator>Danny</dc:creator>
    <dc:date>2018-08-29T08:41:09Z</dc:date>
    <item>
      <title>Combine VLAN and physical interface, which already has an assigned IP</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32422#M6794</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Is there documentation or article that can inform limitations or best practices when configuring a VLAN and using the physical interface with IP address?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jun 2018 17:44:40 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32422#M6794</guid>
      <dc:creator>Ricardo_Olivei1</dc:creator>
      <dc:date>2018-06-19T17:44:40Z</dc:date>
    </item>
    <item>
      <title>Re: Combine VLAN and physical interface, which already has an assigned IP</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32423#M6795</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I assume you are referring to the practice of directly assigning an IP address to a physical interface for untagged/native traffic, then also having VLAN-tagged subinterfaces on that same physical interface.&amp;nbsp; That configuration is most definitely not supported for ClusterXL and may cause some strange performance issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have seen this done on a non-clustered firewall and everything seemed to work, but I'm pretty sure it is not officially supported.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&lt;BR /&gt;Second Edition of my "Max Power" Firewall Book&lt;BR /&gt;&lt;SPAN&gt;Now Available at &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.maxpowerfirewalls.com" rel="nofollow"&gt;http://www.maxpowerfirewalls.com&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jun 2018 18:19:25 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32423#M6795</guid>
      <dc:creator>Timothy_Hall</dc:creator>
      <dc:date>2018-06-19T18:19:25Z</dc:date>
    </item>
    <item>
      <title>Re: Combine VLAN and physical interface, which already has an assigned IP</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32424#M6796</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;Topic: &lt;A href="http://supportcontent.checkpoint.com/solutions?id=sk88700"&gt;Creating VLAN interfaces on a physical interface, which already has an assigned IP address&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;A href="http://supportcontent.checkpoint.com/solutions?id=sk88700"&gt;sk88700&lt;/A&gt;&lt;/STRONG&gt; : It is &lt;STRONG&gt;mandatory &lt;/STRONG&gt;to remove an IP address from a physical interface before creating any VLAN interfaces on that physical interface.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jun 2018 20:29:33 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32424#M6796</guid>
      <dc:creator>Danny</dc:creator>
      <dc:date>2018-06-19T20:29:33Z</dc:date>
    </item>
    <item>
      <title>Re: Combine VLAN and physical interface, which already has an assigned IP</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32425#M6797</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Tim,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the info. It is exactly what I have configured due to an infrastructure limitation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is a non-clustered firewall and apparently seems&amp;nbsp;to work, however, there is an adverse behavior in redundancy when enabling the functionality of ISP Redundancy. The traffic is not in being&amp;nbsp;balanced in accordance with the configured weight, presenting discrepancies in the monitoring.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I searched the documentation for something related, unsuccessfully so far.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jun 2018 20:42:34 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32425#M6797</guid>
      <dc:creator>Ricardo_Olivei1</dc:creator>
      <dc:date>2018-06-19T20:42:34Z</dc:date>
    </item>
    <item>
      <title>Re: Combine VLAN and physical interface, which already has an assigned IP</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32426#M6798</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Danny,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding sk88700, it informs that in order to configure the VLAN interface, the IP address must be removed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, after removing the IP address of the physical interface and configuring the VLAN, it is possible to reconfigure the address in the physical interface for the native traffic,&amp;nbsp;this way not making it clear whether this setting is recommended or not as Tim reported.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By doing a test in the laboratory, I managed through the CLI configure an IP address on the physical interface and after that configure the VLAN interface, without removing the IP address previously configured.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jun 2018 20:55:24 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32426#M6798</guid>
      <dc:creator>Ricardo_Olivei1</dc:creator>
      <dc:date>2018-06-19T20:55:24Z</dc:date>
    </item>
    <item>
      <title>Re: Combine VLAN and physical interface, which already has an assigned IP</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32427#M6799</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE&gt;&lt;PRE class="language-none"&gt;&lt;PRE class="language-none line-numbers"&gt;&lt;CODE&gt;Hello Danny Jung,&lt;BR /&gt;&lt;BR /&gt;Thank you for providing your feedback to SecureKnowledge on sk88700, titled "Creating VLAN interfaces on physical interface, which already has an assigned IP address in SecurePlatform OS / Gaia OS". &lt;BR /&gt;&lt;BR /&gt;Your feedback was: &lt;BR /&gt;------------------&lt;BR /&gt;Please clarify what happens AFTER the VLAN interfaces were configured. Is it supported to create an IP address to the physical interface then? This question has been raised at https://community.checkpoint.com/thread/8176&lt;BR /&gt;------------------&lt;BR /&gt;&lt;BR /&gt;Once this solution is updated, we will notify you by email. &lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;/PRE&gt;&lt;/PRE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Jun 2018 06:44:02 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32427#M6799</guid>
      <dc:creator>Danny</dc:creator>
      <dc:date>2018-06-20T06:44:02Z</dc:date>
    </item>
    <item>
      <title>Re: Combine VLAN and physical interface, which already has an assigned IP</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32428#M6800</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Experiencing traffic balancing issues for ISP Redundancy sounds about right for configuring an interface in a way that is not supported, as in it works most of the time but causes subtle problems or improper behavior in certain situations.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&lt;BR /&gt;Second Edition of my "Max Power" Firewall Book&lt;BR /&gt;&lt;SPAN&gt;Now Available at &lt;/SPAN&gt;&lt;A class="" href="http://www.maxpowerfirewalls.com" rel="nofollow"&gt;http://www.maxpowerfirewalls.com&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Jun 2018 12:52:43 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32428#M6800</guid>
      <dc:creator>Timothy_Hall</dc:creator>
      <dc:date>2018-06-20T12:52:43Z</dc:date>
    </item>
    <item>
      <title>Re: Combine VLAN and physical interface, which already has an assigned IP</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32429#M6801</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Danny,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tks for request one clarification regarding this case, let's wait for the response from Check Point.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My bests&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Jun 2018 18:06:29 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32429#M6801</guid>
      <dc:creator>Ricardo_Olivei1</dc:creator>
      <dc:date>2018-06-22T18:06:29Z</dc:date>
    </item>
    <item>
      <title>Re: Combine VLAN and physical interface, which already has an assigned IP</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32430#M6802</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, this is the answer I got from Check Point:&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;STRONG&gt;The answer will require more investigation which is &lt;SPAN style="text-decoration: underline;"&gt;out of my scope.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;Please open a service request by logging into Check Point User Center.&lt;BR /&gt;&lt;STRONG&gt;Please do not reply to this message.&lt;/STRONG&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I really think Check Point should be able to tell officially if VLAN interfaces are supported on physical interfaces, that get an IP address assigned after the VLAN was created.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Aug 2018 06:49:11 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32430#M6802</guid>
      <dc:creator>Danny</dc:creator>
      <dc:date>2018-08-08T06:49:11Z</dc:date>
    </item>
    <item>
      <title>Re: Combine VLAN and physical interface, which already has an assigned IP</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32431#M6803</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV class=""&gt;&lt;P&gt;&lt;STRONG&gt;Check Point updated &lt;A class="" href="http://supportcontent.checkpoint.com/solutions?id=sk88700" rel="nofollow"&gt;sk88700&lt;/A&gt;: &lt;A href="http://supportcontent.checkpoint.com/solutions?id=sk88700" rel="nofollow"&gt;Creating VLAN interfaces on a physical interface, which already has an assigned IP address&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It is &lt;STRONG&gt;mandatory &lt;/STRONG&gt;to remove an IP address from a physical interface &lt;STRONG&gt;BEFORE &lt;/STRONG&gt;creating VLAN interfaces on it and it is not supported to add an IP address to that physical interfaces &lt;STRONG&gt;AFTER&lt;/STRONG&gt; creating a VLAN interface on it.&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Aug 2018 08:41:09 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32431#M6803</guid>
      <dc:creator>Danny</dc:creator>
      <dc:date>2018-08-29T08:41:09Z</dc:date>
    </item>
    <item>
      <title>Re: Combine VLAN and physical interface, which already has an assigned IP</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32432#M6804</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, it is definitely not supported to configure an IP address natively on an interface that is to be used as a VLAN trunk. We don't block the configuration, as you have discovered here, but it is not supported.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Aug 2018 03:03:02 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/32432#M6804</guid>
      <dc:creator>Ross_Pember</dc:creator>
      <dc:date>2018-08-30T03:03:02Z</dc:date>
    </item>
    <item>
      <title>Re: Combine VLAN and physical interface, which already has an assigned IP</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/53611#M10712</link>
      <description>&lt;P&gt;I added a check for this in our &lt;A href="https://community.checkpoint.com/t5/General-Topics/Common-Check-Point-Commands-ccc/td-p/38488" target="_self"&gt;ccc script&lt;/A&gt; starting from version 4.3&lt;/P&gt;</description>
      <pubDate>Thu, 16 May 2019 14:29:45 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Combine-VLAN-and-physical-interface-which-already-has-an/m-p/53611#M10712</guid>
      <dc:creator>Danny</dc:creator>
      <dc:date>2019-05-16T14:29:45Z</dc:date>
    </item>
  </channel>
</rss>

