Bug #15291
open
Error on Traffic Shaper 0% Bandwidth
Added by Pavan K 2 months ago.
Updated about 1 month ago.
Category:
Traffic Shaper (ALTQ)
Affected Architecture:
All
Description
Link to post on pfSense Forum:
https://forum.netgate.com/topic/186137/error-on-traffic-shaper-0-bandwidth?_=1708915183963
Backstory:
recently we migrated from pfSense 2.4.x to 2.7.2 which was a direct update. Everything worked fine etc the traffic shaping feature.
Following is the error:
There were error(s) loading the rules: pfctl: the sum of the child
bandwidth (1200000000) higher than parent "root_igc4" (1000000000) -
The line in question reads [0]: @ 2024-01-31 16:45:05
Following is our configuration:
Name → FAIRQ_7
Priority→ 7
Scheduler Option → Random Early detection in and out
Bandwidth → None
Add new Queue(Default)
Enable
Name → qFAIRQ_2(Default)
Priority→ 2
Scheduler Option → Default
Bandwidth → None
Add new Queue(ACK)
Enable
Name → qACK_6
Priority→ 6
Scheduler Option → Random Early detection in and out
Bandwidth → None
According to the configuration the Bandwidth on Queue(ACK) should be 0% which was migrated off from 2.4.x but on 2.7.2 it's not letting us save 0% bandwidth for some reason.
And due to this new rules which are created are not taking effect it's only after we disable and enable the Traffic Shaper completely the rule is effective.
Hello,
You need to add a value to bandwidth in the parent interface.
I would recommend you to re create the queues.
dylan mendez wrote in #note-1:
Hello,
You need to add a value to bandwidth in the parent interface.
I would recommend you to re create the queues.
Hi,
Indeed we have given 1GBPS value to the parent bandwidth. But one of the child is without bandwidth which is according to the requirement. The error "bandwidth (1200000000) higher than parent "root_igc4" (1000000000)" is strange because i have calculated all the child queues and it only adds upto 850MBPS and parent is 1GBPS.
I will re-configure on one of the pfSense we have and update the status, but it would be better to know why it's complaining about a issue which does not exist.
Thanks
Pavan, please let us know what the result or rebuilding is since this upgrade was from 2.4 pfSense version, it might have caused an issue. If you still have issues after rebuilding it please let us know.
dylan mendez wrote in #note-3:
Pavan, please let us know what the result or rebuilding is since this upgrade was from 2.4 pfSense version, it might have caused an issue. If you still have issues after rebuilding it please let us know.
Hi, We re-built it from scratch but could not match the configuration we had previously. As of now we have restored it to previous configuration, because pfctl is failing since the recommended values are not accepted.
Also available in: Atom
PDF
Updated by 
Updated by