Conflict with ForceBindIP

I’m using a program called forcebindip to route my traffic to different network interfaces. I’m finding that I can’t use the internet without disabling the Avast web shield.

I don’t want to disable the web shield, but I have to browse with forcebindip. How can I work around this?

I don’t know how this program forcebindip works, if it uses a proxy port. Then you need to add that port to the avastUI, Settings, Troubleshooting, Redirect Settings, HTTP Ports and uncheck the Ignore local communication, see image, click to expand.

However, given its name forcebindip I rather think it won’t be that simple.

forcebindip I believe alters how Windows Socket calls are made.

Is there any other way to work around this block?

I don’t know enough to even attempt an answer really. But that would a) depend on the program which you binding ? and b) the IP address you are binding it too ?

Having read this, http://www.r1ch.net/stuff/forcebindip/ I’m none the wiser as to what it is attempting to do. I haven’t a clue what the 1.2.3.4. bind is in the examples.

Usage

ForceBindIP has no graphical interface. You must configure it like a command-line application. To run ‘app.exe’ and force it to bind to 1.2.3.4, you would run ForceBindIP as follows:

ForceBindIP 1.2.3.4 c:\full\path\to\app.exe

Note that the full path is required; if the path contains spaces, it must be quoted. 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 follows:

ForceBindIP {4FA65F75-7A5F-4BCA-A3A2-59824B2F5CA0} c:\path\to\app.exe

Command line options for the target program may also appear after the path to the executable if needed.

Version 1.2 also provides an optional -i parameter. If you find your chosen application crashes on startup or exhibits other unexpected behaviour, try using -i, eg:

ForceBindIP -i 1.2.3.4 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. Note however that any calls that the application makes to Winsock prior to the DLL being loaded will not have been bound to the chosen interface.

I’m binding 192.168.0.103 ← my wireless adapter ipv4 address to chrome.exe.

1.2.3.4 is a representative of a network adapter’s ip address.

Well that is a local IP address, so I don’t know if removing the Ignore local communication option, without adding any redirect port (in my first post) and see if that works.

Presumable chrome would still be using port 80, etc. for its http connection, etc.

It’s not a local IP address. Trust me, I’m computer literate. My local IP address is 192.168.0.1.

I’ve tried all combinations in the redirect settings panels and nothing has worked so far. Is this hopeless?

But isn’t that one of a range of local network IP addresses.

If you have tried the ignore local communication, I guess that it isn’t possible to coordinate both forms of redirection.

I don’t know if using the -i switch to delay the loader might have any positive impact.

ForceBindIP -i 1.2.3.4 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. Note however that any calls that the application makes to Winsock prior to the DLL being loaded will not have been bound to the chosen interface.

That’s me for the night, almost 4am here.

@ fsxfreak,

You may want to edit your post to remove your local IP address.

Have you tried creating a “rule” in your firewall to see if this helps?

I don’t see the local IP as a threat, Local IPs can’t be targeted by external attack as that isn’t seen from external locations. Otherwise everyone would be at risk of attack as the most common local IP is 192.168.0.1 your router IP.

They have to know your ISP assigned IP address and this isn’t it.

I already tried the -i switch, a day before I posted my problem on here.

Yeah, I spent a day troubleshooting by myself. I’m not an idiot.

Looks like there isn’t a fix for this yet, move along googlers.

No one said you were an idiot, it was a suggestion like the others as you hadn’t mentioned what you had tried.