And it’ll give my true IP rather than my VPNs IP even if it is binded in the client? If this is the case, why does there seem to be disagreement on whether this is a risk and there’s no mention of it in the actively maintained guide I initially followed?
Again, not accusing anyone of lying, I’m just trying to untangle this. I can try disabling DHT and PeX but I’m worried I won’t be able to torrent anything.
things like the DHT and PeX can leak your own home ip address
It also seems like many torrents don’t work without it so I’m not sure what to do. Not accusing you of lying but do you have a source that elaborates on when and how they leak your true IP?
Is there any way to mitigate it besides disabling them and joining a private tracker? This torrenting thing looks more complicated than I hoped haha.
I’d also set it to only allow encrypted connections, which for some reason they don’t say there.
Interesting, I don’t believe that’s mentioned in the first guide either. I’ll look into that, thanks!
If you already don’t mind paying for a VPN, why not look into seedboxes?
I’ll look into that, though I already require a VPN service for other purposes and having two subscriptions might be out of my budget. In fact I was even considering downgrading from Mullvad to Protons’ free VPN tier as even 1 VPN subscription stings me, but of course that also doesn’t support port forwarding.
I wish I could use I2P but I heard it’s rare to find torrents there. If only everyone switched, we could do away with paid VPN requirements.
It’s just extra work to set up but I’m now realizing in the long run it’ll be worth it, so I’ll get on that. Thanks!
As in if you have your VPN binded to your client?