<?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: Data cap limits for users in specific network in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/data-cap-limits-for-users-in-specific-network/m-p/555687#M1775</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/312286"&gt;@FellowCurious&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;If you're trying to create an aggregate amount over time, you'll need to use an external script instead of relying on the firewall. Just scanning over both solutions they also don't appear to take into account long-running sessions, so you'll need a way to account for those. That could be just closing any sessions that exceed a certain duration (via a script), or some other negate for expected sessions.&lt;/P&gt;
&lt;P&gt;Essentially what you'll run into from a brief glance is that some users will have long sessions that will eventually end. They've passed enough traffic to keep it open and it's potentially been open for days if a user just locks their endpoint instead of logging off or shutting down at the end of the day. You might end up with someone closing a session that's technically passed tens or hundreds of GBs that doesn't quite line up with reality.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Just something to keep in mind that this won't be explicitly clean due to how you're pulling the data.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 29 Aug 2023 13:20:19 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2023-08-29T13:20:19Z</dc:date>
    <item>
      <title>Data cap limits for users in specific network</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/data-cap-limits-for-users-in-specific-network/m-p/555586#M1773</link>
      <description>&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;Hi, just like the title says, I'm looking to cap data usage for users in a subnet, something like this:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A class="_3t5uN8xUmg0TOwRCOGQEcU" href="https://github.com/hiep4hiep/PANW-Bandwidth-quota" target="_blank" rel="noopener nofollow ugc"&gt;https://github.com/hiep4hiep/PANW-Bandwidth-quota&lt;/A&gt;, but without having to use scripts, is there a way to do something similar inside the PA firewall?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Aug 2023 23:43:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/data-cap-limits-for-users-in-specific-network/m-p/555586#M1773</guid>
      <dc:creator>FellowCurious</dc:creator>
      <dc:date>2023-08-28T23:43:31Z</dc:date>
    </item>
    <item>
      <title>Re: Data cap limits for users in specific network</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/data-cap-limits-for-users-in-specific-network/m-p/555676#M1774</link>
      <description>&lt;P&gt;Check if this gives you ideas.&lt;/P&gt;
&lt;P&gt;Instead of QoS you can block traffic if quota is exceeded.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.youtube.com/watch?v=7fU91SZ5xDk" target="_blank"&gt;https://www.youtube.com/watch?v=7fU91SZ5xDk&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Aug 2023 12:24:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/data-cap-limits-for-users-in-specific-network/m-p/555676#M1774</guid>
      <dc:creator>Raido_Rattameister</dc:creator>
      <dc:date>2023-08-29T12:24:31Z</dc:date>
    </item>
    <item>
      <title>Re: Data cap limits for users in specific network</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/data-cap-limits-for-users-in-specific-network/m-p/555687#M1775</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/312286"&gt;@FellowCurious&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;If you're trying to create an aggregate amount over time, you'll need to use an external script instead of relying on the firewall. Just scanning over both solutions they also don't appear to take into account long-running sessions, so you'll need a way to account for those. That could be just closing any sessions that exceed a certain duration (via a script), or some other negate for expected sessions.&lt;/P&gt;
&lt;P&gt;Essentially what you'll run into from a brief glance is that some users will have long sessions that will eventually end. They've passed enough traffic to keep it open and it's potentially been open for days if a user just locks their endpoint instead of logging off or shutting down at the end of the day. You might end up with someone closing a session that's technically passed tens or hundreds of GBs that doesn't quite line up with reality.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Just something to keep in mind that this won't be explicitly clean due to how you're pulling the data.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Aug 2023 13:20:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/data-cap-limits-for-users-in-specific-network/m-p/555687#M1775</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2023-08-29T13:20:19Z</dc:date>
    </item>
    <item>
      <title>Re: Data cap limits for users in specific network</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/data-cap-limits-for-users-in-specific-network/m-p/555744#M1776</link>
      <description>&lt;P&gt;This one requires a script to remove devices afterwards, can't have that done manually daily, too much overhead.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Aug 2023 19:29:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/data-cap-limits-for-users-in-specific-network/m-p/555744#M1776</guid>
      <dc:creator>FellowCurious</dc:creator>
      <dc:date>2023-08-29T19:29:55Z</dc:date>
    </item>
  </channel>
</rss>

