What is I2P? The Expert Guide to Anonymous P2P Networks

Published: August 9, 2026 | Reading Time: 25 minutes | Category: Anonymous Networking & Privacy

Executive Summary

I2P (Invisible Internet Project) is a decentralized, anonymous overlay network that enables secure peer-to-peer communication. Unlike Tor, which focuses on anonymous clearnet access, I2P creates a self-contained darknet optimized for internal services, hidden websites (eepsites), and anonymous applications.

Key Differentiator: While Tor routes traffic through the clearnet, I2P keeps everything inside its encrypted network, making it significantly more secure for internal communications but less versatile for regular web browsing.

Part 1: Understanding I2P Architecture

What Makes I2P Unique

FeatureI2PTor
Primary UseInternal P2P networkClearnet access
RoutingGarlic routingOnion routing
Network ScopeSelf-containedExit nodes to clearnet
PerformanceFaster for internal servicesSlower, more hops
User Base~30,000 users2+ million users
Hidden ServicesNative (eepsites)Supported (.onion)
P2P SupportExcellentProblematic
DevelopmentCommunity-drivenGovernment-funded

Core Technical Components

1. Garlic Routing: The Foundation

Garlic routing is I2P's enhanced version of onion routing:

Traditional Onion Routing (Tor):Data → Encrypt Layer 3 → Encrypt Layer 2 → Encrypt Layer 1 → Transmit

Each node removes one layer, revealing next destination

Garlic Routing (I2P):

Multiple Messages (Cloves) → Bundle Together → Encrypt as Single Packet

Multiple layers of encryption + message bundling for traffic analysis resistance

Key Advantages:

  • Message bundling: Multiple messages travel together, obscuring patterns
  • Unidirectional tunnels: Separate paths for sending and receiving
  • Short-lived tunnels: 10-minute lifespan reduces correlation attacks
  • Packet switching: Messages split and reassembled like internet traffic

2. The NetDb (Network Database)

The NetDb is I2P's distributed directory system:

ComponentFunctionStorage
RouterInfoRouter capabilities, keys, contact infoFloodfill routers
LeaseSetCurrent tunnel endpoints for destinationsDistributed
Floodfill RoutersSpecial nodes that store NetDb data~100+ active

How Lookup Works:

1. Client needs to contact eepsite "example.i2p"2. Queries NetDb for LeaseSet of destination

3. Receives current inbound tunnel gateway

4. Establishes outbound tunnel to gateway

5. Communication begins through tunnels

3. Tunnel System

I2P uses unidirectional tunnels—separate paths for inbound and outbound traffic:

Outbound Tunnel (Client → Destination):Client → Router A → Router B → Router C → Destination Gateway

Inbound Tunnel (Destination → Client):

Destination → Router X → Router Y → Router Z → Client Gateway

Tunnel Characteristics:

  • 2-4 hops per tunnel (configurable)
  • 10-minute lifespan (automatic rotation)
  • Multiple tunnels active simultaneously
  • Each tunnel has unique 36-byte tunnel ID

4. Peer Selection and Profiling

I2P's peer profiling system selects optimal routes:

MetricMeasurementPurpose
SpeedBytes/sec throughputPerformance optimization
CapacityTunnel acceptance rateLoad balancing
ReliabilitySuccess/failure ratioStability
IntegrationNetwork participation timeTrustworthiness

Selection Process:

  • Profile all known peers continuously
  • Categorize into tiers (fast, high capacity, standard)
  • Random selection from appropriate tier
  • Weighted by performance metrics
  • Continuous re-evaluation

Part 2: I2P vs Tor - Technical Deep Dive

Fundamental Architectural Differences

Threat Model Comparison

ThreatI2P DefenseTor Defense
Global passive adversaryGarlic routing + message bundlingThree-hop circuits
Traffic analysisPacket switching, cover trafficCircuit padding (limited)
Timing attacksUnidirectional tunnelsSingle circuit bidirectional
Sybil attacksPeer profiling + integration timeDirectory authorities
Network surveillanceSelf-contained networkExit node exposure

Performance Characteristics

MetricI2PTor
Latency500ms-2s (internal)2-10s (to clearnet)
Throughput20-100 KB/s10-50 KB/s
Tunnel build time1-5 seconds1-3 seconds
Concurrent circuitsMultiple tunnelsSingle circuit
ScalabilityLimited by peer countHigh (relays)

When to Use I2P vs Tor

Choose I2P When:

  • Hosting anonymous services (eepsites)
  • P2P file sharing (torrents)
  • Anonymous messaging/email
  • Building decentralized applications
  • Evading Deep Packet Inspection (DPI)
  • Long-term anonymous operations

