News for hackers. Stuff that matters.
Re:Mullvad: Removing the Support for Forwarded Ports by 5e92cb50239222b on Monday May 29, 2023 @10:27AM (#36114331)
You need to be able to accept incoming connections to be able to fully participate in the network. Last time I seriously looked into this, BitTorrent clients didn't support any sort of NAT hole punching (and they often work over TCP in any case). Try running a client with and without a forwarded port and you will see massive difference in the number of peer connections.
Re:Mullvad: Removing the Support for Forwarded Ports by shrimp_emoji on Monday May 29, 2023 @10:28AM (#36114348)
So you're saying there's a chance
Re:Mullvad: Removing the Support for Forwarded Ports by justsomehnguy on Monday May 29, 2023 @10:56AM (#36114607)
Of course, but if everyone is behind the NAT then no one in the swarm can connect to any one. If this is a popular torrent when someone with the connectivity would show up, eventually, but otherwise good luck. Recently it took me four months to complete one torrent and I was the one with the real IP.
Re:Mullvad: Removing the Support for Forwarded Ports by krossitalk on Monday May 29, 2023 @10:51AM (#36114557)
> NAT hole punching

Could we just throw a STUN service in front of this, then?

Re:Mullvad: Removing the Support for Forwarded Ports by Capricorn2481 on Monday May 29, 2023 @02:11PM (#36116408)
I think I might be doing that already, as this is the first I've heard of this. Unless Mullvad was automatically opening a port for me.

Is it possible a lot of average torrenters are already not port forwarding?

Re:Mullvad: Removing the Support for Forwarded Ports by 1letterunixname on Monday May 29, 2023 @05:54PM (#36118566)
Transmission has supported UPnP and NAT-PMP for many years. Although it doesn't always work as reliably as having a client with directly routable address(es), it does exist and works okay.