<?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 VSX Netflow per VS in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Netflow-per-VS/m-p/124961#M18042</link>
    <description>&lt;P&gt;I just tested in lab VSX Netflow with R81 and R81.10 VSX gateway and notice there is a different behaviour between 2 versions.&lt;/P&gt;&lt;P&gt;On R81 VSX gateway, I could sent out netflow per VS with its own IP as source address (verified by wireshark on the collector).&lt;/P&gt;&lt;P&gt;On R81.10 VSX gateway, it is reverted to same behaviour as R80.40 that all netflow is sent by VS0, if VS0 does not have any route to go out, then no netflow can be received by the collector.&lt;/P&gt;&lt;P&gt;Anybody could confirm which behaviour is final? or there are specific procedure for R81.10 to make it same as R81?&lt;/P&gt;</description>
    <pubDate>Tue, 27 Jul 2021 03:21:07 GMT</pubDate>
    <dc:creator>Fung_To_Puk</dc:creator>
    <dc:date>2021-07-27T03:21:07Z</dc:date>
    <item>
      <title>VSX Netflow per VS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Netflow-per-VS/m-p/124961#M18042</link>
      <description>&lt;P&gt;I just tested in lab VSX Netflow with R81 and R81.10 VSX gateway and notice there is a different behaviour between 2 versions.&lt;/P&gt;&lt;P&gt;On R81 VSX gateway, I could sent out netflow per VS with its own IP as source address (verified by wireshark on the collector).&lt;/P&gt;&lt;P&gt;On R81.10 VSX gateway, it is reverted to same behaviour as R80.40 that all netflow is sent by VS0, if VS0 does not have any route to go out, then no netflow can be received by the collector.&lt;/P&gt;&lt;P&gt;Anybody could confirm which behaviour is final? or there are specific procedure for R81.10 to make it same as R81?&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jul 2021 03:21:07 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Netflow-per-VS/m-p/124961#M18042</guid>
      <dc:creator>Fung_To_Puk</dc:creator>
      <dc:date>2021-07-27T03:21:07Z</dc:date>
    </item>
    <item>
      <title>Re: VSX Netflow per VS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Netflow-per-VS/m-p/124977#M18043</link>
      <description>&lt;P&gt;One of two possibilities:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;R81 had the incorrect behavior&lt;/LI&gt;
&lt;LI&gt;This was "fixed" in R81 but was regressed in R81.10&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;This SK suggests the first one is probably the case:&amp;nbsp;&lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk102041" target="_blank"&gt;https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk102041&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;Regardless, I recommend a TAC case.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jul 2021 07:28:41 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Netflow-per-VS/m-p/124977#M18043</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2021-07-27T07:28:41Z</dc:date>
    </item>
    <item>
      <title>Re: VSX Netflow per VS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Netflow-per-VS/m-p/124987#M18045</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What you are seeing in R81.10 is the correct behavior. Traffic should be leaving through VS0 instead of the VS itself. This is also described in&amp;nbsp;&amp;nbsp;&lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk102041" target="_blank"&gt;https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk102041&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, in R81 there was a bug that traffic was sent per VS with its own IP as source address. This bug is already solved and will be released in a Jumbo HF version soon.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Fadi&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jul 2021 08:36:25 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Netflow-per-VS/m-p/124987#M18045</guid>
      <dc:creator>Fadi_Moussa</dc:creator>
      <dc:date>2021-07-27T08:36:25Z</dc:date>
    </item>
    <item>
      <title>Re: VSX Netflow per VS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Netflow-per-VS/m-p/124990#M18046</link>
      <description>&lt;P&gt;That's too bad.&lt;/P&gt;&lt;P&gt;Actuall,y why not let each VS sent netflow on its own? This is what most customer would expect and requested as usually each VS belong to different network which is not accessible (also not allowed) through VS0.&lt;/P&gt;&lt;P&gt;I know some may suggest adding a virtual switch then all VS and VS0 conenct to that switch which would make the netflow able to sent from VS0, but that is explicitly forbidded as each VS belong to different customer/administrator.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jul 2021 08:51:40 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Netflow-per-VS/m-p/124990#M18046</guid>
      <dc:creator>Fung_To_Puk</dc:creator>
      <dc:date>2021-07-27T08:51:40Z</dc:date>
    </item>
    <item>
      <title>Re: VSX Netflow per VS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Netflow-per-VS/m-p/124991#M18047</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I understand your concern.&lt;/P&gt;
&lt;P&gt;I will take it internally with R&amp;amp;D to see if we can develop something else for future releases.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jul 2021 09:05:20 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Netflow-per-VS/m-p/124991#M18047</guid>
      <dc:creator>Fadi_Moussa</dc:creator>
      <dc:date>2021-07-27T09:05:20Z</dc:date>
    </item>
    <item>
      <title>Re: VSX Netflow per VS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Netflow-per-VS/m-p/205767#M38835</link>
      <description>&lt;P&gt;Hi Fadi,&lt;BR /&gt;I would like to know if you have got any update or latest news on this topic.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Saravana&lt;/P&gt;</description>
      <pubDate>Mon, 12 Feb 2024 13:42:32 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Netflow-per-VS/m-p/205767#M38835</guid>
      <dc:creator>sravanan17</dc:creator>
      <dc:date>2024-02-12T13:42:32Z</dc:date>
    </item>
    <item>
      <title>Re: VSX Netflow per VS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Netflow-per-VS/m-p/205790#M38838</link>
      <description>&lt;P&gt;There are VSX changes coming with R82 but not sure about Netflow specifically.&lt;/P&gt;
&lt;P&gt;Please follow this up with your local SE to confirm and ensure it is supported by RFEs.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Feb 2024 15:53:42 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Netflow-per-VS/m-p/205790#M38838</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2024-02-12T15:53:42Z</dc:date>
    </item>
    <item>
      <title>Re: VSX Netflow per VS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Netflow-per-VS/m-p/205860#M38861</link>
      <description>&lt;P&gt;If you need a specific enhancement related to this topic, please raise an RFE through the standard channels.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Feb 2024 09:04:45 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Netflow-per-VS/m-p/205860#M38861</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2024-02-13T09:04:45Z</dc:date>
    </item>
    <item>
      <title>Re: VSX Netflow per VS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Netflow-per-VS/m-p/205862#M38862</link>
      <description>&lt;P&gt;Hi Chris,&lt;BR /&gt;Thanks for your response, noted.&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Saravana&lt;/P&gt;</description>
      <pubDate>Tue, 13 Feb 2024 09:09:14 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Netflow-per-VS/m-p/205862#M38862</guid>
      <dc:creator>sravanan17</dc:creator>
      <dc:date>2024-02-13T09:09:14Z</dc:date>
    </item>
  </channel>
</rss>