Choose Tor When:

  • Accessing clearnet websites anonymously
  • Bypassing censorship (public websites)
  • One-time anonymous browsing
  • Whistleblowing (SecureDrop)
  • Accessing .onion services
  • User-friendly anonymity

Part 3: Setting Up I2P (2026 Guide)

Installation Methods

Method 1: Official I2P Router (Java)

System Requirements:

  • Java 17+ (OpenJDK recommended)
  • 512MB RAM minimum (2GB recommended)
  • 100MB disk space

Installation Steps:

bash

# Linux/macOSwget https://download.i2p2.de/releases/2.12.0/i2pinstall_2.12.0.jarjava -jar i2pinstall_2.12.0.jar

# WindowsDownload installer from i2p.net

Run i2pinstall_2.12.0.exe

Promotional banner

Post-Installation:

1. Start I2P router service2. Access console: http://127.0.0.1:7657

3. Wait for "Network: OK" status

4. Configure bandwidth settings

5. Set up browser proxy

Method 2: I2Pd (C++ Implementation)

Advantages:

  • Lower resource usage
  • Faster startup
  • No Java dependency

Installation:

bash

# Debian/Ubuntusudo apt-get install i2pd# Arch Linuxsudo pacman -S i2pd# macOSbrew install i2pd# Build from sourcegit clone https://github.com/PurpleI2P/i2pd.gitcd i2pdmkdir build && cd buildcmake ..makesudo make install

Configuration:

bash

# Start servicesudo systemctl start i2pd# Enable auto-startsudo systemctl enable i2pd# Access console: http://127.0.0.1:7070

Method 3: Docker Deployment

yaml

# docker-compose.ymlversion: '3'services: i2p: image: geti2p/i2p:latest container_name: i2p-router ports: - "7657:7657" # Router console - "4444:4444" # HTTP proxy - "4445:4445" # HTTPS proxy - "7656:7656" # SAM bridge volumes: - ./i2p-config:/var/lib/i2p environment: - I2P_BANDWIDTH=500000 # 500 KB/s

Browser Configuration

Firefox Setup

Step 1: Install I2P Button Extension

1. Download from addons.mozilla.org2. Install I2P Button extension

3. Configure to use local I2P router

Step 2: Manual Proxy Configuration

1. Settings → Network Settings2. Manual proxy configuration

3. HTTP Proxy: 127.0.0.1, Port: 4444

4. HTTPS Proxy: 127.0.0.1, Port: 4445

5. Check "Proxy DNS when using SOCKS5"

6. No proxy for: localhost, 127.0.0.1

Chromium/Chrome Setup

Using Command Line:

bash

# Launch with I2P proxychromium --proxy-server="http://127.0.0.1:4444" \ --proxy-bypass-list="localhost,127.0.0.1"

Using Extension:

1. Install Proxy SwitchyOmega2. Create I2P profile

3. Set HTTP proxy: 127.0.0.1:4444

4. Set HTTPS proxy: 127.0.0.1:4445

5. Switch to I2P profile when browsing

Verifying Your Setup

Test Connections:

1. Access router console: http://127.0.0.1:76572. Check "Network" status shows "OK"

3. Visit stats.i2p (network statistics)

4. Access i2p-projekt.i2p (project site)

5. Test eepsite browsing

Expected Results:

  • Router console loads immediately
  • Network status: "OK" or "Firewalled" (acceptable)
  • Eepsites load within 5-30 seconds
  • Bandwidth usage visible in console

Part 4: Exploring the I2P Network

Essential Eepsites (I2P Websites)

EepsiteAddressPurpose
I2P Projecti2p-projekt.i2pOfficial project site
I2P Forumi2pforum.i2pCommunity support
Statsstats.i2pNetwork statistics
NotBobnotbob.i2pEepsite uptime tracker
Identiguyidentiguy.i2pIdentity tools
Pastebinpaste.idk.i2pAnonymous pastebin
Searchlegwork.i2pI2P search engine

Anonymous Email: I2P-Bote

Features:

  • Serverless email system
  • End-to-end encryption
  • No email server required
  • Stores messages in DHT

Setup:

1. Install I2P-Bote plugin2. Generate email identity

Promotional banner

3. Share address: [email protected]

4. Send/receive through I2P network

Anonymous Messaging

ApplicationTypeFeatures
I2P-MessengerInstant messagingEnd-to-end encrypted
Tahoe-LAFSFile storageDistributed cloud
SyndieForumsDecentralized
I2P-IRCChatAnonymous IRC

P2P File Sharing

I2PSnark (Built-in BitTorrent):

Features:- Anonymous torrent client

- Built into I2P router

- No external IP exposure

- Trackerless operation support

Access:

1. Router console → I2PSnark2. Add torrent file or magnet link

