Connecting Cascaded Segments via 1 IP Address

WinRoute can be installed on a network that is segmented into different subnets by an additional router behind WinRoute. This is called cascading. In this type of scenario there would be at least one network segment that is in a different subnet than WinRoute, 192.168.2.2/24 in the example below. This means that the WinRoute computer is not aware to the presence of the second network. To understand what that means in terms of communication between the two networks we must consult the routing table, as WinRoute relies on this information for its routing decisions. In simple terms, the routing table, as based on the example below, would state that any traffic that is intended for 192.168.1.2-192.168.1.254 must go out the interface with 192.168.1.1. Traffic with a destination of 206.86.181.1-206.86.181.254 will be sent out the interface with 206.86.181.25. All other traffic will be sent directly to 206.86.181.57 out the interface 206.86.181.25. This means that traffic with destination 192.168.2.1-192.168.2.254 will be sent out the interface with 206.86.181.25, which is not the desired effect. Therefore, the WinRoute computer must be informed that traffic intended for 192.168.2.1-192.168.2.254 needs to go out the interface 192.168.1.1 and go to the router/gateway at address 192.168.1.100, as this is the device that communicates with the 192.168.2.x subnet. This is accomplished by adding a persistent route from the command prompt that will appear, for our example, as follows "route add -p 192.168.2.0 mask 255.255.255.0 192.168.1.100". Note that for Windows 9x systems you cannot make routes persistent, so the route will not remain after a reboot.