[tahoe-dev] dealing with NAT

[Greg Troxel]

  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.)

By 'it is working', do you mean that tahoe client nodes which are behind
the same nat as one of the servers can store shares on those servers?
If so, is the NAT box doing NAT on those packets even though they arrive
on the internal vs external interface, or is tub.locations configured as
I asked, or something else?

One could also say that in a volunteergrid type system it may be just as
well not to use your own server.

-------------- 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/c10a8ba6/attachment.asc>