diff options
| author | Thomas Sjögren <thomas@northernsecurity.net> | 2005-05-23 13:51:02 +0000 |
|---|---|---|
| committer | Thomas Sjögren <thomas@northernsecurity.net> | 2005-05-23 13:51:02 +0000 |
| commit | daed419baebeaa33d0a97ddd17cdbde09c833099 (patch) | |
| tree | f08f05876fa617d74bb98026551d4f9400882092 | |
| parent | 4b93d2a281edb6f5eb7c54acbbba43b22d99a8f6 (diff) | |
| download | tor-daed419baebeaa33d0a97ddd17cdbde09c833099.tar.gz tor-daed419baebeaa33d0a97ddd17cdbde09c833099.zip | |
DynIP and NAT info updated
svn:r4294
| -rw-r--r-- | doc/tor-doc.html | 14 |
1 files changed, 8 insertions, 6 deletions
diff --git a/doc/tor-doc.html b/doc/tor-doc.html index 13f4cd014e..46b6f13f11 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.</li> <li>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, <a href="mailto:tor-volunteer@freehaven.net">even -better</a>.)</li> +server itself knows its IP. Have a look at this +<a href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#DynamicIP"> +entry in the FAQ</a>.</li> +<li>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 +<a href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients"> +this entry</a> offers some examples on how to do this.</li> <li>Your server will passively estimate and advertise its recent bandwidth capacity. Clients choose paths weighted by this capacity, so high-bandwidth |