9d6947fd06
Former-commit-id: 70db40d350e527a17872688d3871203edee95520 Former-commit-id: 31ffc4844d41e72917fe8e22b042b5587537fa76 [formerly 2e33e939cb649736db3192011de508d625bd428f] [formerly b4d68158a1b3450a3fe4137a96d2fdcb903ea30b [formerly 270e15d58ee03f4c238a5f7c625963dd276b2ac2 [formerly 6031855027ec4dd4d7b20a584fccca8a76291c22] [formerly 836b5d0bbb47d10709c0df36e187c9316290f014] [formerly 836b5d0bbb47d10709c0df36e187c9316290f014 [formerly 836b5d0bbb47d10709c0df36e187c9316290f014 [formerly f40fc108219a385fd0581d84771d7fa196d36350]]]]] Former-commit-id: a6a6dd8cca96c15a615709949cc1f9e5c1d121be [formerly b28809c0bb9261aabfeb91c61a319b6d3aecd9bf] Former-commit-id: 8deb6070870381f9242fbf09902d8378b9009cd4 Former-commit-id: 16d290ea7fe6267fd6e397612a4fae60aad136d0 Former-commit-id: 7c4323aaa5357b01e3ae5e4b4a9a4bb3880c62f9 Former-commit-id: a9f7937b7aaeedc709aa3c0dab8a03a03a85a875 [formerly 5b082822ba89b026b73983441d24d8a792e65eff] Former-commit-id: af4e8a4e528e65aab4daedc85e884be17923bfa1
165 lines
7.7 KiB
Markdown
165 lines
7.7 KiB
Markdown
|
|
<p align="center">
|
|
<img src="https://github.com/erebe/wstunnel/raw/master/logo_wstunnel.png" alt="wstunnel logo"/>
|
|
</p>
|
|
|
|
## Description
|
|
|
|
Most of the time when you are using a public network, you are behind some kind of firewall or proxy. One of their purpose is to constrain you to only use certain kind of protocols. Nowadays, the most widespread protocol is http and is de facto allowed by third party equipment.
|
|
|
|
This tool understands this fact and uses the websocket protocol which is compatible with http in order to bypass firewalls and proxies. Wstunnel allows you to tunnel what ever traffic you want.
|
|
|
|
My inspiration came from [this project](https://www.npmjs.com/package/wstunnel) but as I don't want to install npm and nodejs to use this tool, I remade it in Haskell and improved it.
|
|
|
|
**What to expect:**
|
|
|
|
* Good error messages and debug informations
|
|
* Static tunneling (TCP and UDP)
|
|
* Dynamic tunneling (socks5 proxy)
|
|
* Support for http proxy (when behind one)
|
|
* Support for tls/https server (with embedded self signed certificate, see comment in the example section)
|
|
* **Standalone binary for linux x86_64** (so just cp it where you want)
|
|
* Standalone archive for windows
|
|
|
|
[Binaries](https://github.com/erebe/wstunnel/releases/tag/v4.0)
|
|
|
|
P.S: Please do not pay attention to Main.hs because as I hate to write command line code this file is crappy
|
|
|
|
## Command line
|
|
|
|
```
|
|
Use the websockets protocol to tunnel {TCP,UDP} traffic
|
|
wsTunnelClient <---> wsTunnelServer <---> RemoteHost
|
|
Use secure connection (wss://) to bypass proxies
|
|
|
|
wstunnel [OPTIONS] ws[s]://wstunnelServer[:port]
|
|
|
|
Client options:
|
|
-L --localToRemote=[BIND:]PORT:HOST:PORT Listen on local and forwards
|
|
traffic from remote. Can be
|
|
used multiple time
|
|
-D --dynamicToRemote=[BIND:]PORT Listen on local and
|
|
dynamically (with socks5 proxy)
|
|
forwards traffic from remote
|
|
-u --udp forward UDP traffic instead
|
|
of TCP
|
|
--udpTimeoutSec=INT When using udp forwarding,
|
|
timeout in seconds after when
|
|
the tunnel connection is
|
|
closed. Default 30sec, -1 means
|
|
no timeout
|
|
-p --httpProxy=USER:PASS@HOST:PORT If set, will use this proxy
|
|
to connect to the server
|
|
--soMark=int (linux only) Mark network
|
|
packet with SO_MARK sockoption
|
|
with the specified value. You
|
|
need to use {root, sudo,
|
|
capabilities} to run wstunnel
|
|
when using this option
|
|
--upgradePathPrefix=String Use a specific prefix that
|
|
will show up in the http path
|
|
in the upgrade request. Useful
|
|
if you need to route requests
|
|
server side but don't have
|
|
vhosts
|
|
--hostHeader=String If set, add the custom string
|
|
as host http header
|
|
--tlsSNI=String If set, use custom string in
|
|
the SNI during TLS handshake
|
|
--websocketPingFrequencySec=int do a hearthbeat ping every x
|
|
seconds to maintain websocket
|
|
connection
|
|
--upgradeCredentials=USER[:PASS] Credentials for the Basic
|
|
HTTP authorization type sent
|
|
with the upgrade request.
|
|
-H --customHeaders="HeaderName: HeaderValue" Send custom headers in the
|
|
upgrade request. Can be used
|
|
multiple time
|
|
-h --help Display help message
|
|
-V --version Print version information
|
|
Server options:
|
|
--server Start a server that will
|
|
forward traffic for you
|
|
-r --restrictTo=HOST:PORT Accept traffic to be
|
|
forwarded only to this service
|
|
Common options:
|
|
-v --verbose Print debug information
|
|
-q --quiet Print only errors
|
|
```
|
|
|
|
## Examples
|
|
### Simplest one
|
|
On your remote host, start the wstunnel's server by typing this command in your terminal
|
|
```bash
|
|
wstunnel --server ws://0.0.0.0:8080
|
|
```
|
|
This will create a websocket server listening on any interface on port 8080.
|
|
On the client side use this command to forward traffic through the websocket tunnel
|
|
```bash
|
|
wstunnel -D 8888 ws://myRemoteHost:8080
|
|
```
|
|
This command will create a sock5 server listening on port 8888 of a loopback interface and will forward traffic.
|
|
|
|
With firefox you can setup a proxy using this tunnel, by setting in networking preferences 127.0.0.1:8888 and selecting socks5 proxy
|
|
|
|
or with curl
|
|
|
|
```bash
|
|
curl -x socks5h://127.0.0.1:8888 http://google.com/
|
|
#Please note h after the 5, it is to avoid curl resolving DNS name locally
|
|
```
|
|
|
|
### As proxy command for SSH
|
|
You can specify `stdio` as source port on the client side if you wish to use wstunnel as part of a proxy command for ssh
|
|
```
|
|
ssh -o ProxyCommand="wstunnel -L stdio:%h:%p ws://localhost:8080" my-server
|
|
```
|
|
|
|
### When behind a corporate proxy
|
|
An other useful example is when you want to bypass an http proxy (a corporate proxy for example)
|
|
The most reliable way to do it is to use wstunnel as described below
|
|
|
|
Start your wstunnel server with tls activated
|
|
```
|
|
wstunnel --server wss://0.0.0.0:443 -r 127.0.0.1:22
|
|
```
|
|
The server will listen on any interface using port 443 (https) and restrict traffic to be forwarded only to the ssh daemon.
|
|
|
|
**Be aware that the server will use self signed certificate with weak cryptographic algorithm.
|
|
It was made in order to add the least possible overhead while still being compliant with tls.**
|
|
|
|
**Do not rely on wstunnel to protect your privacy, as it only forwards traffic that is already secure by design (ex: https)**
|
|
|
|
Now on the client side start the client with
|
|
```
|
|
wstunnel -L 9999:127.0.0.1:22 -p mycorporateproxy:8080 wss://myRemoteHost:443
|
|
```
|
|
It will start a tcp server on port 9999 that will contact the corporate proxy, negotiate a tls connection with the remote host and forward traffic to the ssh daemon on the remote host.
|
|
|
|
You may now access your server from your local machine on ssh by using
|
|
```
|
|
ssh -p 9999 login@127.0.0.1
|
|
```
|
|
|
|
### Wireguard and wstunnel
|
|
https://kirill888.github.io/notes/wireguard-via-websocket/
|
|
|
|
|
|
## How to Build
|
|
Install the stack tool https://docs.haskellstack.org/en/stable/README/ or if you are a believer
|
|
```
|
|
curl -sSL https://get.haskellstack.org/ | sh
|
|
```
|
|
and run those commands at the root of the project
|
|
```
|
|
stack init
|
|
stack install
|
|
```
|
|
|
|
## TODO
|
|
- [x] Add sock5 proxy
|
|
- [x] Add better logging
|
|
- [x] Add better error handling
|
|
- [x] Add httpProxy authentification
|
|
- [ ] Add Reverse tunnel
|
|
- [x] Add more tests for socks5 proxy
|