𝗠𝗲𝗴𝗮𝘁𝗵𝗿𝗲𝗮𝗱 needs to be updated (lemmy.org)

submitted 2 days ago by kamikkazet@lemmy.org to c/piracy@lemmy.dbzer0.com

54 comments fedilink hide all child comments

mullvad and proton stand as vpn. However, mullvad does not allow torrenting because there is no port forwarding. Mullvad should not be on the list

you are viewing a single comment's thread
view the rest of the comments

[-] pastermil@sh.itjust.works 22 points 2 days ago

I torrent just fine without port forwarding, with more than 2.0 seed ratio on some.

Do you even know what you're rambling about?

[-] mic_check_one_two@lemmy.dbzer0.com 31 points 2 days ago

“Just fine” is relative. Torrenting requires at least one side to have an open port. If you don’t have port forwarding, you’re entirely reliant on other people having their ports open instead. Even if there are 1000 seeds, if all of them have closed ports you’ll be unable to connect to them. It’s kneecapping your connections for no good reason.

[-] JamonBear@sh.itjust.works 1 points 2 days ago

What about holepunching?

[-] mic_check_one_two@lemmy.dbzer0.com 6 points 1 day ago

Hole punching is how torrenting is possible at all without port forwarding. But it still relies on the other person having an open port, because hole punching only works to initiate things on your end.

[-] Darkassassin07@lemmy.ca 3 points 1 day ago* (last edited 1 day ago)

Decided to do some more reading on this topic. TIL:

TCP, the more common protocol; requires at least one side to have a port forwarded through their NAT to the client, so the other side can make a connection to that open port.

uTP on the other hand, can 'holepunch' by sending a packet to a known IP, which opens a port through the sending clients NAT, specifically for that IP. That port can then be used to send and receive by either side until it closes due to inactivity.

So, torrent clients can use uTP holepunching to open a port without requiring manual forwarding, then advertise that open port to public trackers. Client 'A' will try to connect to an IP+port it got from the tracker and get ignored (because the recipient NAT isn't expecting data from that IP and drops the packets). Then when client 'B' decides to connect to client 'A', 'A's port will now be open and allowing data from 'B's IP, thus establishing a connection.

This is slower than a direct connection because both clients need to be made aware of each other and decide to attempt to connect at reasonably similar times. It also requires public trackers with peerexchange enabled and the torrents cannot be flagged as private.

[-] JamonBear@sh.itjust.works 4 points 1 day ago

Bullshit, Trackers and DHT hold IP and port of peers, hole-punching technique allows to open both sides.

The only difference is the speed to establish connection:

With an open port, it is done instantly as peers can reach you directly.
Without, you need to wait for the seeder to fetch your IP from tracker (slow) or to recieve it from DHT (fast).

Now, the reason why it seems hard to seed torrents on private tracker, that disable DHT, is because seeders with closed port will only fetch leechers IP from tacker 1 to 4 times per hour, so by the time the hole-punched connection is established, leecher has already sucked up all the data from peers with open ports.

It's fine to keep port closed if you avoid private tracker and DHT disabled torrents. If you want to build up ratio on a crappy private tracker, seeding a piece of a fat 100Gb+ torrent will do.