[tahoe-dev] dealing with NAT

[Greg Troxel]

Like almost everyone, I am afflicted by NAT in the v4 world.  So far I
haven't tried to set up a tahoe server behind NAT; obviously clients
work well.

I understand that one can set up a static port mapping from the NAT box
back to the tahoe server, and configure the public IP address and port
in tub.location.  However, I suspect that connections from behind the
same NAT may not work, and in any case they'd be less efficient.

So, should I set up tub.location to be both the RFC1918 address/port and
the NATed address/port?  Has anyone tried this?

If so, doesn't this mean other clients will try to connect in the
different RFC1918 address space on their side, and perhaps misconnect
(although not likely; this is for a private grid with a registry for
RFC1918 space so it's different at all the various places).


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20110202/50a01b4c/attachment.pgp>