aboutsummaryrefslogtreecommitdiff
path: root/doc/FAQ
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2003-04-05 19:04:05 +0000
committerRoger Dingledine <arma@torproject.org>2003-04-05 19:04:05 +0000
commit1ae95f66ede45f64fd6795cd7cdcc20f9a780c76 (patch)
treef595fd24a198c8e673883ac4ffb911adfae457c8 /doc/FAQ
parent03f4ed309f8d7743817521dfa9cd361364d2183f (diff)
downloadtor-1ae95f66ede45f64fd6795cd7cdcc20f9a780c76.tar
tor-1ae95f66ede45f64fd6795cd7cdcc20f9a780c76.tar.gz
bring docs closer to reality
svn:r221
Diffstat (limited to 'doc/FAQ')
-rw-r--r--doc/FAQ17
1 files changed, 8 insertions, 9 deletions
diff --git a/doc/FAQ b/doc/FAQ
index bd3a96306..e0f199ac5 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -38,17 +38,16 @@ for you.]
3. Running tor.
-3.1. What's this about roles? What kind of server should I run?
+3.1. What kind of server should I run?
The same executable ("or") functions as both client and server, depending
-on the value of the config variable named 'Role'. Role represents a
-combination of which tasks this particular tor server will do. The default
-Role (role 15) is an onion router: it listens for onion routers, listens
-for onion proxies, listens for application proxies, and it connects to
-all other onion routers it learns about. A directory server (role 63)
-does all of the above and also serves directory requests. A simple
-onion proxy, on the other hand (role 8), only listens for application
-proxies. See part 3.1 of the HACKING document for more technical details.
+on which ports are specified in the configuration file. You can specify:
+* APPort: client applications (eg privoxy, Mozilla) can speak socks to
+ this port.
+* OPPort: onion proxies (client onion routers) connect to this port.
+* ORPort: other onion routers connect to this port
+* DirPort: onion proxies and onion routers speak http to this port, to
+ pull down a directory of which nodes are currently available.
3.2. So I can just run a full onion router and join the network?