README
¶
Go dispatch proxy
A SOCKS5 load balancing proxy to combine multiple internet connections into one. Works on Windows and Linux. Reported to work on macOS. Written in pure Go with no additional dependencies.
Rationale
The idea for this project came from dispatch-proxy which is written in NodeJS. NodeJS is not entirely hard disk friendly considering the multitude of files it creates even for very simple programs. I needed something which was light & portable, preferably a single binary without polluting the entire drive.
Installation
No installation required. Grab the latest binary for your platform from the CI server or from releases and start speeding up your internet connection!
https://ci.appveyor.com/project/extremecoders-re/go-dispatch-proxy/build/artifacts
Usage
The example below are shown on Windows. The steps are similar for other platforms.
The primary purpose of the tool is to combine multiple internet connections into one. For this we need to know the IP addresses of the interface we wish to combine. You can obtain the IP addresses using the ipconfig (ifconfig on linux) command. Alternatively run go-dispatch-proxy -list.
D:\>go-dispatch-proxy.exe -list
--- Listing the available adresses for dispatching
[+] Mobile Broadband Connection , IPv4:10.81.201.18
[+] Local Area Connection, IPv4:192.168.1.2
Start go-dispatch-proxy specifying the IP addresses of the load balancers obtained in the previous step. Optionally, along with the IP address you may also provide the contention ratio(after by the @ symbol). If no contention ratio is specified, it's assumed as 1.
Example 1
SOCKS proxy running on localhost at default port. Contention ratio is specified.
D:\>go-dispatch-proxy.exe 10.81.201.18@3 192.168.1.2@2
[INFO] Load balancer 1: 10.81.201.18, contention ratio: 3
[INFO] Load balancer 2: 192.168.1.2, contention ratio: 2
[INFO] SOCKS server started at 127.0.0.1:8080
Example 2
SOCKS proxy running on a different interface at a custom port. Contention ratio is not specified.
D:\>go-dispatch-proxy.exe -lhost 192.168.1.2 -lport 5566 10.81.177.215 192.168.1.100
[INFO] Load balancer 1: 10.81.177.215, contention ratio: 1
[INFO] Load balancer 2: 192.168.1.100, contention ratio: 1
[INFO] SOCKS server started at 192.168.1.2:5566
Out of 5 consecutive connections, the first 3 are routed to 10.81.201.18 and the remaining 2 to 192.168.1.2. The SOCKS server is started by default on 127.0.0.1:8080. It can be changed using the -lhost and lport directive.
Now change the proxy settings of your browser, download manager etc to point to the above address (eg 127.0.0.1:8080). Be sure to add this as a SOCKSv5 proxy and NOT as a HTTP/S proxy.
Compiling (For Development)
Ensure that Go is installed and available on the system path.
$ git clone https://github.com/extremecoders-re/go-dispatch-proxy.git
$ cd go-dispatch-proxy
# Compile for Windows x86
$ GOOS=windows GOARCH=386 go build
# Compile for Windows x64
$ GOOS=windows GOARCH=amd64 go build
# Compile for Linux x86
$ GOOS=linux GOARCH=386 go build
# Compile for Linux x64
$ GOOS=linux GOARCH=amd64 go build
# Compile for macos x86
$ GOOS=darwin GOARCH=386 go build
# Compile for macos x64
$ GOOS=darwin GOARCH=amd64 go build
No Linux Support
go-dispatch-proxy doesn't support linux at the moment. You can run this tool on linux but it will not function as expected, traffic will not be load balanced across the available interfaces. This is because of how linux works.
go-dispatch-proxy works by specifying the IP address (binding) to be used for each outgoing connection. Unfortunately on linux IP address binding != interface binding. Linux uses the route which has the lowest metric inspite of specifying the source IP address. See this for further information.
One workaround on linux is to use SO_BINDTODEVICE while creating the socket. However this reqires root to work and currently not implemented.
Credits
- dispatch-proxy: A SOCKS5/HTTP load balancing proxy written in NodeJS.
License
Licensed under MIT
Documentation
Source Files