![]() Maybe you've just got the previously released port and claimed for yourself. In other words, there's no proof it was you. No logs+static: There's a database entry but there's no proof/validation/verification that the current user held that port at the time something happened. (They're sloppy if they do and violate your privacy see next point) Unless they already have instruments to poll each server's UPnP mappings, they've absolutely nothing to report back. No logs+UPnP: There are not even database entries to attribute a port to a user at that point in time. Further: non-logging vs logging VPN.Īctually I'm going to explain all 4 scenarios at the time of processing a notice: Note: Differentiate between UPnP (dynamic port-forwarding) and static. This is technically correct, but at the same time a dubious edge-case like what has happened before due to DHCP and dynamic IPs (people wrongly accused due to IP changing and timing differences). Next time I see someone recommending a trashy VPN, I'll send them here. I am writing these posts to form a complete guide for people to follow and set up everything. Usually up to 30min (or tracker refresh time)ĭownloader, open port Seeder, open port: Instant! in either direction Need to wait until Seed sees and connects back to you. EDIT: ExamplesĮxplicit examples where port-forwarding will help establishing a connection:ĭownloader, closed port Seeder, closed port: Tough luck!ĭownloader, closed port -> Seeder, open port: Instant!ĭownloader, open port -> Seeder, closed port: Bummer. Sometimes you also need to allow incoming connections to the client application in your firewall. Disable UPnP and other automatic configuration unless your VPN provider explicitly only works with UPnP.In client settings set the "incoming port" to match the forwarded port from your VPN provider (also referred to as "local port").Pick a client and force it to only ever use the VPN connection in settings (see screenshots).Pick a VPN provider that supports port-forwarding.I believe it's worth it, without seeding torrents would die. On the other hand, it is possible that the no-log VPN is forced to disclose which account currently (at the time of request) has the port in question configured. ![]() Opinion & TLDR: If a VPN tracked/logged you, they don't need port-forwarding to find you. Is it safe (privacy-wise)? Decide for yourself, discussions also in comments There's no way around.Ī detailed explanation would be too long but you can ask in comments. Making outgoing connections is always technically possible but then you rely on the seed/peer to have their ports open! At least one side must be open. ![]() This is always the case for proxies and VPNs, but some VPNs allow the assignment of a port that will always lead to your connected device (and to your client). Normally home users cannot accept incoming connections due to NAT. Without port-forwarding: you may will see slower speeds, slower speed ramp up and if a torrent has very few online seeders you may run into a situation where you cannot connect to anybody at all - no download! Seeding is very hard without port-forwarding. ![]() If you don't want to miss a chance, here's a short explanation:īittorrent relies on your connection working both ways: to accept incoming and outgoing connections. If you are OK with your downloads failing in 10% of cases then continue as usual. > But it has been running fine without any port-forwarding for me! These misguided 'recommendations' are all over this sub and r/piracy too. Sadly nearly equally many people have no idea what's important there and recommend a random popular VPN without port-forwarding. Many people look for a VPN with the primary goal of running Bittorrent. ![]()
0 Comments
Leave a Reply. |