Go to file
jrandom 4ce51261f1 2005-04-28 jrandom
* More fixes for the I2PTunnel "other" interface handling (thanks nelgin!)
    * Add back the code to handle bids from multiple transports (though there
      is still only one transport enabled by default)
    * Adjust the router's queueing of outbound client messages when under
      heavy load by running the preparatory job in the client's I2CP handler
      thread, thereby blocking additional outbound messages when the router is
      hosed.
    * No need to validate or persist a netDb entry if we already have it
And for some udp stuff:
* only bid on what we know (duh)
* reduceed the queue size in the UDPSender itself, so that ACKs go
  through more quickly, leaving the payload messages to queue up in
  the outbound fragment scheduler
* rather than /= 2 on congestion, /= 2/3 (still AIMD, but less drastic)
* adjust the fragment selector so a wsiz throttle won't force extra
  volleys
* mark congestion when it occurs, not after the message has been
  ACKed
* when doing a round robin over the active messages, move on to the
  next after a full volley, not after each packet (causing less "fair"
  performance but better latency)
* reduced the lock contention in the inboundMessageFragments by
  moving the ack and complete queues to the ACKSender and
  MessageReceiver respectively (each of which have their own
  threads)
* prefer new and existing UDP sessions to new TCP sessions, but
  prefer existing TCP sessions to new UDP sessions
2005-04-28 21:54:27 +00:00
2005-04-28 21:54:27 +00:00
2005-04-24 18:42:02 +00:00
2005-04-20 20:14:17 +00:00
2005-04-28 21:54:27 +00:00
2005-04-17 23:23:20 +00:00
2005-04-28 21:54:27 +00:00
2005-04-28 02:11:02 +00:00
2005-04-20 20:14:17 +00:00
2004-12-21 16:32:49 +00:00
2005-04-28 21:54:27 +00:00
2005-03-24 01:19:52 +00:00

<p>If this is your first time running I2P, you will see a link on the left hand
side telling you to "reseed" - click that to get connected to the network (you
only need to do it if that link shows up).  Within 5 minutes, you should see
the number of "Active: " peers rise, and you should see some local "destinations"
listed (if not, <a href="#trouble">see below</a>).  Once those are up, you can:</p>
<ul>
 <li><b>chat anonymously</b> - fire up your own IRC client and connect to the 
     server at <b>localhost port 6668</b>.  This points at one of two anonymously hosted
     IRC servers (irc.duck.i2p and irc.baffled.i2p), but neither you nor they know
     where the other is.</li>
 <li><b>browse "eepsites"</b> - on I2P there are anonymously hosted websites - 
     tell your browser to use the <b>HTTP proxy at localhost port 4444</b>, then
     browse to an eepsite - 
     <ul>
         <li><a href="http://duck.i2p/">duck.i2p</a>: duck's eepsite, with links to other active sites</li>
         <li><a href="http://ugha.i2p/">ugha.i2p</a>: ugha's eepsite, a wiki that anyone can edit, and lots of links</li>
         <li><a href="http://orion.i2p/">orion.i2p</a>: a site which tracks eepsite uptime and changes</li>
         <li><a href="http://files.i2p/">files.i2p</a>: a search engine that tries to keep track of things on I2P</li>
         <li><a href="http://forum.i2p/">forum.i2p</a>: a secure and anonymous connection to <a href="http://forum.i2p.net/">forum.i2p.net</a></li>
         <li><a href="http://www.i2p/">www.i2p</a>: a secure and anonymous connection to <a href="http://www.i2p.net/">www.i2p.net</a></li>
         <li><a href="http://dev.i2p/">dev.i2p</a>: a secure and anonymous connection to <a href="http://dev.i2p.net/">dev.i2p.net</a></li>
         <li>Freenet proxies: <a href="http://fproxy.i2p/">fproxy.i2p</a> and <a href="http://freenet.eco.i2p/">freenet.eco.i2p</a></li>
     </ul>
     There are many more eepsites - just follow the links from the ones you see,
     bookmark your favorites, and visit them often!</li>
 <li><b>browse the web</b> - there are a pair of HTTP "outproxies" in I2P hooked
     up to your own HTTP proxy on port 4444 - simply set your browser's proxy to
     use it (as above) and go to any normal URL - your requests will be bounced
     through the I2P network.</li>
 <li><b>transfer files</b> - there is an <a href="http://duck.i2p/i2p-bt/">I2P port</a>
     of the <a href="http://www.bittorrent.com/">BitTorrent</a> application available.</li>
 <li><b>use anonymous email</b> - postman has created a mail system compatible with normal mail
     clients (POP3 / SMTP) that allows email within I2P as well as mail from and to the normal
     internet!  get your account at <a href="http://www.postman.i2p/">www.postman.i2p</a>.
     We bundle <a href="http://susi.i2p/">susimail</a>, a web based anonymity-oriented pop3/smtp client
     configured to access postman's mail services.</li>
 <li>and lots more</li>
</ul>

<h2>Want your own eepsite?</h2>

<p>We've bundled some software to let you run your own eepsite - a 
<a href="http://jetty.mortbay.org/">Jetty</a> instance listening on 
<a href="http://localhost:7658/">http://localhost:7658/</a>.  Simply place your files in
the <code>eepsite/docroot/</code> directory (or place any standard JSP/Servlet <code>.war</code>
files under <code>eepsite/webapps</code>, or standard CGI script under <code>eepsite/cgi-bin</code>) 
and they'll show up.  Your eepsite's 
<i>destination</i> (which uniquely and securely identifies it) is shown on the I2PTunnel
<a href="/i2ptunnel/">configuration page</a> - if you want other people to see your eepsite,
you need to give them that really huge string.  Just paste it into the 
<a href="http://forum.i2p/viewforum.php?f=16">Eepsite announce</a> forum, add it to
ugha'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
IRC (be sure to split it into two lines, as its too long for one).</p>

<h2><a name="trouble">Troubleshooting</a></h2>

<p>If the left hand side has a warning, telling you to check your NAT or firewall, please
see the <a href="/config.jsp">config page</a> and make sure that you can receive <b>inbound
TCP connections on port 8887</b> (or another port that you specify).  Problems forwarding
that port account for the vast majority of issues people run into.  When it says 
"Active: 72/85", the "72" means how many peers you are connected with now, and "85" means 
how many you have spoken with recently - if that first number is 0, you can bet that there
are firewall issues.  If the second number is under 5, you should reseed (a link on the left
hand side of the page will show up to help you when necessary).</p>

<p>If you are still having problems, you may want to review the information on the 
<a href="http://www.i2p.net/">I2P website</a>, post up messages to the 
<a href="http://forum.i2p.net/">I2P discussion forum</a>, or swing by #i2p or
#i2p-chat on IRC at <a href="irc://irc.freenode.net/#i2p">irc.freenode.net</a>, 
<a href="http://www.invisiblechat.com/">invisiblechat/IIP</a>, or irc.duck.i2p (they're all 
linked together).</p>

<p><b>As a note, you can change this page by editing the file "docs/readme.html"</b></p>
Description
The I2P anonymous network, Java Implementation
Readme 230 MiB
Languages
Java 86.9%
CSS 4.7%
HTML 4.1%
Shell 1.1%
JavaScript 1.1%
Other 1.9%