this post was submitted on 08 Jul 2023
46 points (97.9% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54500 readers
633 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
So question does a vpn in a docker container directly tunnel that docker to the vpn basically not touching anything outside of it(i.e home ip/net)?
Yes, it can only affect the network of the container
Ah interesting. Might be worth looking into the saltbox someone posted above. I currently use a seedbox service
I run wireguard in one container (as a client connected to Mullvad), and then qBittorent in another container but using the network of the wireguard container.
Then I just set up routing rules in wireguard to allow my local network to be exempted from the tunnel so I can reach the web interface of qBittorent.
All my torrent traffic goes over the VPN, I can still reach the webui and none of my other containers are affected. Super simple and very reliable.
Now you got me thinking Might actually make a post asking for an equivalent usenet (box) to have a usenet and seedbox on prem:D
That Saltbox one can be used for both Usenet or torrents