Routing Guide for Multiple ISP
About this Guide
This guide will walk you through the basic routing function which is available in NT Based OS and how determine the proper route to online game server.
Prerequisite
○ Two ISP with Internal IP (LAN) in the same subnet.
○ NT Based OS (Windows 2000, Windows XP, Windows Vista)
○ Static IP Address for Workstations
Two ISP with Internal IP (LAN) in the same subnet?
Subnet is an identifier of network range, common subnet used in private network 255.255.255.0 which means that you can used 254 IP addresses. I will not discuss other subnet to avoid confusion.
Network Diagram
This image is hidden for guests.
Please log in or register to see it.
How to do it:
On the diagram above ISP 1 will be used for browsing, chat and ISP 2 will be used for online games.
For workstations network configuration refer to the image below.
This image is hidden for guests.
Please log in or register to see it.
Since 192.168.0.1 and 192.168.0.2 is already used by the ISP's connection, workstation IP addresses will start at 192.168.0.3 up to 192.168.0.254. (Change X with 3 up to 254 depending on the number of units)
By default, all network traffic pass through ISP 1 (192.168.0.1).
Windows Routing:
First of all we need to identify all the IP address of online games and this is how to do it.
1. Close any other program running.
2. Run the online game and login to the game proper.
3. Switch to desktop window (Alt-TAB) or depends on the online game.
4. After managing to get into desktop without disconnecting the game go to Start > Run > cmd
5. When you are in the command line interface type "netstat"
This image is hidden for guests.
Please log in or register to see it.
6. On the example above we can see the Foreign Address 125.5.127.36, this example is running Flyff.
7. Flyff is identified running on 125.5.127.36 and 125.127.37.
8. Run the command below
This image is hidden for guests.
Please log in or register to see it.
9. The command is used for adding route, need to change only 125.5.127.0 with other identified IP. This will be done on all IP address using the procedure above. Maybe you will notice that I used 125.5.127.0 instead of 125.5.127.36. This is ideal to limit the number of routes. Using 125.5.127.0 MASK 255.255.255.0 we eliminate adding 125.5.127.36 and 125.5.127.37.
Notes:
If you have having hard time to identify the IP address, kindly post the screenshots of the netstat command.