Routing Tables
NetDefendOS, as standard, has one default routing table called main. In addition to the main
table, it is possible to define one or more, additional routing tables for policy-based routing.
(these will sometimes be referred to as alternate routing tables).
Alternate routing tables contain the same information for describing routes as main, except that
there is an extra property defined for each of them which is called ordering. The ordering property
decides how route lookup is done using alternate tables in conjunction with the main table. This
is described further below.
Note: The number of tables is limited by the model
The maximum number of routing tables that can be created is limited by the type of
D-Link hardware model.
Example 4.5. Creating a Routing Table
In this example, a new routing table called MyPBRTable is created with the Ordering property set
to First.
Command-Line Interface
To see the configured routing table:
gw-world:/> add RoutingTable MyPBRTable Ordering=First
Web Interface
1. Go to: Network > Routing > Routing Tables > Add > RoutingTable
2. Now enter:
• Name: MyPBRTable
• 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 (in other words, the all-nets route), 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
Chapter 4: Routing
309