This is a shortened version of the official FAQ. For the full version, please visit https://geti2p.net/faq or http://i2p-projekt.i2p/faq.
If after a few minutes of uptime your router is indicating 0 Active Peers and 0 Known Peers, with a notification in the sidebar that you need to check your network connection, verify that you can access the internet. If your internet connection is functional, you may need to unblock Java in your firewall. Otherwise, you may need to reseed your I2P router. Visit the Reseed Configuration page and click the "Save Changes and Reseed Now" button.
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 default subscription is to http://i2p-projekt.i2p/hosts.txt which is seldom updated.
If you don't have another subscription, you may often have to use "jump" links which is much slower but ensures that your addressbook is only populated by sites you use (in addition to the default subscription addresses).
To speed up browsing on I2P, it's a good idea to add some addressbook subscriptions.
Here are some other public addressbook subscription links. You may wish to add one or two to your susidns subscription list. In the event that addresses conflict in the subscriptions, the lists placed at the top of your susidns configuration will take precedence over those placed further down.
http://stats.i2p/cgi-bin/newhosts.txthttp://no.i2p/export/alive-hosts.txthttp://identiguy.i2p/hosts.txtNote that subscribing to a hosts.txt service is an act of trust, as a malicious subscription could give you incorrect addresses, so be careful subscribing to lists from unknown sources. The operators of these services may have various policies for listing hosts. Presence on this list does not imply endorsement.
Unless an outproxy has been set up for the service you want to connect to, this is not possible. There are only three types of outproxies running right now: HTTP, HTTPS, and email. Note that there is currently no publicly listed SOCKS outproxy. If this type of service is required, try Tor.
You will need to configure your browser to use the HTTP proxy server (by default on host: 127.0.0.1 port: 4444).
See the Browser Proxy Configuration Guide for a more detailed explanation.
An eepsite is a website that is hosted anonymously on the I2P network - you can access it by configuring your web browser to use I2P's HTTP proxy (see above) and browsing to the .i2p suffixed website (e.g. http://i2p-projekt.i2p).
Also ensure your browser is configured to resolve DNS remotely when using the proxy to avoid DNS leaks.
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. http://identiguy.i2p tracks active eepsites.
A tunnel to the main IRC server network within I2P, Irc2P, is created when I2P is installed (see the I2P Tunnel Manager), and is automatically started when the I2P router starts.
To connect to it, tell your IRC client to connect to server: 127.0.0.1 port: 6668.
HexChat-like client users can create a new network with the server 127.0.0.1/6668 (remember to tick "Bypass proxy server" if you have a proxy server configured), or you can connect with the command /server 127.0.0.1 6668.
Different IRC clients may require a different command, consult your IRC client's manual for more information.
| LOCAL PORTS | ||
|---|---|---|
| These are the local I2P port mappings, listening only to local connections by default, except where noted. Unless you require access from other machines, they should only be accessible from localhost. | ||
| Port | Function | Notes |
| 1900 | UPnP SSDP UDP multicast listener | Cannot be changed. Binds to all interfaces. Can be disabled on the Network Configuration page. |
| 2827 | BOB bridge | A higher level socket API for clients.
Can be enabled/disabled on the Client Configuration page.
Can be changed in the bob.config file. [Disabled by default] |
| 4444 | HTTP proxy | Can be disabled or changed in the I2P Tunnel Manager. Can also be configured to bind to a specific interface or all interfaces. |
| 4445 | HTTPS proxy | Can be disabled or changed in the I2P Tunnel Manager. Can also be configured to bind to a specific interface or all interfaces. |
| 6668 | IRC proxy | Can be disabled or changed in the I2P Tunnel Manager. Can also be configured to bind to a specific interface or all interfaces. |
| 7652 | UPnP HTTP TCP event listener | Binds to the LAN address. Can be changed with advanced config i2np.upnp.HTTPPort=nnnn.
Can be disabled on the Network Configuration page. |
| 7653 | UPnP SSDP UDP search response listener | Binds to all interfaces.
Can be changed with advanced config i2np.upnp.SSDPPort=nnnn.
Can be disabled on the Client Configuration page. |
| 7654 | I2P Client Protocol port | Used by client apps. Can be changed to a different port on the Client Configuration page but this is not recommended. Can be bound to a different interface or all interfaces, or disabled, on the Client Configuration page. |
| 7655 | UDP for SAM bridge | A higher level socket API for clients.
Only opened when a SAM V3 client requests a UDP session.
Can be enabled/disabled on the Client Configuration page.
Can 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.
Can be enabled/disabled on the Client Configuration page.
Can be changed in the clients.config file. [Disabled by default] |
| 7657 | I2P Router Console (Web interface) | Can be disabled in the clients.config file.
Can also be configured to bind to a specific interface or all interfaces in that file.
If you make the Router Console available over the network, you might wish to enforce an access password to prevent unauthorized access. |
| 7658 | I2P Web Server | Can be disabled in the clients.config file.
Can also be configured to bind to a specific interface or all interfaces in the jetty.xml file. |
| 7659 | Outgoing mail to smtp.postman.i2p | Can be disabled or changed in the I2P Tunnel Manager. Can also be configured to bind to a specific interface or all interfaces. |
| 7660 | Incoming mail from pop.postman.i2p | Can be disabled or changed in the I2P Tunnel Manager. Can also be configured to bind to a specific interface or all interfaces. |
| 8998 | mtn.i2p2.i2p (I2P's Monotone DVCS) | Can be disabled or changed in the I2P Tunnel Manager. Can also be configured to bind to a specific interface or all interfaces. [Disabled by default] |
| 31000 | Local connection to 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. |
| 32000 | Local control channel for the service wrapper | To change, see the wrapper documentation. |
| INTERNET FACING PORTS | ||
| I2P selects a random port between 9000 and 31000 to communicate with other routers when the program is run for the first time, or when your external IP address changes when running in Laptop Mode. The selected port is shown on the Network Configuration page. | ||
| Outbound UDP from the random port noted on the Network Configuration page to arbitrary remote UDP ports, allowing replies. | ||
| Outbound TCP from random high ports to arbitrary remote TCP ports. | ||
| Inbound UDP to the port noted on the Network Configuration page from arbitrary locations (optional, but recommended). | ||
| Inbound TCP to the port noted on the Network Configuration page from arbitrary locations (optional, but recommended). Inbound TCP may be disabled on the Network Configuration page. | ||
Outbound UDP on port 123, allowing 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). | ||