On Sun, 2009-12-20 at 16:47 +0000, [email protected] wrote: > I am trying limit the amount of bandwidth users consume for services > other than VOIP.
Which seems to be 90% of the requests for TC/QOS to this list.
Tom: I wonder if the TC/QOS stuff can be abstracted (read: dumbed down)
into more simple configuration for the usual cases, like VOIP (for one).
For example, it seems that given this very frequent case, VIOP, I would
think that one wants to always give highest priority to VIOP (to the
limit of 100% of the bandwidth I would think[1]) and let everything else
fight it out the remaining bandwidth (i.e. like most people without VOIP
needs do for 100% of their bandwidth). IOW, for VOIP situations, it
seems more appropriate to simply prioritize traffic rather than creating
minimum/maximum/lending/borrowing bands for it.
Given that policy routing also utilizes the TC configuration files, it
would be nice to see a simpler, more rule based policy routing
configuration as well. One that mimics a regular routing file but
allows port specification, etc.
Given that I don't do routing/qos for a living (i.e. keeping my
knowledge cache of TC in Linux fresh) and only ever visit periodically,
the tc{classes,rules} file gives me a headache every time I do have to
go back to it and realize I have forgotten what I had to re-learn the
last time I wanted to fiddle with it.
In any case, it just seems to me that probably 90% of the QOS and policy
routing use-cases out there could be satisfied with a much simpler
configuration syntax -- one that insulates the user from the terseness
of Linux TC.
Perhaps it's a case of yes, this is all a good idea -- somebody just
needs to find the time to implement it. :-)
Thots?
b.
[1] One probably doesn't really want to be using 100% of their bandwidth
for VOIP as the VOIP application's call-quality will probably suffer
from the congestion of that. But IMHO it's the VOIP application's task
(not Shorewall's) to limit use to some reasonable percentage of
available bandwidth and/or the administrator's responsibility to ensure
that the available bandwidth meets the VIOP application's configuration
and requirements with appropriate overhead to avoid call-quality
affecting congestion.
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
