The Invisible Internet Project

From i2p on reddit. Link is to an i2p page so start up your i2p instances.

In this tutorial, I will show how you can make your own private XMPP server, where you will have full control of your user data, messages, groups, files, all of that federated over anonymizing networks such as tor and i2p.

The article is in English, don't be fooled by the summary.

From divaexchange:

I2P community related updates:

a) a locally installable I2P(d) testnetwork is available in the public domain. Here is the link to github: https://github.com/h-phil/i2pd-testnet-kubernetes . I2Pd (C++) is supported, I2P java not. The author of the testnet might or might not fix that issue. So: PRs are welcome for those who need Java I2P support. This kurbernetes-based testnet (which scales very well) is a side effect of the I2P de-anonymization study (academic work) which has been finished mid of January 2024 (see below).

b) Independent (of the I2P[d] developers) de-anonymization study (academic research, sponsered by diva.exchange, done at Lucerne University of Applied Science, Switzerland): results in a nutshell "there have been no patterns found, using passive network surveillance technologies, to relate a Lease Set to a Router Info - hence it was not possible to de-anonymize an I2P service provider by just using mass surveillance technology".

Remark 1: the study is NOT trying to identify/exploit bugs within the I2P software to de-anonymize service providers within the I2P network (in this context, this is not interesting for the researchers - the overall I2P architecture is the interesting part).

Remark 2: there are two areas of "I2P de-anonymization" research sponsored by diva.exchange - one is focussing on "taking over I2P tunnel control by harrassing network participants" the other one is focussing on "de-anonymization using network surveillance technologies in combination with pattern recognition".

The study will be published sooner or later on academic channels. To get notified, follow here: https://x.com/@DigitalValueX or https://social.diva.exchange/@social (mastodon)

