I'm looking over this traffic shaping available in the tc* files.

I went through this when I did my own traffic shaping outside of
shorewall previously.

For the average (i.e. home, perhaps) user, I've never understood why we
use these more complicated shaping algorithms that define classes and
guaranteed minimums and maximums and so forth.

For most home, or other small use situations, isn't it easier to just
specify priorities of traffic, i.e.

Type                            Priority
VOIP                            1
Interactive (i.e. ssh)          2
All other                       3

Then have TC rules which simply give way to priority.  So if any VOIP
traffic is sitting in the queue, it jumps the queue ahead of all other
traffic.  If and when there is no VOIP in the queue, Interactive traffic
gets to jump the queue and when there is no VOIP or Interactive traffic
then all else just gets FIFO access.

And yes, VIOP traffic can completely fill the link an starve all other
traffic out, and yes, if there is no VOIP, Interactive can completely
starve all of the "All other" traffic out.  But one writes their
priority lists with this in mind.

The way I see it, if VOIP needs 100% of my bandwidth, it should get it.
No other traffic's "minimum" should encroach on VOIP's requirement.
Same can be said of Interactive and All other traffic.  In my thinking,
priority is king and nobody gets any guarantees if higher priority
traffic is at risk.

Nobody gets ceilings either.  If there is no VIOP or Interactive traffic
in the queue, All other traffic should not be limited to some limited
portion of the link, leaving the link under utilized.

I used to do this all with the FIFO classifiers rather than using the
more complicated HTB (and friends) classifiers.

So now on to the question(s):

Could the same be achieved in tcclasses (to steal the wondershaper
example from the traffic_shaping.htm page) with:

#INTERFACE      MARK    RATE       CEIL   PRIORITY    OPTIONS
ppp0            1       full       full       1       tcp-ack,tos-minimize-delay
ppp0            2       full       full       2       default
ppp0            3       full       full       2

Cheers,
b.

Attachment: signature.asc
Description: This is a digitally signed message part

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to