lately i just change from dd-wrt to Victek's Tomato firmware.
by far it's the best firmware i've used for my WRT54GL and also the best QoS in terms of granularity in terms of the configurations. i use a few features in Victek's tomato firmware for QoS.
1. i create services base on ports. set a class for each service, then set a bandwidth control for each class.
2. i create bandwidth limiter for each user in the network. this bandwidth limiter works hand in hand with the QoS that i've configured. i set a minimum guaranteed bandwidth for dl and ul for each user as well as a ceiling for dl and ul for each user. i have a scheduler running for bandwidth limiter. during peak hours, every one will be subject to their respective policy. during off peak hours, there will be no bandwidth limiter, only QoS running.
with this 2 combine, services which are important will be always ahead in the que. and with the guaranteed bw it will ensure that even users running services which are in the lowest class will have a minimum bandwidth to it (eg: torrents).
really happy that i switched over to victek's tomato. anyone with any questions or need help configuring, feel free to pm me or msn me.
Added on December 12, 2009, 4:15 pmp/s: always remember to set at least 85% and below for your maximum download and upload. otherwise it's better if you don't configure QoS at all. we wanna leave that 10-15% of buffer bandwidth so that QoS can make use of it to prioritise your traffic. QoS just won't work with ur internet link is jam packed.
a simple example would be. you have a 3 lane road. would you want cars to be travelling on all 3 lanes? if so, how would you ask the cars to rearrange their position to the front or to the back of the que?
imagine if you have a 3 lane road, and only 2 lanes are full. we still have that 1 lane extra where u can ask the car infront to move to the back, so that the prime ministers car at the back can come to the front.
just a metaphor
This post has been edited by red-queen: Dec 12 2009, 04:15 PM