Policy Framework Configuration Guide - Juniper Networks

Chapter 5: Extended Match Conditions Configuration
Table 20: Route List Match Types for a Prefix List Filter (continued)
Match Type
Match Condition
orlonger
The route shares the same most-significant bits (described by prefix-length), and prefix-length is equal
to or greater than the route’s prefix length.
Example: Configuring a Prefix List
The following example accepts and rejects traffic from sites specified using prefix lists:
[edit]
policy-options {
policy-statement prefix-list-policy {
term ok-sites {
from {
prefix-list known-ok-sites;
}
then accept;
}
term reject-bcasts {
from {
prefix-list known-dir-bcast-sites;
}
then reject;
}
}
}
[edit]
policy-options {
prefix-list known-ok-sites {
172.16.0.3;
10.10.0.0/16;
192.168.12.0/24;
}
[edit]
policy-options {
prefix-list known-dir-bcast-sites {
10.3.4.6;
10.2.0.0/16;
192.168.1.0/24;
}
}
}
Configuring Route Lists for Use in Routing Policy Match Conditions
A route list is a collection of destination prefixes. When specifying a prefix, you can specify
an exact match with a particular route or a less precise match. You can configure either
a common action that applies to the entire list or an action associated with each prefix.
Copyright © 2010, Juniper Networks, Inc.
119