From daed419baebeaa33d0a97ddd17cdbde09c833099 Mon Sep 17 00:00:00 2001 From: Thomas Sjögren Date: Mon, 23 May 2005 13:51:02 +0000 Subject: DynIP and NAT info updated svn:r4294 --- doc/tor-doc.html | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) (limited to 'doc/tor-doc.html') diff --git a/doc/tor-doc.html b/doc/tor-doc.html index 13f4cd014..46b6f13f1 100644 --- a/doc/tor-doc.html +++ b/doc/tor-doc.html @@ -133,12 +133,14 @@ notice this quickly and stop advertising the server. Just try to make sure it's not too often, since connections using the server when it disconnects will break.
  • We can handle servers with dynamic IPs just fine, as long as the -server itself knows its IP. If your server is behind a NAT and it doesn't -know its public 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 port forward and set your Address -config option to use dyndns DNS voodoo to get around this, feel free. If -you write a howto, even -better.)
    • +server itself knows its IP. Have a look at this + +entry in the FAQ. +
  • If your server is behind a NAT and it doesn't +know its public IP (e.g. it has an IP of 192.168.x.y), you need to set +up port forwarding. Forwarding TCP connections is system dependent but + +this entry offers some examples on how to do this.
  • Your server will passively estimate and advertise its recent bandwidth capacity. Clients choose paths weighted by this capacity, so high-bandwidth -- cgit v1.2.3