- cross-posted to:
- technology@lemmy.ml
- technology@lemmy.world
- hackernews@derp.foo
- cross-posted to:
- technology@lemmy.ml
- technology@lemmy.world
- hackernews@derp.foo
Today we announce that we have completely removed all traces of disks being used by our VPN infrastructure!
They’re amazing. I don’t torrent anymore so I’ll definitely be renewing.
What speaks against torrents with mullvad?
No port forwarding.
What do you mean? Is that needed for torrenting?
I have been using mullvad for a month and have 2 tb of Linux isos, should I expect a call from someone?
The BitTorrent protocol basically works like this when you download a torrent:
As soon as you have something downloaded, you become a client on the list of the tracker that theoretically has the torrent available for others. So you would become the “client being asked” of step 3 as well.
But how can you be asked? In a P2P networking context, you can only “be asked” if you have a port open that allows connections to it. Otherwise it’s as if you gave people your home adress but your mailbox has a hole on the bottom that leads directly to the garbage can beneath it, so all mail is immediately lost. Completely unusable.
In other words, it’s (basically) impossible for you to send the torrent data to someone else. You’re a leecher, someone that doesn’t give back to others. If everyone would act like you, torrents wouldn’t work at all.
I have been seeding until I reach a 3 ratio, so am I doing so through my real ip?
Is it visible to copyright holders?
I did bind qbittorrent to the mullvad interface so there is no doubt I am using the VPN, the question is how is it possible that I am reaching a 3 ratio when I shouldn’t be able to seed at all?
Found this apparently other people are seeding as well
I’ve been downloading and seeding ever since too. People are dismissing / moving away from mullvad for nothing.
That’s why I said (basically). If another user has a port open and you connect to them through their open port, a bidirectional connection gets established and then you can also upload. But if the other user also didn’t have a port open, then BitTorrent wouldn’t work. You rely on other people to have ports open, if everyone was using mullvad, then it would stop working.
That clarifies the whole thing, thanks
I don’t know how (in)accurate this description is, but I’ve been seeding hundreds of GB since Mullvad dropped port fwd. Same for the old times when I didn’t bother using a VPN, I never had to enable port forward in my router for it to work.
that’s so weird, that only one of two people need to have an open port. So the person with the closed port can still establish a connection, both upload AND download. However, this process stops the moment the other person closes his port, then NO connection whatsoever can be established? So we’re gonna pretend this makes sense? Or is it about initiating a connection which requires an open port? That’d make a bit more sense
You could read a bit about NAT, which your router does, if you want to know more. But yes, of course only the initiation requires an open port, otherwise like you said, it doesn’t make sense. As soon as a connection is established your router knows where packets should be sent and an “open” port is not necessary.
Isn’t this what STUN is for?
It’s not that simple. Who hosts that server? Which torrent clients implemented support for it? What about symmetric NATs?
In short: no. In long: read up on it yourself.
deleted by creator
Removed by mod