General

Sur quels systèmes I2P peut-il fonctionner ?

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.

Est-il exigé d’installer Java pour utiliser I2P ?

Tandis que la mise en œuvre principale du client I2P exige Java, il existe plusieurs clients de substitution qui n’exige pas Java.

Qu’est ce qu’un « site eep » ?

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.

Qu’est-ce que les nombres « Actifs x/y » signifient dans la console du routeur ?

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.

Mon routeur est-il un « nœud de sortie » vers l’Internet ordinaire ? Je ne veux pas qu’il le soit.

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.

I see IP addresses of all other I2P nodes in the router console. Does that mean my IP address is visible by others?

Yes, and this is how a fully distributed peer-to-peer network works. Every node participates in routing packets for others, so your IP address must be known to establish connections.

While the fact that your computer runs I2P is public, nobody can see your activities in it. You can't say if a user behind this IP address is sharing files, hosting a website, doing research or just running a node to contribute bandwidth to the project.

Je ne peux pas accéder aux sites de l’Internet ordinaire par I2P.

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.

Peut-on utiliser un mandataire sortant en toute sécurité ?

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.

Je m’oppose à certains types de contenus. Comment puis-je éviter d’en distribuer, d’en stocker ou d’y accéder ?

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

Comment puis-je configurer mon navigateur ?

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.

Comment puis-je me connecter à IRC dans 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
  

Comment puis-je mettre en place mon propre site eep ?

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

Quels ports I2P utilise-t-il ?

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 DESCRIPTION
    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.

Les ports locaux d’I2P et les ports d’i2ptunnel n’ont pas besoin d’être accessibles par des machines distantes, mais *devraient* être accessibles localement. Vous pouvez également créer des ports supplémentaires pour les instances d’i2ptunnel sur http://localhost:7657/i2ptunnel/ (et devrez aussi configurer votre pare-feu pour qu’il vous permette l’accès local, mais pas l’accès distant, à moins que vous ne le souhaitiez).

Donc, pour résumer, rien ne doit être accessible par des pairs distants non sollicités, mais si vous pouvez configurer votre traduction d’adresses réseau ou votre pare-feu pour autoriser les UDP et TCP entrants pour le port sortant, vous obtiendrez de meilleures performances. Vous aurez aussi besoin d’être en mesure d’envoyer des paquets UDP sortants à des pairs distants arbitraires (bloquer des IP au hasard avec quelque chose comme PeerGuardian vous pénalise, ne le faites pas).

Il me manque beaucoup d’hôtes dans mon carnet d’adresses. Y a-t-il de bons liens d’abonnement ?

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:

Comment puis-je accéder à la console Web à partir de mes autres machines ou la protéger par mot de passe ?

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.

Comment puis-je utiliser des applications de mes autres machines ?

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

Est-il possible d’utiliser I2P en tant que mandataire SOCKS ?

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.

Si vous souhaitez malgré tout plus d’informations sur l’application de mandataire SOCKS, vous trouverez des conseils utiles sur la page de SOCKS.

Comment puis-je réensemencer manuellement ?

Un routeur I2P n’a besoin d’être ensemencé qu’une seule fois, pour se joindre initialement au réseau. Le réensemencement consiste à obtenir plusieurs fichiers « RouterInfo » (regroupés en un fichier zip signé) d’au moins deux URL de serveur prédéfinies choisies dans un groupe de serveurs HTTPS du réseau visible exploités par des bénévoles.

Un symptôme habituel d’un réensemencement échoué est l’affichage d’une valeur très petite (souvent moins de 5) qui n’augmente pas par l’indicateur « Connus » (dans la barre latérale gauche de la console du routeur). Cela peut se produire, entre autres, si votre pare-feu local limite le trafic sortant ou si la demande de réensemencement est complètement bloquée.

Si vous vous trouvez derrière le pare-feu ou le filtre d’un FAI, vous pouvez utiliser la méthode manuelle suivante (solution technique non automatisée) pour vous joindre au réseau I2P.

À partir de la version 0.9.33, vous pouvez aussi configurer votre routeur pour passer par un mandataire pour le réensemencement. Allez sur http://localhost:7657/configreseed et configurez le type de mandataire, le nom d’hôte et le port.

Se joindre au réseau I2P en utilisant un fichier de réensemencement

Veuillez contacter un ami connu, de confiance, qui utilise un routeur I2P fonctionnel et demandez-lui de vous aider à réensemencer votre routeur I2P en vous envoyant un fichier de réensemencement exporté à partir de son routeur I2P fonctionnel. Il est essentiel que le fichier soit échangé par un moyen de communication sécurisé, chiffré par exemple, afin d’éviter les altérations externes (signature, chiffrement et vérification PGP avec une clé publique fiable). Le fichier même n’est pas signé et n’acceptez que des fichiers provenant d’amis en qui vous avez confiance. N’importez jamais un fichier de réensemencement si vous ne pouvez pas en vérifier la source.

