This is too opened ended of a question. You can use Queing, some routing protocols will allow you to set the bandwidth, and policy routing in conjuction with Queing are a few ways that come to mind.
Are you trying to limit bandwidth based on an application from this IP, all traffic to/from this IP?
Actually Routing Protocols *use* the bandwith command (IGRP/EIGRP) as part of the cost algorithm. Without getting into RRR (RSVP+MPLS+IGP/EGP) you're not going to get much milage here.
As for queueing mechanism, remember queueing is (in most cases) a transmit side function, i.e. it does nothing with incoming traffic (except VOQ on high end routers to avoid HOLB). So can Queueing help us, well not really. The only traffic "rate" controls that can be applied are 'traffic shaping'. That is, a queue is used to pace out traffic to smooth out spikes.
So what can help us, CAR is definitely something to look at. It has the ability to (based on an acl (simple or extended)) rate limit incoming or outgoing traffic..
The gotcha is the potential CPU overhead of keeping state on flows in the sampling window.... (Works just like CIR in Frame Relay)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.