Forcebindip для windows 10

Bind any Windows application to a specific interface or IP address

About

ForceBindIP is a freeware Windows application that will inject itself into another application and alter how certain Windows socket calls are made, allowing you to force the other application to use a specific network interface / IP address. This is useful if you are in an environment with multiple interfaces and your application has no option to bind to a specific interface.

ForceBindIP works in two stages — the loader, ForceBindIP.exe will load the target application in a suspended state. It will then inject a DLL (BindIP.dll) which loads WS2_32.DLL into memory and intercepts the bind(), connect(), sendto(), WSAConnect() and WSASendTo() functions, redirecting them to code in the DLL which verifies which interface they will be bound to and if not the one specified, (re)binds the socket. Once the function intercepts are complete, the target application is resumed. Note that some applications with anti-debugger / injection techniques may not work correctly when an injected DLL is present; for the vast majority of applications though this technique should work fine.

As of version 1.2, all known functions in WS2_32.DLL that either explicitly or implicitly bind to an interface are intercepted. Please note however that certain programs may still end up using the default interface if they implement connections that do not use the standard winsock functions. ForceBindIP will not prevent information leaks that may occur when using applications over a VPN. For example, all host name lookups (DNS requests) will be resolved through the default gateway as these requests originate from the Microsoft DNS Client, not the program.

Usage

ForceBindIP has no user interface, it runs directly from a cmd prompt or a shortcut. To run ‘app.exe’ and force it to bind to 192.0.2.100, you would run ForceBindIP as "C:\Program Files (x86)\ForceBindIP\ForceBindIP.exe" 192.0.2.100 "c:\full\path\to\app.exe". Command line options for the target program may also appear after the path if needed.

Many applications expect to be started from their own folder. If you create a shortcut to ForceBindIP, the target program will start in ForceBindIP’s folder instead. To fix this, edit the properties of the shortcut and set the «Start in» folder to the folder containing the program .exe you’re trying to bind.

ForceBindIP can also take the GUID of an interface if for example the IP address is dynamic. To find out the GUID of your interface, run regedit and browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces. Find the interface which has the dynamic address and then copy the key name. You can then run ForceBindIP as ForceBindIP {4FA65F75-7A5F-4BCA-A3A2-59824B2F5CA0} c:\path\to\app.exe

Version 1.2 and higher provides an optional -i parameter. If the target application crashes on startup or exhibits other unexpected behaviour, try using -i, eg: ForceBindIP -i 192.0.2.100 "c:\full\path\to\app.exe". This will cause the ForceBindIP loader to wait until the application has entered its message loop before injecting the interception DLL. Any network activity the application makes prior to the DLL being loaded will not have been bound to the chosen interface however.

As of version 1.3, a 64 bit build is also available — use ForceBindIP64 with 64 bit applications. Do note that even if your OS is 64 bit, many applications are still 32 bit. If you aren’t sure, run your program normally and check the Task Manager details tab — 32 bit applications are marked with «* 32» next to their name.

Remember to either change to the working directory (cmd prompt) or set the «Start in» option of any shortcuts you make (see above). Missing quotes and wrong «Start in» folders are the most common reasons for ForceBindIP failing to work.

Some examples showing proper command line quoting:

"C:\Program Files (x86)\ForceBindIP\ForceBindIP.exe" 192.0.2.100 "C:\Users\Richard\AppData\Local\Discord\app-0.0.298\Discord.exe"

"C:\Program Files (x86)\ForceBindIP\ForceBindIP64.exe" 192.0.2.100 "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"

Google Chrome Compatibility

Using ForceBindIP with Google Chrome is a popular request. Unfortunately the newest versions of Chrome have moved networking functionality away from the main process which ForceBindIP would normally attach to, and there are strong anti-DLL-injection mechanisms. Unfortunately this means there is no way to use ForceBindIP with Chrome any longer.

Firefox Compatibility

