Home > Articles > Networking > Routing & Switching

Juniper Routing Policy and Firewall Filters

Jan 24, 2003

📄 Contents

␡

Policy Terminology
Comparison of Routing Policies and Firewall Filters
Routing Policy Framework
Configuring Routing Policy
Configuring Firewall Filters
Configuring Traffic Sampling and Forwarding

⎙ Print

< Back Page 2 of 6 Next >

This chapter is from the book 

Juniper Networks Field Guide and Reference

Learn More Buy

Comparison of Routing Policies and Firewall Filters

Although routing policies and firewall filters share a common architecture, several differences exist. The fundamental difference between the policies is their purpose, and because of this, the implementation details, and, consequently, the configuration methods for each are very different. Table 8.1 compares the implementation details for routing policies and firewall filters, highlighting the similarities and differences between the two policies.

Table 8.1 Policy Implementation Details

Policy Architecture	Routing Policy Implementation	Firewall Filter Implementation
Control points	Control routing information that is placed in the routing table with an import routing policy and advertised from the routing table with an export routing policy.	Control packets that are accepted on a router interface with an input firewall filter and that are forwarded from an interface with an output firewall filter.
Configuration tasks: Define policy Apply policy	Define a policy that contains terms, match conditions, and actions. Apply one or more export or import policies to a routing protocol. You can also apply a policy expression, which uses Boolean logical operators with multiple import or export policies. You can also apply one or more export policies to the forwarding table.	Define a policy that contains terms, match conditions, and actions. Apply one input or output firewall filter to a physical interface or physical interface group to filter data packets received by or forwarded to a physical interface (on routers with an Internet Processor II ASIC only). You can also apply one input or output firewall filter to the router's loopback interface, which is the interface to the Routing Engine (on all routers). Doing this allows you to filter local packets received by or forwarded from the Routing Engine.
Terms	Configure as many terms as desired in a policy. Define a name for each term. Terms are evaluated in the order in which you specify them in a policy. Evaluation of a policy ends after a packet matches the criteria in a term and the defined or default policy action of accept or reject is taken. The route is not evaluated against subsequent terms in the same policy or subsequent policies.	Configure as many terms as desired in a firewall filter. Define a name for each term. Terms are evaluated in the order in which you specify them in a firewall filter. Evaluation of a firewall filter ends after a packet matches the criteria in a term and the defined or default action is taken. The packet is not evaluated against subsequent terms in the firewall filter.
Match conditions	Specify zero or more criteria that a route must match. You can specify criteria based on source, destination, or properties of a route. You can also specify the following match conditions, which require more configuration: Autonomous system (AS) path expression—A combination of AS numbers and regular expression operators. Community—A group of destinations that share a common property. Prefix list—A named list of prefixes. Route list—A list of destination prefixes. Subroutine—A routing policy that is called repeatedly from other routing policies.	Specify zero or more criteria that a packet must match. You must match various fields in the packet's header. The fields are grouped into the following categories: Numeric values, such as port and protocol numbers. Prefix values, such as IP source and destination prefixes. Bit-field values, that is, if particular bits in the fields are or are not set, such as IP options, TCP flags, and IP fragmentation fields. You can specify the fields using Boolean logical operators.
Actions	Specify zero or one action to take if a route matches all criteria. You can specify the following actions: Accept—Accept the route into the routing table and propagate it. After this action is taken, the evaluation of subsequent terms and policies ends. Reject—Do not accept the route into the routing table, and do not propagate it. After this action is taken, the evaluation of subsequent terms and policies ends. In addition to the actions described above, you can also specify zero or more of the following types of actions: Next term—Evaluate the next term in the routing policy. Next policy—Evaluate the next routing policy. Actions that manipulate characteristics associated with a route as the routing protocol places it in the routing table or advertises it from the routing table. Trace action, which logs route matches.	Specify zero or one action to take if a packet matches all criteria. (Juniper Networks recommends that you always explicitly configure an action.) You can specify the following actions: Accept—Accept a packet. Discard—Discard a packet silently, without sending an ICMP message. Reject—Discard a packet and send an ICMP destination unreachable message. Routing instance—Specify a routing table to which packets are forwarded. In addition to zero or one of the actions described above, you can also specify zero or more action modifiers. You can specify the following action modifiers: Count—Add packet to a count total. Forwarding class—Set the packet forwarding class to a specified value from 0 through 3. IPSec security association—Used with the source and destination address match conditions, specify an IP Security (IPSec) security association (SA) for the packet. Log—Store the header information of a packet on the Routing Engine. Loss priority—Set the packet loss priority (PLP) bit to a specified value, 0 or 1. Policer—Apply rate-limiting procedures to the traffic. Sample—Sample the packet traffic. Syslog—Log an alert for the packet.
Default policies and actions	If an incoming or outgoing route arrives and a policy related to the route is not explicitly configured, the action specified by the default policy for the associated routing protocol is taken. The following default actions exist for routing policies: If a policy does not specify a match condition, all routes evaluated against the policy match. If a match occurs but the policy does not specify an accept, reject, next term, or next policy action, one of the following occurs: The next term, if present, is evaluated. If no other terms are present, the next policy is evaluated. If no other policies are present, the action specified by the default policy is taken. If a match does not occur with a term in a policy and subsequent terms in the same policy exist, the next term is evaluated. If a match does not occur with any terms in a policy and subsequent policies exist, the next policy is evaluated. If a match does not occur by the end of a policy and no other policies exist, the accept or reject action specified by the default policy is taken.	If an incoming or outgoing packet arrives on an interface and a firewall filter is not configured for the interface, the default policy is taken (the packet is accepted). The following default actions exist for firewall filters: If a firewall filter does not specify a match condition, all packets are considered to match. If a match occurs but the firewall filter does not specify an action, the packet is accepted. If a match occurs, the defined or default action is taken, and the evaluation ends. Subsequent terms in the firewall filter are not evaluated. If a match does not occur with a term in a firewall filter and subsequent terms in the same filter exist, the next term is evaluated. If a match does not occur by the end of a firewall filter, the packet is discarded.

