Rule Order - Advanced Rule Processing

Introduction

The rule order field determines which rule is used when a stream matches two or more rules. This will occur when two rules have endpoints or other criteria that overlap.

For example, Rule A filters all traffic between 192.168.0.1 and 192.168.0.50 while Rule B filters the address 192.168.0.20 . Any traffic from the client at 192.168.0.20 will have to choose between Rule A and Rule B because they both filter that address.

By giving Rule B a lower rule order, the system knows to check that rule before any others. This causes the traffic to be correctly filtered through Rule B. Rule A is then ignored for that stream.

Note: The actual order that rules appear in the manager's list is not used by the processing engine because the list may be sorted by any field, according to user preferences. The rule order field is used instead to signal the desired order of processing to the engine.

Usage

Rule order can be used when building a ruleset that includes general purpose, catch-all rules that apply to the entire client base. It is then possible to add rules for specific clients with a lower rule order, ensuring they get processed before the general rule.

Rule order ranges from 1 (processed first) to 9 (processed last). The default value is 5.

Note that rule order performs a different function than a rule's priority field. It is used only for classifying traffic streams with the correct rule, whereas prioritization will process the classified streams in a certain way.

User Interface

Rule order is configured in the advanced processing tab for a rule. Select the appropriate value for the rule from 1 to 9. Most rules can be left at the default value (5).

Specifications

Name Value
Property Name Rule order
Category Advanced Rule Processing
Values 1 (first) to 9 (last)
Default 5
XML file rules.xml
XML name <ruleOrder>
XML values Integer between 1 (first) and 9 (last) inclusive.