I’ve been using i2p - but now that FreedomBox has removed i2p I’m having trouble getting this sorted. I’d like to recreate the FreedomBox experience for that app which was really great.
Problem Description
This all started with a recent update taking some additional steps with i2p removal from FreedomBox. I was no longer able to access the FreedomBox console at http://freedombox:7657/.
I can see that /usr/share/freedombox/etc/apache2/conf-available/i2p-freedombox.conf is removed and the symlinks in /etc/apache2/conf-available and /etc/apache2/conf-enabled point to the missing file.
What I’d like to do is get copies of the relevant and deleted Freedombox configurations and use those to get i2p working well as it was.
Thus far I have the /usr/share/freedombox/etc/apache2/conf-available/i2p-freedombox.conf file from an older release, but I’m wondering how to find the other modifications FreedomBox did for i2p.
I’m up and running again - only missing the i2p link on the FreedomBox page, but I can type the url freedombox/i2p.
If you are installing i2p on FreedomBox you can use the debian packages distributed from the i2p project.
Follow the installation instructions
note random router port in /var/lib/i2p/i2p-config/router.config
add that port number to your external firewall exceptions (and never share this port number which can be used to identify you)
read the i2p FAQ which contains the port numbers used by i2p - you set these up on your internal firewall
This next step seems to be the key. Once you do this you can access the console from a client on the internal network. After this step, you just need to fix up the settings in the i2p console.
remove the symlink /etc/apache2/conf-available/i2p-freedombox.conf if it’s there
Thanks Joseph for the detailed howto. I was thinking about setting this up for a while now but never got the time. May I ask what use cases you have for this app?
Mainly to see if it works and if I can figure it out. You can proxy http through it while proxying https through Tor. I donate some bandwidth to Tor and i2p.
The i2pd planned replacement looks easier to use in some ways. There is a lot of configuration and you can end up breaking i2p.
I am for anything that avoids the big-tech panopticon.
I’m all with you. Have you heard of https://autonomi.com ? Is just took of after 18 years of development and to me it looks like it could become the killer app for freedombox.
i havent had a deep look into it but phrases like “tokens” and “distributed file systems” may not be as innocent as they seem. there are several alternative “systems” to the mentioned autonomi out there with some allegations as to the “system owning the users data” vs the “users data owning the system”. you may also find citings to possible illegal data/information also stored in these technologies where more naive users are not aware and become a tool to them.
dont take my word for it, but id approach it with more caution.
Tahoe-LAFS was part of FreedomBox until recently. I believe this uses i2p. A user shares storage capacity but does not have access to the specific content they help store on their own hardware. Their own content is accessible but not stored in a place they could identify. Interesting, and could create risk to the user in some circumstances.
As far as I understand it the data is fragmented into many many pieces, encrypted and distributed automatically within the system so there is not one file hosted entirely on one system. Like some kind of distributed self-repairing RAID. (Btw. it was called MaidSafe during the development phase)