The reseed URL has changed. If this is your first install, or you have not run I2P in a long time, you must change it 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/ , then click "Apply", then click the "reseed" link on the left.
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 outproxy squid.i2p has vanished. The only outproxy at the moment is false.i2p. To use these, edit your i2ptunnel setting and set your outproxy list to 'false.2p'. If it doesn't work, they are not up. It is not I2P's fault.
If you consider every eepsite that has ever been created, yes, most of them are down. People and eepsites come and go. A good way to get started in I2P is check out a list of eepsites that are currently up. inproxy.tino.i2p and perv.i2p track active eepsites.
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 16KBps you will generally get no better than 5KBps 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.
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.
An eepsite is a website that is hosted anonymously - you can access it by setting your web browser's HTTP proxy to use the web proxy (typically it listens on localhost port 4444), and browsing to the site.
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.
While it would be technically feasible, 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.
Ok, here's a rundown of the default ports (everything is configurable through various settings, of course):
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 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).
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 %}