3. Downloads through I2P tunnels

4. Seeding continues anonymously

Part 5: Hosting Eepsites

Creating Your Own Hidden Service

Step 1: Generate Destination

Via Router Console:

1. Router console → Hidden Services Manager2. Click "Create New Hidden Service"

3. Choose service type: HTTP

4. Generate new destination

5. Note the .i2p address

Via Command Line:

bash

# Generate destination keysi2prouter keygen mysite

# Output: mysite.i2p (hostname)# mysite.priv (private keys)

Step 2: Configure Web Server

Using Built-in Server:

1. Router console → Hidden Services2. Select your service

3. Set local port (e.g., 8080)

4. Configure document root

5. Start service

Using External Server (Apache/Nginx):

nginx

# Nginx configurationserver { listen 127.0.0.1:8080; server_name localhost; root /var/www/i2p-site; index index.html; # Security headers add_header X-I2P-Location http://yoursite.i2p;}

Connect to I2P:

1. Hidden Services Manager → Add Service2. Name: MySite

3. Destination: Auto-generate or import

4. Target: 127.0.0.1:8080

5. Start tunnel

Step 3: Register Human-Readable Address

Jump Services:

Submit your base32 address to:- stats.i2p (address book)

- identiguy.i2p

- no.i2p

Users can then access via:

http://yoursite.i2p (instead of long base32)

Eepsite Security Best Practices

PracticeImplementationPurpose
Separate identityUnique destination per siteCompartmentalization
No server logsDisable access logsNo evidence trail
HTTPS via I2PSelf-signed certificatesEnd-to-end encryption
Content Security PolicyStrict CSP headersXSS protection
Resource isolationDedicated VM/containerContainment

Part 6: Advanced I2P Configuration

Bandwidth Optimization

Router Configuration:

Settings → Bandwidth:- Share percentage: 50-80%

Promotional banner

- Inbound burst: 500000 (500 KB/s)

- Outbound burst: 500000 (500 KB/s)

- Inbound limit: 300000 (300 KB/s sustained)

- Outbound limit: 300000 (300 KB/s sustained)

Impact Assessment:

SettingNetwork ContributionPersonal Performance
10% shareMinimalFastest
50% shareGoodBalanced
80% shareExcellentSlower
100% shareMaximumSignificant impact

Tunnel Configuration

Default Settings:

  • Inbound tunnels: 2-3
  • Outbound tunnels: 2-3
  • Hop count: 2-4
  • Length variance: Enabled

High-Security Configuration:

Inbound tunnels: 5Outbound tunnels: 5

Hop count: 4

Length variance: Enabled

Exploratory tunnel timeout: 10 minutes

High-Performance Configuration:

Inbound tunnels: 2Outbound tunnels: 2

Hop count: 2

Length variance: Disabled

Exploratory tunnel timeout: 5 minutes

Bridge/Outproxy Setup

Warning: Outproxies reduce anonymity. Use only when necessary.

Configuration:

1. Router console → Outproxies2. Add trusted outproxy address

3. Configure for specific destinations

4. Monitor traffic patterns

Part 7: Security Considerations & Threats

Known Attack Vectors (2026)

1. Deanonymization Attacks

Academic Research Findings:

  • 2025-2026: Multiple papers on I2P deanonymization
  • Attack vectors: Timing analysis, traffic correlation
  • Success rate: 60-80% under specific conditions

Mitigation:

- Regular tunnel rotation (built-in)- Cover traffic generation

- Multiple concurrent tunnels

- Avoid long-lived connections

2. Sybil Attacks

Attack Method:

  • Attacker runs many malicious routers
  • Attempts to control tunnel paths
  • Correlates traffic patterns

I2P Defenses:

- Peer profiling system- Integration time requirements

- Performance-based selection

- Floodfill router diversity

3. Network Partitioning

Risk: Adversary isolates target from network

Detection:

- Monitor router count in NetDb- Check for sudden peer loss

Promotional banner

- Verify floodfill connectivity

- Test multiple eepsite access

Operational Security

Identity Compartmentalization

Best Practices:

1. Separate I2P router per identity2. Unique browser profile per service

3. Different eepsite for each purpose

4. No cross-contamination of data

5. Regular destination rotation

Traffic Pattern Analysis Resistance

TechniqueImplementationEffectiveness
Cover trafficBuilt-in paddingMedium
Variable timingRandom delaysHigh
Message bundlingGarlic routingHigh
Tunnel rotation10-minute lifespanHigh
Multiple pathsConcurrent tunnelsMedium

Part 8: I2P Applications & Use Cases

Use Case 1: Anonymous Blogging

Setup:

1. Create eepsite destination2. Install lightweight CMS (Grav, Hugo)

