Brian,<div><br></div><div>I think that may have worked. I may have just had the tahoe.cfg pointing at the wrong IP addresses. I'm hoping to test it this week and see if others in the grid can see my boxes. (I have set up a separate tunnel for each box.)</div>
<div><br></div><div>It's a less than idea solution, but it might get this grid off the ground.</div><div><br></div><div>Thank you.<br clear="all">----<br>- Think carefully.<br>- Contra mundum - "Against the world" (St. Athanasius)<br>
- Credo ut intelliga - "I believe that I may know" (St. Augustin of Hippo)<br>
<br><br><div class="gmail_quote">On Sun, Dec 20, 2009 at 1:18 PM, Brian Warner <span dir="ltr"><<a href="mailto:warner@lothar.com">warner@lothar.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">Jody Harris wrote:<br>
> For the record, I've tried and failed to use ssh tunneling. Can someone<br>
> explain to be why this solution won't work? I've searched the tickets<br>
> and the mailing list and not found an explanation as to why this fails.<br>
> I think it would be nice to have it documented, if someone can explain it.<br>
<br>
</div></div>How exactly were you setting up the tunnel? And was this tunnel for the<br>
purpose of letting your node connect to the outside world, or for the<br>
outside world to connect to your node?<br>
<br>
If the latter, I'd be using "ssh -R12345:localhost:6789", use the<br>
tahoe.cfg "tub.location" setting to announce the "targethost:12345"<br>
public side of your tunnel, and the "tub.port" setting to tell your node<br>
to listen on localhost:6789 . That ought to cause other nodes to connect<br>
to the outside of your tunnel. Note that without the tub.location<br>
setting, your node will announce its real (internal+unreachable) address<br>
to the other nodes, and they probably won't be able to connect in.<br>
However, if they have public IP addresses, you might be able to connect<br>
out, possibly masking or confusing the problem.<br>
<br>
If the former (i.e. if you're using ssh like an outbound proxy), then<br>
the challenge is that tahoe will connect to the introducer, then connect<br>
to every node announced by the introducer, all using the IP addresses<br>
contained in the various FURLs. So a single tunnel won't do (you'd need<br>
to create a tunnel for each node, and you'd have to intercept the<br>
Introducer messages to trick your node into connecting to the local<br>
tunnel endpoint instead of the actual remote address). But, ssh can<br>
behave like a SOCKS5 server, and you can run your tahoe node under<br>
'tsocks' or 'runsocks' to force all the network connections to go to<br>
that socks server. This is how we suggest people get Tahoe running under<br>
Tor, since the Tor client also behaves like a SOCKS5 server.<br>
<br>
does that help?<br>
cheers,<br>
<font color="#888888"> -Brian<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
tahoe-dev mailing list<br>
<a href="mailto:tahoe-dev@allmydata.org">tahoe-dev@allmydata.org</a><br>
<a href="http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev" target="_blank">http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev</a><br>
</div></div></blockquote></div><br></div>