Policy Architecture

Routing Policy Implementation

Firewall Filter Implementation

Control points

Control routing information that is placed in the routing table with an import routing policy and advertised from the routing table with an export routing policy.

Control packets that are accepted on a router interface with an input firewall filter and that are forwarded from an interface with an output firewall filter.

Configuration tasks:

Define policy
Apply policy

Define a policy that contains terms, match conditions, and actions.

Apply one or more export or import policies to a routing protocol. You can also apply a policy expression, which uses Boolean logical operators with multiple import or export policies.

You can also apply one or more export policies to the forwarding table.

Define a policy that contains terms, match conditions, and actions.

Apply one input or output firewall filter to a physical interface or physical interface group to filter data packets received by or forwarded to a physical interface (on routers with an Internet Processor II ASIC only).

You can also apply one input or output firewall filter to the router's loopback interface, which is the interface to the Routing Engine (on all routers). Doing this allows you to filter local packets received by or forwarded from the Routing Engine.

Terms

Configure as many terms as desired in a policy. Define a name for each term.

Terms are evaluated in the order in which you specify them in a policy.

Evaluation of a policy ends after a packet matches the criteria in a term and the defined or default policy action of accept or reject is taken. The route is not evaluated against subsequent terms in the same policy or subsequent policies.

Configure as many terms as desired in a firewall filter. Define a name for each term.

Terms are evaluated in the order in which you specify them in a firewall filter.

Evaluation of a firewall filter ends after a packet matches the criteria in a term and the defined or default action is taken. The packet is not evaluated against subsequent terms in the firewall filter.

Match conditions

Specify zero or more criteria that a route must match. You can specify criteria based on source, destination, or properties of a route. You can also specify the following match conditions, which require more configuration:

Autonomous system (AS) path expression—A combination of AS numbers and regular expression operators.
Community—A group of destinations that share a common property.
Prefix list—A named list of prefixes.
Route list—A list of destination prefixes.
Subroutine—A routing policy that is called repeatedly from other routing policies.

Specify zero or more criteria that a packet must match. You must match various fields in the packet's header. The fields are grouped into the following categories:

Numeric values, such as port and protocol numbers.
Prefix values, such as IP source and destination prefixes.
Bit-field values, that is, if particular bits in the fields are or are not set, such as IP options, TCP flags, and IP fragmentation fields. You can specify the fields using Boolean logical operators.

Actions

Specify zero or one action to take if a route matches all criteria. You can specify the following actions:

Accept—Accept the route into the routing table and propagate it. After this action is taken, the evaluation of subsequent terms and policies ends.
Reject—Do not accept the route into the routing table, and do not propagate it. After this action is taken, the evaluation of subsequent terms and policies ends.

In addition to the actions described above, you can also specify zero or more of the following types of actions:

Next term—Evaluate the next term in the routing policy.
Next policy—Evaluate the next routing policy.
Actions that manipulate characteristics associated with a route as the routing protocol places it in the routing table or advertises it from the routing table.
Trace action, which logs route matches.

Specify zero or one action to take if a packet matches all criteria. (Juniper Networks recommends that you always explicitly configure an action.) You can specify the following actions:

Accept—Accept a packet.
Discard—Discard a packet silently, without sending an ICMP message.
Reject—Discard a packet and send an ICMP destination unreachable message.
Routing instance—Specify a routing table to which packets are forwarded.

In addition to zero or one of the actions described above, you can also specify zero or more action modifiers. You can specify the following action modifiers:

Count—Add packet to a count total.
Forwarding class—Set the packet forwarding class to a specified value from 0 through 3.
IPSec security association—Used with the source and destination address match conditions, specify an IP Security (IPSec) security association (SA) for the packet.
Log—Store the header information of a packet on the Routing Engine.
Loss priority—Set the packet loss priority (PLP) bit to a specified value, 0 or 1.
Policer—Apply rate-limiting procedures to the traffic.
Sample—Sample the packet traffic.
Syslog—Log an alert for the packet.

Default policies and actions

If an incoming or outgoing route arrives and a policy related to the route is not explicitly configured, the action specified by the default policy for the associated routing protocol is taken.

The following default actions exist for routing policies:

If a policy does not specify a match condition, all routes evaluated against the policy match.
If a match occurs but the policy does not specify an accept, reject, next term, or next policy action, one of the following occurs:
The next term, if present, is evaluated.
If no other terms are present, the next policy is evaluated.
If no other policies are present, the action specified by the default policy is taken.
If a match does not occur with a term in a policy and subsequent terms in the same policy exist, the next term is evaluated.
If a match does not occur with any terms in a policy and subsequent policies exist, the next policy is evaluated.
If a match does not occur by the end of a policy and no other policies exist, the accept or reject action specified by the default policy is taken.

If an incoming or outgoing packet arrives on an interface and a firewall filter is not configured for the interface, the default policy is taken (the packet is accepted).

The following default actions exist for firewall filters:

If a firewall filter does not specify a match condition, all packets are considered to match.
If a match occurs but the firewall filter does not specify an action, the packet is accepted.
If a match occurs, the defined or default action is taken, and the evaluation ends. Subsequent terms in the firewall filter are not evaluated.
If a match does not occur with a term in a firewall filter and subsequent terms in the same filter exist, the next term is evaluated.
If a match does not occur by the end of a firewall filter, the packet is discarded.

< Back Page 2 of 6 Next >

🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Privacy Notice

Overview

Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security

Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children

This site is not directed to children under the age of 13.

Marketing

Pearson may send or direct marketing communications to users, provided that

Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
Such marketing is consistent with applicable law and Pearson's legal obligations.
Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out

Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

As required by law.
With the consent of the individual (or their parent, if the individual is a minor)
In response to a subpoena, court order or legal process, to the extent permitted or required by law
To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
To investigate or address actual or suspected fraud or other illegal activities
To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links

This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020

Email Address