[tahoe-dev] Two nodes can't see each other

Shawn Willden shawn at willden.org
Thu Oct 21 11:54:26 UTC 2010

On Thu, Oct 21, 2010 at 12:57 AM, Shu Lin <linshu at gmail.com> wrote:

> I have been running my own introducer and two server nodes. But these two
> nodes can't see each other running although they are both running and
> connected to the introducer.

Are they behind a router/firewall that is doing NAT?

Most often, that's the cause.  If they're both on private IPs, neither can
initiate a connection to the other.  If one of them is publicly accessible
then a bidirectional connection will be established from the "hidden"
machine to the public machine.

Another possible cause if your nodes aren't NATed is just that your firewall
is blocking the ports the nodes are using.  Look at the "client.port" file
in your .tahoe directory to see what port needs to be open.

> Also, the directories created on these two nodes are totally separated.

Right, because the machines can't connect to one another to place shares on
one another.

> Is there any configuration I missed for these two nodes seeing each other
> in one grid?
> Why I don't have this problem while I use public grid? I can see all other
> nodes running and other's directories.

All (or nearly all) of the pubgrid machines are on public IPs and have the
appropriate ports open, so your node(s) can connect to them even if yours
are behind NAT or have their ports blocked.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20101021/e4c25390/attachment.html>

More information about the tahoe-dev mailing list