.33 downloads

This commit is contained in:
zzz
2008-04-27 13:05:35 +00:00
parent fab547c205
commit 88e860ee15
5 changed files with 44 additions and 25 deletions

View File

@ -3,26 +3,26 @@
{% block content %}<h3>Clean installs</h3>
<ul>
<li>Graphical installer:<br />
<a href="http://mirror.i2p2.de/i2pinstall_0.6.1.32.exe">i2pinstall-0.6.1.32.exe</a>
<a href="http://mirror.i2p2.de/i2pinstall_0.6.1.33.exe">i2pinstall-0.6.1.33.exe</a>
(SHA1
dec477401dc4f5ac98a5e50e107fe2ccc1431ce5
<a href="http://mirror.i2p2.de/i2pinstall_0.6.1.32.exe.sig">sig</a>)<br />
61a333820e5f8726391b22ba8cd55e0a5430c812
<a href="http://mirror.i2p2.de/i2pinstall_0.6.1.33.exe.sig">sig</a>)<br />
Download that file and run it. If you're not on windows, you can
type <code>java -jar i2pinstall-0.6.1.32.exe</code> (yes, really)</li>
type <code>java -jar i2pinstall-0.6.1.33.exe</code> (yes, really)</li>
<li>Headless install:<br />
<a href="http://mirror.i2p2.de/i2pheadless_0.6.1.32.tar.bz2">i2pheadless_0.6.1.32.tar.bz2</a>
<a href="http://mirror.i2p2.de/i2pheadless_0.6.1.33.tar.bz2">i2pheadless_0.6.1.33.tar.bz2</a>
(SHA1
a385d6456df6835d4dc6aec146a51e266e91fbe6
<a href="http://mirror.i2p2.de/i2pheadless_0.6.1.32.tar.bz2.sig">sig</a>)<br />
Run <code>(tar xjvf i2pheadless_0.6.1.32.tar.bz2 ; cd i2p ; vi install-headless.txt)</code></li>
74e94871dca130bde0e49c0855ed8156c4012270
<a href="http://mirror.i2p2.de/i2pheadless_0.6.1.33.tar.bz2.sig">sig</a>)<br />
Run <code>(tar xjvf i2pheadless_0.6.1.33.tar.bz2 ; cd i2p ; vi install-headless.txt)</code></li>
<li>Source install:<br />
<a href="http://mirror.i2p2.de/i2psource_0.6.1.32.tar.bz2">i2psource_0.6.1.32.tar.bz2</a>
<a href="http://mirror.i2p2.de/i2psource_0.6.1.33.tar.bz2">i2psource_0.6.1.33.tar.bz2</a>
(SHA1
0c2eac42c21bdbc7c877dfc0b4e9430a34f7457f
<a href="http://mirror.i2p2.de/i2psource_0.6.1.32.tar.bz2.sig">sig</a>)<br />
ca73e5cf57d57c7de4b49ae41b2890f890d5d0bb
<a href="http://mirror.i2p2.de/i2psource_0.6.1.33.tar.bz2.sig">sig</a>)<br />
Alternately, you can fetch the source from <a href="monotone">monotone</a>.
<br/>
Run <code>(tar xjvf i2psource_0.6.1.32.tar.bz2 ; cd i2p-0.6.1.32 ; ant dist)</code> then either
Run <code>(tar xjvf i2psource_0.6.1.33.tar.bz2 ; cd i2p-0.6.1.33 ; ant dist)</code> then either
run the GUI installer or headless install as above</li>
</ul>
@ -58,7 +58,7 @@ as the default settings of 32 KBps down / 16 KBps up are fairly slow.
<p>
Both automatic and manual upgrades are available for the release.
</p><p>
If you are running 0.6.1.31, your router should detect the
If you are running 0.6.1.31 or 0.6.1.32, your router should detect the
new release, to upgrade simply click the 'Update Available' link on your router console
when it appears.
</p><p>
@ -78,10 +78,10 @@ receive the release.
<h3>Updates from earlier releases (manual method):</h3>
<ol>
<li>Download <a href="http://mirror.i2p2.de/i2pupdate_0.6.1.32.zip">i2pupdate_0.6.1.32.zip</a>
<li>Download <a href="http://mirror.i2p2.de/i2pupdate_0.6.1.33.zip">i2pupdate_0.6.1.33.zip</a>
(SHA1
5b3157096ac5a7af81e9b0555aadc7738c22d79d
<a href="http://mirror.i2p2.de/i2pupdate_0.6.1.32.zip.sig">sig</a>) to your I2P
8f0baefd50ee87bd876d25ca4af38479c0b2599b
<a href="http://mirror.i2p2.de/i2pupdate_0.6.1.33.zip.sig">sig</a>) to your I2P
installation directory and rename as i2pupdate.zip.
(alternately, you can get the source as above and run "ant updater", then copy the
resulting i2pupdate.zip to your I2P installation directory). You do

View File

