-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Dispatch Proxy not working #29
Comments
Please check the SOCKS version. Go dispatch proxy only supports SOCKS v5. |
I set SOCKS as mentioned below: In Windows 10 Internet |
Unfortunately windows only support SOCKS4, not SOCKS5. However if you're using a browser like Firefox you can specify the SOCKS5 proxy in Firefox Options. For Chrome you can use an extension like Proxy SwitchyOmega. |
Thanks again extremecoders-re ! |
Important doubt : |
For this to work, SOCKS4 protocol support has to be coded before such a toggle option.
Not sure the context of this question. Bonding can be used for any network uses case including video streaming. |
Thanks for your kind help. |
windows can do socks 5: #11 (comment) |
this method works but go-dispatch-proxy uses only one interface... why?! thanks |
nevermind, this settings doesn't survive a reboot... i just created a batch to open chrome using proxy directives |
Both network adopter working.
When I call below command I get the below result.
After that I set Internet proxy on Socks localhost:8080
But I see no internet.
On same system older node-js dispatch-proxy version works great.
Please check the bug.
go-dispatch-proxy.exe 192.168.1.11 192.168.187.34
EDIT:
I get below error:
[INFO] Load balancer 1: 192.168.1.11, contention ratio: 1
[INFO] Load balancer 2: 192.168.187.34, contention ratio: 1
[INFO] Local server started on 127.0.0.1:8080
[WARN] unsupported SOCKS version
[WARN] unsupported SOCKS version
[WARN] unsupported SOCKS version
[WARN] unsupported SOCKS version
[WARN] unsupported SOCKS version
[WARN] unsupported SOCKS version
[WARN] unsupported SOCKS version
[WARN] unsupported SOCKS version
Windows 10 64bit
The text was updated successfully, but these errors were encountered: