Outdated instructions Great to see them in upstream now.
The main problems this was attempting to solve was to have a preconfigured TBB copy for accessing .i2p domains and other non-clearnet special TLDs and optimizing I2P operation when tunneled over Tor.
There was also the goal of having an I2P GW, but IMO it is too much work for what is likely inferior security.
But the Tor Browser local connection workaround is broken? Does not work for me.
Got some apparmor denied messages. Had to disable apparmor. Probably upstream issue but nobody else run into that yet? No Debian bug report yet. Or I just messed up.
Could you please get the i2p installation instructions back up to speed? @HulaHoop
I tidied up the rest of that page, so it’s just Patrick’s query re: local connection workaround which you can hopefully fix.
For installation steps in Qubes-Whonix, I presume steps 1 - 3 are in the TemplateVM, while the others will be in the AppVM (we’ll need to explicitly define that too).
Yes, sudo apt-get update, sudo apt-get install i2p, sudo dpkg-reconfigure i2p in TemplateVM in Qubes. I would hope that step sudo dpkg-reconfigure i2p isn’t even required anymore now that there is a package from packages.debian.org.
Not working with privoxy either or after tweaking a lot of settings. I’m out of ideas. The connectivity is absolute shit. No tunnels are forming to sustain a healthy connection.
Downloaded sid I2P version (v9.42 instead of v9.38 in Buster stable) (required dependency libjbigi-jni first before installing I2P)
sudo dpkg-reconfigure I2P
couldn’t connect to anything (Nyx logs show “Have tried resolving or connecting to address [scrubbed] at 3 different places. Giving up.”
re-ran sudo dpkg-reconfigure I2P and disable AppArmor setting
service status check on command line shows I2P is running okay
I can see lots of peers etc. but the main error in router config section is “Network ERR-UDP disabled and inbound TCP host/port not set”
They suggest: “You have not configured an inbound TCP with a hostname and port on the Network config page, however you have disabled UDP. Therefore your router cannot accept inbound connections. Please configure a TCP host and port on the Network configuration page or enable UDP”
Played with various I2P router network settings e.g. enable/disable UDP, prefer IPv4 or IPv6, set TCP ports etc. then reset the connection.
But you can never get a connection to work to any I2P site - Tor Browser says “Error connecting to site XYZ. Try again later etc.” Nyx keeps showing the same error “Have tried resolving or connecting to address [scrubbed] at 3 different places. Giving up.” over and over.
Annoying.
Do we have to set up something special in the I2P router network config or something else?
More Tor Browser config tweaks?
Too much clock skew? (they do warn about that needing to be very accurate in their FAQ somewhere - could be the source of the problem)
Maybe we’d have better luck with latest version 9.44 directly from I2P website? But I doubt it.
Doesn’t like something about being tunneled over Tor and/or something in Whonix config.
The website was not reachable. The website is offline, there is network congestion, or your router is not yet well-integrated with peers. You may want to retry.
EDIT:
It works!
After changing:
network.proxy.share_proxy_settings true
user@host:~$ sudo sh /usr/share/anon-apps-config/usr++bin++download-secbrowser
/usr/share/anon-apps-config/usr++bin++download-secbrowser: 10: /usr/share/anon-apps-config/usr++bin++download-secbrowser: source: not found
I hope we can get this scripted and have I2P and a configured privoxy included OOTB to transform TBB into a I2P Browser on demand in a dedicated snapshot.