I am sure some of us are not satisfied with the Internet speed that we are getting from our ISP. Like in Malaysia, the fastest broadband we can have is 4Mbps download for SGD$113.21 per month but our location must be at least 5KM within the radius or else we cannot apply for it. Unlike Singapore Starhub where they are already offering 100Mbps DL and 10MBps UL for only SGD$124.12 per month. Probably we will have to wait until the year 2020 to have that kind of connection here in Malaysia…
Since having such limited broadband package, some of us might think of applying for two or even more ADSL lines and speed up the Internet. To be honest, not many people does this because it is not easy and will probably need to find a router that supports multiplexing or load balancing. Four 512Kbps lines connected directly to a computer with four network adapter does not automatically gives up 2Mbps because Windows is not capable of doing that.
However if you somehow have access to multiple different Internet connections such as network adapter connected to ISP A and wireless adapter connected to ISP B, you can bind the software to use the Internet from a specific adapter.
ForceBindIP is a freeware Windows application that will inject itself into another application and alter how certain Windows Sockets calls are made, allowing you to force the other application to use a specific network interface or IP address. This is useful if you are in an environment with multiple interfaces and your application has no such option for binding to a specific interface.
This is going to be a really good tool for my friend so I will write based on his scenario. His office has a local area network with a broadband Internet connection and a few wireless network around his office block that is not encrypted. He downloads a lot of stuff from P2P during his work hours but he would only use the wireless network to do that because he doesn’t want to slow down his office’s Internet connection.
If you have read the earlier article, you should know that when you have both wired and wireless connected, Windows places higher priority for wired connection and all the internet traffic is routed there. So when my friend wants to download from P2P using the wireless connection, he would first have to disable the network adapter or unplug the network cable. That would mean he is totally disconnected from his office network and unable to access any shared folders on the file servers. To solve his problem, he can connect both wired and wireless connection, then use ForceBindIP to route the wireless connection to his P2P application. This way he can use access his office’s network shared folders and internet connection while using his wireless from another place to download stuff. This scenario is not ethical but this is just an example on how ForceBindIP could be used.
ForceBindIP doesn’t have a user interface and the configuration is done via command line. No worries because it is not really that hard to use. First you download and install ForceBindIP. Then fire up command prompt by typing cmd in Run or Search programs and files bar. Type ipconfig, hit enter and note down the IPv4 IP address for your Wireless Network Connection and Local Area Connection. Let’s say for example:
Local Area Connection IP: 192.168.2.4
Wireless Network Connection IP: 192.168.2.5
To set Firefox to use the wireless connection, you would have to type the following command in command prompt. Make sure the opening and closing quotes are surrounded in the path for Firefox because it has blank spaces.
ForceBindIP.exe 192.168.2.5 "C:\Program Files\Mozilla Firefox\firefox.exe"
Firefox will open and it would use the Internet connection from the wireless. There is a -i switch that can be used before specifying the IP address of the adapter if the program crashes or on startup or exhibits other unexpected behaviour. Example; ForceBindIP.exe -i 192.168.2.5 C:\path. For more advanced users, instead of using IP address, ForceBindIP can also recognize adapter name or the interface’s GUID. You can find the GUID of your adapter from this registry path:
You can verify whether it is working or not by using AdapterWatch and check the Send Data and Received Data column. Other than that it also shows the name or GUID and IP address of the adapters available on your computer.
Some programs that has been tested to work with ForceBindIP are DC++, uTorrent, Quake II, Quake III, Diablo II, StarCraft, Internet Explorer, Mozilla Firefox, Google Earth, Infantry, Real Player, Unreal Tournament 2004 (requires -i), Outlook 2000 (requires -i). ForceBindIP is said to only work on Windows NT/2000/XP/2003 but I’ve tested it on Windows 7 32-bit and it worked flawlessly. Probably ForceBindIP only works with ethernet and wireless adapter because I couldn’t get it to work on dialup and 3G wireless broadband.