D-Link DFL-260 Product Manual - Page 150
Note: The metric for default routes is 100, Route
UPC - 790069296802
View all D-Link DFL-260 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 150 highlights
4.2.2. Static Routing Chapter 4. Routing Note: The metric for default routes is 100 The metric assigned to the default routes automatically created for the physical interfaces is always 100. These automatically added routes cannot be removed manually by deleting them one at a time from a routing table. Instead, the properties of the interface must be selected and the advanced option Automatically add a route for this interface using the given network must be disabled. This will remove any route that was added automatically at startup. This option has no other purpose but to delete the automatically added routes. The all-nets Route The most important route that should be defined is the route to all-nets which usually corresponds to your ISP for public Internet access. If using the NetDefendOS setup wizard, this route is also added automatically. However, the option also exists for any physical interface to indicate that it should be used for connection to the Internet. In the Web Interface this is an advanced setting in the Ethernet interface properties called: Automatically add a default route for this interface using the given default gateway. When this option is selected, the appropriate 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 Interface core core Destination 192.168.0.10 193.55.66.77 Gateway 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. There is also a core route added for all multicast addresses: Route # 1 Interface core Destination 224.0.0.0/4 Gateway 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. Command-Line Interface 150