Due to circumstances beyond my control, my ability to communicate about release has been severely limited this quarter. However, work is progressing essentially on schedule, major changes are in, bugs are being fixed, and release will happen on October 20th as planned last month.

Thanks for your patience, Idk

Using 2.13.0-0-win(on win7), it reads jetty.xml on the same folder which i2p.exe exist.
//I installed program on custom folder.
//I copy back config on appdata\Local\i2peasy but it still don't use this folder.

and copy config/eepsite to upper folder still not work. It don't show red logs anymore but jetty still don't start. (because the flag icon on tunnels don't show)

If I have tunnels configured in both /var/lib/i2pd/ and in /etc/i2pd/ which takes precedent? They are different and there is overlap in only one entry - for port 4448. i2pd console does not show this many tunels though - can it be that both are getting read?

I2P is a Peer 2 peer network It needs people like you to work. If you dont enable port forwarding you cant properly contribute to I2P because users can’t connect to you directly. If you forward your ports I2P will become a faster and lower latency network.

If you can’t forward ports because youre behind CGNAT contact your internet provider and try to get IPv6. Even that alone would be a big contribution to I2P.

If that isnt possible too get a VPN that supports port forwarding (thats what i did)

sharing is caring.

I was in a workshop where we played with i2p and it seems the traditional way to use i2p is to run a router on localhost, and have your app use the router via the SAM protocol.

Running the router adds a lot of friction, especially on mobile. I realized that we can just connect to a remote, possibly shared router.

What are the trade-offs here? Can I simply share my router with friends?

I want to ask everyone, before touching i2p and other privacy projects or realizing changes to my own privacy issues, has my privacy already been leaked?

Hello, I've just discovered I2P and after using it a bit, I wanted to know if, like on Tor, there are wikis that list websites

My old post here https://www.reddit.com/r/i2p/comments/1pxv52a/instruction_how_to_create_secret_tunnel_inside/ was deleted by reddit as well as my other posts on Reddit and more important my own subreddit too. By the way I try to restore knowledge for all our community reposting from my logs. If something happens again with this post, feel free to post this instruction by yourself, I don't need glory or anything like this keeping this text under my name.

Here is the instruction how to create SECRET tunnel between computers, computer and phone, phone and phone.

I didn't find posts about this topic here. This instruction will explain how to create secret i2p tunnel between server(computer with Linux) and client(Android phone) for all people and for myself so I can access to it from anywhere in case I have new phone/laptop or purged all data on it for crossing the state borders.

Firstly, you need to have binaries on server from there github.com/PurpleI2P/i2pd-tools/ You can build them and save. And for sure you should have already installed i2pd on your computer and phone.

Let's start create a secret tunnel:

1. Now we generate file of secret tunnel for server(computer with Linux):

./keygen yourserver.dat 11

1. Copy this file to i2pd folder on server(computer with Linux):

sudo cp yourserver.dat /var/lib/i2pd/

1. Now we should find destination address for client(Android phone) config:

./keyinfo -b yourserver.dat (we should save address in the string which starts "b33 address:" for step 6)

1. Now we should find public and private keys for server and client configs:

./x25519 (save both strings, we will need them later in step 5 and 6)

1. Now we create config for server(computer with Linux) in tunnels.conf file located in /etc/i2pd/tunnels.conf

[anynameforserverconfig]

type = server

host = 127.0.0.1

port = 22 (for example we create a secret i2p tunnel for ssh service, so we chose port 22)

inport = 22666 (can be any number, just remember to use the same number in client config too)

inbound.length = 1 (1 for faster speed, for more anonymous traffic choose 2,3, etc)

outbound.length = 1 (1 for faster speed, for more anonymous traffic choose 2,3, etc)

inbound.quantity = 4

outbound.quantity = 4

inbound.backupQuantity = 2 (reduce traffic when inactive)

outbound.backupQuantity = 2 (reduce traffic when inactive)

i2cp.reduceOnIdle = true

keys = yourserver.dat

signaturetype = 11

i2cp.leaseSetType = 5

i2cp.leaseSetAuthType = 1

i2cp.leaseSetClient.dh.001 = anyname:publickey (insert here public key from step 4)

1. Now we create config for client(Android phone) in file which should be copied to /sdcard/i2pd/tunnels.conf on Android phone:

[anynameforclientconfig]

type = client

host = 127.0.0.1

port = 22666 (same number as in server config, so your ssh client should use port 22666 for connection)

inbound.length = 1 (1 for faster speed, for more anonymous traffic choose 2,3, etc)

outbound.length = 1 (1 for faster speed, for more anonymous traffic choose 2,3, etc)

inbound.quantity = 4

outbound.quantity = 4

inbound.backupQuantity = 2 (reduce traffic when inactive)

outbound.backupQuantity = 2 (reduce traffic when inactive)

i2cp.dontPublishLeaseSet = true

destination = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.b32.i2p (insert address saved from step 3)

keys = yourclient.dat

i2cp.leaseSetPrivKey = privatekey (insert here private key from step 4)

1. Now restart i2pd on server(computer with Linux), wait for 5-10 minutes, restart i2pd on client(Android phone). All should work now.

Signing the outer layer of an encrypted LeaseSet needs a key blinded from the destination's signing key for each day, which offlinekeys cannot produce. b33offlinekeys derives that material offline, once per day of the batch, and appends it to a normal offline-signed key file. The router gets a file it can publish with for the whole batch, and the destination's signing key never leaves the offline machine.

I’m curious if anyone here has ever tested a DC++ client and hub entirely over I2P.

I’ve started working on a fork of existing DC++ client and hub projects with the goal of making them I2P-only. The idea is to block normal clearnet connections completely and make setup as simple as possible.

Before I spend too much time on it, I’d like to know if anyone thinks this is actually useful or if there are technical reasons why DC++ is a poor fit for I2P.

EDIT

AirDC++ and Luadch are communicating over real I2P through SAM, with separate i2pd instances on each node. Hub connections work, chat works, search works, file lists work both ways, and real file transfers work in both directions.

I’ve also tested larger ISO transfers and verified the files with SHA-256 afterwards.

The Windows client is currently keeping its DC traffic on loopback and letting i2pd handle the actual external traffic. I’ve tested things like killing i2pd in the middle of a transfer and trying normal clearnet hub addresses, and so far the client has failed closed instead of falling back to normal TCP/UDP.

There’s still work left: a few more fail-closed tests, hostile/malformed peer data testing, GUI cleanup, packaging, and a proper security review of the I2P-specific changes.

The final goal is basically: install it, start it, connect to an I2P DC hub. No port forwarding, UPnP, SOCKS or manual I2P setup.

Estimated time to a decent public PoC on github: around 3 weeks.

for unrelated reasons, I switched to a distro based on debian 13, and I immediately couldn't install the repository required to do the debian install in the documentation like I could in the other distro (devuan 6), so I went ahead and installed from the jar file, and now I can't connect to any eepsites whatsoever. Librewolf displays "server not found" upon attempting to access any eepsite, and so does firefox. I believe my ports are set up right since I sure didn't touch anything since installing i2p, and the router has been running for at least 45 minutes, though it took far less time in previous installations.

I will say that I am in fact firewalled, however my firewall of choice (OpenSnitch) isn't blocking anything right now. Should be noted that it still says I'm firewalled.

Any help would be greatly appreciated

i spent one year in prison with no internet access, was I2Pd(I2P for Android) messenger built withing this period of time?

What I mean about AI has more to do with AI being contained to a sandbox that can someone hack into other parts of the internet through various small cracks and I wonder if I2P is entirely separate from the normal internet where it's immune to such problems.

Is there any plan to make an i2p browser for android similar to tor browser for android

hey guys! i've been trying to get xmpp over i2p to work. i've followed the official i2pd docs, and while i can message the users within the server i make, i can't connect to other darknet servers (i installed mod_darknet).

i created an issue here: https://issues.prosody.im/2009

if anybody has any idea what's going on, please let me know! are other people's prosody over i2p setups working? what steps did you take?

edit: My issue now is that I can host from the original machine and access the eepsite on my new machine just fine, but I'm unable to do the reverse of that because it seems like the localhost on my other computer isn't accessible and brings me to a 404 page, even on the machine I'm hosting it from, and both while the webserver is running as well as while it's not. When accessing the local webserver from the new machine prior to this transfer of files, it brought me to the help page with no issue. I figure it's not directly related to the filesystem but it's beyond me what's going on. If it wasn't a firewall issue before, I'm not sure why it would be now.

so I think I definitely fucked up. I'm in the process of switching to linux (devuan 6 to be specific) and I was getting i2p up and running and accessing my eepsite from my windows computer that I'm hosting it on, but in the process of moving the files over I replaced the entire eepsite directory in my linux distro (which was, in hindsight, not smart) and now it seems like my eepsite is only accessible through my other computer. Even if I host the webserver on my other computer and try to connect to it on linux, it gives me a 503 error. On my linux install, there is a series of critical errors relating to the Jetty webserver and how it couldn't find a log directory. On my windows 10 machine I fixed this by moving the eepsite folder around but I have no such luxury on my linux machine. The files in the entire .i2p/eepsite directory are identical to on windows, though, which seemed to be the case before I unwisely copy-pasted the entire directory instead of just the eepPriv.dat file and the docroot stuff like I maybe should have done. I'm thinking I gotta figure out how to completely redo this entire installation on my linux system but I don't really have the knowledge to do that. Any help would be greatly appreciated. I'm running java i2p on both machines.

I’m working on an idea for a communication app that is intentionally very different from Discord, Messenger, etc. The goal is a very lightweight P2P app with no accounts, usernames, permanent rooms, chat history, databases, or cloud infrastructure. Text would come first, with voice potentially added later. Ideally, the app would keep almost everything in RAM and disappear when the session ends.

The interesting part is connecting two people without a middleman. For example, Alice opens the app and generates a temporary connection invitation, then sends it to Bob through whatever external channel they already use, such as WhatsApp, Signal, Messenger, or email. The connection information would not be sent as plain text, but the cryptographic side is a separate topic. What I’m trying to understand first is: **what is the minimum information actually needed for Bob’s computer to establish a direct connection to Alice’s computer?** Is it simply an IP, port, protocol, etc., or does it depend on the network situation?

The main reason I want to avoid a middleman is that I don’t want the communication to depend on infrastructure controlled by the app developer. Ideally, after the initial exchange, it would simply be Alice’s computer ↔ Bob’s computer, with no server carrying their messages or storing anything. I know NATs, firewalls, private IPs, and other networking issues make this difficult, so I’m interested in understanding where truly serverless P2P works and where it becomes impossible without some intermediary.

**TL;DR:** I want to build an extremely lightweight, ephemeral P2P chat app with no accounts, history, or central servers. Users exchange temporary connection information through an external channel, then the two computers try to connect directly. I want to understand the networking required to make this work without a middleman.

I plan to host an online chess tournament on the I2P network that allows computer assistance and features long time controls (given the high latency); it will be live-streamed, and the winner will earn a "GM" title displayed on the tournament website until the next event—I will go ahead with it if there is sufficient support.

I'm out of ideas. I tried Oracle. Open source Java. I tried uninstalling and installing the latest version. I tried updating after that- but every time I try to install I2P, I get the same error.

Does anyone know how to get passed this? At this point, I think there's just something critically wrong with the newest version of I2P's Windows installer. Does anyone have a link for older versions (as in, compatible with Windows)?

Any help is appreciated.

FIXED: It seems that newer versions of I2P's installer aren't compatible with Java 8 (free version). I downloaded an open-source java 26 from Adoptium- and i2p installed just fine.

So I'm currently trying to setup the sideband app on my pc and on my android phone., I have i2p installed on the PC and i2pd installed on the Android phone, sideband is installed on both.

sideband works fine over the Wi-Fi as expected, but the intention is to use it from the phone while on mobile data or other Wi-Fi networks.

so far I can't seem to get the i2p network to send the message over the data connection. I'm wondering if anyone has any insight into setting this up as so far it seems to be going over my head.

I can see the connections making SAM tunnels in the router consoles

The PC sideband keeps switching it i2p B32 address on ever restart and the android one isn't. I'm not sure if it should be static or changing honestly.

I was hoping to get the respect b32 for each reticulum session for sideband and use them as peers to try to direct the network but I can't seem to get the pc b32 to stay put after restart and I'm having a hard time finding where to put there peer in on the android app once it is a consistent b32.

Sorry if I don't know what I'm talking about very clearly, I only dove into this a few days ago and I'm very much a noob at this.

The pc i2p has been up for 40+ hrs while the android i2pd has been active for 18 hours+ so far.

Thank you to anyone you has any idea how to help.

**UPDATE**

editing the Advanced RNS configuration under utilities seems to have allowed me to input the b32 address into the android sideband app, just added an i2p interface block and peer.

**UPDATE**

So I finally got around to testing the last change, and it turns out it works. sideband is now routing the traffic over i2p, works with messages nicely and low rez pictures , high rez will take several minutes (probably 2-5) for a 700KB image so, definitely don't expect a lot out of it. but I knew that going in.

Still don't know if I locked down the b32 of the PC SIdeband app but if its not it means I'll just have to update the peer if Sideband restarts. I may end up moving it over to a Reticulum Daemon if I can find one so I don't have to worry about sideband closing and taking Reticulum with it.

hi im just trying to to the IRC (irc://127.0.0.1:6668/i2p) and librewolf keeps saying that the address is restricted and i was wondering how i could fix this to get to irc. i have tried making it an exception but that didnt work. im on debian13.