Un eepsite est un site web hébergé anonymement - vous pouvez y accéder en réglant votre navigateur pour qu'il utilise le proxy HTTP intégré au routeur I2P (par défaut, il écoute sur le port 4444 de l'adresse locale "localhost" ou 127.0.0.1), et en navigant vers ce site.
S'il en a plus de 10, c'est bon. Des changements dans les versions 0.6.1.31 et 0.6.1.32 ont amélioré l'efficacité du routeur et effectivement réduit le nombre de pairs actifs. Le routeur devrait maintenir des connexions vers un petit nombre de pairs en permanence. La meilleure façon de rester "mieux-connecté" au réseau est de partager plus de bande passante.
Non. C'est normal. Tous les routeurs s'adaptent dynamiquement à l'état du réseau et aux demandes.
C'est à vous de décider, car tout dépend de ce que vous faites, de votre , conception d'une menace, et de la confiance que vous accordez à l'opérateur du nœud de sortie vers l'Internet classique.
À l'instar de Tor, I2P ne crypte pas magiquement l'Internet. Vous êtes vulnerable à l'éventuelle curiosité du prpriétaire du nœud de sortie. La FAQ de Tor contient une bonne explication à ce sujet. Il n'y a pas d'outproxy HTTPS dans I2P, et vous ne pouvez pas cacher votre trafic à l'opérateur du nœud de sortie, pas plus d'ailleur que vous ne pouvez le cacher à toute personne pouvant se brancher d'une façon ou d'une autre sur le lien entre vous et votre correspondant quand vous utilisez l'Internet classique (votre FAI ne vous l'a jamais dit? Comme c'est bizarre!).
De plus, vous pourriez être vulnérable à une collusion entre l'opérateur du outproxy et des opérateurs d'autres services I2P, si vous utilisez le même tunnel (clients partagés "shared clients"). Il y a une autre explication à ça sur le site de zzz ici.
En prennant en compte tous les eepsites jamais créés, oui, la plupart sont morts! Comme les gens, les gens viennent, puis s'en vont. Une bonne façon de démarrer dans I2P consiste à vérifier la liste des eepsites qui sont actuellement actifs: inproxy.tino.i2p et perv.i2p suivent les eepsites actifs.
Voici une plongée dans les ports par défaut (tout est bien entendu configurable par divers réglages):
The local I2P ports and the I2PTunnel ports do not need to be reachable from remote machines, but *should* be reachable locally. You can also create additional ports for I2PTunnel instances via http://localhost:7657/i2ptunnel/ (and in turn, would need to get your firewall to allow you local access, but not remote access, unless desired).
So, to summarize, nothing needs to be reachable by unsolicted remote peers, but if you can configure your NAT/firewall to allow inbound UDP and TCP to port 8887, you'll get better performance. You will also need to be able to send outbound UDP packets to arbitrary remote peers (blocking IPs randomly with something like PeerGuardian only hurts you - don't do it).
Voici les endroits ou vous pouvez le faire, utilisez en un ou plus :
Merci d'inclure dans tout rapport de bug, des informations pertinantes sur le routeur et les logs.
La souscription par dé est http://www.i2p.i2p/hosts.txt qui est rarement mis à jour. Si vous n'avez pas d'autres souscription, vous aurez souvent à utiliser un service de saut 'jump' ce qui est fastidieux.
Here are some other public addressbook subscription links. Vous trouverez ci dessous d'autres lien de souscription public, vous devriez en ajouter un ou deux à votre susidns souscriptions listes. Vous n'avez pas besoin de toutes les ajouter, elles se synchronisent ensemble régulièrement. Les liens utilisent un logiciel cgi-bin qui emploie diverses stratégies pour minimiser le nombre d'adresses identiques qui sont délivrées, ils doivent en être plus efficaces. IMPORTANT : accepter une liste d'hôtes est un acte de confiance. Un acte malveillant pourrait vous donner de fausses adresse. Donc, réfléchissez avant d'accepter. La présence sur cette liste ne signifie pas l'aval d'I2P.
Jrandom était le développeur responsable d'I2P et Syndie pendant de nombreuses années. Nous nous attendons à ce qu'il soit absent au moins jusqu'à la fin 2008. Les domaines *.i2p.net sont resté non fonctionnels suite à une panne de l'hébergement.
Regardez cette page (en englais) pour avoir plus d'informations sur le départ de Jrandom et la migration des sites vers celui ci.
I2P n'est pas mort, il est en développement actif et nous avons anticipé plusieurs versions en 2010.
Il y a plusieurs causes à une grande charge processeur. Voici quelques unes :
Hmm. I2P is an anonymous network, so that's a tricky one. I2P is designed for everyone and not to censor out some/any kind of data. The best way to keep your PC free of (encrypted) traffic you dislike is to not use I2P. Freedom of speech has some costs. But let's address your question in three parts:
The reseed URL has changed. If this is your first install and you have installed an old (0.6.1.30 or earlier) release, or you have not run I2P in a long time, you must change the URL and then click "Reseed" on the console to find other routers. After your router is running, on configadvanced.jsp, add the line i2p.reseedURL=http://netdb.i2p2.de/ OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should work), then click "Apply", then click the "reseed" link on the left.
This works if you are running 0.6.1.27 or later. If you are running release 0.6.1.31 or later, you probably don't need to do this. If you are running release 0.6.1.26 or earlier, either follow the manual reseed instructions below or install the latest release. Possible alternate method - add wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/ to wrapper.config, shutdown the router completely, then start again, then click "reseed". Let us know if this works.
No. Unlike Tor, "exit nodes" or "outproxies" are not an inherent part of the network. Only volunteers who set up and run separate applications will relay traffic to the regular internet. There are very very few of these.
See above. There are very few HTTP "outproxies", they are not an inherent part of the network, and they may not be up. In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have vanished. The only outproxy at the moment is false.i2p. To use it, edit your i2ptunnel settings for eepProxy and set your outproxy list to 'false.i2p' (only). Then stop and restart the eepProxy. If it doesn't work, the outproxy is not up. It is not I2P's fault. If your primary reason to use an anonymous network is to anonymously access sites on the regular internet, you should probably try Tor.
Within I2P, there is no need for HTTPS, as all traffic is encrypted end-to-end. FTP is not supported for technical reasons.
For HTTPS or FTP access to the regular internet, there are no HTTPS or FTP "outproxies". HTTPS is possible if somebody would like to set one up. FTP is probably not. Actually, just about any other sort of outproxy might work, try setting it up with a standard tunnel and see. As explained several times above, outproxies of any type are not a core part of the network, they are services run by individuals and they may or may not be operational at any given time. 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.
You can't. Somebody must set up an outproxy for each service. There are only two types of outproxies running right now: HTTP and email. There is no SOCKS outproxy. If you need this you should probably try Tor.
Click on the My Eepsite Link on the top of your router console for instructions.
Why are downloads, torrents, web browsing, and everything else so slow on I2P? The encryption and routing within the I2P network adds a substantial amount of overhead and limits bandwidth. Anonymity isn't free.
In addition, you and everybody else probably need to increase your bandwidth limits. Two key settings are the inbound and outbund bandwidth limiters on the configuration page. With the default settings of 32KBps you will generally get no better than 15KBps data transfer in I2PSnark. Increasing the settings (but keeping within your actual connection limitations) will increase the potential transfer rate for I2PSnark and all other applications.
Also, do you have sufficient share bandwidth configured to allow participating tunnels to route through your router? Believe it or not, allowing participating traffic keeps you well-integrated in the network and helps your own 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.
See the I2P Bittorrent FAQ (outside I2P)
On the I2PTunnel configuration page, start the ircProxy. Then tell your IRC client to connect to localhost port 6668.
For security purposes, the router's admin console by default only listens for connections on the local interface. However, with a little hacking, you can make it reachable remotely:
clientApp.0.args=7657 127.0.0.1 ./webapps/clientApp.0.args=7657 0.0.0.0 ./webapps/consolePassword=foo (or whatever password you want)
After that fires up, you should now be able to reach your console remotely.
You will be prompted for a username and password though - the username is
"admin" and the password is whatever you specified in step 2 above. Note: the
0.0.0.0 above 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.
By default, the router I2CP interface (port 7654) binds to address 127.0.0.1. To bind to 0.0.0.0, set the router advanced configuration option i2cp.tcp.bindAllInterfaces=true and restart.
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.
The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are supported. There is no SOCKS outproxy so it is of limited use.
In addition, many applications leak sensitive information that could identify you on the internet. I2P only filters connection data, but if the programme 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.
If you would like more information on the socks proxy application anyway, there are some helpful hints on the socks page.
An I2P router only needs to reseed once, to join the network for the first time. Reseeding is nothing more than sending plain HTTP GET requests to fetch a directory listing and download multiple "routerInfo" files from a predefined reseed URL.
A typical symptom of a failed reseed is the "Known" indicator (on the left sidebar of the router console) displaying a very small value (often less than 5) which does not increase. This can occur, among other things, if your firewall limits outbound traffic, and blocked the reseed request.
To reseed an I2P router manually, do the following:
Great! Find us on IRC irc.freenode.net #i2p or post to the forum and we'll post it here (with the answer, hopefully).
{% endblock %}