torproject/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-12-06 19:41:15 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

DynIP and NAT info updated

Browse Source 
svn:r4294
This commit is contained in:
Thomas Sjögren
2005-05-23 13:51:02 +00:00
parent 4b93d2a281
commit daed419bae
1 changed files with 8 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/tor-doc.html
+8 -6
View File
@@ -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