Oliver LEGACY ELITE 2022, Manual

Page: 94 / 410

94
CRADLEPOINT WIRELESS WAN
©2017 Cradlepoint. All Rights Reserved. | +1.855.813.3385 | cradlepoint.com 57
User Manual / IBR900/IBR950 1/5/17
To route local traffic differently than either subset, policy for the subset(s) should be configured with a
higher priority than the more general local source.
Reference
Table: Select the route table to use for routing when this policy is matched. Only user-created route tables may
be selected (Main is reserved for the Main policy).
Route Tables: Static route tables to be used in policy route lookups.
In order for route tables defined here to take effect, a corresponding
Route Policy must be created. Note that route tables defined here are
not available for use in dynamic routing protocols.
Main Route Table: A special route table that contains the main system
routes. It cannot be removed and cannot be referenced by a user-
defined policy. The Main route table is available for use in dynamic
routing protocols.
Click
Add to open the Route Table Editor. Click Add to create a new
route table or Edit to edit an existing route table.
• Destination IP/Network Address: Enter the network address in the
following forms:
•
IPv4: 1.2.3.4/32
• IPv6: 0123:4567::CDEF/128
The optional gateway must match the IP version
entered here.
• Gateway: Enter the gateway in the following
forms:
•
IPv4: 1.2.3.4/32
• IPv6: 0123:4567::CDEF/128
The form must match the ip network address.
If Gateway is blank, a device interface must be
selected. Both Gateway and Device may also be
specified.
• Device: Select the device interface. Selecting null0 will install a black hole route. If Device is blank, a
gateway must be entered. Both Gateway and Device may also be specified.
• Metric: The static route is added to the kernel with the specified Metric, in the range 1–16777215.
• Allow Network Access: Some static routes will need an IP Filter Rule added to allow packets to route
without being blocked by the firewall. Checking the box opens the firewall for all traffic to and from
the specified network. Adding custom rules to the appropriate filtering policy may be more secure than
checking this box.
ROUTE FILTERS
Common route filters may be used by any of the routing protocols. When shown in selection UI, filter
names are prepended with a label to identify the type, i.e. al:AccessListName, pl:PrefixListName, and
rm:RouteMapName. Filter names must be unique across all filters, common and protocol-specific.