source: readme.html @ e7be8c6

Last change on this file since e7be8c6 was e7be8c6, checked in by zzz <zzz@…>, 16 years ago

Added references to the new irc2p server: irc.freshcoffee.i2p

  • Property mode set to 100644
File size: 5.0 KB
1<p>If this is your first time running I2P, you will see a link on the left hand
2side telling you to "reseed" - click that to get connected to the network (you
3only need to do it if that link shows up).  Within 5 minutes, you should see
4the number of "Active: " peers rise, and you should see some local "destinations"
5listed (if not, <a href="#trouble">see below</a>).  Once those are up, you can:</p>
7 <li><b>chat anonymously</b> - fire up your own IRC client and connect to the
8     server at <b>localhost port 6668</b>.  This points at one of three anonymously hosted
9     IRC servers, but neither you nor they know where the other is.</li>
10 <li><b>browse "eepsites"</b> - on I2P there are anonymously hosted websites -
11     tell your browser to use the <b>HTTP proxy at localhost port 4444</b>, then
12     browse to an eepsite -
13     <ul>
14         <li><a href="http://duck.i2p/">duck.i2p</a>: duck's eepsite, with links to other active sites</li>
15         <li><a href="http://ugha.i2p/">ugha.i2p</a>: ugha's eepsite, a wiki that anyone can edit, and lots of links</li>
16         <li><a href="http://orion.i2p/">orion.i2p</a>: a site which tracks eepsite uptime and changes</li>
17         <li><a href="http://forum.i2p/">forum.i2p</a>: a secure and anonymous connection to <a href=""></a></li>
18         <li><a href="http://www.i2p/">www.i2p</a>: a secure and anonymous connection to <a href=""></a></li>
19         <li><a href="http://dev.i2p/">dev.i2p</a>: a secure and anonymous connection to <a href=""></a></li>
20         <li>Freenet proxies: <a href="http://fproxy.i2p/">fproxy.i2p</a></li>
21     </ul>
22     There are many more eepsites - just follow the links from the ones you see,
23     bookmark your favorites, and visit them often!</li>
24 <li><b>browse the web</b> - there are a pair of HTTP "outproxies" in I2P hooked
25     up to your own HTTP proxy on port 4444 - simply set your browser's proxy to
26     use it (as above) and go to any normal URL - your requests will be bounced
27     through the I2P network.</li>
28 <li><b>transfer files</b> - there is an <a href="http://duck.i2p/i2p-bt/">I2P port</a>
29     of the <a href="">BitTorrent</a> application available.</li>
30 <li><b>use anonymous email</b> - postman has created a mail system compatible with normal mail
31     clients (POP3 / SMTP) that allows email within I2P as well as mail from and to the normal
32     internet!  get your account at <a href="http://www.postman.i2p/">www.postman.i2p</a>.
33     We bundle <a href="http://susi.i2p/">susimail</a>, a web based anonymity-oriented pop3/smtp client
34     configured to access postman's mail services.</li>
35 <li>and lots more</li>
38<h2>Want your own eepsite?</h2>
40<p>We've bundled some software to let you run your own eepsite - a
41<a href="">Jetty</a> instance listening on
42<a href="http://localhost:7658/">http://localhost:7658/</a>.  Simply place your files in
43the <code>eepsite/docroot/</code> directory (or place any standard JSP/Servlet <code>.war</code>
44files under <code>eepsite/webapps</code>, or standard CGI script under <code>eepsite/cgi-bin</code>)
45and they'll show up.  Your eepsite's
46<i>destination</i> (which uniquely and securely identifies it) is shown on the I2PTunnel
47<a href="/i2ptunnel/">configuration page</a> - if you want other people to see your eepsite,
48you need to give them that really huge string.  Just paste it into the
49<a href="http://forum.i2p/viewforum.php?f=16">Eepsite announce</a> forum, add it to
50ugha's <a href="http://ugha.i2p/I2pLinks">wiki</a>, <a href="http://orion.i2p/">orion's list</a>, or paste it in the #i2p or #i2p-chat channels on
51IRC (be sure to split it into two lines, as its too long for one).</p>
53<h2><a name="trouble">Troubleshooting</a></h2>
55<p>If the left hand side has a warning, telling you to check your NAT or firewall, please
56see the <a href="/config.jsp">config page</a> and make sure that you can receive <b>inbound
57TCP and UDP connections on port 8887</b> (or another port that you specify).  Problems forwarding
58that port account for the vast majority of issues people run into.  When it says
59"Active: 72/85", the "72" means how many peers you are connected with now, and "85" means
60how many you have spoken with recently - if that first number is 0, you can bet that there
61are firewall issues.  If the second number is under 5, you should reseed (a link on the left
62hand side of the page will show up to help you when necessary).</p>
64<p>If you are still having problems, you may want to review the information on the
65<a href="">I2P website</a>, post up messages to the
66<a href="">I2P discussion forum</a>, or swing by #i2p or
67#i2p-chat on IRC at <a href="irc://"></a>, irc.postman.i2p, irc.freshcoffee.i2p or
68irc.arcturus.i2p (they're all linked together).</p>
70<p><b>As a note, you can change this page by editing the file "docs/readme.html"</b></p>
Note: See TracBrowser for help on using the repository browser.