@ -186,7 +186,7 @@ currently take advantage of TOR to outproxy.</p>
<ul>
<li>implicit transparent load balancing of messages
across multiple peers, rather than a single path</li>
<li>resiliance vs. failures by running multiple
<li>resilience vs. failures by running multiple
tunnels in parallel, plus rotating tunnels</li>
<li>scale each client's connections at O(1) instead
of O(N) (Alice has e.g. 2 inbound tunnels that are

View File

@ -2,13 +2,16 @@
{% block title %}I2P Anonymous Network{% endblock %}
{% block content %}
<p><b>Latest version:</b><br />
2008-03-09 - I2P 0.6.1.32 - {{ urlify("release-0.6.1.32", "Announcement", "html")}}
2008-04-26 - I2P 0.6.1.33 - {{ urlify("release-0.6.1.33", "Announcement", "html")}}
- <a href="download">Download</a><br />
2007-09-28 - Syndie 1.101a -
<!-- <a href="http://dev.i2p.net/pipermail/i2p/2007-September/001355.html">Announcement</a> -->
- <a href="http://syndie.i2p2.de/download.html">Download</a>
</p>
<p><b>Latest News:</b><br />
2008-04-26 - I2P 0.6.1.33
<a href="release-0.6.1.33.html">Released</a>
<br />
2008-04-20 -
<a href="http://trac.i2p2.i2p/">We are now using Trac as bugtracker</a>
<br />
@ -20,9 +23,6 @@
<a href="http://forum.i2p2.de/">forum.i2p2.de</a>.
<a href="http://forum.i2p/">forum.i2p</a> is back up.
<br />
2008-03-09 - I2P 0.6.1.32
<a href="release-0.6.1.32.html">Released</a>
<br />
2008-02-05 - Upgrading from 0.6.1.30 or earlier -
<a href=upgrade-0.6.1.30.html>instructions</a>
<br />

View File

@ -127,7 +127,7 @@ of messages transferred would fit easily within a single unfragmented UDP packet
the largest of the messages would fit within 20-30 packets. As mule pointed out, TCP
adds a significant overhead when dealing with so many small packets, as the ACKs are
within an order of magnitude in size. With UDP, we can optimize the transport for
both efficiency and resiliance by taking into account I2P's particular needs.</p>
both efficiency and resilience by taking into account I2P's particular needs.</p>
<p>It will be a lot of work though.</p>
@ -215,7 +215,7 @@ samples when dealing with longer tunnels.</p>
</li>
<li><h3 id="ordering">Strict ordering of participants within tunnels</h3>
<b><i>Implemented in I2P 0.6.1.33</a></i></b>
<b><i>Implemented in I2P <strike>0.6.1.33</strike> 0.6.2</a></i></b>
<p>As Connelly <a href="http://dev.i2p/pipermail/i2p/2004-July/000335.html">proposed</a>
to deal with the <a href="http://prisms.cs.umass.edu/brian/pubs/wright-tissec.pdf">predecessor attack</a>
@ -327,6 +327,23 @@ pass it along, except at any peers where the clove exposed includes delay instru
<li><h2 id="performance">Performance</h2><ul>
<li><h3 id="reply">Persistent Tunnel / Lease Selection</h3>
<b><i>Outbound tunnel selection implemented in 0.6.1.30, inbound lease selection scheduled for release 0.6.2</i></b>
<p>Selecting tunnels and leases at random for every message creates
a large incidence of out-of-order delivery, which prevents the streaming lib from
increasing its window size as much as it could.
By persisting with the same selections for a given connection,
the transfer rate is much faster.
</p></li>
<li><h3 id="reply">Reply LeaseSet Bundling</h3>
<b><i>Scheduled for fixing in release 0.6.2</i></b>
<p>Currently, I2P bundles a reply leaseset (typically 1056 bytes) with every outbound
client message, which is a massive overhead. A fix is in testing now.
</p></li>
<li><h3 id="sessionTag">Migrate sessionTag to synchronized PRNG</h3>
<p>Right now, our <a href="how_elgamalaes">ElGamal/AES+SessinTag</a> algorithm works by tagging each
@ -348,7 +365,9 @@ delivery).</p>
</li>
<li><h3 id="streaming">Full streaming protocol improvements</h3>
<b><i>Several improvements implemented in I2P 0.6.1.28, but still lots here to investigate</i></b>
<b><i>Several improvements implemented in I2P 0.6.1.28,
and significant additional fixes in 0.6.1.33,
but still lots here to investigate</i></b>
<p>Since I2P <a href="http://dev.i2p.net/pipermail/i2p/2004-November/000491.html">0.4.2</a>,
we have had a full sliding window streaming library, improving upon the older

View File

@ -79,7 +79,7 @@ the tunnels themselves.</p>
<p>I2P is an inherently packet switched network, even with these
tunnels, allowing it to take advantage of multiple tunnels running
in parallel, increasing resiliance and balancing load. Outside of
in parallel, increasing resilience and balancing load. Outside of
the core I2P layer, there is an optional end to end streaming library
available for client applications, exposing TCP-esque operation,
including message reordering, retransmission, congestion control, etc.</p>