Then you can register a “domain” on reg.i2p with something like yourname.i2p as well.
Then you can register a “domain” on reg.i2p with something like yourname.i2p as well.
You can try using BiglyBT on android following these instructions: https://github.com/BiglySoftware/BiglyBT/wiki/I2P#user-content-biglybt-i2p-and-android
Otherwise, I’d suggest using a desktop to run i2psnark, BiglyBT, or qBittorrent and use i2pd along with those clients.
Script was fixed and now correctly copies the reseed certificates from the repo to the data directory. Running the script on a fresh alpine container now results in a working i2pd router with no config necessary. This fixes the “Firewall Status: Unknown” issue.
Can your container reach the internet? If you shell into your container can you ping
anything outside your network?
Step 5 from the guide shows how to test if i2pd is running on your Alpine container. If you are using i2pd on another machine, similar commands will work as well.
For the Alpine Container:
ps
command to see if the i2pd program is runningservice i2pd status
to see that status. Ex. * status: started
ip -4 a
and navigate to the i2pd web console at http://:7070
That is i2p-java and i2p+ only. i2pd is only the router which is why it is so small and fast.
Here is a relevant guide: https://geti2p.net/en/about/browser-config
For the IP address, just put in your container’s IP address instead of 127.0.0.1
You can use one i2pd router for many clients/services, as long as your device can handle it.
https://geti2p.net/en/docs/how/threat-model#sybil
Good write-up from the I2P team on this topic. Page includes other attack vectors as well.
This is a good point. I also feel like private trackers are meant for people who actually seed content they download, and just have good intentions to help share content. This also comes with hardware requirements (disk space) sometimes that not everyone has.
Here is an ansible role you can use to deploy i2pd to linux servers and such: https://codeberg.org/systemfailure.net/ansible_i2pd. Otherwise, on most distros the i2pd package should be able to be installed from the package managers in the terminal.
Yes, I did exactly this when I2P support was first in beta. I have a docker stack with Gluetun as my network for all my *arr containers and I was able to still point my qBittorrent to my i2pd router and it worked just fine.
It is experimental indeed. While it “works”, it is no where near the reliability and efficiency of other I2P torrent clients like I2Psnark or BiglyBT, both of which are Java based.
The most known outproxy: https://stormycloud.org/i2p-outproxy/
That is the lacking area. There needs to be a development in the area of DHT crawlers and indexers to help find torrents on I2P like how btdigg works, but for I2P torrents. Hopefully one day.
Yes, absolutely. I have a VPS that runs a i2pd router and I can set my clients to point to my VPS and I am able to use the I2P network. In doing so, I had to make sure I forwarded the correct ports on my VPS so that it would reach the i2pd application. I will do a write up soon.
From my experience, some popular I2P torrents have gotten up to 1 MB/s download, but I usually average around 200 KB/s. While it is not blazing fast, it does provide a good deal of anonymity for everyone involved with the torrent.
Also, you can lower the anonymity and increase speeds by reducing the number of hops from 3 to 2 or 1. You can choose how “anonymous” you’d like to be while torrenting, at the cost of speed.
Guide for Linux: https://strict3443.codeberg.page/i2p-info/hugo/public/posts/how-to-use-i2p-on-qbittorrent-nox/
You can install i2pd with sudo apt install i2pd
and then point your services towards your i2p router (Ex. 127.0.0.1) and you are good to go.
The I2P network thanks you.
https://geti2p.net/en/download for the java version, which comes with extra apps. Otherwise, you can go to https://i2pd.website/ for the C++ version which is much lighter and you can just point your browser/torrent clients at the i2p router and you are good to go.