Re: How can I test my tc script?

[Andrew Beverley <andy@andybev.com>]

On Sun, 2011-02-06 at 19:33 -0400, Optimum Wireless Services wrote:
> On Sun, 2011-02-06 at 17:11 +0000, Andrew Beverley wrote:
> > On Sun, 2011-02-06 at 12:28 -0400, Optimum Wireless Services wrote:
> > > On Sun, 2011-02-06 at 15:54 +0000, Andrew Beverley wrote:
> > > > > Just wondering, I have a total of 15Mbps for our total bandwidth. If I
> > > > > devide that into 512kbps then I can only have about 29 users at that
> > > > > rate.
> > > > 
> > > > You could use HTB's "ceil" parameter for each leaf class to specify the
> > > > max rate per user - that value can be anything up to and including the
> > > > maximum rate of the root qdisc. It's the total of all the "rate"
> > > > parameters of the leaf classes that should add up to the root's total.
> > > > 
> > > 
> > > If I have users on different packages then how would I accomplish that?
> > > 
> > 
> > Something like:
> > 
> > tc qdisc add dev ... root handle 1: htb
> > tc class add dev ... parent 1: classid 1:1 htb rate 2000kbit
> > ...
> > tc class add dev .... htb rate 200kbit ceil 2000kbit prio 1
> > tc class add dev .... htb rate 200kbit ceil 2000kbit prio 1
> > tc class add dev .... htb rate 200kbit ceil 1000kbit prio 2
> > tc class add dev .... htb rate 200kbit ceil 1000kbit prio 2
> > tc class add dev .... htb rate 200kbit ceil 500kbit prio 3
> > tc class add dev .... htb rate 200kbit ceil 500kbit prio 3
> > tc class add dev .... htb rate 200kbit ceil 500kbit prio 3
> > tc class add dev .... htb rate 200kbit ceil 500kbit prio 3
> > tc class add dev .... htb rate 200kbit ceil 500kbit prio 3
> > tc class add dev .... htb rate 200kbit ceil 500kbit prio 3
> > 
> > Note that all the rates add up to the root, but that each leaf class has
> > the ceil set at the top limit.
> 
> How would the filtering be done here?

In the same way as Marek's original script. Just replace his HTB leaf
class rules with ones similar to the above.

You could also use something like:

tc filter add dev eth0 parent ... protocol ip handle ... flow \
	hash keys nfct-dst divisor 1024

to balance loads between client IP address rather than connection stream
(which may help a lot if you get it correct).

Andy

> 
> Filter by type of service and attach to one of the leafs?
> 

Filter by IP hash as per Marek's email.

Andy