<?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 ASA rate limit bandwidth hogs in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-rate-limit-bandwidth-hogs/m-p/4633319#M1090997</link>
    <description>&lt;P&gt;Hey there,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am running into the problem every so often where one or two users that are bandwidth hogs create a bad service level for everyone else.&amp;nbsp; I am trying to find a way within a ASA to essentially rate limit the top talkers or bandwidth hogs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Say I have a 50 meg internet connection, it is a public space and can have anything from 5 to 200 users at any given time.&lt;/P&gt;&lt;P&gt;What seems to happen every now and then is one of the users has something doing synching or backup and it runs at 48mbps, the rest of the users get a slow speed and start to complain.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It is basically the bully in the playground is hogging all the toys...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a way for the ASA to basically track either the top talker or all users and have a police limit of 25 megs...&amp;nbsp; This way, that bully is limited to 25 megs and everone else who is playing fairly still has access to the 25 megs?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 16 Jun 2022 16:33:57 GMT</pubDate>
    <dc:creator>Alex-Pr</dc:creator>
    <dc:date>2022-06-16T16:33:57Z</dc:date>
    <item>
      <title>ASA rate limit bandwidth hogs</title>
      <link>https://community.cisco.com/t5/network-security/asa-rate-limit-bandwidth-hogs/m-p/4633319#M1090997</link>
      <description>&lt;P&gt;Hey there,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am running into the problem every so often where one or two users that are bandwidth hogs create a bad service level for everyone else.&amp;nbsp; I am trying to find a way within a ASA to essentially rate limit the top talkers or bandwidth hogs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Say I have a 50 meg internet connection, it is a public space and can have anything from 5 to 200 users at any given time.&lt;/P&gt;&lt;P&gt;What seems to happen every now and then is one of the users has something doing synching or backup and it runs at 48mbps, the rest of the users get a slow speed and start to complain.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It is basically the bully in the playground is hogging all the toys...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a way for the ASA to basically track either the top talker or all users and have a police limit of 25 megs...&amp;nbsp; This way, that bully is limited to 25 megs and everone else who is playing fairly still has access to the 25 megs?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jun 2022 16:33:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-rate-limit-bandwidth-hogs/m-p/4633319#M1090997</guid>
      <dc:creator>Alex-Pr</dc:creator>
      <dc:date>2022-06-16T16:33:57Z</dc:date>
    </item>
    <item>
      <title>Re: ASA rate limit bandwidth hogs</title>
      <link>https://community.cisco.com/t5/network-security/asa-rate-limit-bandwidth-hogs/m-p/4633350#M1091001</link>
      <description>&lt;P&gt;You can consider deploying QoS - make sure you required service get high priority compare to p2p and download.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;check example steps :&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/82310-qos-voip-vpn.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/82310-qos-voip-vpn.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jun 2022 17:21:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-rate-limit-bandwidth-hogs/m-p/4633350#M1091001</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2022-06-16T17:21:55Z</dc:date>
    </item>
    <item>
      <title>Re: ASA rate limit bandwidth hogs</title>
      <link>https://community.cisco.com/t5/network-security/asa-rate-limit-bandwidth-hogs/m-p/4633362#M1091002</link>
      <description>&lt;P&gt;Interesting idea.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do you know what are the typical protocols that will be bandwidth hogs so I can match on that? What I was hoping for is to be able to match for the IP of the top talkers.&amp;nbsp; In ASDM, you can see the top talkers.&amp;nbsp; I am curious if the QOS policy can match directly on top talkers..&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks again&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jun 2022 17:43:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-rate-limit-bandwidth-hogs/m-p/4633362#M1091002</guid>
      <dc:creator>Alex-Pr</dc:creator>
      <dc:date>2022-06-16T17:43:51Z</dc:date>
    </item>
    <item>
      <title>Re: ASA rate limit bandwidth hogs</title>
      <link>https://community.cisco.com/t5/network-security/asa-rate-limit-bandwidth-hogs/m-p/4633405#M1091004</link>
      <description>&lt;P&gt;For that one you need to Monitor or setup, a Priority for HTTP/voice/any other get higher priority&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;the QoS depends on business requirements, look at the document, start implementing step by step - and monitor to get optimal results.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jun 2022 19:07:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-rate-limit-bandwidth-hogs/m-p/4633405#M1091004</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2022-06-16T19:07:14Z</dc:date>
    </item>
  </channel>
</rss>

