submitted 1 year ago* (last edited 1 year ago) by iHUNTcriminals@lemm.ee to c/piracy@lemmy.dbzer0.com

15 comments fedilink hide all child comments

I'm posting here because I assume a lot of you use vpns and this sub seems to have the most users to ask.

I was thinking about getting a VPN but was wondering about port forwarding.

I'm a Linux head so I would be downloading distros via torrent. If the VPN does not support port forwarding is it still possible to use for Linux torrents? I'm not going to be "seeding" media and extreme amounts of data, but the device would always be on and torrenting. In this case does port forwarding matter?

I guess I don't really understand dynamic and static port forwarding.

For my use case would mullvad or protonvon work even though they both use dynamic port forwarding? Or do I have to find one with static ports...?

This VPN would be used on a server with docker...

The other one I was looking at was airvpn, which is static, but I also read it might become more popular for people that use it for... Whatever... since mullvad stopped static ports.

Are there work around for dynamic ports? In case I ever want to host a website in the future?

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

[-] InformalTrifle@lemmy.world 12 points 1 year ago

Some vpns support usually a single port forward but it can be restricted to certain servers and potentially tricky to set up. Others can answer better on individual providers.

But just to correct a common misconception, port forwarding has nothing to do with seeding vs leeching. Port forwarding is so that you are connectable (others can connect to you). Two peers that are not connectable cannot connect to each other, but as long as one is connectable then a connection can be made and data can be uploaded/downloaded between the two.

So not being connectable will reduce the number of peers you can connect to, which will only really be an issue on torrents with few peers

[-] Pulptastic@midwest.social 1 points 1 year ago

This idea of ports and connectability is something I don't understand. I guess I don't know what ports really do.

As I dig into VPN setup I realize how little I understand about networking. I search for answers and find I don't even understand the answers and have a hard time finding search terms that lead me to that basic level to build up my understanding.

[-] InformalTrifle@lemmy.world 1 points 1 year ago

In simpler times, everyone that connected to the internet had an IP address. It’s 4 bytes, which means 4 digits between 0 and 255, so your IP might be 127.6.99.0. In these simpler times everyone could connect to everyone else, but if you want to run different services on your ip like a web server, email, etc, you had to do it on different ports. So if I connect to you on port 80, by convention that was web traffic. On port 21 was for file transfer. But that’s just convention. Any service can be on any port as long as you know which ip and which port to connect to. BitTorrent is no different. It listens on a port for connections from others.

It then got more complicated because people had multiple devices on their home internet connection and there aren’t enough ip addresses to give every device one. So then there was port forwarding (nat). All the devices share one IP address, and the router has rules for which port for incoming connections to forward to which internal device. Two devices can’t use the same port because there would be no way to know where to send the connection.

VPN is the same concept. You’re sharing an IP with that other people on one VPN server and if you want other people to connect to you you need a port forwarded just to you, like you would do on your router.

Very high level. I’ll try to answer if you have more specific questions