Beruflich Dokumente
Kultur Dokumente
http://www.i2p2.de/faq.html
FAQ
I2P - FREQUENTLY ASKED QUESTIONS
Index
Welcome to I2P Download News Announcements Meetings Roadmap Task list About I2P FAQ Forums (within I2P) Bounties Get involved Donate! I2P Team Hall of Fame Documentation How does it work? Tech intro App Dev Papers Development API Licenses Report a Bug Syndie Links T-Shirt Mirror Mirror 2 Secure Site Impressum
General
1. What systems will I2P run on? 2. Whats an "eepsite" and how do I configure my browser so I can use them? 3. My router has very few active peers, is this OK? 4. What do the Active x/y numbers mean in the router console? 5. My active peers / known peers / participating tunnels / connections / bandwidth vary dramatically over time! Is anything wrong? 6. Is using an outproxy safe? 7. Most of the eepsites within I2P are down? 8. What ports does I2P use? 9. Why is I2P listening for connections on port 32000? 10. I think I found a bug, where can I report it? 11. What happened to *.i2p.net? What happened to jrandom? Is I2P dead? 12. I have a question!
Setup
13. My router has been up for several minutes and has zero or very few connections 14. Why is I2P so slow? 15. I'm missing lots of hosts in my addressbook. What are some good subscription links? 16. How do I set up my own eepsite? 17. Bittorrent / I2PSnark / Azureus I2P Plugin Questions? 18. How do I connect to IRC within I2P? 19. I can't access regular Internet sites through I2P. 20. I can't access https:// or ftp:// sites through I2P.
1 of 12
11/14/2012 10:11 PM
FAQ - I2P
http://www.i2p2.de/faq.html
21. Is it possible to use I2P as a SOCKS proxy? 22. How do I configure my browser? 23. How can I access the web console from my other machines or password protect it? 24. How can I use applications from my other machines? 25. How do I reseed manually? 26. My router is using too much CPU?!?
Misconception
27. How do I access IRC, BitTorrent, or other services on the regular Internet? 28. Is my router an "exit node"(outproxy) to the regular Internet? I don't want it to be. 29. I am opposed to certain types of content. How do I keep from distributing, storing, or accessing them?
30. I'm using FreeBSD and when I start I2P I receive an error about libm.so.4! 31. In wrapper.log I see an error stating Protocol family unavailable when I2P is loading
2 of 12
11/14/2012 10:11 PM
FAQ - I2P
http://www.i2p2.de/faq.html
3 of 12
11/14/2012 10:11 PM
FAQ - I2P
http://www.i2p2.de/faq.html
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. 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 confignet.jsp, or by setting router.maxParticipatingTunnels=nnn on configadvanced.jsp.
I am opposed to certain types of content. How do I keep from distributing, storing, or accessing them? (link)
Hmm. I2P is an anonymous network, so that's a tricky one. I2P is designed to withstand censorship, providing a means for everyone to communicate freely. The best way to keep your PC free of (encrypted) traffic that you dislike is to not use I2P. Freedom of speech has some costs. But let's address your question in three parts: 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 (outproxy). 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. You must be thinking of Freenet. Nobody's content is being stored on your computer by running I2P. Access - If there are some eepsites you don't like, don't go there. Or, use a blocking proxy like Privoxy or some type of "net nanny".
My active peers / known peers / participating tunnels / connections / bandwidth vary dramatically over time! Is anything wrong? (link)
No. This is normal. All routers adjust dynamically to changing network conditions and demands.
My router has been up for several minutes and has zero or very few connections (link)
You may need to reseed your I2P router. With recent versions of I2P you can go to http://localhost:7657/configreseed and click the Save Changes and Reseed Now button. If this method doesn't workor you're using a very old versionyou may need to reseed manually. The reseed URL changed a few years ago. 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.
4 of 12
11/14/2012 10:11 PM
FAQ - I2P
http://www.i2p2.de/faq.html
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. ...but you *really* should upgrade to the latest version.
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.
5 of 12
11/14/2012 10:11 PM
FAQ - I2P
http://www.i2p2.de/faq.html
2. Choose CONNECT from New Client Tunnel dropdown list, click Create 3. In the new page, name and describe your new https tunnel as you like. The Access Point is your local port for the new https proxy recommended port's 4445. Outproxy should be the outproxy's .i2p address which supports https. See this forum post of h2ik's for the address. Make sure Shared Client, Delay Connect, AutoStart are checked. Other options should be left at the defaults. Click Save. In tunnel manger, click the Start button next to your new tunnel. 4. In firefox, click through Tools>Options>Advanced>Network>Setting. Untick Use this proxy for all protocol, set SSL proxy: to localhost:4445. 5. Done.
Unless an outproxy has been 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 not a SOCKS outproxy. If this type of service is required, try Tor.
6 of 12
11/14/2012 10:11 PM
FAQ - I2P
http://www.i2p2.de/faq.html
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.
How can I access the web console from my other machines or password protect it? (link)
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: 1. Open ~/.i2p/clients.config and replace clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/ with clientApp.0.args=7657 0.0.0.0 ./webapps/ 2. Go to http://localhost:7657/configadvanced.jsp and add a new option: consolePassword=foo (or whatever password you want) 3. Go to http://localhost:7657/index.jsp 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. 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.
7 of 12
11/14/2012 10:11 PM
FAQ - I2P
http://www.i2p2.de/faq.html
advanced configs with external tools are possible but could introduce leaks in your setup.
What do the Active x/y numbers mean in the router console? (link)
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.
Local I2P ports, listening only to local connections by default, except where noted:
8 of 12
11/14/2012 10:11 PM
FAQ - I2P
http://www.i2p2.de/faq.html
1900: UPnP SSDP UDP multicast listener. Cannot be changed. Binds to all interfaces. May be disabled on confignet.jsp. 2827: BOB bridge, a higher level socket API for clients Disabled by default. May be enabled/disabled on configclients.jsp. 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: UPnP HTTP TCP event listener. Binds to the LAN address. May be changed with advanced config i2np.upnp.HTTPPort=nnnn. May be disabled on confignet.jsp. 7653: UPnP SSDP UDP search response listener. Binds to all interfaces. May be changed with advanced config i2np.upnp.SSDPPort=nnnn. May be disabled on confignet.jsp. 7654: I2P Client Protocol port, used by client apps. May be changed to a different port on configclients.jsp but this is not recommended. May be to bind to a different interface or all interfaces, or disabled, on configclients.jsp. 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.jsp. 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.jsp. May be changed in the clients.config file. 7657: Your router console May be disabled in the clients.config file. 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: Incoming mail from pop.postman.i2p May be disabled
9 of 12
11/14/2012 10:11 PM
FAQ - I2P
http://www.i2p2.de/faq.html
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.i2p2.i2p (Monotone - disabled by default) 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.
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 unsolicited remote peers, but if you can configure your NAT/firewall to allow inbound UDP and TCP the outbound facing port, 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).
10 of 12
11/14/2012 10:11 PM
FAQ - I2P
http://www.i2p2.de/faq.html
I'm using FreeBSD and when I start I2P I receive an error about libm.so.4! (link)
When trying to start the router using "i2prouter start", you may see output like the following: $ ./i2prouter start Starting I2P Service... /libexec/ld-elf.so.1: Shared object "libm.so.4" not found, required by "i2psvc" In order to be inclusive and try to ensure that I2P will run on as many systems as possible, up until I2P 0.8.9 we used a java wrapper compiled for FreeBSD 6.x. If you're receiving this error you most likely are missing the necessary compatibility libraries. These libraries may be installed by performing the following steps: Switch to the root user with su or log in as root. cd /usr/ports/misc/compat6x make install If you cannot install these compatibility libraries (or do not want to), other possibilities would be to compile the wrapper for your system, starting I2P with the runplain.sh script, or you can replace the wrapper with one from the source tarball. For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and compiled on systems running FreeBSD 7.2.
In wrapper.log I see an error that states "Protocol unavailable" when loading the Router Console (link)
family
Often this error will occur with any network enabled java software on some systems that are configured to use IPv6 by default. There are a few ways to solve this: On Linux based systems, you can echo 0 > /proc/sys/net/ipv6 /bindv6only Look for the following lines in wrapper.config. #wrapper.java.additional.5=-Djava.net.preferIPv4Stack=true #wrapper.java.additional.6=-Djava.net.preferIPv6Addresses=false If the lines are there, uncomment them by removing the "#"s. If the lines are not there, add them without the "#"s. Another option would be to remove the ::1 from ~/.i2p/clients.config WARNING: For any changes to wrapper.config to take effect, you must completely stop the router and the wrapper. Clicking Restart on your router console will NOT reread this file! You must click Shutdown, wait 11 minutes, then start I2P.
11 of 12
11/14/2012 10:11 PM
FAQ - I2P
post it here (with the answer, hopefully).
http://www.i2p2.de/faq.html
12 of 12
11/14/2012 10:11 PM