On 8/7/10 6:42 AM, Mariano Absatz wrote: > Anyway, I'd like to know if what I did is somehow reasonable and if > there's also a way to limit outgoing bandwidth.
Not with simple traffic shaping. Here's the problem. Simple traffic shaping breaks the traffic into three priority classes and then uses 3 SFQ qdiscs to ensure fairness within each class. When there is outbound congestion, the high priority class gets priority over the second highest and so on. The way that Linux traffic shaping works, we would have to limit the overall traffic bandwidth *before* breaking it into classes. While that would work as far as bandwidth-limiting goes, it would break the prioritization since the three priority classes would never see any congestion (the limiting would ensure that). If we were to limit *after* breaking the traffic into classes, we would need three separate limits -- one for each class. But using complex traffic shaping, it is easy to do what you want. a) Specify the limit you want in the OUT-BANDWIDTH column for your outgoing interface. b) Define a single default class that can use all of that limit. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
