Best Queue practise!!



  • Hi Guys,

    Please let me know the best queue practice can be followed for a network with ADSL broadband connections.
    Please refer the methods that can be used to get the details of my network side.
    It will be good if you can attach an article to refer while implementing it on the real world scenario.



  • ACK prioritization is very common.

    Unless you are having a problem, forget about traffic-shaping.

    When you say "ADSL broadband connections", are saying you have a multi-WAN setup?



  • I have only 1 ADSL broadband connection.



  • "Best" is subjective, so there is no universal answer.

    If you prefer simplicity and low latency, setup a single CODELQ queue for WAN.



  • Can you please see the current queues in the picture attached is fine?




  • Here, this tutorial is a good place to start: http://www.linksysinfo.org/index.php?threads/qos-tutorial.68795/

    That is the best tutorial I have found.

    Regarding your queues, I have no idea what your intended goal is, so I cannot know whether your setup is working properly.



  • I really hope someone ports Cake. Then we can stop these kinds of discussions for the most part. Traffic shaping seems to be too hard of a topic for most people.

    Back to the topic. I see there is a sizable chunk of bandwidth going over qLink, which probably means the floating rules are wrong. It seems to be a common issue that people don't have a good catch-all for internet traffic.



  • @Harvy66:

    I really hope someone ports Cake. Then we can stop these kinds of discussions for the most part. Traffic shaping seems to be too hard of a topic for most people.

    Back to the topic. I see there is a sizable chunk of bandwidth going over qLink, which probably means the floating rules are wrong. It seems to be a common issue that people don't have a good catch-all for internet traffic.

    Not necessarily. The Queues page seems to be slightly bugged in some versions of 2.x.

    22k pps in a single direction (and the bandwidth) does seem to be rather high for an ADSL link. He'd need to refresh the page to find the correct values reflected.



  • @dreamslacker:

    @Harvy66:

    I really hope someone ports Cake. Then we can stop these kinds of discussions for the most part. Traffic shaping seems to be too hard of a topic for most people.

    Back to the topic. I see there is a sizable chunk of bandwidth going over qLink, which probably means the floating rules are wrong. It seems to be a common issue that people don't have a good catch-all for internet traffic.

    Not necessarily. The Queues page seems to be slightly bugged in some versions of 2.x.

    22k pps in a single direction (and the bandwidth) does seem to be rather high for an ADSL link. He'd need to refresh the page to find the correct values reflected.

    Good catch. Those numbers must be wrong. I assume that was what he was asking about. I missed that…  :-\

    @OP, use the pfTop GUI page to see an accurate readout of the throughput that your queues are seeing. Sadly, that page in your screen-shot commonly displays skewed/delayed/wrong values.



  • @dreamslacker:

    @Harvy66:

    I really hope someone ports Cake. Then we can stop these kinds of discussions for the most part. Traffic shaping seems to be too hard of a topic for most people.

    Back to the topic. I see there is a sizable chunk of bandwidth going over qLink, which probably means the floating rules are wrong. It seems to be a common issue that people don't have a good catch-all for internet traffic.

    Not necessarily. The Queues page seems to be slightly bugged in some versions of 2.x.

    22k pps in a single direction (and the bandwidth) does seem to be rather high for an ADSL link. He'd need to refresh the page to find the correct values reflected.

    The numbers may be wrong, but the ratios shouldn't be far off, and that's a lot of qLink traffic relative to the other queues.



  • @Harvy66:

    The numbers may be wrong, but the ratios shouldn't be far off, and that's a lot of qLink traffic relative to the other queues.

    It looks off by about 100x (assuming a 4mbps down rated DSL line), so that would be about 300Kbit/s of traffic on qLink.

    I agree that there shouldn't be any traffic on qLink by default (if he ran the shaper wizard) since there are no auto-generated rules to pipe into qLink.

    Without knowing exactly what the rule-set are, it'd be difficult to nail this down. For all we know, he's managed to get a floating rule in to pipe SQUID or local traffic down qLink (which is what I'd do but I create my entire shaper config by hand).


Log in to reply