[tahoe-dev] Can Tahoe works well in this scenario?

[Greg Troxel]

Shu Lin <linshu at gmail.com> writes:

Certainly coda may not do what you want; I just thought you should know
about it.

> For fixing the firewall, I don't quite understand you suggestion. Even
> through, I fixed my setup by opening a port in my firewall last time as you
> suggest if you remember. But, I don't think opening a port is eventually
> acceptable in my deployment. I prefer a zero firewall configuration effort
> as NAT traversal is so a popular technology already. I don't think Skype
> will get success if it has to ask everybody to twist their firewall ports at
> home. :-)

It's hard to tell, but it sounds like you are fundamentally
misunderstanding the network traffic required for tahoe.  Relative to
all nodes that might be clients or servers, you need:

  a public IP address for the introducer, reachable by all servers and
  clients

  servers need either a public IP address, not firewalled, or an address
  with static NAT and firewall allowance so that clients (including
  other servers) can connect.  If the server's address is not global,
  you need to hand configure the static NAT situation

  clients need to be able to reach all servers


Putting all nodes behind a NAT with a strict firewall and no manual
config just isn't going to work.
-------------- 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/20101204/68c25301/attachment.pgp>