General

Auf welchen Systemen wird I2P laufen?

I2P is written in the Java programming language. It has been tested on Windows, Linux, FreeBSD and OSX. An Android port is also available.

In terms of memory usage, I2P is configured to use 128 MB of RAM by default. This is sufficient for browsing and IRC usage. However, other activities may require greater memory allocation. For example, if one wishes to run a high-bandwidth router, participate in I2P torrents or serve high-traffic hidden services, a higher amount of memory is required.

In terms of CPU usage, I2P has been tested to run on modest systems such as the Raspberry Pi range of single-board computers. As I2P makes heavy use of cryptographic techniques, a stronger CPU will be better suited to handle the workload generated by I2P as well as tasks related to the rest of the system (i.e. Operating System, GUI, Other processes e.g. Web Browsing).

A comparison of some of the available Java Runtime Environments (JRE) is available here: https://trac.i2p2.de/wiki/java. Using Sun/Oracle Java or OpenJDK is recommended.

Ist die Installation von Java erforderlich, um I2P verwenden zu können?

Während die Haupt-I2P-Client-Implementierung Java erfordert, gibt es mehrere alternative Clients, die Java nicht benötigen.

Was ist eine "Eepseite" ?

An eepsite is a website that is hosted anonymously, a hidden service which is accessible through your web browser. It can be accessed by setting your web browser's HTTP proxy to use the I2P web proxy (typically it listens on localhost port 4444), and browsing to the site.

Was bedeuten die Active x/y Nummern in der Router Konsole?

x is the number of peers you've sent or received a message from successfully in the last minute, y is the number of peers seen in the last hour or so. Try hovering your cursor over the other lines of information for a brief description.

Ist mein Router ein "Exit Node" ins reguläre Internet? Dieses möchte ich nicht.

No. Unlike Tor, "exit nodes" - or "outproxies" as they are referred to on the I2P network - are not an inherent part of the network. Only volunteers who specifically set up and run separate applications will relay traffic to the regular Internet. There are very, very few of these. By default, I2P's HTTP Proxy (configured to run on port 4444) includes a single outproxy: false.i2p. This is run on a voluntary basis by Meeh. There is an outproxy guide available on our forums, if you would like to learn more about running an outproxy.

Ich kann keine normalen Internetseiten über I2P erreichen.

I2P is primarily not intended, nor designed, to be used as a proxy to the regular internet. With that said, there are services which are provided by volunteers that act as proxies to clearnet based content - these are referred to as "outproxies" on the I2P network. There is an outproxy configured by default in I2P's HTTP client tunnel - false.i2p. While this service does currently exist, there is no guarantee that it will always be there as it is not an official service provided by the I2P project. If your main requirement from an anonymous network is the ability to access clearnet resources, we would recommend using Tor.

Ist es sicher, einen Ausgangsproxy zu benutzen?

I2P does not encrypt the Internet, neither does Tor - for example, through Transport Layer Security (TLS). I2P and Tor both aim to transport your traffic as-is securely and anonymously over the corresponding network, to its destination. Any unencrypted traffic generated at your system will arrive at the outproxy (on I2P) or the exit node (on Tor) as unencrypted traffic. This means that you are vulnerable to snooping by the outproxy operators. One way to protect your outproxy traffic against this is to ensure that any traffic that will be handled by the outproxy is encrypted with TLS.

For more information, you may read the Tor FAQ's answer to this question: https://www.torproject.org/docs/faq#CanExitNodesEavesdrop

In addition, you may be vulnerable to collusion between the outproxy operator and operators of other I2P services, if you use the same tunnels ("shared clients"). There is additional discussion about this on zzz.i2p. This discussion has been mirrored on our forums as well.

Ultimately, this is a question that only you can answer because the correct answer depends on your browsing behaviour, your threat model, and how much you choose to trust the outproxy operator.

Ihnen sind manche Inhalte äusserst zuwider. Wie können Sie verhindern, das Sie diese verteilen, speichern oder abfrufen?

