[or-cvs] setting up your own network is now a faq entry where it bel...

[arma@xxxxxxxx]

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

Modified Files:
	tor-doc.html 
Log Message:
setting up your own network is now a faq entry where it belongs


Index: tor-doc.html
===================================================================
RCS file: /home2/or/cvsroot/tor/doc/tor-doc.html,v
retrieving revision 1.97
retrieving revision 1.98
diff -u -d -r1.97 -r1.98
--- tor-doc.html	26 Aug 2005 23:00:14 -0000	1.97
+++ tor-doc.html	26 Aug 2005 23:39:59 -0000	1.98
@@ -122,51 +122,11 @@
 <h2>Setting up your own network</h2>
 
 <p>
-If you want to experiment locally with your own network, or you're cut
-off from the Internet and want to be able to mess with Tor still, then
-you may want to set up your own separate Tor network.
-
-<p>
-To set up your own Tor network, you need to run your own directory
-servers, and you need to configure each client and server so it knows
-about your directory servers rather than the default ones.
-
-<ul>
-<li>1: Grab the latest release. Use at least 0.1.1.6-alpha.</li>
-<li>2: For each directory server you want,</li>
-<ul>
-<li>2a: Set it up as a server (see <a href="#server">"setting up a
-server"</a> above), with a least ORPort, DirPort, DataDirectory, and Nickname
-defined. Set "AuthoritativeDirectory 1", and set "RecommendedVersions"
-to a comma-separated list of acceptable
-versions of the code for clients and servers to be running.</li>
-<li>2b: Create a file called approved-routers in its DataDirectory.
-Leave it empty for now.</li>
-<li>2c: Run it: <tt>tor --list-fingerprint</tt> if your torrc is in
-the default place, or <tt>tor -f torrc --list-fingerprint</tt> to
-specify a torrc. This will generate your keys and output a fingerprint
-line.</li>
-</ul>
-<li>3: Now you need to teach clients and servers to use the new
-dirservers. For each fingerprint, add a line like<br>
-<tt>DirServer 18.244.0.114:80 719B E45D E224 B607 C537 07D0 E214 3E2D 423E 74CF</tt><br>
-to the torrc of each client and server who will be using your network.</li>
-<li>4: Each server (including the dir-servers) should set
-"AssumeReachable 1" in their torrc. This bypasses the reachability detection
-and lets the network bootstrap.
-<li>5: If you are running the network using local/private IP space, the
-dirservers need to set "DirAllowPrivateAddresses 1" in their torrc, and
-all the servers need to explicitly set their Address to their IP in the
-torrc.
-<li>6: Collect the 'fingerprint' lines from
-each server (including directory servers), and include them (one per
-line) in each approved-routers file. You can hup the tor process for
-each directory server to reload the approved-routers file (so you don't
-have to restart the process).</li>
-<li>7: Be sure to start at least 3 servers in addition to the
-dir-servers. If they're not succeeding at building circuits, hup them
-until they do.</li>
-</ul>
+See the <a
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#OwnTorNetwork";>new
+FAQ entry</a> for how to set up your
+own Tor network.
+</p>
 
 </body>
 </html>