I2P installation is broken due to outdated repository sources

[errantelectron]

The sources list file etc/apt/sources.list.d/i2p.list in the PiNodeXMR repository has not been updated, and seems to overwrite the apt sources for I2P with outdated content any time the user tries to set up I2P integration.

The i2p installation script appears to have been updated in an attempt to fix this, but still uses that out of date file.

Even if the user separately edits their local /etc/apt/sources.list.d/i2p.list or manually adds the up to date sources with sudo apt-add-repository ppa:i2p-maintainers/i2p, attempting to run PiNodeXMR's I2P installation then overwrites outdated content again before it begins - causing the installation to fail (though PiNodeXMR will wrongly report successful installation of I2P).

[shermand100]

Thanks for highlighting this.

I had seen over at the /r/Monero sub on Reddit some renewed recent interest in the I2P implementation with Monero and it's something I'd always supported but not personally used, nor have I asked for any advice with from PiNodeXMR user so I admit this setup menu option had been unattended for some time.

This attached Pull request would be the proposed fix which brings us away from the Debian based install and in-line with what we now use as the Ubuntu Server based OS.

Note it's the Java based I2P as it comes packaged with a super simple to use Web Interface but is a little bulkier as a package at ~250MB, however I stand that PiNodeXMR where possible is to try and be as beginner friendly as possible so the Web UI is welcome rather than a CLI style .config file edit.

I've followed and tested with reference to:
https://geti2p.net/en/download/debian#ubuntu

Steps 1), 2), 3), and at the bottom of the page - Post-install work

The system works, the Web UI configures correctly and I believe the custom etc/apt/sources.list.d/i2p.list is now obsolete and so removed.

As I've done quite a bit of testing with files removed/added, I'd like to take a moment to test this simple install is all that's needed on a clean system. So:

Script:
PPA amends and passes GPG Key check ✅
Installs I2P ✅
dpkg-reconfigure - set memory use, AppArmour ✅
Auto-start on boot ✅
Web UI and setup Wizard reachable on IP/Hostname http://pinodexmr.local:7657/ ✅ - Merge required 2b5b999

[shermand100]

@errantelectron The pull request attached to this issue has a Ubuntu specific installation and setup method that doesn't break repository lists, and keeps same useability and documentation.

Any thoughts or final ideas before merge.
Thanks for highlighting how obsolete the old installer had become.

[errantelectron]

I'm not as knowledgeable about this as one might assume from my initial post (which was the result of a lot of tinkering trying to get I2P configured) but that looks good.

Won't have an opportunity to test it for another day or two, but happy to do that if you want a second person to try it before merging.

[shermand100]

Ok, so I've merged that change into the main. If you want to try it out then just do a PiNodeXMR update from the terminal settings menu (less than 5 mins), then you'll have that new I2P install script.

We can re-open this if it doesn't do as expected.

[errantelectron]

Thanks - that makes it easier to make the changes. Updating now and will report back (forced a full update as the regular update doesn't trigger due to the version number not having been incremented). Given there may be others interested in I2P also I've created a pull request to increment up the version number to enable the standard update approach to work.

[errantelectron]

I think there may still be an issue with the I2P install script, so maybe hold off on merging that version number increase until it's figured out.

After updating PiNodeXMR I've tried uninstalling I2P via apt and manually removing the /home/pinodexmr/.i2p/ directory with the aim of ensuring previous configurations aren't interfering, but on then running the I2P install script I notice the attached error is thrown, and the I2P web console isn't reachable via LAN (when trying port 7657 of either the LAN IP or the pinodexmr.local hostname).

My impression is that it's now succeeding at installing I2P and starting the router, but is failing to configure it for web console access from the LAN.

[shermand100]

Ok, lets have another go...

So my I2P was working but for testing again this morning I've removed it with:

sudo apt remove i2p -y && sudo apt autoremove -y
rm -R /home/pinodexmr/.i2p

I then did a PiNodeXMR update from the terminal settings menu to make sure I have the same I2P installer as the current default with the exact same permissions as you.
Installed I2P again from the terminal settings menu under 'extra network tools' which at the end printed this...

Which is as expected ( the start/stop repetition ) due to the I2P starting on install - the script adds the local access IP and hostname in the installer as below:

	##add lan ip to config (default blocks lan access to web client)
	#This allows access from ip e.g.: 192.168.1.116:7657
	sed -i "/clientApp.0.args*/c\clientApp.0.args=7657 ::1,127.0.0.1,"${DEVICE_IP}" ./webapps/" /home/pinodexmr/.i2p/clients.config.d/00-net.i2p.router.web.RouterConsoleRunner-clients.config
	#This allows access from hostname e.g: http://pinodexmr.local:7657
	echo "routerconsole.allowedHosts=pinodexmr.local" >> /home/pinodexmr/.i2p/router.config

Then the script restarts the router for the changes to take effect, so I would expect yours to have the same repetition in the above black image.

And that was it. From there I went to my Web UI -> I2P tab -> I2P Server Interface button

And was greeted by the welcome screen

[errantelectron]

That looks almost identical to what I had tried, with the one difference that I previously did the forced PiNodeXMR update prior to uninstalling I2P and its associated apt packages rather than afterward.

Repeating in the same order as you I get the same error though, and the I2P web console link remains unresponsive over LAN (with the install script having reported successful completion - for clarity it doesn't hang at the point I've screenshotted).

I suspect that the problem might not lie in the PiNodeXMR code base though, and that perhaps my earlier attempts to get I2P installed may have somehow broken something elsewhere relating to the I2P configuration path.

I'll try a complete fresh reflash of my pi next and then re-attempt, though it's probably going to be a week from now before I get to test that.

[shermand100]

Just a thought...

Did you install I2P under the user 'pinodexmr' when prompted or leave it as the default 'i2pavc'

It may not find it if it left as 'i2pavc'

I setup as detailed here: ( Except I think the default RAM usage is now 256, whatever is default is fine except the username)

https://github.com/shermand100/PiNodeXMR/wiki/i2p-Setup-and-Use

[errantelectron]

I did specify pinodexmr on the most recent few install attempts, but I think I missed it on the very first one (prior to having started this thread IIRC) - if that has created anything persistent somewhere that the later attempts can't overwrite then it might be my problem.

[errantelectron]

Update: Even with a fresh reflash of Ubuntu, fresh install of PiNodeXMR, and making sure to specify the correct username on first running the I2P installer, I still get the very same error.

I can only assume there is some kind of incompatibility in how the I2P packages get configured on the device I'm using (Rock Pi 4).

The default username for radxa's Ubuntu images for this device is "rock" rather than "pi" or "ubuntu", but I believe the only installation problem this should cause is a failure of PiNodeXMR to automatically deactivate the default user account? I'll try another install with the intermediate step of creating a "pi" user account just to be sure though.