Actions
Bug #1335
closed
Scheduled Floating Queue Rules not prioritized correctly.
Status:
Not a Bug
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
When you configure a Floating Queue rule with a schedule, it prioritizes it above all other rules when the schedule is activated. I tried to create P2P catch all that runs only during certain times of the day with a floating queue rule, placed it as the last rule, but all traffic went the P2P queue anyway when it was active. It should prioritize according to the placement when active.
Updated by Chris Buechler about 8 years ago
- Status changed from New to Not a Bug
they're prioritized the same as rules without a schedule. sounds like the order wasn't right to match, or were expecting it to reclassify already-established connections which won't happen.
Actions