[tahoe-dev] Tahoe-lafs and nodes behind NAT (behind another NAT)

[Jody Harris]

I realize that it's a really, really hard problem to solve.

What I asked with this last message is, "Has anyone considered SIP as a
possible solution to this problem?"
RFC 3261: http://www.ietf.org/rfc/rfc3261.txt?number=3261

Another possible solution might be the protocol that Jabber uses to
establish peer-to-peer file transfers. "Has anyone considered the
possibility of using this as a solution?"
http://xmpp.org/extensions/xep-0096.html

I'm not a programmer (per se). I'm not going to learn how to program in
Python. I am, however, a problem solver. I'm really, really interested in
finding interesting solutions to interesting problems. THIS clearly is an
"interesting problem."

I know it's a really really hard problem to solve. I've pointed to two
opensource projects that have solved similar problems.

If this level of usage is outside the parameters of what tahoe-lafs is
trying to address, that's fine. I'm just asking.

Thanks,
Jody
----
- Think carefully.
- Contra mundum - "Against the world" (St. Athanasius)
- Credo ut intelliga - "I believe that I may know" (St. Augustin of Hippo)


On Fri, Dec 18, 2009 at 9:37 PM, Shawn Willden <shawn at willden.org> wrote:

> On Friday 18 December 2009 04:43:13 pm Jody Harris wrote:
> > Am I to understand this to mean that resolving this issue is not a
> priority
> > for the tahoe development team?
>
> Well, I can't speak for the "tahoe development team" (whatever that is) but
> what I meant is that this is a really hard problem to solve, and it's
> really
> sad that it impedes so much progress.
>
> As for the solution, there are a lot of different NAT traversal techniques
> that address various forms of NAT.  What's needed is for someone to do the
> research on the tools and techniques that are most applicable, and then
> take
> a shot at adding traversal support to Tahoe.
>
> Perhaps you'd like to do it?  A good place to start might be to find out
> what
> NAT traversal libraries exist and how hard they are to use, and how hard
> they
> are to port to all of the platforms Tahoe runs on.  Python libs would be
> ideal, but C or C++ libs aren't too bad, as long as they're portable.
>
>        Shawn.
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at allmydata.org
> http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20091218/28ee2503/attachment.html>