• I'm new to shaping but I think I have things working the way I want in 2.2. One thing I don't understand, however, is why does the wizard create the default LAN queue "qLink" with a lower priority (2) than "qOthersLow" (3)?


  • qLink is the default queue on LAN.  Everything goes there before being directed to the proper queue based on your floating rules.


  • Right, but on the WAN side the default queue "qDefault" has a higher priority (3) than "qOthersLow" (2).

    So why is "qOthersLow" lower than default on WAN, but higher than default on LAN? I would think you'd want "qOthersLow" lower than default on both LAN and WAN.


  • I just remembered that HFSC doesn't use priorities so what the GUI has is irrelevant.  The WebGUI tries to handle all shapers that it supports with the one interface, but it can be confusing.  Ignore the priority settings.  They are used by the PRIQ and CBQ shapers, not HFSC.


  • But I'm asking about PRIQ.  Hence the title of this thread.  :)


  • Correct, HFSC uses priority in a mostly moot way. It uses priority to determine packet ordering within a scheduling quantum. It really doesn't make a difference unless you care about microsecond or you like to set that stuff. 99.9% of what HFSC does is shape bandwidth in a smooth way. Sizing your real time bandwidth correctly will make more of a difference.


  • @Dave:

    But I'm asking about PRIQ.  Hence the title of this thread.  :)

    To answer the topic question, the difference in pre-made priorities could be a mistake, but it won't make any difference unless you limit your LAN link rate, and most people don't. It probably should be corrected.

    My guess.


  • But I'm asking about PRIQ.  Hence the title of this thread.  :)

    Sorry about that, chief.  Between my real job and trying to help out in a dozen or more threads, sometimes a slip of the brain occurs.