D-Link 800 - DFL 800 - Security Appliance, User Manual, Page: 130 / 469

There is also a core route added for all multicast addresses:
Route # Interface Destination Gateway
1 core 224.0.0.0/4
To include the core routes when you display the active routing table, you have to specify an option
to the routing command.
Example 4.2. Displaying the Core Routes
This example illustrates how to display the core routes in the active routing table.
CLI
gw-world:/> routes -all
Flags Network Iface Gateway Local IP Metric
----- ------------------ -------------- --------------- --------------- ------
127.0.0.1 core (Shared IP) 0
192.168.0.1 core (Iface IP) 0
213.124.165.181 core (Iface IP) 0
127.0.3.1 core (Iface IP) 0
127.0.4.1 core (Iface IP) 0
192.168.0.0/24 lan 0
213.124.165.0/24 wan 0
224.0.0.0/4 core (Iface IP) 0
0.0.0.0/0 wan 213.124.165.1 0
Web Interface
1. Select the Routes item in the Status dropdown menu in the menu bar
2. Check the Show all routes checkbox and click the Apply button
3. The main window will list the active routing table, including the core routes
Tip
For detailed information about the output of the CLI routes command. Please see the
CLI Reference Guide.
4.2.3. Route Failover
Overview
D-Link Firewalls are often deployed in mission-critical locations where availability and connectivity
is crucial. A corporation relying heavily on access to the Internet, for instance, could have their
operations severely disrupted if an Internet connection fails.
As a consequence, it is quite common to have backup Internet connectivity using a secondary
Internet Service Provider (ISP). The connections to the two service providers often use different
access methods to avoid a single point of failure.
To allow for a situation with, for example, multiple ISPs, NetDefendOS provides a Route Failover
capability so that should one route fail, traffic can automatically failover to another, alternate route.
NetDefendOS implements Route Failover through the use of Route Monitoring in which
NetDefendOS monitors the availability of routes and then switches traffic to an alternate route
should the primary, preferred one fail.
4.2.3. Route Failover Chapter 4. Routing
130