Project

General

Profile

Actions

Bug #1728

closed

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

Added by Tony Graziano over 13 years ago. Updated over 13 years ago.

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

0%

Estimated time:
Plus Target Version:
Release Notes:
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".


Files

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
Actions

Also available in: Atom PDF