Changes between Version 51 and Version 52 of FAQ

Timestamp:

2011-10-10T06:55:01Z (13 years ago)

Author:

tjgillies

Comment:

added another question about NAT

FAQ

@@ -132 +132 @@
 * [http://tahoe-lafs.org/pipermail/tahoe-dev/2011-June/006388.html question about sharing...] (especially [http://tahoe-lafs.org/pipermail/tahoe-dev/2011-June/006427.html this message by Brian Warner])
 * [http://tahoe-lafs.org/pipermail/tahoe-dev/2011-June/006424.html revocation of read-access to an immutable file]
+
+'''[=#Q21_NAT Q21:] How come sometimes my client is connected to my server even though the server is behind NAT?'''
+
+A: 
+Ideally,  all clients attempt to open connections to all servers, and all servers attempt to open connections to all clients. So, if the client is not behind NAT, then even if the server is behind NAT. However, this is not currently the case. 
+**Currently** what it does is that all clients attempt to open connections to all servers, but if there is a connection between two Tahoe-LAFS processes (== Tahoe-LAFS nodes) it can re-use that connection for any client or server in either node. So, when you enabled a storage server on the public facing server, that caused the node behind NAT to initiate a TCP connection to the node on the public facing server. Once that connection was established, that enabled the node there to *use* the server behind NAT.