Did some work looking at this because I already have I2P running on Win10 (after some work), so have a bit of experience with this thing that’s promising but needs some additional contributors.
Before getting into the steps you’ll need to do to make this work, you should know that at the moment it won’t run with full features(many broken features), but will run.
First, start by downloading the latest tarball and extract as described on this page.
https://geti2p.net/en/download#unix
I found that permissions won’t allow the installer to create necessary directories, so I prepared target install directories as follows
mkdir ~/i2p
mkdir ~/i2p/run
mkdir ~/i2p/run/p
Execute the following command in a normal User console to run the installer, pointing to the first directory created in the previous step
java -jar i2pinstall_0.9.26.jar -console
Now,
you have to edit the file “i2prouter” in the root directory of the i2p app (ie in this example the directory ~/i2p/)
Open the file in a text editor with root permissions, you can use vim or first open a root console and within that root console you can invoke your favorite graphical text editor by exact name (do not use kdesu or gnomesu or similar), can be leafpad, geany, kwrite, kate, etc.
Modify the following line to point to your app install directory
Line 39 edit “I2p_CONFIG_DIR=”/root/.i2p" replacing /root/.i2p with your your app directory which is likely displayed a few lines above "I2P=* yourdirectory* " In my example that would be the full path name /home/username/i2p/
Modify the following lines as follows, the first two edits modify to run the app from within
The following 2 edits modify the TEMP of your app to run in your app directory instead of in a root location
Line 41
Prepend (add to the beginning of the line) a hash (#) to disable
Line 44
Remove the hash (#)
Line 128
Prepend a hash (#) is probably not critical but that line references upstart which only for Ubuntu
I doubt anyone who is reading this should be running SLES or SLED still using the SysVinit system(All openSUSE should ignore this) but those people should inspect and likely enable the special SUSE init configuration in lines 163-178.
OK,
Now, in theory you should be able to run “~/ip2/ip2router start” but you’ll see an error about the java wrapper. Thiinking this is all too strange for default packaging to not include a wrapper for ordinary and common x86/x64 systems, I still followed the steps to create a wrapper with no effect.
So, the proper way to start ip2 should be the following command “.runplain” in my example would be
~/i2p/runplain.sh
And, now the ip2router should be running fine.
If it’s not already open, you should now be able to open a web browser to the following to view the locally running i2p console
http://127.0.0.1:7657/home
Your next step should be to continue to follow the documentation and point your web browser’s proxy settings to
localhost:4444
Consider the optional steps I didn’t do which is to create a non-interactive User account (account which can’t login) and configure it as the runtime User in the i2prouter file. You also will likely have to modify the permissions for the application file tree to enable read/write for this special account. If you’re considering exploring the dark net, you should consider <all> security options.
I’ve found the experience very slow, but I assume it’s YMMV for everyone.
HTH,
TSU