<?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: Untagged (native) VLAN on Trunked Interface in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Untagged-native-VLAN-on-Trunked-Interface/m-p/99594#M8680</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/29539"&gt;@stallwoodj&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;It is only possible to use untagged (ethernet frames with 1518 byte) or tagged (ethernet frames with 1522 byte). If you have problems with VLAN 1 in your network, you can only solve this on the network side. VSX can only use untagged or tagged but not both at the same time on one interface.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 20 Oct 2020 13:25:01 GMT</pubDate>
    <dc:creator>HeikoAnkenbrand</dc:creator>
    <dc:date>2020-10-20T13:25:01Z</dc:date>
    <item>
      <title>Untagged (native) VLAN on Trunked Interface</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Untagged-native-VLAN-on-Trunked-Interface/m-p/99589#M8678</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;will there ever be a facility for VSX clusters to use the untagged VLAN on interfaces dedicated to VLANs?&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a customer whose existing network is using VLAN 1, which I can't present as either untagged or tagged 1 on our multi-gig bonds.&lt;/P&gt;&lt;P&gt;I'd prefer not to have to either create a dedicated interface or put via an intermediate switch to strip the tag.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Jamie&lt;/P&gt;</description>
      <pubDate>Tue, 20 Oct 2020 12:37:19 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Untagged-native-VLAN-on-Trunked-Interface/m-p/99589#M8678</guid>
      <dc:creator>stallwoodj</dc:creator>
      <dc:date>2020-10-20T12:37:19Z</dc:date>
    </item>
    <item>
      <title>Re: Untagged (native) VLAN on Trunked Interface</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Untagged-native-VLAN-on-Trunked-Interface/m-p/99593#M8679</link>
      <description>&lt;P&gt;No, that's not possible without a dedicated interface and using VLAN1 will be always a problematic configuration.&lt;/P&gt;
&lt;P&gt;Wolfgang&lt;/P&gt;</description>
      <pubDate>Tue, 20 Oct 2020 13:20:10 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Untagged-native-VLAN-on-Trunked-Interface/m-p/99593#M8679</guid>
      <dc:creator>Wolfgang</dc:creator>
      <dc:date>2020-10-20T13:20:10Z</dc:date>
    </item>
    <item>
      <title>Re: Untagged (native) VLAN on Trunked Interface</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Untagged-native-VLAN-on-Trunked-Interface/m-p/99594#M8680</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/29539"&gt;@stallwoodj&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;It is only possible to use untagged (ethernet frames with 1518 byte) or tagged (ethernet frames with 1522 byte). If you have problems with VLAN 1 in your network, you can only solve this on the network side. VSX can only use untagged or tagged but not both at the same time on one interface.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Oct 2020 13:25:01 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Untagged-native-VLAN-on-Trunked-Interface/m-p/99594#M8680</guid>
      <dc:creator>HeikoAnkenbrand</dc:creator>
      <dc:date>2020-10-20T13:25:01Z</dc:date>
    </item>
  </channel>
</rss>

