Sometimes a network is not reachable via the routes configured on the default router. In this case it is necessary to add an entry to the VA's routing table so that it is able to reach a VA on another subnet that would normally be unreachable.
The VA, as supplied, does not include a method to permanently define a static route.
Log onto the VA as root and type the following command:
ip route add network/n via gateway-ip where network is the IP address of the network, n is the number of bits in the subnet mask, and gateway-ip is the address of a router that knows how to get to the remote network.
For example, ip route add 10.25.0.0/16 via 192.168.1.10 will allow you to get to the 10.25.0.0 subnet whose subnet mask is 255.255.0.0 through the router located at 192.168.1.10
Once this is working, copy the attached S40route.txt file to a convenient working location and rename it to S40route (remove the .txt) .Using Wordpad, edit the S40route file so that it contains the network, subnet mask in CIDR notation, and gateway to your network. I do not recommend that you use Notepad for this as Notepad does not undertand the Unix/Linux end-of-line character.
Copy the file S40route to the /etc/rc.d/rc3.d directory. If unsure how to do this, we suggest you download the free WinSCP utility.
Log on to the console of the Virtual Appliance using root credentials.
If you have not already done so, you can use the vi editor to edit the file to customize it for your location.
Type "chmod 777 /etc/rc.d/rc3.d/S40route" without the quotes.
Type ip route show. Take notice which routes are listed.
Reboot the virtual appliance. Again, log on and type IP route show. You should see the new route in your list of routes.
Remember that as you deploy additional VAs or upgrade to newer version, these steps must be repeated on the new VAs. If you deploy VAs by cloning, you may wish to add this file to your source or template VA.