Simple QUeues with Parent Option

[whalen]

Could someone give me an example of how to use a simple queue w/ a parent simple queue? I understand technically how to do it, but I am not sure on a situation when it would be beneficial.

Thanks,
Ryan

[pedja]

O yes, it is very powerful option.

At first, you have a group of clients with simple queue for each of them, but you want to limit them all together to some bandwidth.

Example: each user can have 64k but you want all of them to be able to use total of 256k. Make one simple queue to shape to 256k and make it parent to each single client’s simple queue.

Also, you have simple queue shaping user to 128k but you want to additionaly limit his p2p traffic to 32k. Make simple queue that limits p2p traffic and make it children of a primary simple queue for a user.

SImpel rules can also use packet marking to shape marked connections, meaning that now you may subshape various types of connections separately.

Great option indeed.

[whalen]

@pedja

O yes, it is very powerful option.

At first, you have a group of clients with simple queue for each of them, but you want to limit them all together to some bandwidth.

Example: each user can have 64k but you want all of them to be able to use total of 256k. Make one simple queue to shape to 256k and make it parent to each single client’s simple queue.

Also, you have simple queue shaping user to 128k but you want to additionaly limit his p2p traffic to 32k. Make simple queue that limits p2p traffic and make it children of a primary simple queue for a user.

SImpel rules can also use packet marking to shape marked connections, meaning that now you may subshape various types of connections separately.

Great option indeed.

Thanks for the info.

So lets say I have 2 clients that I want to limit to 512Kbps each, but the max they both can use at once in total is 512Kbps…

How would my parent queue look? What would be the source/destinateion/target IP?

Thanks!!
Ryan

[pedja]

For some reason, there is no option to set IP list in destination field.

The easiest way is to put all users in one IP group, and use simple queue to shape whole group, and then subqueues to shape each user alone.

If you cannot do that then you could play with mangling, since simple queues may shape connectios by marked packets. At least that is what it said in manual. My attempt to use marked packets did not succeed.