Project

General

Profile

Actions

Bug #1334

closed

Traffic Shaper Rules ignored

Added by Abdiel Marin over 14 years ago. Updated over 13 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
-
Target version:
-
Start date:
03/07/2011
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

I was trying to add some queue rules to the Floating Rules for traffic shaping. The system allows you to add a "PASS" rule, with a queue assigned to it. I didn't realize I had to set it to "QUEUE" the first time I configured it.

I wanted to add a schedule to the P2P Catch all, so I changed the default queue from P2P to OtherDefault, and added a rule in the floating rules with any set to protocol source/dest etc., a schedule, set to P2P queue , with the type mistakingly set to pass. Filter reload showed no errors.

After a reboot, the Traffic shaper started sending everything to the high priority queue, ignoring my configuration. Deleting the rule I added did not help. The only way I was able to go back to the original behavior was to remove the traffic shaper and any leftover floating rules, backup, then restore, then added the shaper back via the wizard.

After this, most of it worked as expected, VOIP calls were properly sent to the VOIP queue both ways in IPSEC, and for incoming calls from the VOIP carrier via WAN or OPT1. But for outgoing calls on wan it went to the default queue.

After making a few other configuration changes, it started sending my VOIP packets to the High Priority Queue again.

I also noticed that if you check "Apply the action immediately on match", the rule is ignored, and it goes to the default queue.

Actions

Also available in: Atom PDF