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

Create successful ePaper yourself

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

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

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

Match Condition<br />

Description<br />

precedence<br />

ip-precedence-field<br />

IP precedence field. In place of the numeric field value, you can specify one of the following text<br />

synonyms (the field values are also listed): critical-ecp (0xa0), flash (0x60), flash-override (0x80),<br />

immediate (0x40), internet-control (0xc0), net-control (0xe0), priority (0x20), or routine (0x00). You<br />

can specify precedence in hexadecimal, binary, or decimal form.<br />

prefix-list name<br />

Destination or source prefixes in the specified list name. Specify the name of a prefix list defined at<br />

the [edit policy-options prefix-list prefix-list-name] hierarchy level.<br />

protocol number<br />

IP protocol field. In place of the numeric value, you can specify one of the following text synonyms (the<br />

field values are also listed): ah (51), egp (8), esp (50), gre (47), icmp (1), igmp (2), ipip (4), ipv6 (41),<br />

ospf (89), pim (103), rsvp (46), tcp (6), or udp (17).<br />

service-filter-hit<br />

This condition matches if the packet is received from a filter where a service-filter-hit action was<br />

applied.<br />

source-class<br />

class-name<br />

One or more source-class names.<br />

source-port number<br />

TCP or UDP source port field. You cannot specify the port and source-port match conditions in the<br />

same term.<br />

Normally, you specify this match in conjunction with the protocol match statement to determine which<br />

protocol is being used on the port. For more information, see “Overview of Protocol Match Conditions”<br />

on page 217.<br />

In place of the numeric field, you can specify one of the text synonyms listed under destination-port.<br />

source-prefix-list name<br />

Source prefixes in the specified list name. Specify the name of a prefix list defined at the [edit<br />

policy-options prefix-list prefix-list-name] hierarchy level.<br />

tcp-established<br />

TCP packets other than the first packet of a connection. This is a synonym for "(ack | rst)".<br />

This condition does not implicitly check that the protocol is TCP. To check this, specify the protocol<br />

tcp match condition.<br />

tcp-flags number<br />

TCP flags.<br />

Normally, you specify this match in conjunction with the protocol match statement to determine which<br />

protocol is being used on the port. For more details, see “Overview of Protocol Match Conditions” on<br />

page 217.<br />

In place of the numeric value, you can specify one of the following text synonyms (the field values are<br />

also listed): ack (0x10), fin (0x01), push (0x08), rst (0x04), syn (0x02), or urgent (0x20).<br />

tcp-initial<br />

First TCP packet of a connection. This is a synonym for "(syn & !ack)".<br />

This condition does not implicitly check that the protocol is TCP. To check this, specify the protocol<br />

tcp match condition.<br />

ttl number<br />

IPv4 time-to-live number. Specify a TTL value or a range of TTL values. For number, you can specify<br />

one or more values from 0 through 255. This match condition is supported only on M120, M320,<br />

MX Series, and T Series routers.<br />

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

201

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

Saved successfully!

Ooh no, something went wrong!