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.

Chapter 9: Firewall Filter <strong>Configuration</strong><br />

Both for filters with a single term and for filters with multiple terms, if a term does not<br />

contain a from statement, the action in the term’s then statement is performed on all<br />

packets.<br />

If a term does not contain a then statement or if you do not specify an action in the<br />

then statement, and if the packet matches the conditions in the term’s from statement,<br />

the packet is accepted.<br />

Each firewall filter has an implicit discard action at the end of the filter, which is equivalent<br />

to the following explicit filter term:<br />

term implicit-rule {<br />

then discard;<br />

}<br />

Therefore, if a packet matches none of the terms in the filter, it is discarded.<br />

Overview of Match Conditions in Firewall Filter Terms<br />

Configuring IPv4 Match Conditions<br />

In the from statement in a firewall filter term, you specify characteristics that the packet<br />

must have for the action in the subsequent then statement to be performed. The<br />

characteristics are referred to as match conditions. The packet must match all conditions<br />

in the from statement for the action to be performed, which also means that their order<br />

in the from statement is not important.<br />

Each protocol family supports a different set of match conditions, and some match<br />

conditions are supported only on certain routers. For example, a number of match<br />

conditions for VPLS traffic are supported only on the MX Series Ethernet Services Routers.<br />

Table 25 on page 197 describes the firewall filter match conditions that are supported for<br />

IPv4 traffic.<br />

To configure firewall filter match conditions for IPv4 traffic:<br />

• Include the match-conditions statement at the [edit firewall family family-name filter<br />

filter-name term term-name from]<br />

Table 25: IPv4 Firewall Filter Match Conditions<br />

Match Condition<br />

Description<br />

keyword-except<br />

Negate a match. For example, destination-port-except number.<br />

ah-spi spi-value<br />

IPsec authentication header (AH) security parameter index (SPI) value. Match on this specific SPI<br />

value.<br />

ah-spi-except<br />

spi-value<br />

IPsec AH SPI value. Do not match on this specific SPI value.<br />

destination-address<br />

address<br />

Destination prefix.<br />

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

197

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

Saved successfully!

Ooh no, something went wrong!