“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 3 weeks ago (3 children)

What about holepunching?

[–] mic_check_one_two@lemmy.dbzer0.com 6 points 2 weeks ago (2 children)

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 4 points 2 weeks ago* (last edited 2 weeks 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.

load more comments (1 replies)