this way is easier to understand, making errors less likely.
Many other products do not use the specific interface in the routing table, but specify the IP address
of the interface instead. The routing table below is from a Microsoft Windows XP workstation:
====================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 13 d4 51 8d dd ...... Intel(R) PRO/1000 CT Network
0x20004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
===================================================================
===================================================================
Active Routes:
Network Destination
Netmask
Gateway
Interface Metric
0.0.0.0
0.0.0.0
192.168.0.1 192.168.0.10
20
10.0.0.0
255.0.0.0
10.4.2.143
10.4.2.143
1
10.4.2.143
255.255.255.255
127.0.0.1
127.0.0.1
50
10.255.255.255
255.255.255.255
10.4.2.143
10.4.2.143
50
85.11.194.33
255.255.255.255
192.168.0.1 192.168.0.10
20
127.0.0.0
255.0.0.0
127.0.0.1
127.0.0.1
1
192.168.0.0
255.255.255.0 192.168.0.10 192.168.0.10
20
192.168.0.10
255.255.255.255
127.0.0.1
127.0.0.1
20
192.168.0.255
255.255.255.255 192.168.0.10 192.168.0.10
20
224.0.0.0
240.0.0.0
10.4.2.143
10.4.2.143
50
224.0.0.0
240.0.0.0 192.168.0.10 192.168.0.10
20
255.255.255.255
255.255.255.255
10.4.2.143
10.4.2.143
1
255.255.255.255
255.255.255.255 192.168.0.10 192.168.0.10
1
Default Gateway:
192.168.0.1
===================================================================
Persistent Routes:
None
The corresponding routing table in NetDefendOS will be similar to the following:
Flags Network
Iface
Gateway
Local IP
Metric
----- ------------------ -------- -------------- --------- ------
192.168.0.0/24
lan
20
10.0.0.0/8
wan
1
0.0.0.0/0
wan
192.168.0.1
20
NetDefendOS Route Definition Advantages
The NetDefendOS method of defining routes makes the reading and understanding of routing
information easier.
A further advantage with the NetDefendOS approach is that the administrator can directly specify a
gateway for a particular route and the following is true:
•
A separate route does not need to be defined that includes the gateway IP address.
•
It does not matter even if there is a separate route which includes the gateway IP address and
that routes traffic to a different interface.
Composite Subnets can be Specified
Another advantage with the NetDefendOS approach to route definition is that it allows the
administrator to specify routes for destinations that are not aligned with traditional subnet masks.
4.2.2. Static Routing
Chapter 4. Routing
173
Summary of Contents for NetDefend DFL-1660
Page 28: ...1 3 NetDefendOS State Engine Packet Flow Chapter 1 NetDefendOS Overview 28 ...
Page 88: ...2 6 3 Restore to Factory Defaults Chapter 2 Management and Maintenance 88 ...
Page 166: ...3 10 DNS Chapter 3 Fundamentals 166 ...
Page 254: ...4 7 5 Advanced Settings for Transparent Mode Chapter 4 Routing 254 ...
Page 268: ...5 4 IP Pools Chapter 5 DHCP Services 268 ...
Page 368: ...6 7 Blacklisting Hosts and Networks Chapter 6 Security Mechanisms 368 ...
Page 390: ...7 4 7 SAT and FwdFast Rules Chapter 7 Address Translation 390 ...
Page 414: ...8 3 Customizing Authentication HTML Pages Chapter 8 User Authentication 414 ...
Page 490: ...9 8 6 Specific Symptoms Chapter 9 VPN 490 ...
Page 528: ...10 4 6 Setting Up SLB_SAT Rules Chapter 10 Traffic Management 528 ...
Page 544: ...11 7 HA Advanced Settings Chapter 11 High Availability 544 ...
Page 551: ...12 3 5 Limitations Chapter 12 ZoneDefense 551 ...
Page 574: ...Default 512 13 9 Miscellaneous Settings Chapter 13 Advanced Settings 574 ...
Page 575: ...13 9 Miscellaneous Settings Chapter 13 Advanced Settings 575 ...