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 33: Layer 2 Bridging Firewall Filter Match Conditions (MX Series Ethernet Services Routers<br />

Only) (continued)<br />

Match Condition<br />

traffic-type type<br />

Description<br />

Traffic type. Specify broadcast, multicast, unknown-unicast, or known-unicast.<br />

traffic-type-except type<br />

Do not match on the traffic type.<br />

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

value<br />

(Supported with bridging, VPLS, and Layer 2 CCC traffic only) IEEE 802.1p user priority field. Specify<br />

a single value or multiple values from 0 through 7.<br />

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

value<br />

(Supported with bridging, VPLS, and Layer 2 CCC traffic only) Do not match on the IEEE 802.1p user<br />

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

user-vlan-id number<br />

First VLAN identifier that is part of the payload.<br />

user-vlan-id-except<br />

number<br />

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 Layer 2 bridging or VPLS packet.<br />

vlan-ether-type-except<br />

value<br />

Do not match on the VLAN Ethernet type field of a Layer 2 bridging or VPLS packet.<br />

Related<br />

Documentation<br />

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

• Overview of Protocol Match Conditions on page 217<br />

Overview of Protocol Match Conditions<br />

In a standard firewall filter, if you specify a port match condition or a match of the ICMP<br />

type, ICMP code, or TCP flags field or the TCP establish or TCP initial match conditions,<br />

there is no implied protocol match. If you use one of the following match conditions in a<br />

term, you should also explicitly specify the protocol as a match condition in the same<br />

term:<br />

• destination-port—For IPv4, specify the match protocol tcp or protocol udp in the same<br />

term. For IPv6, specify the match next-header tcp or next-header udp in the same term.<br />

• icmp-code—For IPv4, specify the match protocol icmp in the same term. For IPv6,<br />

specify the match next-header icmp or next-header icmp6 in the same term.<br />

• icmp-type—For IPv4, specify the match protocol icmp in the same term. For IPv6, specify<br />

the match next-header icmp or next-header icmp6 in the same term<br />

• port—For IPv4, specify the match protocol tcp or protocol udp in the same term. For<br />

IPv6, specify the match next-header tcp or next-header udp in the same term.<br />

• source-port—For IPv4, specify the match protocol tcp or protocol udp in the same term.<br />

For IPv6, specify the match next-header tcp or next-header udp in the same term.<br />

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

217

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

Saved successfully!

Ooh no, something went wrong!