arch-privoxyvpn
dnsleaktest
Our great sponsors
arch-privoxyvpn | dnsleaktest | |
---|---|---|
7 | 5 | |
97 | 369 | |
- | - | |
5.6 | 3.6 | |
about 1 month ago | 21 days ago | |
Shell | Shell | |
GNU General Public License v3.0 only | MIT License |
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.
arch-privoxyvpn
- Gluetun (VPN for a few containers) Alternative?
-
Transmission Container through Wireguard Help
It sounds like you're looking for something like this, available in community apps. You would then create a custom docker network, and assign Transmission's network to the privoxyvpn container (and move the ports from transmission to privoxy)
-
Please, help me understand how my IP was leaked
First, a bit about my setup. Everything is in Docker. I have a qbittorrent container, which tunnels through binhex's privoxyvpn container, which is connected to ExpressVPN. Somehow though, when I visit https://iknowwhatyoudownload.com using my normal IP, they're able to identify a sample of the torrents I've downloaded over the last 2 weeks via this setup (I don't have a torrent client installed anywhere else and I know these specific items were indeed downloaded through my qbittorrent.)
-
VPN client in a thin Docker container for multiple VPN providers, written in Go, and using OpenVPN, DNS over TLS, with a few proxy servers built-in.
I'm currently using binhex/arch-privoxyvpn. Is there a reason why I should use Gluetun instead?
- Suggestions: dockerized VPN client (wireguard/openvpn) that is exposed so that i can connect to it via proxy (sock5/http) on local devices
dnsleaktest
-
Should i use my vpn provider's native client or use a wireguard/openvpn client instead?
I am currently trying out Guetun in docker with ExpressVPN but am getting possible DNS leaks reported by this test. I ran this test in the docker exec console for my qBittorrent container which is routed through my Gluetun container. This is the output I get after running. I have also tried some other tests like doileak.com torrent IPtest. The reults i get from that say that I have an ipv4 udp leak. How do i know for sure that I'm not leaking my IP? TIA!
-
Do I need to install Stubby or dnscrypt-proxy ?
If you want to check what DNS is being used system-wide. https://github.com/macvk/dnsleaktest
-
Please, help me understand how my IP was leaked
I've confirmed the following: * curl ifconfig.cc inside the qbittorrent container gives me the VPN IP, not my own. * Using https://ipleak.net shows my VPN IP, not my own, when downloading their torrent in qbittorrent. * When using https://github.com/macvk/dnsleaktest inside my qbittorrent container, I get a different set of DNS server than when using it outside of it. These are the servers specifically from inside: You use 6 DNS servers: 104.156.251.15 [United States of America AS20473 The Constant Company LLC] 107.191.42.180 [United States of America AS20473 The Constant Company LLC] 144.202.14.9 [United States of America AS20473 The Constant Company LLC] 2001:19f0:5:18e8:5400:1ff:febe:3032 [United States of America AS20473 The Constant Company LLC] 2001:19f0:300:60d2::33 [United States of America AS20473 The Constant Company LLC] 2001:19f0:300:6256:5400:ff:fe1a:c6e7 [United States of America AS20473 The Constant Company LLC]
-
DNS for wireguard interface inside netns (with systemd-resolved)
I recreated the simple (wg moved into netns) setup and introduced the nsswitch file you posted above. I then ran a DNS leak test script from within the netns and it didn't report any leaks. I ran wireshark in parallel, and unlike before, there was no DNS traffic on the host's ethernet interface. This looks really promising.
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.
compose-transmission-wireguard - Run Transmission through a WireGuard tunnel with Docker Compose.
docker-windscribe-socks-server - Containerizes a SOCKS5 proxy server with traffic tunneled through Windscribe's VPN service
arch-delugevpn - Docker build script for Arch Linux base with Deluge, Privoxy and OpenVPN
arch-plexpass - Docker build script for Arch Linux base with Plex Pass Media Server installed
openvpn-client
arch-sabnzbdvpn - Docker build script for Arch Linux base with SABnzbd, Privoxy and OpenVPN
namespaced-openvpn - Wrapper for OpenVPN on Linux solving various privacy issues
openvpn-pihole - 🕵️ A truly delicious combination of two wonderful pieces of software to setup a pi.hole-backed VPN as quick as possible.
arch-rtorrentvpn - Docker build script for Arch Linux base with ruTorrent, rTorrent, autodl-irssi, Privoxy and OpenVPN
vpn-only-network-namespace
systemd - The systemd System and Service Manager