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 />

from {<br />

match-conditions;<br />

}<br />

then {<br />

action;<br />

action-modifiers;<br />

}<br />

}<br />

}<br />

}<br />

To configure an IPv4 firewall filter, you can configure the filter at the [edit firewall]<br />

hierarchy level without including the family inet statement. The [edit firewall] and [edit<br />

firewall filter family inet] hierarchies are equivalent. The family family-name statement<br />

is required only to specify a protocol family other than IPv4.<br />

NOTE: For stateless firewall filtering, you must allow the output tunnel traffic<br />

through the firewall filter applied to input traffic on the interface that is the<br />

next-hop interface towards the tunnel destination. The firewall filter affects<br />

only the packets exiting the router by way of the tunnel.<br />

Configuring Standard Firewall Filters<br />

When you configure a standard firewall filter, you must configure the following<br />

components:<br />

• Protocol family for which you want to filter traffic.<br />

• Filter name.<br />

• At least one term, with a unique name for each term. A term is used to define match<br />

conditions that specify the fields or values that a packet must contain and actions to<br />

perform on traffic that matches the specified conditions.<br />

• One or more match conditions for each term.<br />

• Action for each term (recommended, because otherwise, packets are automatically<br />

accepted if they meet the configured match conditions).<br />

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

193

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

Saved successfully!

Ooh no, something went wrong!