hev-socks5-tproxy
redsocks
| hev-socks5-tproxy | redsocks | |
|---|---|---|
| 1 | 5 | |
| 375 | 3,196 | |
| - | - | |
| 7.3 | 0.0 | |
| 4 days ago | 20 days ago | |
| C | C | |
| GNU General Public License v3.0 only | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
hev-socks5-tproxy
redsocks
- Routing traffic to socks proxy
-
How to transparently route ALL outbound traffic from the docker container thru the socks5 server running on host? (meaning the entire docker container and everything running inside it should use the specified socks5 proxy)
I used redsocks (https://github.com/darkk/redsocks) for that, but with completely external proxies. However, this solution requires configuring iptables rules inside the container, which may be unsuitable for your usecase
-
Arti 0.1.0: Tor re-written in Rust now has a stable API
I don't think you can generally expect all processes to transparently use a SOCKS proxy? You might be able to finagle a custom vpn around it, I suppose. But AFAIK SOCKS isn't 100% transparent at the IP layer allowing all protocols to transparently layer on top?
I guess SOCKS5 handles tcp and udp - so you might get away with redsocks (which explicitly recommends against using with TOR):
https://github.com/darkk/redsocks
See also transocks (SOCKS4 tcp only): https://transocks.sourceforge.net
And transocks (in go) https://github.com/cybozu-go/transocks
-
My own SOCKS protocol redirector with a trans-warp engine
Who nowadays might be interested in a yet another transparent SOCKS protocol redirector/wrapper if we, besides many other projects, already have Redsocks for firewall- and tsocks for LD_PRELOAD- based traffic forwarding?
-
Poor man's VPN (pay for only what you need)
Second this. I haven't tried proxychains. iptables with redsocks[1] for redirection works pretty nice.
[1] https://github.com/darkk/redsocks
What are some alternatives?
goproxy - 🔥 Proxy is a high performance HTTP(S) proxies, SOCKS5 proxies,WEBSOCKET, TCP, UDP proxy server implemented by golang. Now, it supports chain-style proxies,nat forwarding in different lan,TCP/UDP port forwarding, SSH forwarding.Proxy是golang实现的高性能http,https,websocket,tcp,socks5代理服务器,支持内网穿透,链式代理,通讯加密,智能HTTP,SOCKS5代理,黑白名单,限速,限流量,限连接数,跨平台,KCP支持,认证API。
gluetun - VPN client in a thin Docker container for multiple VPN providers, written in Go, and using OpenVPN or Wireguard, DNS over TLS, with a few proxy servers built-in.
transocks - Transparent SOCKS5 / HTTP proxy in Go
conntracker - A good addition to your conntrack-tools package. Conntracker acts like a firewall sniffer, it analysis, realtime, with very low overhead, all iptables (or nf_tables) existing flows and inform you, at the very end of its execution, all flows in a sorted and consumable way.
tsocks - tsocks, a transparent SOCKS proxying library.
ebpf-tproxy-splicer - This is a project to develop an ebpf program that uses ebpf tc to redirect ingress ipv4 udp/tcp flows toward specific dynamically created sockets and acts as a stateful firewall.
ts-warp - Transparent proxy server and traffic wrapper
miniupnp - UPnP IGD implementation
nordvpn - NordVpn Docker Client
Mongoose - Embedded Web Server
Burrow-Client - DNS Tunneling Client for iOS