Limitations of 2.0



  • i would like to bring to light some aspects which currently have noway to configure directly but can be configured using a combination of things:

    • suppose if we create limiters then there is noway to assign it to clients without assigning a rule for it and if we create rules just to assign limiter to a certain client then other rules dont apply
    • this is related to the first one, suppose if i have rules for sending http etc traffic to different queues and just to apply limiters to a single client, we create a rule for it and then that takes over and the other rules for sending traffic to different queues is never applied so basically if the first problem was solved then this would solve itself.

    there r some other limitations also but lets start with one at a time, correct me if im wrong and if there is any way to simply apply limiters without creating rules for it so atleast rules for passing appropriate traffic to queues can continue to work.



  • You can specify limiters and queues on the same rule.
    If you want more specific policy on the queues than you enforce limiters on the incoming side and enforce queues on the outgoing side.
    IE to shape a specific LAN client with a limiter to fixed bandwidth you do that on the LAN interface.
    to prioritize SSH traffic and HTTP traffic for him you apply that on the floating rules.



  • what i meant is u can only apply limiters and a single queue to a single rule so if u just want o reduce clients speed overall but want all his traffic to flow in the usual hhtp etc queues then u would have to create a new set of rules for it, a single rule can send traffic to a single queue.

    all my rules r on the floating tab and even specifying on either of the directions at least puts one side of the queues ineffective which i don't want to happen, all i want to do is simply limit client download and upload speed but in that range he can still make use of queues like other clients without limiters so at least his surfing is bursted like others due to traffic shaping in spite of he having limiters so at least all his traffic uses different speeds in the limiter range for the type of traffic he is generating rather than all his traffic with the same level of priority.

    wouldn't it be better to separate the limiter from the rules, at least it would confuse users less on the direction and the interface and would simply do the task of limiting client speed



  • No you are wrong.
    It does not make the other side useless :)

    Limiters apply before queues so, trust me, queues will still apply if you do not select any queue on the limiter rule.



  • I've queues and limiter working togheter. And it works as expected.

    Clients are limited to limiter setting.
    And overall traffic is shaped according to queues.

    Queues in floating.
    Limiter in LAN.



  • @ermal:

    No you are wrong.
    It does not make the other side useless :)

    Limiters apply before queues so, trust me, queues will still apply if you do not select any queue on the limiter rule.

    what i meant was when u have everything on the floating tab then only one rule can apply at a time so if i set a limiter then traffic from the client is always going to hit that rule and wont match the others below it for queues in both directions.



  • @casinmirad:

    I've queues and limiter working togheter. And it works as expected.

    Clients are limited to limiter setting.
    And overall traffic is shaped according to queues.

    Queues in floating.
    Limiter in LAN.

    could u provide a sample screenshot of a single queue under floating tab and the rule under lan for the limiter?



  • @ermal:

    No you are wrong.
    It does not make the other side useless :)

    Limiters apply before queues so, trust me, queues will still apply if you do not select any queue on the limiter rule.

    if what u say is true then is that the reason y any other queue rule cant be moved in position over the limiter rule under floating tab or is it  a bug?



  • @xbipin:

    could u provide a sample screenshot of a single queue under floating tab and the rule under lan for the limiter?

    In floating: queues are the same ones created by shaper wizard. Nothing changed here.

    In LAN default pass(*) rule just put your limiter(s) in In/Out setting WITHOUT anything in Ackqueue/Queue setting.
    If for any reason you populate the Ackqueue/Queue setting, all floating rules will go ineffective and only that Queue will be applied to all traffic.

    (*) If you have a MultiWAN setup, you have to put it in you LAN default pass with the loadbalancer/failover Gateway setting.


Log in to reply