this post was submitted on 01 Mar 2024
203 points (95.5% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54758 readers
428 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
ProtonVPN for port forwarding, Mullvad for easy usage (Wireguard on Linux).
I use vopono on Linux too.
ProtonVPN works great via Wiregurd on Linux as well just not through the GUI; you can download the configs and connect through terminal or other Wireguard client
ProtonVPN also provides Wireguard config files if you don't want to use their shitty python based GUI. Supports port forwarding aswell, althought it sucks to set up and requires to manually disable ipv6 support
I created a simple script to automatically request a port to ProtonVPN servers and assign it to qbittorrent:
https://github.com/giu176/ProtonVPN-auto-NATPMP
Thank you, luckily arch-qbittorrentvpn already does those things, so I don't have to
Thanks for sharing! I still need the script because I already have a tunnel on a Mikrotik OS vm router to route all my containers through the vpn.
Another benefit of using network namespaces is that I can just disable IPv6 in the network namespace itself.
I'll admit, I have no idea what the benefit of port forwarding is. I use Mullvad in a Gluten container.
It's when you open a publicly facing port and map (forward) it to a local port your machine. In this case, it's opened at the vpn provider's public gateway. Otherwise, it would typically be opened in your router instead.
You can then configure your torrent client to listen on that local port that the public port is forwarded to. I think generally the public and the local port are the same number when using VPN.
If you do that, then others have the ability to initiate a connection to you instead of only you being able to initiate the connection to somebody else.
When seeding/leeching to/from someone else, at least one of you needs a port open. So, if you always have one open, you allow yourself to connect to anyone on the network regardless if they have one open or not.
Sorry if I confused you more, I'm not that great at explaining.
Faster downloads (sometimes significantly), easier to connect to seeders.