Today we announce that we have completely removed all traces of disks being used by our VPN infrastructure!

  • Eager Eagle
    link
    fedilink
    English
    21 year ago

    In other words, it’s (basically) impossible for you to send the torrent data to someone else.

    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.

    • @Azzu@lemm.ee
      link
      fedilink
      11 year ago

      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’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

        • @Azzu@lemm.ee
          link
          fedilink
          01 year ago

          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.

          • I know a bit about NATs, or how I like to call it, LAN, basically. But if you don’t even have a NAT to begin with and are directly connected (to your modem), then you don’t even need to open a port. Easy peasy