====================================================================
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.
For example, it is perfectly legal to define one route for the destination IP address range 192.168.0.5
to 192.168.0.17 and another route for IP addresses 192.168.0.18 to 192.168.0.254. This is a feature
that makes NetDefendOS highly suitable for routing in highly complex network topologies.
4.2.2. Static Routing
Chapter 4. Routing
153
Summary of Contents for DFL-1600 - Security Appliance
Page 27: ...1 3 NetDefendOS State Engine Packet Flow Chapter 1 NetDefendOS Overview 27 ...
Page 79: ...2 7 3 Restore to Factory Defaults Chapter 2 Management and Maintenance 79 ...
Page 146: ...3 9 DNS Chapter 3 Fundamentals 146 ...
Page 227: ...4 7 5 Advanced Settings for Transparent Mode Chapter 4 Routing 227 ...
Page 241: ...5 4 IP Pools Chapter 5 DHCP Services 241 ...
Page 339: ...6 7 Blacklisting Hosts and Networks Chapter 6 Security Mechanisms 339 ...
Page 360: ...7 4 7 SAT and FwdFast Rules Chapter 7 Address Translation 360 ...
Page 382: ...8 3 Customizing HTML Pages Chapter 8 User Authentication 382 ...
Page 386: ... The TLS ALG 9 1 5 The TLS Alternative for VPN Chapter 9 VPN 386 ...
Page 439: ...Figure 9 3 PPTP Client Usage 9 5 4 PPTP L2TP Clients Chapter 9 VPN 439 ...
Page 450: ...9 7 6 Specific Symptoms Chapter 9 VPN 450 ...
Page 488: ...10 4 6 Setting Up SLB_SAT Rules Chapter 10 Traffic Management 488 ...
Page 503: ...11 6 HA Advanced Settings Chapter 11 High Availability 503 ...
Page 510: ...12 3 5 Limitations Chapter 12 ZoneDefense 510 ...
Page 533: ...13 9 Miscellaneous Settings Chapter 13 Advanced Settings 533 ...