I believe you can do it if you know what the destination IP address is of your gaming connections. You don't need two NICs, and you don't need a dual-WAN router. Here's how to do it.
1. Connect the LAN ports of the two routers together with a hub or switch, and connect your computer.
2. Configure your routers' LAN ports on different subnets. Be sure to disable LAN DHCP in both routers. For instance:
Cable LAN: 192.168.0.1
DSL LAN: 192.168.1.1
3. Set up a static IP on your NIC, and then add an alternate connection.
Static IP: 192.168.0.100, Gateway: 192.168.0.1
Alternate connection: 192.168.1.100, Gateway: 192.168.1.1
Notice I made the static IP on the Cable modem's subnet. This is because connections will use this as a default.
4. Set up network routing table entries for your gaming destinations. To do this, find the IP address of your gaming destination, substitute a zero for the last of the four "dotted" numbers (the last octet), and enter this command in a command window. The "xxx" represents the actual network numbers in your gaming destination address:
route add xxx.xxx.xxx.0 mask 255.255.255.0 192.168.1.1
This creates a "subnet" route so that if the destination is anything on that subnet, it will send it to the specified gateway (192.168.1.1) which is your DSL.
This way, connections for any subnet you enter with the "route add..." command will get sent over the DSL, while everything else will go over the Cable modem. You may need to put these "route add..." commands in your autoexec.bat file so they will install on the next reboot.
If you're worried about network collisions (which I don't think you will have to worry about), you can do this with two NICs and wire each NIC directly to its router. Just be sure you know which NIC is which and assign the proper subnet number which matches the router it's attached to.
It's possible you may have trouble with the default routing to the Cable modem. If you do, execute a "route print" and post the results here.
http://www.techsupportforum.com/forums/f31/manage-two-internet-connections-same-pc-101350.html
0 Comments