Gnoppix I2P Daemon

i2pd (I2P Daemon) is a lightweight C++ implementation of the I2P (Invisible Internet Project) client. I2P itself is a decentralized, anonymous peer-to-peer network designed to protect online privacy.

What it is used for: It routes your traffic through a global volunteer network, hiding your true IP address and location. Users rely on it for secure messaging, anonymous file-sharing, and hosting or browsing hidden internal websites (called “eepsites”) away from surveillance or censorship.

Why it is good: I2P provides extreme anonymity using end-to-end encryption and “garlic routing.” The i2pd version specifically is highly favored because, unlike the original client, it doesn’t require Java. It is faster, consumes far less CPU and memory, and removes unnecessary bloat, making it perfect for running securely on low-power devices like standard home routers or a Raspberry Pi.

---

1. Verifying and Managing the Service

i2pd runs as a system daemon on Gnoppix. Because it is already installed, you can manage its state using standard systemd commands.

Check Service Status

To verify that the daemon is active and running correctly:

sudo systemctl status i2pd

You should see active (running) in the output.

Starting and Stopping

If you ever need to manually toggle the service:

# Start the daemon
sudo systemctl start i2pd

# Stop the daemon
sudo systemctl stop i2pd

# Restart the service (required after editing configurations)
sudo systemctl restart i2pd

---

2. Accessing the Web Console

i2pd features a built-in web management interface to monitor router performance, active tunnels, and network integration.

• Web Console Address: Open your web browser and navigate to http://127.0.0.1:7070

💡 Important Note on Reseeding: When the service is freshly started or restarted, it undergoes a “reseed” process to securely find and connect to network peers. Check the Network Status on the console main page. It may initially show Testing or Offline, but will transition to OK within a few minutes once it securely integrates into the distributed network.

---

3. Configuring Your Browser for I2P (.i2p sites)

To browse deep-web eepsites (URLs ending in .i2p), your web browser must route traffic through the local i2pd HTTP proxy. By default, this proxy listens on 127.0.0.1 at port 4444.

Recommended Method: Dedicated Browser Profile (Firefox / LibreWolf)

To protect your privacy and isolate your identities, it is highly recommended to use a dedicated browser profile or a specific browser instance exclusively for I2P traffic.

1. Open your browser’s Preferences/Settings and search for Network Settings.
2. Click Settings… to open the connection parameters.
3. Select Manual proxy configuration.
4. Configure the following fields:

• HTTP Proxy: 127.0.0.1
• Port: 4444

5. Check the box for “Also use this proxy for HTTPS” (or mirror the settings into the SSL Proxy fields).
6. Ensure that the No Proxy for box contains 127.0.0.1, localhost to maintain access to your local Web Console.
7. Click OK to apply.

Alternative Method: Pattern-Based Routing (FoxyProxy Extension)

If you prefer to use a single browser instance for both normal web traffic and I2P, install the FoxyProxy Standard extension and set up a conditional rule:

• Proxy Type: HTTP
• IP Address: 127.0.0.1
• Port: 4444
• URL Pattern: *.i2p (This triggers the proxy only when attempting to resolve an I2P address).

---

4. Validating the Setup

Once your browser is configured and the i2pd console status reads OK, verify your connection by loading an internal resource or directory:

• Project Landing Page: http://i2pd.i2p
• Identiguy (Addressbook helper): http://identiguy.i2p
• Postman Torrent Tracker: http://tracker2.postman.i2p

---

5. Configuration and Advanced Tunnels

Advanced network infrastructure, anonymous hosting, and custom tunnels are handled in the /etc/i2pd/ directory:

• /etc/i2pd/i2pd.conf: Main operational configuration. Manages bandwidth allocations, proxy ports, daemon log verbosity, and security flags.
• /etc/i2pd/tunnels.conf: Used to define application-specific inbound and outbound hidden services. This file is where you configure private endpoints, local IRC servers, or host local static sites hidden completely behind the I2P network layer.

Always issue a sudo systemctl restart i2pd after modifying configuration parameters.

---