Firefox requires the about:config?filter=browser.launcherProcess.enabled preference set to false, otherwise ForceBindIP attaches to the launcher and not the actual program.

Is ForceBindIP Safe?

Due to the way the program works (opening another program and injecting a DLL into it), it may trigger a warning in anti-virus or security products. ForceBindIP is not malicious and completely safe to use by itself, however some software might object to the presence of an injected DLL. This is common with games that use anti-cheat systems, as a DLL injected into the game could look very similar to a hack / cheat. As ForceBindIP is quite popular, it is hopefully not going to get you banned from any games, but you should still use it at your own risk on games with anti-cheat systems.

Note that ForceBindIP is only guaranteed to be safe if you download it through my website (r1ch.net). There are unfortunately fake versions of ForceBindIP floating around on the internet that include malware. Never click on any ads when searching for software as this is one of the main ways malicious versions are distributed.

Download

ForceBindIP will work on 32 and 64 bit Windows XP / Vista / 7 / 8 / 10. The Visual Studio 2015 Runtimes (x86 and x64) are required for ForceBindIP to function (the installer will let you know if they’re missing).

ForceBindIP-1.32-Setup.exe (101 KiB). Setup with uninstaller.

ForceBindIP-1.32.zip (42 KiB). Zip file for manual installation. The ForceBindIP EXE and and BindIP DLL files must be placed in the same folder.

Donate

If you find ForceBindIP useful, please support my work by making a PayPal donation. Thanks!

Version History

• v1.32 (2017-12-01)
  Updated usage instructions and improved error messages when failing to launch the target process. No functional changes.
• v1.31 (2016-08-30)
  Fixed binding to the wrong port when overriding listening sockets. The problem had appeared due to code changes needed for 64 bit support. Thanks to Marvin Wagner for the report.
• v1.3 (2015-12-29)
  Updated loader to load BindIP.dll from the installation folder.
  Updated installer to check for pre-requisites.
  No longer installs to the system folder.
• v1.2a (2009-09-17)
  Re-released with obfuscated function names to work around false positive anti virus detection.
• v1.2 (2008-06-03)
  Updated to include additional Winsock functions (WSA family).
  Added -i parameter for delayed injection.
• v1.0 (2005-10-18)

  First public version.

Необходимость привязать программу к конкретному сетевому интерфейсу (сетевой карте) возникает не слишком часто. В том случае, если компьютер одновременно подключен к двум (и более) подсетям, к примеру, к корпоративной через Ethernet кабель и к публичной сети через Wi-Fi, как заставить приложение (тот же интернет браузер) отправлять данные только через конкретный интерфейс?

Windows при маршрутизации пакетов на системах с несколькими сетевыми интерфейсами выбирает интерфейс, через который слать данные в соответствии со своей таблицей маршрутизацией. Этот механизм не позволяет заставить определенное приложение всегда работать через конкретный сетевой интерфейс. Решение о маршруте отправки пакета все равно остается за ОС.

