18.07.2013 Views

Sidewinder G2 6.1.1 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.1 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.1 Administration Guide - Glossary of Technical ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Figure 4-2. Example <strong>of</strong><br />

active rules<br />

rule group<br />

Rule 1<br />

Rule group A<br />

Rule group B<br />

Rule 9<br />

active rules<br />

Rule 1<br />

Rule 2<br />

Rule 3<br />

Rule 4<br />

Rule 5<br />

Rule 6<br />

Rule 7<br />

Rule 8<br />

Rule 9<br />

Policy configuration basics<br />

contents <strong>of</strong><br />

rule group A<br />

contents <strong>of</strong><br />

rule group B<br />

The rules within an active group are processed in sequential order.<br />

When traffic arrives at the <strong>Sidewinder</strong> <strong>G2</strong>, it will first be processed by<br />

the active IP Filter rules. If the traffic does not match any IP Filter<br />

rules, it is forwarded on to the active proxy rules. If a rule match is<br />

found, the traffic is processed according to that rule and will not be<br />

processed by any other rules. Therefore, the order <strong>of</strong> the rules and<br />

nested rule groups within an active rule group is very important.<br />

The rule groups you specify in the Active Rules window (one for<br />

proxy and one for IP Filter) work together as follows: All traffic<br />

coming into and leaving the <strong>Sidewinder</strong> <strong>G2</strong> is compared to any active<br />

IP Filter rules that you have configured. The IP Filter rules examine<br />

packets at the IP layer. If a match is not found in the IP Filter rules,<br />

the traffic is then examined by the active proxy rules, which examine<br />

the traffic at the Application layer.<br />

Understanding Policy Configuration 4-3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!