forked from I2P_Developers/i2p.www
faq, download, index updates
This commit is contained in:
@ -49,6 +49,22 @@ if you can, bearing in mind the Internet-facing ports I2P uses,
|
||||
<a href="http://www.i2p2.de/faq#ports">described here</a> among other ports.</p>
|
||||
|
||||
<h3>Updates from earlier releases:</h3>
|
||||
<p>
|
||||
Automatic and manual upgrades from earlier releases to release 0.6.1.30
|
||||
are currently unavailable.
|
||||
You can build your own i2pupdate.zip file from
|
||||
<a href="http://mirror.i2p2.de/i2p-0.6.1.30.tar.bz2">the source</a>
|
||||
or <a href="monotone">monotone</a>,
|
||||
or wait for 0.6.1.31.
|
||||
Both automatic and manual upgrades will be available for the upcoming
|
||||
0.6.1.31 release; please see
|
||||
<a href="http://forum.i2p.net/viewtopic.php?t=2532">this forum post</a> (forum.i2p.net) or
|
||||
<a href="http://forum.i2p/viewtopic.php?t=2532">here</a> (forum.i2p)
|
||||
for important information about how to configure your router to automatically
|
||||
receive the upcoming 0.6.1.31 release.
|
||||
</p>
|
||||
|
||||
<!--
|
||||
<ol>
|
||||
<li>With the new announcement system, you should see a link on your
|
||||
<a href="http://localhost:7657/index.jsp">router console</a> allowing
|
||||
@ -68,5 +84,6 @@ if you can, bearing in mind the Internet-facing ports I2P uses,
|
||||
NOT need to unzip that file.</li>
|
||||
<li>Click <a href="http://localhost:7657/configservice.jsp">"Graceful restart"</a></li>
|
||||
<li>Grab a cup of coffee and come back in 11 minutes</li>
|
||||
-->
|
||||
</ol>
|
||||
{% endblock %}
|
||||
|
@ -1,6 +1,55 @@
|
||||
{% extends "_layout.html" %}
|
||||
{% block title %}FAQ{% endblock %}
|
||||
{% block content %}<h3 id="remote_webconsole">How can I access the web console from my other machines or password protect it?
|
||||
{% block content %}
|
||||
<h3 id="reseed">My router has been up for several minutes and has zero or very few connections
|
||||
<span class="permalink">(<a href="#reseed">link</a>)</span></h3>
|
||||
<p>
|
||||
The reseed URL has changed. If this is your first install, you must change it and then
|
||||
click "Reseed" on the console to find other routers.
|
||||
After your router is running,
|
||||
on <a href="http://localhost:7657/configadvanced.jsp">configadvanced.jsp</a>,
|
||||
add the line <tt>i2p.reseedURL=http://i2pdb.tin0.de/netDb/</tt> ,
|
||||
then click "Apply", then click the "Reseed" link on the left.
|
||||
</p>
|
||||
|
||||
<h3 id="exit">Is my router an "exit node" to the regular internet? I don't want it to be.
|
||||
<span class="permalink">(<a href="#exit">link</a>)</span></h3>
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
|
||||
<h3 id="outproxy">I can't access regular internet sites through I2P.
|
||||
<span class="permalink">(<a href="#outproxy">link</a>)</span></h3>
|
||||
<p>
|
||||
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 outproxies at the moment are true.i2p and krabs.i2p.
|
||||
To use these, <a href="http://localhost:7657/i2ptunnel/edit.jsp?tunnel=0">edit your i2ptunnel setting</a>
|
||||
and set your outproxy list to 'true.i2p,krabs.i2p'.
|
||||
If it doesn't work, they are not up. It is not I2P's fault.
|
||||
</p>
|
||||
|
||||
<h3 id="down">Most of the eepsites within I2P are down?
|
||||
<span class="permalink">(<a href="#down">link</a>)</span></h3>
|
||||
<p>
|
||||
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.
|
||||
<a href="http://inproxy.tino.i2p/status.php">inproxy.tino.i2p</a> and
|
||||
<a href="http://perv.i2p/stats.cgi">perv.i2p</a> track active eepsites.
|
||||
</p>
|
||||
|
||||
<h3 id="myeepsite">How do I set up my own eepsite?
|
||||
<span class="permalink">(<a href="#myeepsite">link</a>)</span></h3>
|
||||
<p>
|
||||
Click on the <a href="http://localhost:7658/">My Eepsite Link</a>
|
||||
on the top of your router console for instructions.
|
||||
</p>
|
||||
|
||||
<h3 id="remote_webconsole">How can I access the web console from my other machines or password protect it?
|
||||
<span class="permalink">(<a href="#remote_webconsole">link</a>)</span></h3>
|
||||
<p>
|
||||
For security purposes, the router's admin console by default only listens
|
||||
|
@ -99,7 +99,7 @@ uses AES256 with ephemeral keys):</p>
|
||||
|
||||
<p><img src="/_static/images/endToEndEncryption.png" alt="end to end layered encryption" /></p>
|
||||
|
||||
<p>The specific use of these algorithms are outlined <a href="how_cryptography">elsewhere</a></p>
|
||||
<p>The specific use of these algorithms are outlined <a href="how_cryptography">elsewhere</a>.</p>
|
||||
|
||||
<p>The two main mechanisms for allowing people who need militant grade anonymity use the network are
|
||||
explicitly delayed garlic routed messages and more comprehensive tunnels to include support for pooling
|
||||
@ -119,7 +119,9 @@ tunnel and another K hops through the inbound tunnel - the size of the network (
|
||||
<a href="http://freenetproject.org">freenet</a> to allow it to use alternate transports, such as
|
||||
<a href="http://java.sun.com/products/jms/index.jsp">JMS</a>, then grew into its own as an
|
||||
'anonCommFramework' in April 2003, turning into I2P in July, with code being cut in earnest in August '03,
|
||||
reaching the 0.2 release in September, 0.3 in March, and 0.4 in September. I2P is currently moving forward according to
|
||||
reaching the 0.2 release in September, 0.3 in March '04, and 0.4 in September '04.
|
||||
Release 0.5 followed in early '05 and 0.6 in mid-'05.
|
||||
I2P is currently moving forward according to
|
||||
the <a href="roadmap">roadmap</a>.</p>
|
||||
|
||||
<p>The network itself is not ready for general use, and should not be used by those who need anonymity
|
||||
@ -136,12 +138,10 @@ are being written in Python. The code works on the current <a href="http://www.k
|
||||
we are hoping to get it working on <a href="http://gcc.gnu.org/java/">GCJ</a> sooner rather than later.</p>
|
||||
|
||||
<h2>Where?</h2>
|
||||
<p>Anyone interested should subscribe to the <a href="http://dev.i2p.net/pipermail/i2p/">mailing list</a> and
|
||||
join us on the irc channel #i2p (hosted concurrently on irc.freenode.net, irc.postman.i2p, and irc.freshcoffee.i2p). Weekly development meetings are held there every
|
||||
Tuesday at 9pm GMT with <a href="meetings">archives available</a>.</p>
|
||||
<p>Anyone interested should
|
||||
join us on the irc channel #i2p (hosted concurrently on irc.freenode.net, irc.postman.i2p, and irc.freshcoffee.i2p).
|
||||
There are currently no scheduled development meetings, however
|
||||
<a href="meetings">archives are available</a>.</p>
|
||||
|
||||
<p>The current source is available through an anonymous CVS repository</p>
|
||||
<pre>
|
||||
cvs -d :pserver:anoncvs@i2p.net/cvsroot co i2p</pre>
|
||||
<p>with the password <code>anoncvs</code>. </p>
|
||||
<p>The current source is available in <a href="monotone.html">monotone</p>.
|
||||
{% endblock %}
|
||||
|
@ -10,7 +10,11 @@
|
||||
- <a href="http://syndie.i2p2.de/download.html">Download</a>
|
||||
</p>
|
||||
<p><b>Latest News:</b><br />
|
||||
2008-02-01 <a href="statnotes0108">status notes 01 2008</a></p>
|
||||
2008-02-01 <a href="statnotes0108">status notes 01 2008</a>
|
||||
<br />
|
||||
2008-02-05 Upgrading to the upcoming 0.6.1.31 - instructions at
|
||||
<a href="http://forum.i2p.net/viewtopic.php?t=2532">forum.i2p.net</a> or
|
||||
<a href="http://forum.i2p/viewtopic.php?t=2532">forum.i2p</a>
|
||||
|
||||
<p>I2P is an anonymizing network, offering a simple layer that identity-sensitive
|
||||
applications can use to securely communicate. All data is wrapped with several
|
||||
|
@ -2,8 +2,8 @@
|
||||
{% block title %}Old Tunnel Implementation{% endblock %}
|
||||
{% block content %}
|
||||
|
||||
<b>Note: NOT used! see tunnel-alt.html</b>
|
||||
|
||||
<b>Note: Obsolete - NOT used! see <a href="tunnel-alt.html">tunnel-alt.html</a> for the new implementation</b>
|
||||
<br>
|
||||
<code>$Id: tunnel.html,v 1.10 2005/01/16 01:07:07 jrandom Exp $</code>
|
||||
<pre>
|
||||
1) <a href="#tunnel.overview">Tunnel overview</a>
|
||||
|
Reference in New Issue
Block a user