Project

General

Profile

Bug #1728

Shaper wizard not defining queues properly, doesn't shape manually by floating, ip or voip assignments

Added by Tony Graziano almost 8 years ago. Updated almost 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Traffic Shaper
Target version:
-
Start date:
07/29/2011
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.0
Affected Architecture:
All

Description

When running through the wizard for shaping, the following occurs when applying the configuration:

29 08:43:38 php: : The command '/sbin/pfctl -o basic -f /tmp/rules.debug' returned exit code '1', the output was 'bandwidth for qInternet higher than interface /tmp/rules.debug:41: errors in queue definition parent qInternet not found for qACK /tmp/rules.debug:42: errors in queue definition parent qInternet not found for qVoIP /tmp/rules.debug:43: errors in queue definition pfctl: Syntax error in config file: pf rules not loaded'
Jul 29 08:43:38 php: : New alert found: There were error(s) loading the rules: bandwidth for qInternet higher than interface /tmp/rules.debug:41: errors in queue definition parent qInternet not found for qACK /tmp/rules.debug:42: errors in queue definition parent qInternet not found for qVoIP /tmp/rules.debug:43: errors in queue definition pfctl: Syntax error in config file: pf rules not loaded The line in question reads [41]: queue qInternet on le1 bandwidth 16777.216Kb cbq ( ecn ) { qACK, qVoIP }
Jul 29 08:43:38 php: : There were error(s) loading the rules: bandwidth for qInternet higher than interface /tmp/rules.debug:41: errors in queue definition parent qInternet not found for qACK /tmp/rules.debug:42: errors in queue definition parent qInternet not found for qVoIP /tmp/rules.debug:43: errors in queue definition pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [41]: queue qInternet on le1 bandwidth 16777.216Kb cbq ( ecn ) { qACK, qVoIP }

The queue order does not define all the queues properly and the calculations for bandwidth are not correctly being interpreted by the shaping (should not have to manually adjust it to %).

Additionally, the methods to define by IP address for VOIP shaping or by system type no longer work. If system type is no longer supported, shouldn't it be taken out of the wizard? If it is supported, the definitions for the protocol:port should be inserted back into the wizard inc/xml files. Floating rules always see the traffic defined as "default".

shaper-config-pfsense2.testdomain.tld.xml (2.37 KB) shaper-config-pfsense2.testdomain.tld.xml Tony Graziano, 07/29/2011 09:36 AM
ezshaper.xml (867 Bytes) ezshaper.xml Tony Graziano, 07/29/2011 11:41 AM

Associated revisions

Revision 834a3e6a (diff)
Added by Ermal Luçi almost 8 years ago

Correctly check the values for VoIP on multi_lan traffic shaper wizard. Reported-by: http://forum.pfsense.org/index.php/topic,32833.15.html. Ticket #1728

Revision b0d088eb (diff)
Added by Ermal Luçi almost 8 years ago

Correctly check the values for VoIP on multi_lan traffic shaper wizard. Reported-by: http://forum.pfsense.org/index.php/topic,32833.15.html. Ticket #1728

History

#1 Updated by Ermal Luçi almost 8 years ago

Can you provide the ezshaper from config.xml that caused this?

#2 Updated by Tony Graziano almost 8 years ago

<shaper>
<queue>
<interface>wan</interface>
<name>wan</name>
<scheduler>CBQ</scheduler>
<bandwidth>2</bandwidth>
<bandwidthtype>Mb</bandwidthtype>
<enabled>on</enabled>
<queue>
<interface>wan</interface>
<name>qInternet</name>
<bandwidth>2</bandwidth>
<bandwidthtype>Mb</bandwidthtype>
<enabled>on</enabled>
<ecn>on</ecn>
<queue>
<interface>wan</interface>
<priority>6</priority>
<name>qACK</name>
<bandwidth>16.25</bandwidth>
<bandwidthtype>%</bandwidthtype>
<enabled>on</enabled>
<ecn>on</ecn>
<borrow>on</borrow>
</queue>
<queue>
<interface>wan</interface>
<priority>3</priority>
<name>qDefault</name>
<bandwidth>8.125</bandwidth>
<bandwidthtype>%</bandwidthtype>
<enabled>on</enabled>
<default>on</default>
<ecn>on</ecn>
<borrow>on</borrow>
</queue>
<queue>
<interface>wan</interface>
<priority>7</priority>
<name>qVoIP</name>
<bandwidth>384</bandwidth>
<bandwidthtype>Kb</bandwidthtype>
<enabled>on</enabled>
<ecn>on</ecn>
<borrow>on</borrow>
</queue>
</queue>
</queue>
<queue>
<interface>lan</interface>
<name>lan</name>
<scheduler>HFSC</scheduler>
<bandwidth/>
<bandwidthtype/>
<enabled>on</enabled>
<queue>
<name>qLink</name>
<interface>lan</interface>
<qlimit>500</qlimit>
<priority>2</priority>
<bandwidth>20</bandwidth>
<bandwidthtype>%</bandwidthtype>
<enabled>on</enabled>
<default>on</default>
<ecn>on</ecn>
</queue>
<queue>
<name>qInternet</name>
<interface>lan</interface>
<bandwidth>16</bandwidth>
<bandwidthtype>Mb</bandwidthtype>
<enabled>on</enabled>
<ecn>on</ecn>
<linkshare3>16Mb</linkshare3>
<linkshare>on</linkshare>
<upperlimit3>16Mb</upperlimit3>
<upperlimit>on</upperlimit>
<queue>
<name>qACK</name>
<interface>lan</interface>
<priority>6</priority>
<bandwidth>19.962</bandwidth>
<bandwidthtype>%</bandwidthtype>
<enabled>on</enabled>
<ecn>on</ecn>
<linkshare3>19.962%</linkshare3>
<linkshare>on</linkshare>
</queue>
<queue>
<name>qVoIP</name>
<interface>lan</interface>
<priority>7</priority>
<bandwidth>32</bandwidth>
<bandwidthtype>Kb</bandwidthtype>
<enabled>on</enabled>
<ecn>on</ecn>
<realtime3>384Kb</realtime3>
<realtime>on</realtime>
</queue>
</queue>
</queue>
</shaper>

#4 Updated by Ermal Luçi almost 8 years ago

The ezshaper part not the shaper part.

#5 Updated by Tony Graziano almost 8 years ago

ezshaper part of config.xml attached.

#6 Updated by Tony Graziano almost 8 years ago

Using the build 2.0-RC3 (i386)
built on Fri Jul 29 22:08:01 EDT 2011
Still seeing the same error messages. Have seen it does not error on selecting PRIQ in the wizard.

Using (PRIQ) both the VOIP selection AND floating rules it is still not matching against the ports needed to shape VOIP.

Where is the relevant config when selecting VOIP (other than creating the queues) that defines ports for the wizard? The floating rules are generic/simple enough.

#7 Updated by Ermal Luçi almost 8 years ago

  • Status changed from New to Resolved

Also available in: Atom PDF