3. Configure Tor-like mirror (optional)

4. Publish via I2P only

5. No server logs enabled

Advantages:

  • No domain registration
  • No hosting provider
  • No payment trail
  • Resilient to takedown

Use Case 2: Secure File Sharing

Tools:

  • Tahoe-LAFS: Distributed storage
  • I2PSnark: Anonymous torrents
  • Syncthing-I2P: Encrypted sync

Workflow:

1. Encrypt files locally2. Upload to Tahoe-LAFS grid

3. Share capability string

4. Recipients download via I2P

5. Decrypt with shared key

Use Case 3: Anonymous Communication

Secure Chat Setup:

1. Install I2P-Messenger2. Generate chat identity

3. Exchange addresses out-of-band

4. Communicate through I2P tunnels

5. Enable OTR or Signal protocol

Use Case 4: Censorship Circumvention

In Restrictive Countries:

1. Use obfuscated I2P transport2. Bridge through friendly routers

3. Access blocked content via eepsites

4. Mirror clearnet sites internally

5. Distribute content via I2P

Part 9: Troubleshooting Common Issues

Problem: "Network: Firewalled"

Causes:

  • Router behind NAT
  • Firewall blocking ports
  • UPnP disabled

Solutions:

1. Enable UPnP on router2. Forward ports 7654-7664 TCP/UDP

3. Configure manual port forwarding

4. Use SSU address detection

5. Accept "Firewalled" status (still functional)

Problem: Slow Eepsite Loading

Diagnosis:

Check router console:- Tunnel build success rate

- Network participation level

- Bandwidth allocation

- Peer count (should be >100)

Optimization:

1. Increase bandwidth share2. Reduce tunnel hop count

3. Wait for network integration (24-48 hours)

4. Check for ongoing network attacks

5. Verify system resources (RAM/CPU)

Problem: Cannot Access Clearnet

Explanation:
I2P is designed for internal network use only.

Solutions for Clearnet Access:

Option 1: Use Tor Browser for clearnetOption 2: Configure I2P outproxy (not recommended)

Option 3: Run both I2P and Tor simultaneously

Option 4: Use VPN for clearnet, I2P for internal

Part 10: The Future of I2P

Development Roadmap (2026)

FeatureStatusExpected
QUIC transportTesting2026 Q3
Restricted routesDevelopment2026 Q4
LS2 (LeaseSet 2)DeployedActive
NTCP2 transportDeployedActive
SSU2 transportTesting2026 Q2
Mobile optimizationsOngoingContinuous

Emerging Threats

Quantum Computing:

  • Current encryption: ECDSA, ElGamal
  • Post-quantum algorithms under evaluation
  • Migration plan in development

Network Attacks:

  • Increasing sophistication of deanonymization
  • DDoS against floodfill routers
  • Sybil attacks with cloud infrastructure

Comparison with Newer Networks

NetworkArchitectureMaturityUse Case
I2PP2P garlic routingMature (20+ years)Anonymous services
TorOnion routingMatureClearnet access
FreenetDistributed storageMatureContent storage
LokinetOnion routingGrowingSpeed-focused
NYMMixnetNewMetadata protection

Quick Reference: I2P Commands

Essential Ports

PortServiceAccess
7657Router consolehttp://127.0.0.1:7657
4444HTTP proxyBrowser proxy
4445HTTPS proxyBrowser proxy
7656SAM bridgeApplications
7658I2PSnarkhttp://127.0.0.1:7658
7667I2P-BoteEmail client

Configuration Files

FileLocationPurpose
router.config~/.i2p/Router settings
clients.config~/.i2p/Client tunnels
i2ptunnel.config~/.i2p/Server tunnels
hosts.txt~/.i2p/Address book

Final Assessment

Who Should Use I2P?

Ideal Users:

  • Privacy researchers and journalists
  • Whistleblowers needing long-term anonymity
  • Developers building anonymous applications
  • P2P file sharing enthusiasts
  • Censorship circumvention activists
  • Security-conscious individuals

Not Recommended For:

  • Casual users needing simple web browsing
  • Those requiring clearnet access
  • Users needing high bandwidth (streaming)
  • People wanting plug-and-play solutions

Security Rating

AspectRatingNotes
Anonymity★★★★☆Strong for internal network
Usability★★★☆☆Requires technical knowledge
Performance★★★☆☆Slower than clearnet
Resilience★★★★★Decentralized, hard to block
Ecosystem★★★☆☆Smaller than Tor

Tags: #I2P #InvisibleInternetProject #AnonymousNetworking #GarlicRouting #Eepsites #Privacy #Darknet #P2P #CensorshipResistance #2026Guide

This guide is for educational purposes. Always comply with local laws regarding network usage and content access.