16.03.2014 Views

Policy Framework Configuration Guide - Juniper Networks

Policy Framework Configuration Guide - Juniper Networks

Policy Framework Configuration Guide - Juniper Networks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Junos 10.4 <strong>Policy</strong> <strong>Framework</strong> <strong>Configuration</strong> <strong>Guide</strong><br />

• service-filter-hit (service filters and family inet or inet6 only)<br />

• syslog (family inet and inet6 only)<br />

• three-color-policer policer-name<br />

• topology topology-name (family inet and inet6 only)<br />

• traffic-class code-point (family inet6) only<br />

NOTE: You can specify only one of the following actions in a single term:<br />

accept, discard, logical-system logical-system-name, next term, reject,<br />

routing-instance routing-instance-name, or topology topology-name. You<br />

can, however, specify one of these actions with one or more nonterminating<br />

actions in a single term. For example, within a term, you can specify accept<br />

with count and syslog.<br />

Related<br />

Documentation<br />

• Overview of Match Conditions in Firewall Filter Terms on page 197<br />

• How to Specify Firewall Filter Match Conditions on page 220<br />

• Configuring Actions in Firewall Filter Terms on page 226<br />

How Firewall Filters Are Evaluated<br />

When a firewall filter consists of a single term, the filter is evaluated as follows:<br />

• If the packet matches all the conditions, the action in the then statement is taken.<br />

• If the packet matches all the conditions and if there is no action specified in the<br />

then statement, the default action accept is used.<br />

• If the packet does not match all the conditions, it is discarded.<br />

When a firewall filter consists of more than one term, the terms in the filter are evaluated<br />

sequentially:<br />

1. The packet is evaluated against the conditions in the from statement in the first term.<br />

2. If the packet matches the from statement, the action in the then statement is<br />

performed. Then:<br />

• If the next term action is not specified, the evaluation ends. Subsequent terms in<br />

the filter are not evaluated.<br />

• If the next term action is present, the evaluation continues to the next term.<br />

3. If the packet does not match the from statement in the first term, it is evaluated against<br />

the conditions in the from statement in the second term.<br />

This process continues until either the packet matches the from conditions in one of<br />

the subsequent terms or there are no more terms.<br />

196<br />

Copyright © 2010, <strong>Juniper</strong> <strong>Networks</strong>, Inc.

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

Saved successfully!

Ooh no, something went wrong!