<?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: VSNext Bond in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSNext-Bond/m-p/256104#M50164</link>
    <description>&lt;P&gt;You can share trunks in VSNext same as legacy VSX, discussed here:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.checkpoint.com/t5/Security-Gateways/VLAN-trunk-in-vsnext/m-p/231565" target="_blank"&gt;https://community.checkpoint.com/t5/Security-Gateways/VLAN-trunk-in-vsnext/m-p/231565&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 28 Aug 2025 06:30:04 GMT</pubDate>
    <dc:creator>emmap</dc:creator>
    <dc:date>2025-08-28T06:30:04Z</dc:date>
    <item>
      <title>VSNext Bond</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSNext-Bond/m-p/256092#M50162</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm trying to be ahead future problems, and I was learning VSnext, I'm kind of confident with VSX so I'd love to learn more about this new step on VSX technology. One thing that bring my attention is, I wasn't able to see if it's possible to share interfaces between multiple VGW. I haven't install one yet, but looking the many resources, there's one where I can see for example, first vsw is created for mgmt with ID 500, and eth2 was assigned, so others VSs cannot access this interface anymore.&lt;/P&gt;&lt;P&gt;With that las behavior came to my mind the scenario where I have a bond3, eth1 and eth3 bonded for example, if I create a VGW using bond3 (trunk), can I create another VGW that also uses same bond3? Actual VSX (legacy haha) allows to use same bond by different VSs just without repeating vlan. That's possible in VSnext??&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;David.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Aug 2025 01:09:21 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSNext-Bond/m-p/256092#M50162</guid>
      <dc:creator>Oscar_David_Gom</dc:creator>
      <dc:date>2025-08-28T01:09:21Z</dc:date>
    </item>
    <item>
      <title>Re: VSNext Bond</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSNext-Bond/m-p/256104#M50164</link>
      <description>&lt;P&gt;You can share trunks in VSNext same as legacy VSX, discussed here:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.checkpoint.com/t5/Security-Gateways/VLAN-trunk-in-vsnext/m-p/231565" target="_blank"&gt;https://community.checkpoint.com/t5/Security-Gateways/VLAN-trunk-in-vsnext/m-p/231565&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Aug 2025 06:30:04 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSNext-Bond/m-p/256104#M50164</guid>
      <dc:creator>emmap</dc:creator>
      <dc:date>2025-08-28T06:30:04Z</dc:date>
    </item>
  </channel>
</rss>

