Wizard sets default qLink Lower than qOthersLow



  • I'm brand new, so please be gentle…

    A couple weeks ago I replaced my dd-wrt box with pfSence. I'm on 2.3 and trying out traffic shaping. After running the wizard I noticed that on my LAN interface qLink (priority=2, queue limit=500) is the default queue. This seems strange to me since qOthersLow (priority=3, no limit) is a higher priority.

    I have a few questions...
    Did the wizard work correctly?
    If yes, then why is the default lower than low?
    What is the significance of the queue limit?
    Should I change the default, or just trust the wizard?

    Thanks
    Rich



  • @pfuser0:

    I'm brand new, so please be gentle…

    A couple weeks ago I replaced my dd-wrt box with pfSence. I'm on 2.3 and trying out traffic shaping. After running the wizard I noticed that on my LAN interface qLink (priority=2, queue limit=500) is the default queue. This seems strange to me since qOthersLow (priority=3, no limit) is a higher priority.

    I have a few questions...
    Did the wizard work correctly?
    If yes, then why is the default lower than low?
    What is the significance of the queue limit?
    Should I change the default, or just trust the wizard?

    Thanks
    Rich

    The logic behind the default setup is kinda compex, especially for noobs. Hell, it confuses me too…

    1. A default queue should almost always be a low priority. You can't prioritize the bulk of your traffic... your connection can't magically send faster.

    2. The qLink is actually intended to be a work-around so that routed LAN-to-LAN traffic does not get traffic-shaped along with WAN traffic.

    You neglected to mention what algorithm you were using. HFSC does not even use the "Priority" parameter, and plain old Priority queueing has it's own set of fundamental problems. (The exact priority is less important than who has the high priority when there is congestion[/].)



  • You neglected to mention what algorithm you were using. HFSC does not even use the "Priority" parameter, and plain old Priority queueing has it's own set of fundamental problems.

    Thanks.
    I'm using PRIQ, but I don't remember actually choosing it over HFSC. I'll try switching.
    It still looks like qLink was being used for LAN<–>WAN traffic. In my setup the only LAN<->LAN traffic hitting the router is management traffic (no DNS/DHCP).

    Anyone willing to share their insight into Queue Limit?



  • @pfuser0:

    You neglected to mention what algorithm you were using. HFSC does not even use the "Priority" parameter, and plain old Priority queueing has it's own set of fundamental problems.

    Thanks.
    I'm using PRIQ, but I don't remember actually choosing it over HFSC. I'll try switching.
    It still looks like qLink was being used for LAN<–>WAN traffic. In my setup the only LAN<->LAN traffic hitting the router is management traffic (no DNS/DHCP).

    Anyone willing to share their insight into Queue Limit?

    You are worrying about things that are currently not very useful to you. Here, read this QoS tutorial.

    The wizard is intended to be 1 setup that can work well everywherd, so everyone gets the qLink setup because it causes no harm to those who do not run multi-LAN.

    Queue limits make little difference. Most defaults are optimal. Search the forum for more info.


Log in to reply