redsocks
tsocks
| redsocks | tsocks | |
|---|---|---|
| 5 | 1 | |
| 3,187 | 0 | |
| - | - | |
| 0.0 | 0.0 | |
| 10 days ago | almost 2 years 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.
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
tsocks
-
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?
What are some alternatives?
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.
ts-warp - Transparent proxy server and traffic wrapper
hev-socks5-tproxy - A simple, lightweight socks5 transparent proxy for Linux. (IPv4/IPv6/TCP/UDP)
transocks - Transparent SOCKS5 / HTTP proxy in Go
nordvpn - NordVpn Docker Client
Burrow-Client - DNS Tunneling Client for iOS
poor-mans-vpn - An ansible playbook to set up wireguard server.
GoodbyeDPI - GoodbyeDPI — Deep Packet Inspection circumvention utility (for Windows)
outline-apps - Outline Client and Manager, developed by Jigsaw. Outline Manager makes it easy to create your own VPN server. Outline Client lets you share access to your VPN with anyone in your network, giving them access to the free and open internet.
GreenTunnel - GreenTunnel is an anti-censorship utility designed to bypass the DPI system that is put in place by various ISPs to block access to certain websites.
algo - Set up a personal VPN in the cloud