Skip to content
e2ret edited this page Aug 31, 2026 · 9 revisions

I2P — Anonymous network

i2p

I2P (Invisible Internet Project) is an anonymous overlay network. Traffic passes through several encrypted layers and intermediate nodes, hiding both the source and the destination.

In NOEMA RNSGate Lite, I2P is used to connect two gateways without public IP addresses. Each gateway gets an address like xxxxxxxx.b32.i2p — an anonymous identifier.

The I2P tab

Shows:

  • i2pd daemon status (ACTIVE / INACTIVE)
  • The gateway's current b32 address
  • Number of active tunnels

Setting up a tunnel

  1. Click SETUP I2P TUNNEL
  2. Wait 2–5 minutes — I2P needs time to stabilize
  3. The b32 address will appear in the field and in the Addresses tab
  4. Share the address with the other gateway's operator

Connecting to another gateway

  1. Get the remote gateway's b32 address
  2. Enter it into the Add to config field
  3. Click ADD TO CONFIG
  4. Click RESTART RNSD (or via System)

The two gateways will then form an encrypted Reticulum tunnel over I2P — anonymously, with no public IPs.

Typical scenario

Two gateways in different cities:

  • Gateway A (Belgorod) — no public IP, behind NAT
  • Gateway B (Moscow) — no public IP, behind NAT

Both get b32 addresses and exchange them. After setup, the gateways connect over I2P and form a single Reticulum network.

File locations

/etc/i2pd/tunnels.d/reticulum.conf   — tunnel config
/var/lib/i2pd/reticulum.dat          — tunnel keys (important for Backup)
/var/lib/i2pd/router.keys            — router keys

⚠️ Important: tunnel keys are included in the Backup (System#backup--restore). The b32 address is preserved when restoring from an archive.

Notes

  • I2P needs 5–10 minutes to stabilize initially after startup
  • Frequent reconnects in the first few minutes are normal behavior
  • Devices with less than 512 MB RAM may experience i2pd instability
  • i2pd logs are available in the Logs tab

Clone this wiki locally