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

Table 32: VPLS Firewall Filter Match Conditions (continued)<br />

Match Condition<br />

prefix-list name<br />

Description<br />

(MX Series routers only) Destination or source prefixes in the specified list name. Specify the name of<br />

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

NOTE: VPLS prefix lists support only IPV4 addresses. IPV6 addresses included in a VPLS prefix list will<br />

be discarded.<br />

source-mac-address<br />

address<br />

Source MAC address of a VPLS packet.<br />

source-port number<br />

(MX Series routers only) TCP or UDP source port field. You cannot specify the port and source-port<br />

match conditions in the same term.<br />

source-port-except<br />

number<br />

(MX Series routers only) Do not match on the TCP or UDP source port field. You cannot specify the port<br />

and source-port match conditions in the same term.<br />

source-prefix-list<br />

name<br />

(MX Series routers only) Source prefixes in the specified prefix list. Specify a prefix list name defined<br />

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

NOTE: VPLS prefix lists support only IPV4 addresses. IPV6 addresses included in a VPLS prefix list will<br />

be discarded.<br />

tcp-flags flags<br />

(MX Series routers only) One or more of the following TCP flags:<br />

• Bit-name: fin, syn, rst, push, ack, urgent<br />

• Numerical value: 0x01 through 0x20<br />

• Text synonym: tcp-established, tcp-initial<br />

You can string together multiple flags using logical operators.<br />

Configuring the tcp-flags match condition requires that you configure the next-header-tcp match<br />

condition.<br />

traffic-type<br />

type-name<br />

(MX Series routers only) Traffic type. Specify broadcast, multicast, unknown-unicast, or known-unicast.<br />

traffic-type-except<br />

type-name<br />

(MX Series routers only) Do not match on the traffic type. Specify broadcast, multicast, unknown-unicast,<br />

or known-unicast.<br />

user-vlan-1p-priority<br />

number<br />

IEEE 802.1p user priority field. Specify a single value or multiple values from 0 through 7.<br />

user-vlan-1p-priority-except<br />

number<br />

Do not match on the IEEE 802.1p user priority field. Specify a single value or multiple values from 0<br />

through 7.<br />

user-vlan-id number<br />

(MX Series routers only) First VLAN identifier that is part of the payload.<br />

user-vlan-id-except<br />

number<br />

(MX Series routers only) Do not match on the first VLAN identifier that is part of the payload.<br />

vlan-ether-type value<br />

VLAN Ethernet type field of a VPLS packet.<br />

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

213

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

Saved successfully!

Ooh no, something went wrong!