go-dispatch-proxy icon indicating copy to clipboard operation
go-dispatch-proxy copied to clipboard

Problem setting Go dispatch proxy,

Open phpll-cyber opened this issue 2 years ago • 2 comments
trafficstars

Hello I connect to the VPN with the settings application of Windows 10 And I want to exclude one software from the VPN, for that I need to define that the Internet traffic of that software will go through Go dispatch proxy and not through the VPN

I ran the command go-dispatch-proxy.exe 100.79.1.12

And that was the result

[INFO] Load balancer 1: 100.79.1.12, contention ratio: 1
[INFO] Local server started on 127.0.0.1:8080
[DEBUG] 91.108.56.120:443 -> 100.79.1.12:0
[DEBUG] 91.108.56.120:80 -> 100.79.1.12:0
[DEBUG] 149.154.167.92:80 -> 100.79.1.12:0
[DEBUG] 149.154.167.92:443 -> 100.79.1.12:0
[DEBUG] 149.154.175.53:443 -> 100.79.1.12:0
[DEBUG] 149.154.175.53:80 -> 100.79.1.12:0
[DEBUG] 149.154.175.53:80 -> 100.79.1.12:0
[DEBUG] 149.154.175.53:443 -> 100.79.1.12:0
[DEBUG] 149.154.175.53:443 -> 100.79.1.12:0
[DEBUG] 149.154.167.92:443 -> 100.79.1.12:0
[DEBUG] 149.154.167.92:80 -> 100.79.1.12:0
[DEBUG] 149.154.175.53:80 -> 100.79.1.12:0
[DEBUG] 149.154.175.53:443 -> 100.79.1.12:0
[DEBUG] 149.154.175.53:80 -> 100.79.1.12:0
[DEBUG] 149.154.175.53:443 -> 100.79.1.12:0
[DEBUG] 149.154.175.53:80 -> 100.79.1.12:0
[DEBUG] 149.154.167.92:80 -> 100.79.1.12:0
[DEBUG] 149.154.167.92:443 -> 100.79.1.12:0
[WARN] client connection request failed
[WARN] client connection request failed
[DEBUG] 149.154.167.92:443 -> 100.79.1.12:0
[DEBUG] 149.154.167.92:80 -> 100.79.1.12:0
[DEBUG] 149.154.167.41:80 -> 100.79.1.12:0
[DEBUG] 149.154.167.41:80 -> 100.79.1.12:0
[DEBUG] 149.154.175.53:443 -> 100.79.1.12:0
[DEBUG] 149.154.175.53:80 -> 100.79.1.12:0
[WARN] unsupported address type
[WARN] unsupported address type
[WARN] unsupported address type
[DEBUG] 149.154.167.41:80 -> 100.79.1.12:0
[WARN] client connection request failed
[DEBUG] 149.154.167.92:443 -> 100.79.1.12:0
[DEBUG] 149.154.167.41:443 -> 100.79.1.12:0
[DEBUG] 149.154.167.41:443 -> 100.79.1.12:0
[DEBUG] 149.154.167.92:80 -> 100.79.1.12:0
[DEBUG] 149.154.167.41:80 -> 100.79.1.12:0
[WARN] client connection request failed
[WARN] client connection request failed
[WARN] client connection request failed
[WARN] client connection request failed
[WARN] unsupported address type
[DEBUG] 149.154.167.92:80 -> 100.79.1.12:0
[DEBUG] 149.154.167.41:80 -> 100.79.1.12:0
[DEBUG] 149.154.167.41:443 -> 100.79.1.12:0
[WARN] client connection request failed
[DEBUG] td.telegram.org:443 -> 100.79.1.12:0
[WARN] unsupported address type
[DEBUG] 149.154.167.41:443 -> 100.79.1.12:0
[DEBUG] 149.154.167.41:80 -> 100.79.1.12:0
[WARN] client connection request failed
[WARN] client connection request failed
[WARN] unsupported address type
[WARN] client connection request failed
[DEBUG] 149.154.167.41:443 -> 100.79.1.12:0
[DEBUG] 149.154.167.41:80 -> 100.79.1.12:0
[WARN] client connection request failed
[WARN] client connection request failed
[DEBUG] 149.154.167.92:443 -> 100.79.1.12:0
[WARN] client connection request failed
[WARN] client connection request failed
[WARN] client connection request failed
[WARN] unsupported address type

What could be the problem? And how can it be solved?

phpll-cyber avatar Jul 03 '23 00:07 phpll-cyber

When you turn on the VPN in Windows, by default all outgoing traffic including those from dispatch-proxy will be routed over it.

The feature you are looking for is called "Split Tunneling". After enabling split tunneling you can exclude go-dispatch-proxy.exe from the VPN. That way as the specific software uses go-dispatch-proxy its traffic will also not be routed over the VPN,

For more details check this links:

  • https://windowsreport.com/vpn-split-tunneling-windows-10/
  • https://protonvpn.com/support/protonvpn-split-tunneling/

extremecoders-re avatar Jul 03 '23 06:07 extremecoders-re

So how do you do Split Tunneling with Go dispatch proxy?

phpll-cyber avatar Jul 05 '23 10:07 phpll-cyber