[tahoe-dev] dealing with NAT

[Jody Harris]

Most of the nodes on VolunteerGrid2 are set up behind routers with
port-forwarding to the nodes. With the exception of one 6+ year old router,
it is working we haven't experienced any problems. (The router in question
is scheduled for replacement.)

---
- Think carefully.


On Wed, Feb 2, 2011 at 9:36 AM, Greg Troxel <gdt at ir.bbn.com> wrote:

>
> 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).
>
>
>
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20110202/9e64bb7c/attachment-0001.html>