Simple SOCKS5/HTTP tunnel. SOCKS5 on client side provides NO AUTHENTICATION TCP/UDP proxy. Version 2.0 based on QUIC and TLS-TCP.
. | .
. f .
. i .
HTTP -----| r |------ outbound1
| e |
| | |
client---------------- tunnel ----------------server--- outbound2
| | |
| w |
SOCKS5 -----| a |------ outbound3
. l .
. l .
. | .
- HTTP proxy
- SOCKS5 TCP proxy
- SOCKS5 UDP proxy
- QUIC
- TLS-TCP(based on TLS on TCP)
./certgengenerates cert and private key- modify
config/client.tomlandconfig/server.toml - start server(
./stunnel_server config/server.toml) and client(./stunnel_client config/client.toml) with the same cert
Browser connect client address(127.0.0.1:1080) via SOCKS5 or connect client address(127.0.0.1:8080) via HTTP.
---------------- ------------- -------------
| | | | | |
| gatewaysocks | --- TCP/UDP --> | autoproxy | ------- TCP/UDP -----> | stunnel |
| | | | | | |
---------------- ------------- | -------------
^ ^ |
| | | -------------
| | | | |
| | |--- TCP/UDP -----> | direct |
| | | |
| | -------------
----------------- ------------------
| devices | | set system |
| in the same | | proxy settings |
| router | | to autoproxy |
----------------- ------------------