В моем случае для решения задачи привязки программы к сетевой карте, пришлось искать стороннее решение. В своих изысканиях я остановился на утилите ForceBindIP (http://www.r1ch.net/stuff/forcebindip/). Разберёмся, как ею пользоваться (для работы требуется наличие установленной библиотеки Visual Studio 2015 Runtime).

Архив с Portable версией утилиты содержит 4 файла:

• BindIP.dll
• BindIP64.dll
• ForceBindIP.exe
• ForceBindIP64.exe

Как видно из имен файлов, одна пара файлов предназначена для x86 ОС/приложений, другая – для x64.

К примеру, Firefox на x64 битной ОС является 32-битным приложением, поэтому для его привязки к сетевой карте нужно использовать ForceBindIP.exe. В то время, как для RDP клиента (mstsc.exe) на x64 придется использовать ForceBindIP64.exe

Рассмотрим примеры использования утилиты ForceBind:

Предположим, у нас имеется 2 сетевые карты с IP адресами 10.10.1.10 и 192.168.1.12. Наша задача, настроить систему так, чтобы Firefox всегда работал через второй интерфейс.

Следующая команда запустит Firefox в режиме привязки к сетевой карте 192.168.1.12:

ForceBindIP.exe 192.168.1.12 "c:\Program Files (x86)\Mozilla Firefox\firefox.exe"

Если IP адрес интерфейса динамический, можно осуществить привязку не к IP адресу, а к GUID интерфейса (GUID всех сетевых интерфейсов можно найти в ветке HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces).

Картинка с сайта: vmblog.ru

ForceBindIP.exe {1bcd2a3b-6d77-4be1-a233-112d75fac422}"c:\Program Files (x86)\Mozilla Firefox\firefox.exe"

Для привязки mstsc.exe на x64 битной системе к интерфейсу 10.10.1.10, воспользуйтесь командой:

ForceBindIP64.exe 10.10.1.10 c:\Windows\System32\mstsc.exe

TL;DR

ForceBindIP lets you bind an application to a specific network adapter or IP address, bypassing Windows’ default network metric selection.

This guide explains how to use it on both 32-bit and 64-bit systems—with options for command line usage or with third-party GUIs.

Table of Contents

1. How Windows Chooses a Network Adapter
2. What is ForceBindIP?
3. Using ForceBindIP in 32-bit Windows
4. Using ForceBindIP in 64-bit Windows
5. ForceBindIP GUI Options
   • ForceBindIP GUI v1.5 by LibTiff
   • ForceBindIP GUI 1.0 Beta by Michael Jones
   • ForceBindIP GUI by Donlawat

How Windows Chooses a Network Adapter

There are times when you are able to have both a wired and wireless adapter connected to different networks at the same time.

A simple example is when you’re connected to your home router using the wired Ethernet adapter while an unencrypted Wi-Fi network is also available to connect using your wireless adapter.

With both wired and wireless adapters connected to different networks at the same time, Windows does not give you the advantage of binding both of the adapters to give you a faster connection speed.

Картинка с сайта: whatsoftware.com

Which network adapter is being used for Internet purposes will depend on the metric being automatically assigned to the network adapter by Windows.

Although it is possible to disable the automatic metric feature and override it with a custom value, this will only route all but not specific Internet applications to a network adapter.

The ability to configure which IP address or network adapter to use for an application is commonly found in a BitTorrent client software such as uTorrent, Vuze, Tixati and Deluge.

If your program does not support IP or network adapter binding, fortunately there is a very unique free and small program called ForceBindIP that allows you to control which network adapter or IP address to use on an application.

What is ForceBindIP

ForceBindIP is a command line application without a friendly graphical user interface that allows you to easily bind a selected application with an IP or network adapter.

In order to use ForceBindIP, you will need to know the IP address of the network adapter that you want to use to bind and the full path to the application.

You can either type “ipconfig” in command prompt to show the IP address of the network adapters or simply download AdapterWatch and use it to display the information in a GUI.

Картинка с сайта: whatsoftware.com

ForceBindIP was made during the Windows XP era when a 64-bit Windows operating system wasn’t very commonly used. Installing ForceBindIP on a 64-bit Windows operating system is a bit different compared to installing on 32-bit OS. Hence, the method to launch ForceBindIP is also not the same since the installation path has changed.

Install and Use ForceBindIP in 32-bit Windows

For 32-bit Windows, the ForceBindIP setup installer will copy 2 files, BindIP.dll and ForceBindIP.exe, to the C:\Windows\System32\ folder. You can conveniently run ForceBindIP.exe from any location in command prompt because the system32 path is a recognized environment variable. So if you want to bind an IP address, for example 192.168.2.32 to Firefox, the command would be:

ForceBindIP.exe 192.168.2.32 “C:\Program Files\Mozilla Firefox\firefox.exe”

It is important to enclose the full path of the program with a double quote because there are whitespaces in between the characters in the path.

Install and Use ForceBindIP in 64-bit Windows

Installing ForceBindIP using the setup installer on a 64-bit Windows operating system will result in the 2 files BindIP.dll and ForceBindIP.exe being copied to C:\Windows\SysWOW64\ and not the system32 folder. Unfortunately the SysWOW64 is not a recognized environment variable which means you cannot run ForceBindIP.exe from any location in command prompt.

There are 2 solutions to this problem which is either to run ForceBindIP.exe from SysWOW64 or manually copy the 2 files to the System32 folder and the latter will allow you to conveniently run ForceBindIP.exe from any location in command prompt. If you don’t want to manually copy the files to system32, the command line to bind Firefox to the IP 192.168.2.32 is as follows:

%SystemRoot%\SysWOW64\ForceBindIP.exe 192.168.2.32 “C:\Program Files\Mozilla Firefox\firefox.exe”

Download ForceBindIP

Run ForceBindIP with a GUI (Graphical User Interface)

Although ForceBindIP does not come with a GUI, the required command line parameters aren’t that complicated. However, not everyone is familiar in using command prompt and manually typing commands. Hence there are a few third party frontend GUI programs for ForceBindIP to help the less experience users in binding a specific IP address to an application.

1. ForceBindIP GUI v1.5 by LibTiff

Картинка с сайта: whatsoftware.com

This version of ForceBindIP GUI by LibTiff requires the user to manually enter the IP address that you want to bind to the application and then you are able to browse the executable file.

Clicking the Force IP button will attempt to use ForceBindIP to bind the provided IP address to the selected program. You can save the binds to an external list so that you can quickly run multiple programs with the previous binded settings.

It works even if the ForceBindIP files are installed on a 64-bit Windows operating system so there is no need to manually move the files to System32 folder. There is no -i support though.

Download ForceBindIP GUI v1.5 by LibTiff

2. ForceBindIP GUI 1.0 Beta by Michael Jones

Картинка с сайта: whatsoftware.com

ForceBindIP GUI by Michael Jones requires Java to run and it has some advantages over the GUI version by LibTiff mentioned above. First you get to select the IP address which is very useful for users who doesn’t know how to look up the internal IP address for the network adapter. Then you get to create a list of applications that automatically runs and binds to the selected IP address by clicking the “Launch Apps” button. The favorite list is automatically saved and will be restored when you re-run the program.

Download ForceBindIP GUI 1.0 Beta by Michael Jones

3. ForceBindIP GUI by Donlawat

Картинка с сайта: whatsoftware.com

ForceBindIP GUI by Donlawat does not work out of the box on 64-bit Windows operating systems because it is hard coded to detect and run ForceBindIP from the system32 folder but not in SysWOW64. So if you want to use this GUI version of ForceBindIP on a 64-bit Windows, you just need to manually copy BindIP.dll and ForceBindIP.exe to the C:\Windows\System32\ folder. Moreover, it requires .NET Framework 3.5 to run which needs to be manually installed from “Turn Windows features on or off” (OptionalFeatures.exe) in Windows 8 and 10.

However, a slight advantage of this GUI version is the ability to bind a program with an IP address using the delayed injection -i method which is not found in the first two GUI mentioned above.

Download ForceBindIP GUI by Donlawat

Final Notes:

Although the official ForceBindIP website stated that it will only run on Windows NT/2000/XP/2003, it does actually work in Vista, 7, 8, 8.1 and even the latest Windows 10 for both 32-bit and 64-bit. If the program crashes after binding an IP, you can try adding an optional -i parameter to the command line. Not all programs can be bound to a specific IP address because they do not use the standard Winsock functions. You can verify if it is working by looking at the Received and Sent Data column in AdapterWatch.

— possibility of forced binding of the program to a certain network interface;

— from the command line;

— automatic addition of DLL to the folder with «bound» programs;

— new entries in the system registry;

— Compatible with any version of Windows (regardless of capacity).