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.
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.
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.
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:
Run ps command to see if the i2pd program is running
Run service i2pd status to see that status. Ex. * status: started
Find your container’s local IP address with ip -4 a and navigate to the i2pd web console at http://:7070
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.
I'll check out MuWire, was unaware that it used DHT.
Also, I am just saying that tracker2.postman.i2p is the only torrent directory we have currently, and its best way to find and advertise torrents for others. Trackers (where your client announces to) are helpful to finding peers of the same torrent.
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.
What I mean is if I create a new torrent of Big Buck Bunny with a InfoHash of b1946ac92492d2347c6235b4d2611184 for example, no one will find my torrent by searching for "Big Buck Bunny". Unless I post this hash somewhere, advertising "Hey, this torrent is Big Buck Bunny" like what 1337x and other torrent sites do, you won't "find" it. Basically, we have to use a torrent indexer like tracker2.postman.i2p to search the metadata and find torrents we want. If that makes sense.
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.
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.
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.
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.
Update 2023-10-26
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.
Update 2023-10-26
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
pinganything 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:
pscommand to see if the i2pd program is runningservice i2pd statusto see that status. Ex.* status: startedip -4 aand navigate to the i2pd web console athttp://:7070That 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.
It would be nice to have qBittorrent auto add I2P trackers to all torrents to help cross-seed them.
I'll check out MuWire, was unaware that it used DHT.
Also, I am just saying that tracker2.postman.i2p is the only torrent directory we have currently, and its best way to find and advertise torrents for others. Trackers (where your client announces to) are helpful to finding peers of the same torrent.
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.
What I mean is if I create a new torrent of Big Buck Bunny with a InfoHash of b1946ac92492d2347c6235b4d2611184 for example, no one will find my torrent by searching for "Big Buck Bunny". Unless I post this hash somewhere, advertising "Hey, this torrent is Big Buck Bunny" like what 1337x and other torrent sites do, you won't "find" it. Basically, we have to use a torrent indexer like tracker2.postman.i2p to search the metadata and find torrents we want. If that makes sense.
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.