08-30-2011 12:10 PM - edited 03-04-2019 01:27 PM
We have a Cisco 2851 in our data center thats currently our access router, firewall and vpn endpoint.
We see a large amount of web traffic (currently about 10mbit sustained). I would like to limit each clients bandwidth either by ip address, session or connection, it doesn't matter.
Our pipe is 50mb, and id love to have each user set to a bout 200k with a 300k burst -ish.
I have looked through documentation and am coming up blank
Any help would be appreciated.
08-30-2011 01:02 PM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Per user QoS, except for a few users, is often impractical on most platforms.
For inbound traffic, you can certainly police or shape traffic, but this doesn't always reduce congestion on the link.
For outbound traffic, you can very much control traffic, but before trying a complex QoS configuration, you might try FQ for all outbound flows. This more or less provides proportional bandwidth to all the flows and tends to drop packets from the high bandwidth usage flows first.
08-30-2011 01:51 PM
Hey man, I appreciate the reply, I will have a look at the fair queue.
I was trying to prevent one client from soaking us. Where that one client can be googlebot, image scrapers and other automated scripted agents that crawl page after page of image heavy content.
I would of course prefer to not track every outbound request, but in preventing a random user from using more than X kbps, you kind of end up at the conclusion that every user must be watched.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide