Important - Ensuring all-nets appears in the main table
A common mistake with Policy-based routing is the absence of the default route with a
destination interface of all-nets in the default main routing table. If there is no route
that is an exact match then the absence of a default all-nets route will mean that the
connection will be dropped.
Example 4.3. Creating a Policy-based Routing Table
In this example we create a Policy-based Routing table called TestPBRTable.
Web Interface
1.
Go to Routing > Routing Tables > Add > RoutingTable
2.
Now enter:
•
Name: TestPBRTable
•
For Ordering select one of:
•
First - the named routing table is consulted first of all. If this lookup fails, the lookup will continue in the
main routing table.
•
Default - the main routing table will be consulted first. If the only match is the default route (all-nets),
the named routing table will be consulted. If the lookup in the named routing table fails, the lookup as a
whole is considered to have failed.
•
Only - the named routing table is the only one consulted. If this lookup fails, the lookup will not
continue in the main routing table.
3.
If Remove Interface IP Routes is enabled, the default interface routes are removed, that is to say routes to
the core interface (which are routes to NetDefendOS itself).
4.
Click OK
Example 4.4. Creating the Route
After defining the routing table TestPBRTable, we add routes into the table.
Web Interface
1.
Go to Routing > Routing Tables > TestPBRTable > Add > Route
2.
Now enter:
•
Interface: The interface to be routed
•
Network: The network to route
•
Gateway: The gateway to send routed packets to
•
Local IP Address: The IP address specified here will be automatically published on the corresponding
interface. This address will also be used as the sender address in ARP queries. If no address is specified,
the firewall's interface IP address will be used.
•
Metric: Specifies the metric for this route. (Mostly used in route fail-over scenarios)
3.
Click OK
Example 4.5. Policy-based Routing Configuration
This example illustrates a multiple ISP scenario which is a common use of Policy-based Routing. The following is
4.3.5. The Ordering parameter
Chapter 4. Routing
139
Summary of Contents for 800 - DFL 800 - Security Appliance
Page 24: ...1 3 NetDefendOS State Engine Packet Flow Chapter 1 NetDefendOS Overview 24 ...
Page 69: ...2 6 4 Restore to Factory Defaults Chapter 2 Management and Maintenance 69 ...
Page 121: ...3 9 DNS Chapter 3 Fundamentals 121 ...
Page 181: ...4 7 5 Advanced Settings for Transparent Mode Chapter 4 Routing 181 ...
Page 192: ...5 5 IP Pools Chapter 5 DHCP Services 192 ...
Page 282: ...6 7 Blacklisting Hosts and Networks Chapter 6 Security Mechanisms 282 ...
Page 300: ...mechanism 7 3 7 SAT and FwdFast Rules Chapter 7 Address Translation 300 ...
Page 301: ...7 3 7 SAT and FwdFast Rules Chapter 7 Address Translation 301 ...
Page 318: ...8 3 Customizing HTML Pages Chapter 8 User Authentication 318 ...
Page 322: ...ALG 9 1 5 The TLS Alternative for VPN Chapter 9 VPN 322 ...
Page 377: ...Management Interface Failure with VPN Chapter 9 VPN 377 ...
Page 408: ...10 4 6 SLB_SAT Rules Chapter 10 Traffic Management 408 ...
Page 419: ...11 5 HA Advanced Settings Chapter 11 High Availability 419 ...
Page 426: ...12 3 5 Limitations Chapter 12 ZoneDefense 426 ...
Page 449: ...13 9 Miscellaneous Settings Chapter 13 Advanced Settings 449 ...