redsocks
gluetun
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
gluetun
-
Custom command on docker startup after watchtower update
healthcheck: # https://github.com/qdm12/gluetun/issues/641#issuecomment-933856220 test: "curl -sf https://example.com || exit 1" interval: 1m timeout: 10s retries: 2
-
Communicating with another docker container that is networked through a VPN container
I have containers a,b,c. Container C is running Gluetun (https://github.com/qdm12/gluetun) which is a VPN container.
- Restart vpn connection (new ip) from inside the container?
-
It's this time of the year again... which open-source project are you donating to?
The last couple of years I have been donating to Gluetun.
-
How to host a docker based proxy for selected containers
One option I could find is Gluetun, which looks very popular and actively maintained. In this case we have one single point of contact with VPN provider. The other containers should be run with network_mode: service:gluetun. If I understand correctly, those container will use VPN for every network operation, even for inter-container communication. Would they be visible for the containers not attached to gluetun (e.g. the SWAG reverse proxy)?
-
Express vpn container
Try setting it up. https://github.com/qdm12/gluetun See if it works for your needs.
-
Easy port-forwarding on linux
After some digging around, I found this project, which I think should get a lot more light on itself. It allows to setup port-forwarding on linux very easily, together with a lot of other things !
-
running a docker with a torrent client and vpn INSIDE the container... bad idea?
I setup Gluetun with qbittorrent in docker. Gluetun connects to the nord via manual login and I get to choose the specific servers I want it to you in its environment variables.
-
Gluetun killswitch
Hi guys, I have a dumb question: according to their github page, one of the features is the killswitch. It is not clear to me whether this would shutdown other containers (connected to it) when vpn drops, or only when the whole internet connection goes down
-
NordVPN - AUTH_FAILED Your credentials might be wrong
# See https://github.com/qdm12/gluetun/wiki
What are some alternatives?
hev-socks5-tproxy - A simple, lightweight socks5 transparent proxy for Linux. (IPv4/IPv6/TCP/UDP)
docker-wireguard-pia - A Docker container for using Wireguard with PIA.
transocks - Transparent SOCKS5 / HTTP proxy in Go
openvpn-client
tsocks - tsocks, a transparent SOCKS proxying library.
docker-transmission-openvpn - Docker container running Transmission torrent client with WebUI over an OpenVPN tunnel
ts-warp - Transparent proxy server and traffic wrapper
nordlynx
nordvpn - NordVpn Docker Client
Burrow-Client - DNS Tunneling Client for iOS
docker-qBittorrentvpn - Docker container which runs a headless qBittorrent client with WebUI and optional OpenVPN