rserver or whatever you like ... you can name it.

• In client mode

  ./rserver -AsClient -Address :1080 -Password="this-password" -RemoteServer=1.2.3.4:5000 -Method=aes-256-cfb

• In server mode

  ./rserver -AsServer -Address=:5000 -Password="this-password" -Method=aes-256-cfb

Currently supported encryption methods are aes-128-cfb, aes-192-cfb and aes-256-cfb.

rserver is a network relay server that can handle TCP connections and could bypass a firewall. rserver follows SOCKS5 protocol and thus, you can work with rserver using many commands such as curl: curl --socks5 127.0.0.1:1080 google.com -vvv -L. Before you run any command, first you need to run servers in both server and client mode.

go get github.com/luSunn/rserver and then you do make or go build

$ cat client.json
# local
{
   	"address": "127.0.0.1:1080",
       "isclient": true,
       "logfile": "/var/log/rserver.log",
	"method": "aes-192-cfb",
	"password": "I'm-having-a-wonderful-day-so-far",
	"servers": [
	"myserver1:8080",
	"myserver2:9000",
	"myserver3:7979"	
	],
}

$ ./rserver -C client.json

# remote
$ cat remote.json 
	
{
	"address": ":8080",
	"isserver": true,
	"log": "/var/log/rserver.log",
	"method": "aes-192-cfb",
	"password": "I'm-having-a-wonderful-day-so-far",
}
	
$ ./rserver -C client.json

rserver works pretty much simple. According to rfc1928, SOCKS5 servers should accept username and password to authenticate users but since rserver can only talk between clients and remote servers, it is no longer necessary to implement that authentication. When clients get requests from users, a client server soon encrypts SOCSK5's header and send it to a remote server and then a remote server connects to a target and sends data back to a client. Header's first two bytes are reserved for the data length.

#assuming rserver is running in client mode at port :1080...
$ ssh -l xun -p5000 -o ProxyCommand='nc -x localhost:1080 %h %p' server.net # this is useful when the network has aggressive port filterings.

$ google-chrome proxy-server=socks://127.0.0.1:1080 # open Chrome browser with a proxy

$ dropbox proxy manual socks5 127.0.0.1 1080  # configure dropbox with socks5

• Support UDP relay
• Support UDP associate command.
• Wrap whole connection with proper encryption method so that we can perfectly bypass firewall.