3
wan
wannet
(none)
(none)
To see the active routing table enter:
gw-world:/> routes
Flags Network
Iface
Gateway
Local IP
Metric
----- ------------------ -------------- --------------- --------------- ------
192.168.0.0/24
lan
0
213.124.165.0/24
wan
0
0.0.0.0/0
wan
213.124.165.1
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
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.
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 #
Interface
Destination
Gateway
1
core
192.168.0.10
2
core
193.55.66.77
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.
4.2.2. Static Routing
Chapter 4. Routing
129
Содержание 800 - DFL 800 - Security Appliance
Страница 24: ...1 3 NetDefendOS State Engine Packet Flow Chapter 1 NetDefendOS Overview 24 ...
Страница 69: ...2 6 4 Restore to Factory Defaults Chapter 2 Management and Maintenance 69 ...
Страница 121: ...3 9 DNS Chapter 3 Fundamentals 121 ...
Страница 166: ...interfaces without an overriding IGMP Setting Default 1 000 4 6 4 Advanced IGMP Settings Chapter 4 Routing 166 ...
Страница 181: ...4 7 5 Advanced Settings for Transparent Mode Chapter 4 Routing 181 ...
Страница 192: ...5 5 IP Pools Chapter 5 DHCP Services 192 ...
Страница 282: ...6 7 Blacklisting Hosts and Networks Chapter 6 Security Mechanisms 282 ...
Страница 300: ...mechanism 7 3 7 SAT and FwdFast Rules Chapter 7 Address Translation 300 ...
Страница 301: ...7 3 7 SAT and FwdFast Rules Chapter 7 Address Translation 301 ...
Страница 303: ... Changed on a regular basis such as every three months 8 1 Overview Chapter 8 User Authentication 303 ...
Страница 318: ...8 3 Customizing HTML Pages Chapter 8 User Authentication 318 ...
Страница 322: ...ALG 9 1 5 The TLS Alternative for VPN Chapter 9 VPN 322 ...
Страница 377: ...Management Interface Failure with VPN Chapter 9 VPN 377 ...
Страница 408: ...10 4 6 SLB_SAT Rules Chapter 10 Traffic Management 408 ...
Страница 419: ...11 5 HA Advanced Settings Chapter 11 High Availability 419 ...
Страница 426: ...12 3 5 Limitations Chapter 12 ZoneDefense 426 ...
Страница 449: ...13 9 Miscellaneous Settings Chapter 13 Advanced Settings 449 ...