I’ve been putting off renewing my mullvad membership because of the port forwarding thing. I only want to use it for torrenting. Is it really crucial to find a VPN that supports port forwarding? If so, what’s the go to option now that it’s becoming increasingly uncommon?
Quote from some old guide:
The Importance of Being Connectable:
When it comes to torrents, being connectable can go a long way in helping your ratio. Connectivity is directly related to port forwarding, your router, and incoming torrent connections. Here’s how it works:
You upload a new torrent. After going through the upload page and adding the torrent to your client, the client connects to the tracker to do the following:
- Tell the tracker it is going to begin seeding a torrent.
- Ask the tracker if there are any peers it doesn’t know about.
Normally, no one has downloaded the torrent from the site between the time that you upload the torrent and when you add it to your client. So your client will now wait, for 45 minutes (or however long it’s been told to wait by the tracker), until it will connect back and ask for more peers.
Now suppose someone downloads your torrent from the site after you added the torrent to your client. Normally, the person’s client will ask the tracker for peers, to which the tracker will return your IP address to connect to. That client will then connect to your client, using the IP address and port number it got from the tracker pertaining to your client and the port it accepts incoming connections on. This is where being connectable comes into play. We’ll assume your IP address is 139.129.43.5 and your port number used for torrenting is 3058.
When the peer attempts to connect to you on that designated port, your router has to know what to do with the incoming connection. It receives an incoming connection from the peer, on port 3058. If you have your port forwarded to your client correctly, that is, you’ve told the router what to do with incoming data on a specific port, the router knows to send anything coming in on port 3058 to the computer your client is running on. Now, if you are not connectable, the router doesn’t know what to do with items coming in on port 3058, so they are discarded, and the other peer isn’t able to connect to you.
If your port isn’t forwarded correctly, the peer who just added your torrent to their client will have to wait for 45 minutes, until your client updates with the tracker, and gets the new peer’s IP address and port to connect to. If the peer is connectable, you will then make an outbound connection to them, and it will connect successfully. Outbound connections aren’t normally blocked by a router, unlike incoming ones, this is why a client doesn’t need a port forward for outgoing connections. This scenario is also why you can still seed even if you aren’t connectable. This can have very negative consequences for your ratio though as I will now explain.
Here’s how not being connectable will hurt you. When you are seeding a torrent in a large swarm and a new peer comes online, his client will attempt to make connections to the other peers. If you aren’t connectable, you will have to wait (at max) 45 minutes until your client learns of their existence, before you can start uploading data to them. During this time the peer is getting data from other peers, but not you. By the time your client finally learns of the new peer’s existence, the client will already be done downloading! You won’t get nearly as much upload than if you were connectable. Depending on the size of the torrent, your client may not get any upload for that peer, because he will have completed the torrent before your client even knew he was present.
The absolute worst case scenario is when both peers aren’t connectable. Neither peer will be able to connect to the other, and both will sit without connection indefinitely.
How will this work if you are behind double NAT by your isp
Thanks for the explanation! First time I have somewhat understood what port forwarding does for torrents.
I’m more concerned with the fact that they’re removing features without reducing price or making up for it elsewhere. I have no desire to support that business when there are perfectly fine alternatives.
5€ is already dirt cheap. If you have another ~ 5€ service that can max out my 1 Gbps connection when I download, I am all ears.
there are perfectly fine alternatives.
Would you mind making some examples please?
https://lemmy.world/post/698471
ProtonVPN and AirVPN off the top of my head.
ProtonVPN has dynamic port forwarding via a Windows client (or a python script if on Linux). Just a heads up, since it could be awkward to work out if you’re downloading from a headless server.
I’ve heard AirVPN is good. I switched to iVPN and I’m satisfied
Heads up if you don’t already know, IVPN recently announced they are dropping port forwarding like Mullvad recently did. https://www.ivpn.net/blog/gradual-removal-of-port-forwarding/
Oh motherfucker
AirVPN I guess then
I’ve been using airvpn for years, no complaints.
Oyoyoy. What then?
Moved from mulvad to ivpn and now what?
Usenet
I use PIA (probably the cheapest out there). If you just care about torrenting, they’re quite good. I can saturate my Gbit connection and they offer PF (only for p2p applications though)
I tried getting port forwarding to work with PIA, but it seems to be unavailable within the US. Has that been the case for you as well? Not sure if it’d be worth using an international server with 1/10 the speed in order to enable port forwarding, but I would love to be able to be connectable.
How do you use it? Why do you say it is not available? I am in Europe but I’ve never seen anybody report what you’re saying.
Like I said, it is limited to p2p applications. You cannot host a web server or something similar.
But yeah if you’re in Europe then it makes sense that it’d be available to you!Try using this instead of the app
https://github.com/thrnz/docker-wireguard-pia
It’s a lot more technical but it’s worth trying.
I’m actually using that exact same docker image :) port forwarding still doesn’t work within the US though. I love the speeds I get from Wireguard compared to OpenVPN though.
Is it really crucial to find a VPN that supports port forwarding
It’s crucial when the only seeder won’t open their port.
what’s the go to option now that it’s becoming increasingly uncommon
My opinion: I wish qbittorrent 4.6 would release sooner, it comes with I2P support, which I’ve seen discussed on lemmy a few times.
It’s important for rare/poorly seeded torrents, but not at all important if it’s a new release movie or something like that which will be well seeded.
True but this’ll only work long term if you download every new thing that you’ll want to watch now or sometime down the road.
For me it’s incredibly important. If I don’t have port forwarding my status on qbit is restricted and I get like 10% of the speed I do when it’s open. This is for big torrents
4.6 is now at beta1 which is by far and large usable. I think the 4.6 branch will take some time to stablize as it is moving to the libtorrent 2.x branch (from which I2P support comes). Their most recent 2.0.9 has just fixed some I2P related bugs.
I wish qbittorrent 4.6 would release sooner
Is there an ETA or something? I am waiting on it at the moment, but I don’t know their release schedule or anything
How does port forwarding work if you have multiple torrent clients on the same network, all sharing a public IP?
You put them on different ports and make multiple forwards, one for each.
Each peer can choose any port they want – to open to the swarm. You’re not restricted to one particular port, so there’s no need to clash with another per on your network. The defaults in the settings are merely suggestions.
I think you should try to find a VPN that supports it, but you can live without it if you have to.
If you don’t have a listening port other clients can’t request a connection. You can still limp along without accepting incoming connection requests and it may not even make a big difference. Still it’s a lot better to have it. You’ll connect to more peers.
BTW, It’s not always necessary to use port forwarding to enable a listening port, but commonly it is. Machines with a public facing IP don’t need to use port forwarding, but most people are either on a private network or VPN where it’s required.
Is it really crucial to find a VPN that supports port forwarding?
It is not required but you will have a much better torrenting experience by being connectable (port forwarded). When you are fully connectable you are able to make direct connections to all peers in torrent swarms so overall your upload/download speeds would be faster and you can still participate in small torrent swarms.
When you are firewalled (not port forwarded) you can only make direct connections to peers that themselves are connectable (port forwarded).
In practice when you are in large torrent swarms it may not make much difference, there’s often plenty of connectable peers in large torrent swarms that you can connect with. However in smaller torrent swarms if no one is connectable then all the firewalled peers can only see each other, no data will transfer. They are all stuck waiting for a connectable peer to join the swarm & help with the data transfer.
Nice explanation, thanks!
Now it makes sense why when occasionally my VPN will stop when I’m downloading, and I’m able to get a bunch more connections than usual.
If you care about seeding you need it. If you don’t you’re fine but come on, you know you should care lol.
I use PIA, probably the cheapest option out there and it does have PF.
Is PIA still supporting Gab? They are burnt for me since they actively advertised them as affiliates…
What’s gab?
It’s a fascist social network
I notice the difference with it off. Its shit without it. I get no incoming connections to existing torrents I’m seeding and when I add a new magnet link it just stays stuck on obtaining metadata and never Downloads.
When I have the port forwarded it runs like clockwork.
My setup is containerized with a gluetun container acting as the VPN network and the interface binded inside the qbittorrent container. .
I’m using gluetun with AirVPN and my transmission containers’s connection to peers isn’t great. I have port forwarding enabled (verified working using the test button in transmission). But I can connect to 0 or 1 peer out of 12 on a specific torrent, and without the VPN I can immediately connect to 6 peers.
Did you do anything tricky with your container stack that isn’t part of the gluetun guide?
No you don’t need port forwarding
One important aspect is that two peers without port forwarding will never be able to connect to each other. This is important for torrents with low amount of peers. Unless a connectable peer comes in to essentially relay data by grabbing the content from the other person and then seeding to you, you won’t be able to download. For popular torrents with plenty of connectable peers to go around this is less of an problem, it will only cause some performance issues.
This isn’t quite true, if three peers support https://en.wikipedia.org/wiki/Micro_Transport_Protocol, a third peer that has a port forward can act as a STUN server for the two peers without and let them connect directly to each other.
I don’t know how well it works in practice, but Transmission supports it so I’ll rely on it while this whole PF business settles down.
From what I’ve gathered certain really illegal content was being created and uploaded; and paid for using crypto. It really is a harsh shame to people who have obscure files or services and have been using the service for more than 5 years. I think they should reevaluate their policy and allow registered non-crypto accounts to have access to it after a certain period of time. Simply removing the feature is unacceptable; I put my trust in IVPN after much research. I’m concerned about how the other providers will handle the windfall of new users signing up for the feature and if they will keep it active.
I think it just makes you more discoverable to other peers for dl/seeding, don’t quote me on that I might be misremembering
Port forwarding lets you connect with a peer that doesn’t have port forwarding basically. You may not notice a difference.
Aside from torrent the other p2p where an open port can be important is Soulseek, you could be blacklisted by users from downloading pretty quickly if you don’t/can’t share music.
I switched to mullvad a few months back and what I noticed coming from AirVPN is how much less captcha requests I get, I’m not much into p2p so I’ll probably stay with them.
Wait…soulseek is still a thing???
Oh yeah, very much so.
Yup! And not even just torrents/Soulseek, other p2p apps like eMule also require incoming ports for the best performance.
… okay, okay cue the “people still use eMule?” comments :D
If you want to run a seedbox behind a VPN (like I do) then you’d want to be connectable, so a VPN with portforwarding would be crucial. I run my own OpenVPN server on a public VPS (so a dedicated IP instead of shared IP) but I only use private trackers so a dedicated IP is fine and also technically required, so my local seedbox whitebox server connects to my OpenVPN server as an OpenVPN client, and tunnels all traffic over the VPN with an iptables prerouting rule on my public VPS for the traffic on my qbtorrent-nox inbound port to reach my local server.
This way I can run whatever hardware I want in my seedbox and have full control over the hardware while also masking my home IP.
Port forwarding tripled my upload speed. I didn’t really notice a difference on download.