I2P is an anonymous network - it is designed to withstand attempts at blocking or censoring of content, thus providing a means for communication that anyone can use. I2P traffic that transits through your router is encrypted with several layers of encryption. Except in the case of a serious security vulnerability (of which none are currently known), it is not possible to know what the contents of the traffic are and thus not possible to distinguish between traffic which one is opposed to or not opposed to. We consider the 3 parts of the question:

  • Distribution
    All traffic on I2P is encrypted in multiple layers. You don't know a message's contents, source, or destination. All traffic you route is internal to the I2P network, you are not an exit node (referred to as an outproxy in our documentation). Your only alternative is to refuse to route any traffic, by setting your share bandwidth or maximum participating tunnels to 0 (see above). It would be nice if you didn't do this, you should help the network by routing traffic for others. Over 95% of users route traffic for others.
  • Storage
    I2P does not do distributed storage of content, this has to be specifically installed and configured by the user (with Tahoe-LAFS, for example). That is a feature of a different anonymous network, Freenet. By running I2P, you are not storing content for anyone.
  • Access
    If there are hidden services which you dislike, you may refrain from visiting them. Your router will not request any content without your specific instruction to do so.

Getting Started

Wie kann ich meinen Browser entsprechend einstellen?

The proxy config for different browsers is on a separate page with screenshots. More advanced configs with external tools, such as the browser plug-in FoxyProxy or the proxy server Privoxy, are possible but could introduce leaks in your setup.

Wie verbinde ich mich mit dem IRC innerhalb von I2P?

A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is installed (see the I2PTunnel configuration page), and is automatically started when the I2P router starts. To connect to it, tell your IRC client to connect to localhost 6668. HexChat-like client users can create a new network with the server localhost/6668 (remember to tick "Bypass proxy server" if you have a proxy server configured). Weechat users can use the following command to add a new network:

    /server add irc2p localhost/6668
  

Wie kann ich meine eigene Eepsite einrichten?

Click on the Website link at the top of your router console for instructions.

Welche Ports werden von I2P genutzt?

The ports that are used by I2P can be divided into 2 sections:

  1. Internet-facing ports, which are used for communication with other I2P routers
  2. Local ports, for local connections

These are described in detail below.

  1. Internet-facing ports
    Note: Since release 0.7.8, new installs do not use port 8887; a random port between 9000 and 31000 is selected when the program is run for the first time. The selected port is shown on the router configuration page.
    OUTBOUND
    • UDP from the random port listed on the configuration page to arbitrary remote UDP ports, allowing for replies
    • TCP from random high ports to arbitrary remote TCP ports
    • Outbound UDP on port 123, allowing for replies. This is necessary for I2P's internal time sync (via SNTP - querying a random SNTP host in pool.ntp.org or another server you specify)
    INBOUND
  2. Local I2P ports, listening only to local connections by default, except where noted:
    PORT PURPOSE BESCHREIBUNG
    1900 UPnP SSDP UDP multicast listener Cannot be changed. Binds to all interfaces. May be disabled on confignet.
    2827 BOB bridge A higher level socket API for clients. Disabled by default. May be enabled/disabled on configclients. May be changed in the bob.config file.
    4444 HTTP proxy May be disabled or changed on the i2ptunnel page in the router console. May also be configured to be bound to a specific interface or all interfaces.
    4445 HTTPS proxy May be disabled or changed on the i2ptunnel page in the router console. May also be configured to be bound to a specific interface or all interfaces.
    6668 IRC proxy May be disabled or changed on the i2ptunnel page in the router console. May also be configured to be bound to a specific interface or all interfaces.
    7652 HTTP TCP event listener Binds to the LAN address. May be changed with advanced config i2np.upnp.HTTPPort=nnnn. May be disabled on confignet.
    7653 UPnP SSDP UDP search response listener Binds to the LAN address. May be changed with advanced config i2np.upnp.SSDPPort=nnnn. May be disabled on confignet.
    7654 I2P Client Protocol port Used by client apps. May be changed to a different port on configclients but this is not recommended. May be to bind to a different interface or all interfaces, or disabled, on configclients.
    7655 UDP for SAM bridge A higher level socket API for clients Only opened when a SAM V3 client requests a UDP session. May be enabled/disabled on configclients. May be changed in the clients.config file with the SAM command line option sam.udp.port=nnnn.
    7656 SAM bridge A higher level socket API for clients Disabled by default for new installs as of release 0.6.5. May be enabled/disabled on configclients. May be changed in the clients.config file.
    7657 Your router console May be disabled in the clients.configfile. May also be configured to be bound to a specific interface or all interfaces in that file.
    7658 Your eepsite May be disabled in the clients.config file. May also be configured to be bound to a specific interface or all interfaces in the jetty.xml file.
    7659 Outgoing mail to smtp.postman.i2p May be disabled or changed on the i2ptunnel page in the router console. May also be configured to be bound to a specific interface or all interfaces.
    7660 Outgoing mail to smtp.postman.i2p May be disabled or changed on the i2ptunnel page in the router console. May also be configured to be bound to a specific interface or all interfaces.
    8998 mtn.i2p-projekt.i2p (Monotone) May be disabled or changed on the i2ptunnel page in the router console. May also be configured to be bound to a specific interface or all interfaces.
    31000 Local connection to the wrapper control channel port Outbound to 32000 only, does not listen on this port. Starts at 31000 and will increment until 31999 looking for a free port. To change, see the wrapper documentation. For more information see below.
    32000 Local control channel for the service wrapper To change, see the wrapper documentation. For more information see below.