Pour importer le fichier i2preseed.zip reçu dans votre routeur I2P local :

  • Rendez-vous sur http://localhost:7657/configreseed
  • Sous « Réensemencement manuel à partir d’un fichier », cliquez sur « Parcourir... »
  • Sélectionnez le fichier i2preseed.zip
  • Cliquez sur « Réensemencer à partir d’un fichier »

Vérifiez la présence du message suivant dans le journal :
Reseed got 100 router infos from file with 0 errors

Partager un fichier de réensemencement

Pour les amis de confiance, vous pouvez utiliser votre routeur I2P local pour les aider à démarrer :

  • Rendez-vous sur http://localhost:7657/configreseed
  • Sous « Créer un fichier de réensemencement », cliquez sur « Créer un fichier de réensemencement »
  • Envoyez le fichier i2preseed.zip à votre ami de façon sécurisée

Ne révélez en aucun cas ce fichier à des utilisateurs inconnus, car il contient des données confidentielles délicates (100 RouterInfo) provenant de votre propre routeur I2P ! Afin de protéger votre anonymat, vous pourriez patienter, au hasard, pendant quelques heures ou jours avant de partager le fichier avec votre ami de confiance. Il est aussi recommandé d’utiliser cette procédure avec modération (< 2 par semaine).

Directives générales pour le réensemencement manuel d’I2P

  • Ne publiez pas publiquement le fichier de réensemencement ni ne partagez ces fichiers avec l’ami d’un ami !
  • Ce fichier ne devrait être utilisé que pour un nombre très limité d’amis (< 3) !
  • Le fichier n’est valide que pendant quelques jours (< 20) !

Comment puis-je accéder à IRC, BitTorrent ou autres services sur l’Internet ordinaire ?

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.

Je ne peux pas accéder aux sites https:// ou ftp:// par I2P.

  • 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?

Une utilisation élevée de l’UCT peut avoir plusieurs causes possibles. Voici une liste de contrôle :

  • 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
    Faites-vous tourner un client BitTorrent sur ​​I2P ? Essayez de réduire le nombre de torrents, les limites de bande passante ou encore de le fermer complètement pour voir si cela remédie à la situation.
  • 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
    Assurez-vous d’utiliser la dernière version d’I2P pour profiter de performances améliorées et des correctifs de bogues.
  • 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.
  • Tunnels participants
    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.

Mon routeur est en ligne depuis plusieurs minutes, mais n’a pas ou très peu de connexions

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.

Mon routeur a très peu de pairs actifs, est-ce normal ?

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

Mes pairs actifs / pairs connus / tunnels participants / connexions / bande passante varient considérablement au fil du temps ! Il y a-t-il un problème ?

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.

Dans wrapper.log, je vois une erreur qui indique « Famille de protocoles non disponible » lors du chargement de la console de routeur

Fréquemment, cette erreur se produira avec n’importe quel logiciel Java prenant en charge le réseau sur certains systèmes configurés pour utiliser IPv6 par défaut. Il y existe quelques façons de corriger cela :

  • Sur les systèmes basés sur Linux, vous pouvez utiliser echo 0 > /proc/sys/net/ipv6/bindv6only
  • Chercher les lignes suivantes dans wrapper.config.
    #wrapper.java.additional.5=-Djava.net.preferIPv4Stack=true
    #wrapper.java.additional.6=-Djava.net.preferIPv6Addresses=false

    Si les lignes y sont, ôter le commentaire en supprimant les « # ». Si les lignes n’y sont pas, les ajouter sans « # ».
Une autre option serait de supprimer ::1 dans ~/.i2p/clients.config

AVERTISSEMENT : Pour que des modifications de wrapper.config prennent effet, vous devez fermer le routeur et l’enveloppeur. Cliquer sur Redémarrer dans la console de votre routeur ne relira PAS ce fichier ! Vous devez cliquer sur Fermeture, attendre 11 minutes, puis démarrer I2P.

La plupart des sites eep d’I2P sont-ils hors services ?

Si vous prenez en compte tous les sites eep jamais créés, alors oui, la plupart d’entre eux sont hors service. Les personnes et les sites eep vont et viennent. Une bonne façon de se lancer dans I2P est de consulter une liste de sites eep qui sont actuellement en service. http://identiguy.i2p.xyz suit les sites eep actifs.

Pourquoi I2P écoute-t-il sur le 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.

Je pense avoir trouvé un bogue, où puis-je le signaler ?

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.


J’ai une question !

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).