c) I2P Docker / I2P-SAM news: docker images (https://hub.docker.com/r/divax/i2p) and a complete I2P SAM library (https://github.com/diva-exchange/i2p-sam) are updated regularily. The docker images and the SAM library are used in the academic context. They are well tested and reliable.

​

I am on a tor site and it has 2 links to an i2p site. The first says "I2P [b32]" and has a link of http://acruexirfkgcqhwxyu75v7dtahr3a44hmbfygngsvubmkrbd6axa.b32.i2p/. This link works in my browser configured for i2p. The second link just says "I2P" and has a url of http://mysu.i2p/ which fails to load. Any ideas?

From StormyCloud:

We are thrilled to share our latest development with the community: CheckI2P.com. This tool is designed for anyone using the Invisible Internet Project (I2P) and seeks a fast and reliable way to verify their connection to an I2P Outproxy.

What is CheckI2P.com?

CheckI2P.com is a straightforward web tool that instantly informs you whether your internet traffic is being correctly routed through an I2P Outproxy. When you visit the site, you'll receive one of two messages:

"You are NOT using a known outproxy" – indicating that your current setup is not connected through an I2P Outproxy.

"You are connected to [insert outproxy name]" – confirming that your connection is securely routed through a recognized I2P Outproxy.

Why This Matters

For those not familiar, I2P is a network layer that allows for censorship-resistant, secure, and anonymous communication. Using an Outproxy is crucial for accessing regular websites outside the I2P network.

Contribute to the Project

We are constantly looking to expand our list of recognized outproxies. If you're aware of any reliable outproxies not currently included, feel free to suggest them in the comments. Moreover, for those who are technically inclined, contributions through Pull Requests are greatly appreciated at our GitHub repository: https://github.com/WaxySteelWorm/checki2p.com

Future Plans

Our vision for CheckI2P.com goes beyond its current functionality. We aim to integrate additional tools for testing various I2P functions, thereby making it a comprehensive resource for I2P users. Your feedback on the current iteration and suggestions for future features are immensely valuable to us.

Prowlarr has a setting for per indexer proxy. It seems most people use this for FlareSolverr but it also supports http and socks. I have i2p working and I can set up i2p as a proxy in a browser and everything works. But when I configure it in prowlarr I get an error 500. Has anyone else gotten this to work this way? I've only found a guide for setting up prowlarr with i2p globally but that breaks clearnet trackers.

Another blogpost on i2p and tor. Not bad from what I can tell. The more exposure the better.

So I'm trying to bridge to physical locations together. At one location I control the firewall and at the other I don't. I would normally use Wireguard but its all dynamic IPs so it would break every so often.

My though was to use I2P to create a bridge between the 2 places. I will use 0 hops on each with encrypted lease sets.

Is this a sain setup? What drawbacks will this have and will it be problematic? Also what security should I use for my encrypted lease set? I want only one device to connect and no others.

Edit: I think I'll use i2p for dns

This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network. It contains significant improvements to the Network Database, an essential structure within the I2P network used for discovering your peers.

The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them. This will help the network limit the effect of tunnel spam. It will also help the network heal during and after DDoS attacks.

The NetDb changes also help secure individual routers and the applications that use them. Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router. This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.

Also included are a number of bug fixes and enhancements across the I2PSnark and SusiMail applications.

As usual, we recommend that you update to this release. The best way to maintain security and help the network is to run the latest release.

RELEASE DETAILS

Changes

• i2psnark: Uncomment and fix local torrent file picker
• NetDB: Lookup handler/throttler fixes
• Router: Restructure netDb to isolate data received as a client from data received as a router
• Router: Implement handling and penalties for congestion caps
• Router: Temporarily ban routers publishing in the future
• Transports: Disable SSU 1

Bug Fixes

• Addressbook: Workaround for i2p-projekt.i2p etag bug (Gitlab #454)
• Console: Clear out "proxy must be running" status after success
• Console: Don't lose tabs in log messages
• Console: Fix sidebar not immediately showing results of manual update check
• Console: Fix visibility of radio/checkboxes (light theme)
• Console: Prevent overflow of sidebar status
• Debian: Change JRE dependency order (Gitlab #443, Debian #1024461)
• i2psnark: Increase comment bucket size to reduce duplicates
• i2psnark: Prevent start-all from within search results erroring (Gitlab #445)
• i2ptunnel: Exempt tunnel name from XSS filter (Gitlab #467)
• i2ptunnel: Fix gzip footer check in GunzipOutputStream (Gitlab #458)
• i2ptunnel: Remove nonstandard Proxy-Connection headers (Gitlab #452)
• NTCP2: Fix updating address on transition to firewalled (Gitlab #435)
• SAM: Fix accept after soft restart (Gitlab #399)
• SAM: Reset incoming socket if no subsession is matched (Gitlab #456)
• SSU2: Fix uncaught IAE caused by itags with zero values (Gitlab #415)
• SSU2: Prevent rare IAE in peer test timer (Gitlab #433)
• Susimail: Dark theme fixes
• Susimail: Fix binary content-encoding
• Susimail: Fix incorrect "previous" icons
• Susimail: Fix setting encoding for attachments
• Susimail: Flush output to fix truncated mails
• Sybil: Don't ban NAT64 addresses
• Transport: Fix NPE during soft restart (Gitlab #437)
• UPnP: Fix handing of multiple IGDs
• UPnP: Fix missing port in Host header causing failures on libupnp-based devices

Other

• API 0.9.61
• Translation updates

Full list of fixed bugs

SHA256 Checksums:

d08db62457d4106ca0e36df3487bdf6731cbb81045b824a003cde38c7e1dfa27  i2pinstall_2.4.0_windows.exe
ef5f3d0629fec292aae15d027f1ecb3cc7f2432a99a5f7738803b453eaad9cad  i2pinstall_2.4.0.jar
30ef8afcad0fffafd94d30ac307f86b5a6b318e2c1f44a023005841a1fcd077c  i2psource_2.4.0.tar.bz2
97be217bf07319a50b6496f932700c3f3c0cceeaf1e0643260d38c9e6e139b53  i2pupdate_2.4.0.zip
8f4a17a8cbadb2eabeb527a36389fd266a4bbcfd9d634fa4f20281f48c486e11  i2pupda#**___**

I2P+ is an enhanced version of I2P that aims to deliver a superior user experience. Updated themes, easier to understand configuration and diagnostics, and an enhanced feature set make I2P+ a compelling alternative to the official I2P release. Additionally, I2P+ implements improvements to the router's network performance and, for routers that are firewalled, can significantly increase participating traffic and network responsiveness. Is I2P+ compatible with I2P?

The changes relate to user interaction and enhanced presentation of the console and webapps, in addition to network performance improvements, leaving the underyling crypto untouched, so it remains 100% compatible with I2P. On the network, an I2P+ router will identify as a normal I2P router. Updating from I2P to I2P+, or from I2P+ to I2P, is as simple as providing the router with the relevant update file and restarting. Installation

If you're running a manually installed version of I2P (from the Java installer, not the Easy Installer Bundle, nor a Linux repository or .deb file), updating is as simple as dropping the i2pupdate.zip file into your I2P application folder and restarting the router. Note: Do not extract the zip file, simply copy it to the I2P application folder and restart I2P... I2P will extract the zip automatically and update. (Java 1.8 or later required). For information about migrating from a repo or .deb install, visit the I2P+ site linked below.

To enable updates for I2P+, visit the update page at http://127.0.0.1:7657/configupdate and enable unsigned development updates. The default update address will inform you of release updates, or for development updates (aka rolling release), replace the address with: http://skank.i2p/dev/i2pupdate.zip

Note: If you have installed I2P from the Easy Installer Bundle, this will need to be uninstalled first and your configuration directory renamed or deleted - see the included INSTALL.txt file for more info. New in this release (2.4.0+):

• Complete console and webapp translations for all listed languages
• Optimized and improved Javascript for both the console and I2PSnark
• Improved page rendering for console and webapps
• I2PSnark filter bar rewritten to use search query parameters instead of Javascript
• Additional "Connected" filter option for I2PSnark
• Fix lightbox image display feature in I2PSnark
• Improved rendering times for identicons
• Reverse the order of in-console wrapper logs to match router logs (newest entry first)
• Add a magnet column to I2PSnark's main view with a toggle to switch between magnets and links
• Process tunnel control requests in the Tunnel Manager in situ to avoid a page reload
• Display page load bar when checking for router updates and display latest update info
• Indicate on /jobs when table cells are updated
• Add security and cache-control headers to resources served by I2PTunnel HTTP server when not present
• Improvements to console and webapp themes
• Console logging improvements

Note: Update contains a new GeoIP database and full translations for all available languages. More information

• Please visit: skank.i2p or i2pplus.github.io
• Changelog: skank.i2p/changelog.html or i2pplus.github.io/changelog.html
• Source code is available from: gitlab.com/i2pplus/I2P.Plus or git.skank.i2p/i2pplus/I2P.Plus
• Torrent Pool of the latest releases: tracker2.postman.i2p/index.php?view=TPoolDetail&id=1256

If you're on I2P then these could be added to your list of trackers.

http://i32bdpbyflc5l7ibhqmq7f72gglflrd6sgnmlqj6xsdjis5yjuga.b32.i2p/announce

http://4izytry23uiwxs2epg6swoygyi4vvsd4hwvj5u6onodmoh7gfmha.b32.i2p/announce

Hi ppl, are there Tracker with search function beside postman?

Copied from an excellent post by sugarw0000kie on that other site. All credit for the guide to them.

Finally messed around with this and didn't see much about it, feel free to remove if breaking any rules

For this to work you'll need prowlarr, qbittorrent, and the other arrs (radarr/sonarr/readarr etc) and of course i2p router. (You could just use prowlarr to simplify searching for things without sonarr/radarr integration, then you’d just need prowlarr/qbittorrent with i2p)

In prowlarr, we need to set up proxy through i2p. So go settings-->general--> click enable proxy

​ This seems to work

enter your hostname (default 127.0.0.1) and port 4444 or whatever you have your http proxy set to in your i2p install. Make sure to set the ignored addresses with .com/.net etc (* denotes wildcard), so it won't request non i2p addresses through the router, otherwise i believe it will try to search any of your other indexers through i2p which is probably not good

Now you should be able to add Postman tracker like any other tracker in prowlarr as long as it's able to use your router as the proxy

​ aughta come up like this

From here you will need to make sure you have qbittorrent working with i2p. There is a guide floating around for this but to add to that you'll want to get the lt20 version, as the other one (i believe the default download) does not yet offer i2p support

In your i2p router you'll want to make sure your SAM bridge is enabled. Then in qbittorrent go preferences-->connection and enable i2p and put in your router with hostname and port 7656 (i believe that's the default correct me if i'm wrong)

​

it should look like this, if you don't see this option under "Connection" you probly don't have the lt20 version

Biglybt doesn't seem to have integration with the *arrs, but assuming you have qbittorrent setup with i2p from there it's a matter of going into radarr/sonarr and adding it as a download client like normal.

If you've never done this before, in qbittorrent under Web ui enable the web interface, should be able to leave the ip address blank (or otherwise enter how sonarr/radarr would need to access it) and enter an unused port like 6969. Put in login credentials. go to localhost:6969 or w/e you used and check that you can see the web interface from qbittorrent.

​

what mine looks like

on sonarr/radarr side, go settings-->download client--> and enter the ip address and port you gave it as well as the username/password. Usually helpful to add a category. Hit the test button to ensure it works

​

meanwhile in the *arrs

(If you just want to use prowlarr w/o sonarr radarr integration to the steps are the same to connect qbittorrent, just done in prowlarr itself. It can be used like a search engine along with all of your clearnet torrent/usenet indexers this way)

Hope this helps!

You too can contribute to I2P, fellow anonymity supporter

https://www.ovhcloud.com/en/vps/

Pick Ubuntu 22.04 as your OS and follow the instructions on https://geti2p.net/en/download/debian

You can ssh -L 7657:localhost:7657 ubuntu@yourhostname, login with the password you from the link you got in the email, then open http://localhost:7657 and configure your I2P instance. For the bandwidth, you can enter 12500 up and 12500 down (100Mb/s = 12500 KB/s) with a 90% share (if you aren't using the VPS for anything else).

You can also add more tunnels on http://localhost:7657/configtunnels . For more information on tunnel types (exploratory and client) see https://geti2p.net/en/docs/how/peer-selection .

Hello,

i just setup retroshare with i2p. But currently i have no friends or groups. Is there a special place to find people or do i2p people not use retroshare?

I was wondering why my speed was only about 250KB/s and I think this is why: there simply aren't many high speed nodes in the network!

If you have a VPS sitting around, just spinning, do consider contributing.

With a simple docker-compose

version: "3.5"
services:
    i2p:
        image: geti2p/i2p
        container_name: i2p
        restart: always
        volumes:
            - ./i2pconfig:/i2p/.i2p
        network_mode: host

you can have i2p running in no time. Or follow the official installation instructions

Simply SSH with a local port forwarding to the router console ssh -L 7657:127.0.1.1:7657 $yourHost and open http://localhost:7657/

You can then configure your instance to share bandwidth.

I would expect 40Mb (5MB/s) up and down, but the router is at 1/16 of the possible speed. Is this the max speed?

This is a little guide to show you how to setup a small container dedicated to an i2p router such as i2pd. This allows for a central router for all your clients on your LAN for example.

Read the guide

i2pd Alpine Setup Script

Today qBittorrent launched v4.6.0 which should support experimental i2p mode. I downloaded this version as a Flatpak from Flathub, but at Settings -> Connection there is no option for i2p mode. Only to set up a proxy, but SAM is not available as a proxy method which i2p uses. I also checked with the command "flatpak run org.qbittorrent.qBittorrent --version" that I'm indeed on the right version.

Do you have any ideas or similar issues?

The release of qBittorrent v4.6.0 stable comes with I2P support. While experimental, we can still get a working torrent setup using qBittorrent now. qBittorrent-nox is the Web-UI only version, and currently it does not have configuration settings in the Web-UI for I2P settings. This guide will show you how to setup qBittorrent-nox and manually change the qBittorrent.conf file to allow for I2P torrenting!

Guide can be found here: https://strict3443.codeberg.page/i2p-info/hugo/public/posts/how-to-use-i2p-on-qbittorrent-nox/

qBittorrent Changelog: https://github.com/qbittorrent/qBittorrent/blob/release-4.6.0/Changelog

Largely correct as far as I can tell.

Any support outside of qbitorrent yet? I know it's not FOSS, but I much prefer working in Tixati. Do I need to refamiliarize myself with qbitorrent if I want to try i2p?