894bd997a9
- altered code to support a client bound interface - altered code to support an admin bound interface - added configurations and defaults. - removed timeout function at the end of main. - the final go routine was converted to a foreground routine. |
||
|---|---|---|
| certs@ec246b228c | ||
| html | ||
| logging | ||
| .gitignore | ||
| .gitmodules | ||
| README.md | ||
| connection.go | ||
| connection_table.go | ||
| instrumentation.go | ||
| listener_admin.go | ||
| listener_client.go | ||
| vpn-server.go | ||
README.md
RVPN Server
Build Instructions
Get the dependencies
go get github.com/gorilla/websocket
go get github.com/dgrijalva/jwt-go
git clone git@git.daplie.com:Daplie/localhost.daplie.me-certificates.git
ln -s localhost.daplie.me-certificates/certs/localhost.daplie.me certs
Run the VPN
go build && ./go-rvpn-server
In another terminal execute the client
bin/stunnel.js --locals http:hfc.daplie.me:3000,http://test.hfc.daplie.me:3001 --stunneld wss://localhost.daplie.me:8000 --secret abc123
A good authentication
INFO: 2017/02/02 21:22:22 vpn-server.go:88: startup
INFO: 2017/02/02 21:22:22 vpn-server.go:90: :8000
INFO: 2017/02/02 21:22:22 vpn-server.go:73: starting Listener
INFO: 2017/02/02 21:22:22 connection_table.go:19: ConnectionTable starting
INFO: 2017/02/02 21:22:24 connection.go:113: websocket opening 127.0.0.1:55469
INFO: 2017/02/02 21:22:24 connection.go:127: access_token valid
INFO: 2017/02/02 21:22:24 connection.go:130: processing domains [hfc.daplie.me test.hfc.daplie.me]
Change the key on the tunnel client to test a valid secret
INFO: 2017/02/02 21:24:13 vpn-server.go:88: startup
INFO: 2017/02/02 21:24:13 vpn-server.go:90: :8000
INFO: 2017/02/02 21:24:13 vpn-server.go:73: starting Listener
INFO: 2017/02/02 21:24:13 connection_table.go:19: ConnectionTable starting
INFO: 2017/02/02 21:24:15 connection.go:113: websocket opening 127.0.0.1:55487
INFO: 2017/02/02 21:24:15 connection.go:123: access_token invalid...closing connection
A Poor Man's Reverse VPN written in Go
Context
Even in the worst of conditions the fanciest of firewalls can't stop a WebSocket running over https from creating a secure tunnel.
Whether at home behind a router that lacks UPnP compliance, at school, work, the library - or even on an airplane, we want any device (or even a browser or app) to be able to serve from anywhere.
Motivation
We originally wrote this in node.js as node-tunnel-server, but there are a few problems:
- metering
- resource utilization
- binary transfer
metering
We want to be able to meter all traffic on a socket. In node.js it wasn't feasible to be able to track the original socket handle all the way back from the web socket authentication through the various wrappers.
A user connects via a websocket to the tunnel server and an authentication token is presented. If the connection is established the socket should then be metered and reported including total bytes sent and received and size of payload bytes sent and received (because the tunnelling adds some overhead).
resource utilization
node.js does not support usage of multiple cores in-process. The overhead of passing socket connections between processes seemed non-trivial at best and likely much less efficient, and impossible at worst.
binary transfer
node.js doesn't handle binary data very well. People will be transferring gigabytes of data.
Short Term Goal
Build a server compatible with the node.js client (JWT authentication) that can meter authenticated connections, utilize multiple cores efficiently, and efficienty garbage collect gigabytes upon gigabytes of transfer.