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.

Junos 10.4 <strong>Policy</strong> <strong>Framework</strong> <strong>Configuration</strong> <strong>Guide</strong><br />

Table 24: Firewall Filter Application Points (continued)<br />

Application Point<br />

Filter Type<br />

Supported Hierarchy<br />

Comments<br />

Protocol family on<br />

interface—Filter is applied to<br />

a specific protocol family on<br />

the logical interface.<br />

Address resolution protocol<br />

(ARP) policer you define at<br />

the [edit firewall policer<br />

hierarchy level.<br />

[edit interfaces interface-name<br />

unit unit-number family inet<br />

policer arp policer-name]<br />

Only the protocol family inet is<br />

supported.<br />

Define and apply an ARP<br />

policer to override the ARP<br />

policer that is installed by<br />

default. The default ARP<br />

policer is shared by all<br />

interfaces configured on<br />

the router. An ARP policer<br />

you define can be applied<br />

to one or more specific<br />

interfaces only.<br />

ARP policers are supported<br />

on Ethernet, Gigabit<br />

Ethernet, and aggregated<br />

Ethernet interfaces, routing<br />

interfaces, and logical<br />

tunnel interfaces. For<br />

logical tunnel interfaces,<br />

only Ethernet and virtual<br />

LAN (VLAN) encapsulation<br />

is supported.<br />

Protocol family on<br />

interface—Filter is applied to<br />

a specific protocol family on<br />

the logical interface.<br />

Service filter applied as an<br />

output or input filter to a<br />

service set that you define at<br />

the [edit firewall family<br />

family-name service-filter<br />

filter-name] hierarchy level.<br />

Only the protocol families<br />

inet and inet6 are supported.<br />

• [edit interfaces interface-name<br />

unit unit-number family (inet |<br />

inet6) service input service-set<br />

service-set-name service-filter<br />

filter-name]<br />

• [edit interfaces interface-name<br />

unit unit-number family (inet |<br />

inet6) service output<br />

service-set service-set-name<br />

service-filter filter-name]<br />

Supported only on<br />

Adaptive Services (AS) and<br />

Multiservices (MS) PICs.<br />

For the service-set-name,<br />

specify a service set<br />

configured at the [edit services<br />

service-set] hierarchy level.<br />

Protocol family on<br />

interface—Filter is applied to<br />

a specific protocol family on<br />

the logical interface.<br />

Postservice filter you define<br />

at the [edit firewall family<br />

family-name service-filter<br />

filter-name] hierarchy level.<br />

Only the protocol families<br />

inet and inet6 are supported.<br />

[edit interfaces interface-name<br />

unit unit-number family (inet |<br />

inet6) service input<br />

post-service-filter filter-name]<br />

A postservice filter is<br />

applied to traffic returning<br />

to the services interface<br />

after service processing.<br />

The filter is applied only if<br />

a service set is configured<br />

and selected.<br />

Protocol family on<br />

interface—Filter is applied to<br />

a specific protocol family on<br />

the logical interface.<br />

Reverse packet forwarding<br />

(RPF) check filter you define<br />

at the [edit firewall family<br />

family-name filter filter-name]<br />

[edit interfaces interface-name<br />

unit unit-number family (inet |<br />

inet6) rpf-check fail-filter<br />

filter-name]<br />

Supported on MX Series<br />

routers only.<br />

Only the protocol families<br />

inet and inet6 are supported.<br />

188<br />

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

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

Saved successfully!

Ooh no, something went wrong!