Die lokalen I2P Ports und die I2P Tunnel Ports müssen nicht von extern erreichbar sein, *sollten* aber lokal erreichbar sein. Sie können auch weitere Ports für I2P Tunnel Instanzen via http://localhost:7657/i2ptunnel/ erstellen (und damit die Notwendigkeit, diese Ports in der Firewall lokal freizugeben, jedoch nicht von extern, ausser dieses ist so gewünscht).

Zusammengefasst muss kein Port von externen Peers erreichbar sein, falls Sie jedoch in ihrer NAT/Firewall eingehende TCP und UDP Verbindungen auf dem externem I2P Port freischalten, bekommen Sie eine bessere Performance. Auch sollten Sie ausgehende UDP Pakete an externe Peers erlauben (das Blockieren von verschiedenen IPs mit Tools wie PeerGuardian schadet ihrer Performance nur - machen Sie dieses nicht).

Sie vermissen viele Adressen in Ihrem Adressbuch. Was sind gute Subscription Links?

This question can be answered in 3 parts:

  1. My router often displays a message saying "Website Not Found In Addressbook", why do I see this message?

    Human-readable addresses such as http://website.i2p are references to a long, random string known as a destination. These references are registered and stored at addressbook services such as stats.i2p, which is run by zzz. You will often encounter a "b32" address. A "b32" is a hash (specifically, a SHA256 hash) of the destination. This hash is appended with ".b32.i2p" and serves as a convenient way to link to your hidden service, without requiring any registration on an addressbook service.

    It is possible to add subscriptions to your router's configuration which may reduce the frequency of these messages.

  2. What is an addressbook subscription?

    This is a list of files hosted on various I2P websites each of which contain a list of I2P hosts and their associated destinations.

    The addressbook is located at http://localhost:7657/dns where further information can be found.

  3. What are some good addressbook subscription links?

    You may try the following:

Wie können Sie die Webkonsole von anderen Systemen erreichen oder mit einem Passwort absichern?

For security purposes, the router's admin console by default only listens for connections on the local interface. There are two methods for accessing the console remotely:

  1. SSH Tunnel
  2. Configuring your console to be available on a Public IP address with a username & password

