<?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: Limiting bandwidth in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/limiting-bandwidth/m-p/911560#M959739</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, there are always people who ignore policy, but a good LART deployed early and often will quickly remedy that &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My personal favorite LART is a hard-bound copy of the policy and procedure manual, printed in 90-point type.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 03 Dec 2007 12:43:29 GMT</pubDate>
    <dc:creator>Nathan Spitzer</dc:creator>
    <dc:date>2007-12-03T12:43:29Z</dc:date>
    <item>
      <title>Limiting bandwidth</title>
      <link>https://community.cisco.com/t5/network-security/limiting-bandwidth/m-p/911555#M959732</link>
      <description>&lt;P&gt;I have an ASA5510 with a T1 connection. I have a few users who download large files with a download manager that takes up all of my bandwidth and then everyone complains the internet is slow. Is there a way on the firewall to limit each connection to a maximum bandwidth so that one user cant take all of the bandwidth?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 11:37:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/limiting-bandwidth/m-p/911555#M959732</guid>
      <dc:creator>dstjames123</dc:creator>
      <dc:date>2019-03-11T11:37:02Z</dc:date>
    </item>
    <item>
      <title>Re: Limiting bandwidth</title>
      <link>https://community.cisco.com/t5/network-security/limiting-bandwidth/m-p/911556#M959733</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You could use QoS to limit FTP downloads, however HTTP downloads are used just as often. If you need to restrict per connect bandwidth Packeteer (www.packeteer) makes some products that can do it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH and please rate.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Nov 2007 17:16:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/limiting-bandwidth/m-p/911556#M959733</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2007-11-29T17:16:43Z</dc:date>
    </item>
    <item>
      <title>Re: Limiting bandwidth</title>
      <link>https://community.cisco.com/t5/network-security/limiting-bandwidth/m-p/911557#M959734</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Like the other poster said, packeteer makes some things that will fix this. Also, forcing HTTP and FTP through a proxy server will allow you to limit throughput on a user basis. I have done this with Squid which allowed me to solve similar issues. In addition, a proxy server will lessen the load on the internet link. If most of the T1 is http, it can dramatically reduce the load.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me also comment that the root of this issue is a policy or personel issue. Sometimes the best solution to these issues is therefore not to spend a boatload of time and/or money on a technology solution but to implement a policy or procedure that state that download managers are not to be used in such a way as to degrade the T1 performance. Tell those users causing problems NOT TO DO IT AGAIN. Inform their managers they are causing service degredation and it needs to stop.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Dec 2007 02:01:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/limiting-bandwidth/m-p/911557#M959734</guid>
      <dc:creator>Nathan Spitzer</dc:creator>
      <dc:date>2007-12-02T02:01:51Z</dc:date>
    </item>
    <item>
      <title>Re: Limiting bandwidth</title>
      <link>https://community.cisco.com/t5/network-security/limiting-bandwidth/m-p/911558#M959735</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;there will always be people who will ignore&lt;/P&gt;&lt;P&gt;policy or procedure.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Instead of spending money on packeteer, which&lt;/P&gt;&lt;P&gt;is a good product by the way, the alternative&lt;/P&gt;&lt;P&gt;solution is to implement checkpoint firewall&lt;/P&gt;&lt;P&gt;solution.  Checkpoint firewalls come with QoS&lt;/P&gt;&lt;P&gt;(formerly Floodgate) integrate and it can do &lt;/P&gt;&lt;P&gt;exactly what you describe.  For a small&lt;/P&gt;&lt;P&gt;enterprise, that's something you probably want&lt;/P&gt;&lt;P&gt;instead of deploying another device on the&lt;/P&gt;&lt;P&gt;network.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Dec 2007 23:56:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/limiting-bandwidth/m-p/911558#M959735</guid>
      <dc:creator>kevin.jones1</dc:creator>
      <dc:date>2007-12-02T23:56:56Z</dc:date>
    </item>
    <item>
      <title>Re: Limiting bandwidth</title>
      <link>https://community.cisco.com/t5/network-security/limiting-bandwidth/m-p/911559#M959737</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;access-list qos_acl permit tcp any eq 20 any&lt;/P&gt;&lt;P&gt;&lt;THIS matches="" traffic=""&gt;&lt;/THIS&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map qos-class-map&lt;/P&gt;&lt;P&gt; match access-list qos_acl&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map qos&lt;/P&gt;&lt;P&gt; class qos-class-map&lt;/P&gt;&lt;P&gt;  police output 8000 2000&lt;/P&gt;&lt;P&gt;&lt;THIS limits="" their="" bandwidth="" to="" 8k=""&gt;&lt;/THIS&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service-policy qos interface inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i'm by no means a qos expert, but this seemed to work on my asa5505.&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/security/asa/asa72/configuration/guide/qos.html" target="_blank"&gt;http://www.cisco.com/en/US/docs/security/asa/asa72/configuration/guide/qos.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;you can of course configure the ACL and police rates to your own liking.  you could just limit all tcp traffic to something like 64000/user with 32000/burst as an example.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Dec 2007 05:34:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/limiting-bandwidth/m-p/911559#M959737</guid>
      <dc:creator>srue</dc:creator>
      <dc:date>2007-12-03T05:34:06Z</dc:date>
    </item>
    <item>
      <title>Re: Limiting bandwidth</title>
      <link>https://community.cisco.com/t5/network-security/limiting-bandwidth/m-p/911560#M959739</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, there are always people who ignore policy, but a good LART deployed early and often will quickly remedy that &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My personal favorite LART is a hard-bound copy of the policy and procedure manual, printed in 90-point type.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Dec 2007 12:43:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/limiting-bandwidth/m-p/911560#M959739</guid>
      <dc:creator>Nathan Spitzer</dc:creator>
      <dc:date>2007-12-03T12:43:29Z</dc:date>
    </item>
  </channel>
</rss>

