Updated links in support/*
This commit is contained in:
@ -49,7 +49,7 @@
|
||||
</ol>
|
||||
<h3 id="systems">What systems will I2P run on?
|
||||
<span class="permalink">(<a href="#systems">link</a>)</span></h3>
|
||||
<p>While I2P has been reported to run PCs as meagre as a low-end Pentium II with 64 MB of RAM, you'll have a much better experience on a Pentium III (or better) with 128MB of RAM (or more). A <a href="http://trac.i2p2.de/wiki/java">chart comparing the performance</a> of the various JREs can be found at <a href="http://trac.i2p2.de/wiki/java">http://trac.i2p2.de/wiki/java</a>, but in short: it's at all possible, use Sun/Oracle Java or OpenJDK.</p>
|
||||
<p>While I2P has been reported to run PCs as meagre as a low-end Pentium II with 64 MB of RAM, you'll have a much better experience on a Pentium III (or better) with 128MB of RAM (or more). A <a href="http://{{ i2pconv('trac.i2p2.i2p') }}/wiki/java">chart comparing the performance</a> of the various JREs can be found at <a href="http://{{ i2pconv('trac.i2p2.i2p') }}/wiki/java">http://{{ i2pconv('trac.i2p2.i2p') }}/wiki/java</a>, but in short: it's at all possible, use Sun/Oracle Java or OpenJDK.</p>
|
||||
<p>I2P has been tested on Windows, Linux, FreeBSD (see the note <a href="#compat6x">below</a>), OSX, and OpenSolaris. There is work underway to bring I2P to the Android platform.</p>
|
||||
|
||||
|
||||
@ -58,8 +58,8 @@
|
||||
|
||||
Here are some places, pick one or more.
|
||||
<ul>
|
||||
<li><a href="http://trac.i2p2.de/report/1">trac.i2p2.de</a> ticket (preferred method)</li>
|
||||
<li><a href="http://pastethis.i2p/">pastethis.i2p</a> and follow up on IRC in #i2p</li>
|
||||
<li><a href="http://{{ i2pconv('trac.i2p2.i2p') }}/report/1">{{ i2pconv('trac.i2p2.i2p') }}</a> ticket (preferred method)</li>
|
||||
<li><a href="http://{{ i2pconv('pastethis.i2p') }}/">{{ i2pconv('pastethis.i2p') }}</a> and follow up on IRC in #i2p</li>
|
||||
<li>Discuss with the developers on IRC in #i2p-dev</li></ul>
|
||||
|
||||
<p>
|
||||
@ -97,7 +97,7 @@ We do not know if or when jrandom will return.
|
||||
The *.i2p.net domains were left in a non-functioning state after a power
|
||||
outage at the hosting company.</p>
|
||||
<p>See <a href="jrandom-awol.html">this page</a> for jrandom's parting message and additional information
|
||||
on the migration of *.i2p.net to <a href="index.html">this website</a>.</p>
|
||||
on the migration of *.i2p.net to <a href="{{ site_url() }}">this website</a>.</p>
|
||||
<p>I2P remains in active development.</p>
|
||||
|
||||
<h3 id="cpu">My router is using too much CPU?!?
|
||||
@ -198,13 +198,13 @@ All routers adjust dynamically to changing network conditions and demands.
|
||||
If you are running release 0.6.1.31 or later, you probably don't need to do this.
|
||||
If you are running release 0.6.1.26 or earlier, either follow the
|
||||
<a href="#manual_reseed">manual reseed instructions</a> below
|
||||
or install the <a href="download">latest release</a>.
|
||||
or install the <a href="{{ url_for('downloads_list') }}">latest release</a>.
|
||||
Possible alternate method - add
|
||||
<tt>wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/</tt>
|
||||
to wrapper.config, shutdown the router completely, then start again, then click "reseed".
|
||||
Let us know if this works.
|
||||
</p>
|
||||
<p>...but you *really* should <a href="download">upgrade</a> to the latest version.</p>
|
||||
<p>...but you *really* should <a href="{{ url_for('downloads_list') }}">upgrade</a> to the latest version.</p>
|
||||
|
||||
<h3 id="peers">My router has very few active peers, is this OK?
|
||||
<span class="permalink">(<a href="#peers">link</a>)</span></h3>
|
||||
@ -261,7 +261,7 @@ The best way to stay "better-connected" to the network is to <a href="http://loc
|
||||
</li><li>In the new page, <b>name</b> and <b>describe</b> your new https tunnel as you like.
|
||||
The <b>Access Point</b> is your local port for the new https proxy recommended port's <b>4445</b>.
|
||||
<b>Outproxy</b> should be the outproxy's .i2p address which supports https.
|
||||
See this forum post of <a href="http://forum.i2p/viewtopic.php?p=31356#31356">h2ik</a>'s for the address.
|
||||
See this forum post of <a href="http://{{ i2pconv('forum.i2p') }}/viewtopic.php?p=31356#31356">h2ik</a>'s for the address.
|
||||
Make sure <b>Shared Client</b>, <b>Delay Connect</b>, <b>AutoStart</b> are checked.
|
||||
Other options should be left at the defaults. Click Save. In tunnel manger, click the <b>Start</b> button next to your new tunnel.
|
||||
</li><li>In firefox, click through <b>Tools</b>><b>Options</b>><b>Advanced</b>><b>Network</b>><b>Setting</b>.
|
||||
@ -284,7 +284,7 @@ The best way to stay "better-connected" to the network is to <a href="http://loc
|
||||
</p><p>
|
||||
In addition, you may be vulnerable to collusion between the outproxy operator
|
||||
and operators of other I2P services, if you use the same tunnels ("shared clients").
|
||||
There is additional discussion about this on <a href="http://zzz.i2p/topics/217">zzz.i2p</a>.
|
||||
There is additional discussion about this on <a href="http://{{ i2pconv('zzz.i2p') }}/topics/217">zzz.i2p</a>.
|
||||
</p>
|
||||
|
||||
<h3 id="proxy_other">How do I access IRC, BitTorrent, or other services on the regular Internet?
|
||||
@ -301,7 +301,7 @@ The best way to stay "better-connected" to the network is to <a href="http://loc
|
||||
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://perv.i2p/stats.cgi">perv.i2p</a> tracks active eepsites.
|
||||
<a href="http://{{ i2pconv('perv.i2p') }}/stats.cgi">perv.i2p</a> tracks active eepsites.
|
||||
</p>
|
||||
|
||||
<h3 id="myeepsite">How do I set up my own eepsite?
|
||||
@ -332,15 +332,14 @@ keeps you well-integrated in the network and helps your own transfer speeds.
|
||||
</p><p>
|
||||
I2P is a work in progress. Lots of improvements and fixes are being implemented, and
|
||||
generally speaking, running the latest release will help your performance.
|
||||
If you haven't, <a href="download.html">install the latest release</a>.
|
||||
If you haven't, <a href="{{ url_for('downloads_list', lang=g.lang) }}">install the latest release</a>.
|
||||
</p>
|
||||
|
||||
<h3 id="snark">Bittorrent / I2PSnark / Azureus I2P Plugin Questions?
|
||||
<span class="permalink">(<a href="#snark">link</a>)</span></h3>
|
||||
<p>
|
||||
See the
|
||||
<a href="http://forum.i2p/viewtopic.php?t=2068">I2P Bittorrent FAQ</a>
|
||||
<a href="http://forum.i2p2.de/viewtopic.php?t=2068">(outside I2P)</a>
|
||||
<a href="http://{{ i2pconv('forum.i2p') }}/viewtopic.php?t=2068">I2P Bittorrent FAQ</a>
|
||||
</p>
|
||||
<h3 id="irc">How do I connect to IRC within I2P?
|
||||
<span class="permalink">(<a href="#irc">link</a>)</span></h3>
|
||||
@ -426,7 +425,7 @@ router advanced configuration option <tt>i2cp.tcp.bindAllInterfaces=true</tt> an
|
||||
extremely dangerous.
|
||||
</p><p>
|
||||
If you would like more information on the socks proxy application anyway,
|
||||
there are some helpful hints on the <a href="socks.html">socks page</a>.
|
||||
there are some helpful hints on the <a href="{{ site_url('docs/api/socks') }}">socks page</a>.
|
||||
</p>
|
||||
|
||||
<h3 id="ports">What ports does I2P use?
|
||||
@ -639,7 +638,7 @@ click <em>Shutdown</em>, wait 11 minutes, then start I2P.</p>
|
||||
<span class="permalink">(<a href="#question">link</a>)</span></h3>
|
||||
<p>
|
||||
Great! Find us on IRC irc.freenode.net #i2p or post to
|
||||
the <a href="http://forum.i2p/">forum (within I2P)</a> and we'll post it here (with
|
||||
the <a href="http://{{ i2pconv('forum.i2p') }}/">forum (within I2P)</a> and we'll post it here (with
|
||||
the answer, hopefully).
|
||||
</p>
|
||||
{% endblock %}
|
||||
|
@ -115,6 +115,6 @@ bandwidth, latency, and CPU usage.</p>
|
||||
</ul>
|
||||
<p>
|
||||
Additional ideas for improving the streaming library are described on the
|
||||
<a href="streaming.html#future">streaming library page</a>.
|
||||
<a href="{{ site_url('docs/api/streaming') }}#future">streaming library page</a>.
|
||||
</p>
|
||||
{% endblock %}
|
||||
|
Reference in New Issue
Block a user