These are detailed below:

  1. SSH Tunnel
    If you are running a Unix-like Operating System, this is the easiest method for remotely accessing your I2P console. (Note: SSH server software is available for systems running Windows, for example https://github.com/PowerShell/Win32-OpenSSH)
    Once you have configured SSH access to your system, the '-L' flag is passed to SSH with appropriate arguments - for example:
            ssh -L 7657:localhost:7657 (System_IP)
            
    where '(System_IP)' is replaced with your System's IP address. This command forwards port 7657 (the number before the first colon) to the remote system's (as specified by the string 'localhost' between the first and second colons) port 7657 (the number after the second colon). Your remote I2P console will now be available on your local system as 'http://localhost:7657' and will be available for as long as your SSH session is active. If you would like to start an SSH session without initiating a shell on the remote system, you can add the '-N' flag:
            ssh -NL 7657:localhost:7657 (System_IP)
            
  2. Configuring your console to be available on a Public IP address with a username & password
    1. Open ~/.i2p/clients.config and replace
                      clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
                
      with
                      clientApp.0.args=7657 ::1,127.0.0.1,(System_IP) ./webapps/
                
      where you replace (System_IP) with your system's public IP address
    2. Go to http://localhost:7657/configui and add a console username and password if desired - Adding a username & password is highly recommended to secure your I2P console from tampering, which could lead to de-anonymization.
    3. Go to http://localhost:7657/index and hit "Graceful restart", which restarts the JVM and reloads the client applications
    After that fires up, you should now be able to reach your console remotely. Load the router console at http://(System_IP):7657 and you will be prompted for the username and password you specified in step 2 above if your browser supports the authentication popup.
    NOTE: You can specify 0.0.0.0 in the above configuration. This specifies an interface, not a network or netmask. 0.0.0.0 means "bind to all interfaces", so it can be reachable on 127.0.0.1:7657 as well as any LAN/WAN IP. Be careful when using this option as the console will be available on ALL addresses configured on your system.

Wie können Sie Applikationen von anderen Systemen aus nutzen?

Please see the previous answer for instructions on using SSH Port Forwarding, and also see this page in your console: http://localhost:7657/configi2cp

Ist es möglich, I2P als SOCKS Proxy zu nutzen?

The SOCKS proxy has been functional since release 0.7.1. SOCKS 4/4a/5 are supported. I2P does not have a SOCKS outproxy so it is limited to use within I2P only.

Many applications leak sensitive information that could identify you on the Internet and this is a risk that one should be aware of when using the I2P SOCKS proxy. I2P only filters connection data, but if the program you intend to run sends this information as content, I2P has no way to protect your anonymity. For example, some mail applications will send the IP address of the machine they are running on to a mail server. There is no way for I2P to filter this, thus using I2P to 'socksify' existing applications is possible, but extremely dangerous.

Wenn Sie dennoch mehr Informationen zu der SOCKS Proxy Anwendung haben möchten, gibt es einige hilfreiche Tips auf der SOCKS Webseite.

Wie reseede ich manuell?

Ein I2P-Router muss nur einmal geseedet werden, um dem Netzwerk zum ersten Mal beizutreten. Beim Reseeding werden mehrere "RouterInfo"-Dateien (in einer signierten Zip-Datei gebündelt) von mindestens zwei vordefinierten Server-URLs geholt, die von einem von einer Gruppe von Freiwilligen betriebenen Clearnet-HTTPS-Servern ausgewählt wurden.

Ein typisches Symptom eines fehlgeschlagenen Reseedens ist eine geringe Anzeige der "Bekannten" Peers (in der linken Seite der Router Konsole) (oft weniger als 5) und diese Nummer nicht ansteigt. Dieses passiert, neben anderen Gründen, wenn Ihre lokale Firewall eingehenden Verkehr blockiert oder reseed Anfragen komplett blockiert werden.

Falls Sie hinter einer Firewall oder Filter ihres ISP sind, können Sie folgende manuelle Methode (nicht automatische, technische Lösung) nutzen um dem I2P Netzwerk beizutreten.

Seit Version 0.9.33 können Sie Ihren Router auch aufs Reseeden via eines Proxies konfigurieren. Besuchen Sie http://localhost:7657/configreseed und geben Sie den Proxytyp, Hostname und Port an.

Mit Hilfe einer Reseed Datei dem I2P Netzwerk beitreten.

Bitte kontaktieren Sie einen bekannte, vertrauenswürdigen Bekannten mit einem funktionierenden I2P Router und fragen Sie diesen nach Hilfe beim Reseeden ihres I2P Routers. Fragen Sie nach einer aus dem laufenden Router exportiereten Reseed Datei. Diese Datei sollte unbedingt über einen sicheren Kanal (zB. PGP verschlüsselt mit einem vertrauenswürdigen Schlüssel) versendet werden, damit sie nicht modifiziert werden kann. Die Datei selber ist nicht signiert, bitte akzeptieren Sie diese Datei nur aus vertrauenswürdiger Quelle. Importieren Sie nie eine Reseed Datei wenn Sie nicht ihre Quelle verifizieren können.

So importieren Sie die erhaltende i2preseed.zip Datei in Ihren lokalen I2P Router:

  • Gehen Sie auf http://localhost:7657/configreseed
  • Unter "Manuelles Reseeden aus einer Datei" klciken sie auf "Durchsuchen"
  • Wählen Sie die i2preseed.zip Datei
  • Klicken sie auf "Reseed aus Datei"

Kontrollieren Sie ihr log auf die folgende Nachricht:
Reseed got 100 router infos from file with 0 errors

Eine Reseed Datei verteilen

Sie können ihren lokalen I2P Router nutzen um vertrauenswürdigen Bekannten einen Start ins I2P Netz zu geben.

  • Gehen Sie auf http://localhost:7657/configreseed
  • Klicken Sie auf "Reseed Datei erzeugen" unter "Reseed Daei erzeugen"
  • Senden Sie die i2preseed.zip Datei gesichert zu Ihren Bekannten.

Geben Sie diese Datei keinesfalls an unbekannte Nutzer, da es sensitive, private Daten (100 Router Informationen) ihres I2P Routers enthält! Um ihre Anonymität zu wahren sollten sie ein paar Stunden/Tage warten bevor Sie die Datei weitergeben. Es ist ausserdem empfolen, dieses nur selten zu machen (<2 mal je Woche).

Generelle Hinweise zum Manuellen Reseeden von I2P

  • Publizieren Sie nicht die Reseed Datei oder reichen diese an Freunde eines Freundes weiter.
  • Diese Datei sollte nur für eine geringe Anzahl an Bekannten (<3) genutzt werden!
  • Die Datei ist nur wenige Tage gültig (<20)!

Wie erreichen Sie IRC, BitTorrent oder andere Services im normalen Internet?

Unless an outproxy has been specifically set up for the service you want to connect to, this cannot be done. There are only three types of outproxies running right now: HTTP, HTTPS, and email. Note that there is no SOCKS outproxy. If this type of service is required, we recommend that you use Tor. Please be aware that the Tor project recommends against using BitTorrent over Tor, as there are serious anonymity-related issues associated with doing so.

Ich kann keine https:// oder ftp:// Seiten ü I2P besuchen.

  • HTTPS
    Within I2P, there is no requirement to use HTTPS. All traffic is encrypted end-to-end, any further encryption, e.g. with the use of HTTPS, doesn't create any further anonymity-related benefits. However, if one would like to use HTTPS or has a requirement to do so, the existing default I2P HTTP Proxy has support for HTTPS traffic. Any hidden service operator would have to specifically set up and enable HTTPS access.
  • FTP
    FTP is not supported for technical reasons. There are no FTP "outproxies" to the Internet—it may not even be possible to set up one. Any other kind of outproxy may work if it's set up with a standard tunnel. If you would like to set up some type of outproxy, carefully research the potential risks. The I2P community may or may not be able to help with the technical aspects, feel free to ask. As explained several times above, any existing outproxy isn't a core part of the network. They are services run by individuals and they may or may not be operational at any given time.

Troubleshooting

My router is using a large amount of CPU, what can I do about this?

Es gibt viele Gründe für hohe CPU Last. Hier ist eine Kontrolliste:

  • Java Runtime Environment
    Try to use either OpenJDK or Sun/Oracle Java if it's available for your system. You can check which version of java you have installed by typing java -version at a command/shell prompt. Performance tends to suffer with other implementations of java.
  • File sharing applications, e.g. BitTorrent
    Nutzen Sie einen Bittorrent Klienten über I2P? Versuchen Sie die Anzahl an Torrents oder die Bandbreitenlimits zu verringern, oder schalten Sie diesen komplett aus, um zu sehen, ob dieses hilft.
  • High bandwidth settings
    Are your bandwidth limits set too high? It is possible that too much traffic is going through your I2P router and it is overloaded. Try reducing the setting for share bandwidth percentage on the configuration page.
  • I2P Version
    Stellen Sie sicher, das Sie die aktuellste Version von I2P nutzen um die Vorteile von besserer Performance und weniger Fehlern zu geniessen.
  • Memory allocation
    Has enough memory been set aside for use by I2P? Look at the memory graph on the graphs page to see if the memory usage is "pegged"—the JVM is spending most of its time in garbage collection. Increase the setting wrapper.java.maxmemory in the file wrapper.config.
  • Bursts of high-usage vs. constant 100% usage
    Is the CPU usage simply higher than you would like, or is it pegged at 100% for a long time? If it is pegged, this could be a bug. Look in the logs for clues.
  • Java-related
    You may be using the Java-based BigInteger library instead of the native version, especially if you are running on a new or unusual OS or hardware (OpenSolaris, mipsel, etc.). See the jbigi page for instructions on diagnosing, building, and testing methods.
  • Fremde Tunnel, an denen Sie teilnehmen
    If your native jbigi library is working fine, the biggest user of CPU may be routing traffic for participating tunnels. This uses CPU because at each hop a layer of encryption must be decoded. You can limit participating traffic in two ways - by reducing the share bandwidth on the confignet page, or by setting router.maxParticipatingTunnels=nnn on the configadvanced page.

Ihr Router ist für einige Minuten aktiv und hat keine oder wenige Verbindungen

New installations of I2P carry out the reseeding process automatically, as well as when the number of known peers falls to a drastically low value. If you need to carry out a reseed of your router, please see the reseed instructions.

Mein Router hat sehr wenige aktive Peers, ist das OK?

If your router has 10 or more active peers, everything is fine. The router should maintain connections to a few peers at all times. The best way to stay "better-connected" to the network is to share more bandwidth. The amount of bandwidth that is shared by the router can be changed on the configuration page: http://localhost:7657/config

Meine active Peers / known Peers / Participating Tunnel / Verbindungen / Bandbeite ändern sich stark! Ist irgendwas kaputt?

No, there isn't anything wrong. This is normal behavior. All routers adjust dynamically to changing network conditions and demands. Routers come online and go offline depending on whether the system it is installed on is operational or not, as well as whether there is an available network connection. Your router is constantly updating its local Network Database. Tunnels which your router is participating in expire every 10 minutes and may or may not be rebuilt through your router.

What makes downloads, torrents, web browsing, and everything else slower on I2P as compared to the regular internet?

The encryption and routing within the I2P network adds a substantial amount of overhead and limits bandwidth. We can try to clarify this with the aid of a diagram:

In this diagram, the path that some I2P traffic takes as it travels through the network is traced. A user's I2P router is denoted by the box labeled 'A' and an I2P Hidden Service (for example, the http://stats.i2p website) is labelled as 'B'. Both the client and the server are using 3-hop tunnels, these hops are represented by the boxes labelled 'P', 'Q', 'R', 'X', 'Y', 'Z', 'P_1', 'Q_1', 'R'_1, 'X_1', 'Y_1' and 'Z_1'.

The boxes labelled 'P', 'Q' and 'R' represent an outbound tunnel for A while the boxes labelled 'X_1', 'Y_1', 'Z_1' represent an outbound tunnel for 'B'. Similarly, the boxes labelled 'X', 'Y' and 'Z' represent and inbound tunnel for 'B' while the boxes labelled 'P_1', 'Q_1' and 'R_1' represent an inbound tunnel for 'A'. The arrows in between the boxes show the direction of traffic. The text above and below the arrows detail some example bandwidth between a pair of hops as well as example latencies.

When both client and server are using 3-hop tunnels throughout, a total of 12 other I2P routers are involved in relaying traffic. 6 peers relay traffic from the client to the server which is split into a 3-hop outbound tunnel from 'A' ('P', 'Q', 'R') and a 3-hop inbound tunnel to 'B' ('X', 'Y', 'Z'). Similarly, 6 peers relay traffic from the server to back to the client.

First, we can consider latency - the time that it takes for a request from a client to traverse the I2P network, reach the the server and traverse back to the client. Adding up all latencies we see that:

      40 + 100 + 20 + 60 + 80 + 10 + 30 ms        (client to server)
    + 60 + 40 + 80 + 60 + 100 + 20 + 40 ms        (server to client) 
    -----------------------------------
    TOTAL:                          740 ms

The total round-trip time in our example adds up to 740 ms - certainly much higher than what one would normally see while browsing regular internet websites.

Second, we can consider available bandwidth. This is determined through the slowest link between hops from the client and server as well as when traffic is being transmitted by the server to the client. For traffic going from the client to the server, we see that the available bandwidth in our example between hops 'R' & 'X' as well as hops 'X' & 'Y' is 32 KB/s. Despite higher available bandwidth between the other hops, these hops will act as a bottleneck and will limit the maximum available bandwidth for traffic from 'A' to 'B' at 32 KB/s. Similarly, tracing the path from server to client shows that there is maximum bandwidth of 64 KB/s - between hops 'Z_1' & 'Y_1, 'Y_1' & 'X_1' and 'Q_1' & 'P_1'.

We recommend increasing your bandwidth limits. This helps the network by increasing the amount of available bandwidth which will in turn improve your I2P experience. Bandwidth settings are located on the http://localhost:7657/config page. Please be aware of your internet connection's limits as determined by your ISP, and adjust your settings accordingly.

We also recommend setting a sufficient amount of shared bandwidth - this allows for participating tunnels to be routed through your I2P router. Allowing participating traffic keeps your router well-integrated in the network and improves your transfer speeds.

I2P is a work in progress. Lots of improvements and fixes are being implemented, and, generally speaking, running the latest release will help your performance. If you haven't, install the latest release.

In der Datei wrapper.log sehe ich einen Fehler, der sagt "Protokollfamilie nicht verfügbar" beim Laden der Router Konsole

Dieser Fehler tritt öfters bei Systemen auf, die IPv6 als Default gesetzt haben und Java Software mit Netzwerkfunktionen nutzen. Es gibt ein paar Möglichkeiten, dieses zu lösen:

  • Auf Linux-basierten Systemen verwenden Sie echo 0 > /proc/sys/net/ipv6/bindv6only
  • Suchen Sie folgende Zeilen in der wrapper.config Datei.
    #wrapper.java.additional.5=-Djava.net.preferIPv4Stack=true
    #wrapper.java.additional.6=-Djava.net.preferIPv6Addresses=false

    Wenn diese Zeilen bereits so vorhanden sind, kommentiere sie aus, indem du die "#"s entfernst. Andernfalls füge die Zeilen ohne die '#'s hinzu.
Eine andere Möglichkeit wäre, die ::1 aus ~/.i2p/clients.config zu entfernen

WARNUNG: Damit Änderungen an der wrapper.config wirksam werden, müssen der Router und der Wrapper vollständig gestoppt werden. Ein Klick auf Neustart in der Router-Konsole liest diese Datei NICHT erneut ein! Klicke Herunterfahren, warte 11 Minuten, dann starte I2P neu.

Sind die meisten Eepsites im I2P-Netzwerk nicht erreichbar?

Falls Sie alle Eepsites, die jemals erstellt wurden, betrachten, ja, die meisten sind aus. Benutzer und Eepsites kommen und gehen. Ein guter Startpunkt in I2P ist das Kontrollieren welcher der Eepsites aktiv sind. http://identiguy.i2p.xyz verfolgt den Status aktiver Eepsites.

Warum lauscht I2P auf dem Port 32000 ?

The Tanuki java service wrapper that we use opens this port —bound to localhost— in order to communicate with software running inside the JVM. When the JVM is launched it is given a key so it can connect to the wrapper. After the JVM establishes its connection to the wrapper, the wrapper refuses any additional connections.

More information can be found in the wrapper documentation.

Ich glaube, ich habe eine Fehler gefunden. Wo kann ich diesen melden?

You may report any bugs/issues that you encounter on our bugtracker, which is available over both clearnet and I2P. We have a discussion forum, also available on I2P and clearnet. You can join our IRC channel as well: either through our IRC network, IRC2P, or on Freenode.

Please include relevant information from the router logs page which is available at: http://127.0.0.1:7657/logs. We request that you share all of the text under the 'I2P Version and Running Environment' section as well as any errors or warnings displayed in the various logs displayed on the page.


Ich habe eine Frage!

Great! Find us on IRC:

  • on irc.freenode.net channel #i2p
  • on IRC2P channel #i2p
or post to the forum and we'll post it here (with the answer, hopefully).