+Si vous souhaitez améliorer ou traduire la documentation ou d'autres versants du projet, merci de vous reporter à +la page consacrée aux volontaires. +
D'autres détails sont disponibles ici: +
+Il y a aussi le forum I2P +et l'IRC. + +
Informations du panneau de contrôle
+Plusieurs des statistiques du panneau de contrôle peuvent être configurées pour être +affichées sous forme de graphiques pour l'analyse à postériori. +
GÉNÉRAL
-
+
- Identité locale: +Cliquez sur "Afficher" pour voir l'empreinte Base64 à 44 caractères (256 bits) de votre routeur. Le hachage +complet est affiché sur votre page d'infos routeur. Ne la divulguez jamais à personne, +car l'info routeur contient votre adresse IP. +
- Version: +La version d'I2P qui vous affiche actuellement cette page. +
- Lancé depuis: +Indique depuis combien de temps le routeur tourne. +
- Réseau: +Statut de joignabilité du routeur par les autres routeurs. +Plus d'infos sur la page de configuration. +
Pairs
-
+
- Actifs: +le premier nombre est celui des routeurs avec qui le votre a communiqué dans les dernières minutes. Ça peut varier de +8-10 à plusieurs centaines, suivant votre bande passante, son ratio de partage, et le trafic généré localement. Le +second est celui des pairs vus dans les dernières heures. Ces nombres penvent varier sensiblement sans conséquence. +[Activer les courbes]. +
- Rapides: +le nombre de pairs que vous mettez à contribution pour construire vos tunnels clients. En général dans une tranche de +8 à 30. Vos pairs rapides sont détaillés sur la page profils. +[Activer les courbes]. +
- Hautes capacités: +nombre des pairs que vous utilisez pour construire quelques uns de vos tunnels exploratoires. Habituellement de 8 à 75. +Les pairs rapides font partie du groupe des \"Hautes capacités\". Vos pairs à hautes capacités sont aussi listés sur +la page profils. +[Activer les courbes]. +
- Bien intégrés: +vous utilisez ce groupe pour vos requêtes à la base de données du réseau. Ils sont souvent des pairs de remplissage par +diffusion ("floodfill"). Vos pairs "bien intégrés" sont affichés en bas de la même page +profils. +
- Connus: +c'est tous les routeurs dont vous connaissez l'existance. Il sont listés sur la page +base de données du réseau. De moins de 100 à 1000 ou plus. Ce nombre ne représente pas la +taille totale du réseau; il varie en fonction de votre bande passante totale, du ratio de partage, et du trafic local. +I2P n'a pas besoin que chaque routeur connaisse tous les autres. +
Bande passante entrée/sortie
Destinations locales
Tunnels entrée/sortie
-
+
- Exploratory: +Tunnels built by your router and used for communication with the floodfill peers, +building new tunnels, and testing existing tunnels.+
- Client: +Tunnels built by your router for each client's use. +
- Participating: +Tunnels built by other routers through your router. +This may vary widely depending on network demand, your +shared bandwidth, and amount of locally-generated traffic. +The recommended method for limiting participating tunnels is +to change your share percentage on the configuration page. +You may also limit the total number by setting router.maxParticipatingTunnels=nnn on +the advanced configuration page. [Enable graphing]. +
- Share ratio: +The number of participating tunnels you route for others, divided by the total number of hops in +all your exploratory and client tunnels. +A number greater than 1.00 means you are contributing more tunnels to the network than you are using. +
Congestion
-
+
- Job lag: +How long jobs are waiting before execution. The job queue is listed on the jobs page. +Unfortunately, there are several other job queues in the router that may be congested, +and their status is not available in the router console. +The job lag should generally be zero. +If it is consistently higher than 500ms, your computer is very slow, or the +router has serious problems. +[Enable graphing]. +
- Message delay: +How long an outbound message waits in the queue. +This should generally be a few hundred milliseconds or less. +If it is consistently higher than 1000ms, your computer is very slow, +or you should adjust your bandwidth limits, or your (bittorrent?) clients +may be sending too much data and should have their transmit bandwidth limit reduced. +[Enable graphing] (transport.sendProcessingTime). +
- Tunnel lag: +This is the round trip time for a tunnel test, which sends a single message +out a client tunnel and in an exploratory tunnel, or vice versa. +It should usually be less than 5 seconds. +If it is consistently higher than that, your computer is very slow, +or you should adjust your bandwidth limits, or there are network problems. +[Enable graphing] (tunnel.testSuccessTime). +
- Handle backlog: +This is the number of pending requests from other routers to build a +participating tunnel through your router. +It should usually be close to zero. +If it is consistently high, your computer is too slow, +and you should reduce your share bandwidth limits. +
- Accepting/Rejecting: +Your router's status on accepting or rejecting +requests from other routers to build a +participating tunnel through your router. +Your router may accept all requests, accept or reject a percentage of requests, +or reject all requests for a number of reasons, to control +the bandwidth and CPU demands and maintain capacity for +local clients.
Legal stuff
The I2P router (router.jar) and SDK (i2p.jar) are almost entirely public domain, with +a few notable exceptions:
-
+
- ElGamal and DSA code, under the BSD license, written by TheCrypto +
- SHA256 and HMAC-SHA256, under the MIT license, written by the Legion of the Bouncycastle +
- AES code, under the Cryptix (MIT) license, written by the Cryptix team +
- SNTP code, under the BSD license, written by Adam Buckley +
- The rest is outright public domain, written by jrandom, mihi, hypercubus, oOo, + ugha, duck, shendaras, and others. +
On top of the I2P router are a series of client applications, each with their own set of +licenses and dependencies. This webpage is being served as part of the I2P routerconsole +client application, which is built off a trimmed down Jetty +instance (trimmed down, as in, we do not include the demo apps or other add-ons, and we simplify configuration), +allowing you to deploy standard JSP/Servlet web applications into your router. Jetty in turn makes use of +Apache's javax.servlet (javax.servlet.jar) implementation. +This product includes software developed by the Apache Software Foundation +(http://www.apache.org/).
+ +Another application you can see on this webpage is I2PTunnel +(your web interface) - a GPL'ed application written by mihi that +lets you tunnel normal TCP/IP traffic over I2P (such as the eepproxy and the irc proxy). There is also a +susimail web based mail client available on +the console, which is a GPL'ed application written by susi23. The addressbook application, written by +Ragnarok helps maintain your hosts.txt files (see ./addressbook/ for +more information).
+ +The router by default also includes human's public domain SAM bridge, +which other client applications (such the bittorrent port) can use. +There is also an optimized library for doing large number calculations - jbigi - which in turn uses the +LGPL licensed GMP library, tuned for various PC architectures. Launchers for windows users are built with Launch4J, and the installer is built with IzPack. For +details on other applications available, as well as their licenses, please see the +license policy. Source for the I2P code and most bundled +client applications can be found on our download page. +.
+ +