[or-cvs] mention that we still don"t want servers with high packet l...

Roger Dingledine arma at seul.org
Fri Dec 17 00:14:31 UTC 2004


Update of /home2/or/cvsroot/tor/doc
In directory moria.mit.edu:/home2/arma/work/onion/cvs/tor/doc

Modified Files:
	tor-doc.html 
Log Message:
mention that we still don't want servers with high packet loss or
high latency


Index: tor-doc.html
===================================================================
RCS file: /home2/or/cvsroot/tor/doc/tor-doc.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -d -r1.26 -r1.27
--- tor-doc.html	17 Dec 2004 00:03:40 -0000	1.26
+++ tor-doc.html	17 Dec 2004 00:14:25 -0000	1.27
@@ -224,6 +224,13 @@
 that have at least 20 kilobytes/s each way. If you have more bandwidth
 to offer, that's even better.</p>
 
+<p>If your server is behind a NAT and it doesn't know its own IP (e.g.
+it has an IP of 192.168.x.y), then we can't use it as a server yet.
+(If you want to do dyndns DNS voodoo to get around this, feel free.) And
+if it frequently has a lot of packet loss or really high latency, we
+also can't handle it as a server yet. Otherwise, please help out!
+</p>
+
 <p>To set up a Tor server, do the following steps after installing Tor.
 (These instructions are Unix-centric; if you're excited about working
 with us to get a Tor server working on Windows, let us know and we'll
@@ -324,7 +331,7 @@
 about your directory servers rather than the default ones.
 
 <ul>
-<li>1: Grab the latest release. Use at least 0.0.9rc6.
+<li>1: Grab the latest release. Use at least 0.0.9.
 <li>2: For each directory server you want,
 <ul>
 <li>2a: Set it up as a server (see <a href="#server">"setting up a



More information about the tor-commits mailing list