Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem setting Go dispatch proxy, #33

Open
phpll-cyber opened this issue Jul 3, 2023 · 2 comments
Open

Problem setting Go dispatch proxy, #33

phpll-cyber opened this issue Jul 3, 2023 · 2 comments

Comments

@phpll-cyber
Copy link

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?

@extremecoders-re
Copy link
Owner

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:

@phpll-cyber
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants