2.3 change bandwidth per queue
-
I'm sorry, I don't maintain an index of citations for everything that I have read in my life. Just saying I read it somewhere at some point. I place no stake in its correctness at the time that I read or currently, just that I read it in an unknown context. While the information could have been false at the time that I read it, I would find it very strange that someone would be have ran a fud campaign against CBQ.
Here's a fun read about D-CBQ https://pdfs.semanticscholar.org/87a6/9a173cf9c787607511a8551a8e0331da028a.pdf and it's attempt to decouple delay and bandwidth. It seems there have been several attempts to change CBQ to decouple or reduce delay from bandwidth. https://pdfs.semanticscholar.org/1433/b2afcd8e08de52b1fba6127c89808f58b3f2.pdf
-
So back to the original question, is there a way to change the cbq shapers interface bandwidth value, and any other child bandwidth values if needed, and avoid the error; "The sum of child bandwidth is higher than parent". Or is waiting months for the next release our only option?
-
I'll try editing the config.xml.
https://forum.pfsense.org/index.php?topic=110438.0 -
So back to the original question, is there a way to change the cbq shapers interface bandwidth value, and any other child bandwidth values if needed, and avoid the error; "The sum of child bandwidth is higher than parent". Or is waiting months for the next release our only option?
The "… sum of child bandwidth..." problem is probably unrelated to the GUI problem. The "sum child" thing is caused by pf/pfctl errors being directly relayed from the underlying pf/ALTQ sub-system itself, meaning that you are making a mistake. (I experienced this error often when playing with HFSC's m1/d/m2 params in a parent<->leaf queue setup, but the error was always my own...)
The GUI problem does seem to be valid though. The edit of the config.xml seems to be most logical option... which is unfortunate.
-
Making CBQ child bandwidth % changes by config.xml will accept anything I want. Via the GUI I get errors if I change the parent bandwidth value. Currently running ver 2.3.1_1 and the GUI still doesn't show child bandwidth values in the Shaper by Interface. So apparently not fixed with the last patch.
Does anyone in an escalated position read these issues and are inclined to fix them? Because XLM shaper restores function, it seems this may entirely be a GUI issue. Since the GUI doesn't have the % field for entry the XML shows a valueless entry of <bandwidth></bandwidth>rather than say <bandwidth>50</bandwidth>.