D-Link NetDefend DFL-210 User Manual page 129
Network security firewall
Hide thumbs
Also See for NetDefend DFL-210:
- User manual (495 pages) ,
- Log reference manual (476 pages) ,
- Cli reference manual (213 pages)
Table of Contents
Advertisement
4.2.2. Static Routing
3
wan
To see the active routing table enter:
gw-world:/> routes
Flags Network
----- ------------------ -------------- --------------- --------------- ------
192.168.0.0/24
213.124.165.0/24
0.0.0.0/0
Web Interface
To see the configured routing table:
1.
Go to Routing > Routing Tables
2.
Select and right-click the main routing table in the grid
The main window will list the configured routes
To see the active routing table in the Web Interface, select the Routes item in the Status dropdown menu in the
menu bar - the main window will list the active routing table
Initial Static Routes
When the D-Link Firewall is configured for the first time, the routing table will have one route
defined for each interface. The routes will have default IP addresses which must be changed to the
appropriate IP address ranges for traffic to flow.
The most important route that must be defined is the route to all-nets which should correspond with
the ISP and public Internet access. If using the NetDefendOS setup wizard, this route is added
automatically.
The option exists on any interface to indicate that it is the interface for connection to the Internet.
When this option is selected the all-nets route is automatically added to the main routing table for
the interface.
Core Routes
NetDefendOS automatically populates the active routing table with Core Routes. These routes are
present for the system to understand where to route traffic that is destined for the system itself.
There is one route added for each interface in the system. In other words, two interfaces named lan
and wan, and with IP addresses 192.168.0.10 and 193.55.66.77, respectively, will result in the
following routes:
Route #
1
2
When the system receives an IP packet whose destination address is one of the interface IPs, the
packet will be routed to the core interface. In other words, it is processed by NetDefendOS itself.
wannet
(none)
Iface
lan
wan
wan
Tip
Notice that in the CLI example above, it was necessary to first select the name of a
specific routing table with the cc command (change category or change context)
before manipulating individual routes. This is necessary for any category that could
contain more than one named group of objects.
Interface
core
core
(none)
Gateway
Local IP
213.124.165.1
Destination
192.168.0.10
193.55.66.77
129
Chapter 4. Routing
Metric
0
0
0
Gateway
- Quick Links:
- The Cli
Hide quick links:
Advertisement
Table of Contents
Troubleshooting
