Skip Navigation

Stop relying on VPNs - Just use your computer with i2p

After the Mullvad fiasco I decided to stop using VPNs all together, since port forwarding is always going to be a problem on all of them, if you read the reasons why Mullvad had to shut down that service.

There is a better way using i2p which conceals your IP and makes it impossible for anyone to know what or if you're downloading at all! No DMCA notices, no problem.

I wrote this small guide to another comment and figured I'd share it in its own post since I'm seeing so many people ask for VPN recommendations.

So there are 2 main implementations of i2p. First is the main Dev’s Java client here https://geti2p.net/en/download

The other is i2pd, which is C++.

I use the Java one personally but both would work. Someone posted back on reddit a guide on /r/i2p for qbittorrent, which is what I use now for this too. The guide was shared as a public torrent you can download with this info hash: 3f1d51095f9b116739172c1bced149acf2b10692

Use that hash with any of the various public trackers and you should be able to download that guide.

But if you just want a basic setup, that Java client comes with i2psnark, which is a Bittorrent client already setup.

The only other thing you want to do is go and search the biggest tracker for stuff, which is called PaTracker, Postman’s tracker. http://tracker2.postman.i2p, only accessible from i2p itself, which you’ll need to have setup and running first to view.

This tracker needs more seeders and uploaders in general, and by improving those things service for everyone is better. So the more the merrier.

Thanks! Feel free to ask any questions, there also might be other people who use i2p now for torrenting. I'm sure they'll help too.

138 comments
  • Can you go a bit more into detail what it actually is, what are its advantages and disadvantages and how it works? I find it weird that people are still paying for VPNs if the superior solution that consists of just running this program existed this whole time, there's gotta be a catch that you're not mentioning. What or who exactly guarantees anonymity and safety if using this tool?

    • I did explain in another comment some general information about I2P. The one where I mention how it is a darknet but is much different than Tor.

      The reason many more people don't use it yet is because it is hard to setup. That's pretty much it. Similar to lemmy or other things that exist it is just difficult to get people using it unless it is significantly easier to use.

      However, recently things have gotten easier. The dev for i2p has included an easy windows installer for i2p that should make this much better for most users. So some development has happened there.

      Also just recently qBittorrent included support for I2P in their latest release. Before that, only 2 Bittorrent clients existed. Now we're up to 3.

      The biggest advantage is that you don't need to spend money anymore for a VPN. Or any money for a seedbox either if you have a home computer you can just leave up to seed for you.

      The biggest disadvantage is the hard setup and (so far) lack of torrent availability. More stuff is getting added all the time but we need more scene groups adding their releases to i2p (cross-seeding).

      • The biggest advantage is that you don't need to spend money anymore for a VPN

        Unless you use it for accessing and switching to and from Canadian/UK Netflix or something like that on a Roku or Firestick, I presume.

  • Huh, I've been using a VPN for torrent without setting up any kind of port forwarding! Can someone explain why you might want to do this?

    • Port forwarding, which Mullvad was allowing until recently, allows other people to connect to your bittorrent client that is downloading/seeding torrents. This makes it easier for you to find others who can either help you download, or seed for other users in the network.

      Basically it improves download speeds and allows you to easily upload to everyone else.

      • I see, thanks for clarifying! Even without port-forwarding, I'm able to make some connections. Is there just a more limited set of destination IPs I'm able to connect to? What dictates whether or not I'm able to connect?

  • Thanks for the info. Although this can't really replace VPNs for my specific use-cases, this is still very useful info to have just in case. Good to know there are alternatives. Thanks also for including the info hash for the guide.

  • PSA: qbittorrent has early access (still in development) for native i2p torrenting. I recommend waiting for that to be officially released

  • I'm looking up I2P vs VPN and people are saying that I2P cannot replace VPN but I fail to understand why. Can I get some more insight to that?

    • I2p is a closed network where everyone participates and using cryptography packets are encrypted so so only the destination can reason them. All packets are sent through short lived tunnels which are connections of various nodes in the network that change at every so often.

      You traffic never hits the main internet. Its a full darknet with a torrent network system , email, websites, private encrypted messaging and more built on top of it.

      So they are all encrypted. Nobody knows the IP of anyone else

    • I think the only use-case maybe not covered is finding torrents that aren't uploaded to the I2P tracker yet. They need to be cross-seeded from people who originally uploaded them or from people downloading them from the clearnet to be available.

      An example of this is anime. There is significantly less anime available on i2p currently than there are on sites like nyaa.si. People can cross-seed these torrents to make them available on i2p. I do that, for instance. But other than that I can't think of any other use case that isn't covered.

  • Has anyone tried to use this with Docker and Raspberry Pi? It doesn't appear to work for me: i2p_1 | standard_init_linux.go:219: exec user process caused: no such file or directory which I think is probably an architecture error. I saw somewhere on Reddit someone was working on an Arm64 docker, but can't find the post now.

  • Can you port forward with i2p?

    • Yes. When you setup I2P, if you are on a home router with NAT, you setup port forwarding for I2P to get through. I believe it supports UPnP as well, which would circumvent this need.

      You don't need to configure anything else for being connectable from the wider network. The torrent clients remain connectable allowing you to easily seed.

138 comments