[tahoe-dev] Tahoe-LAFS + sshfs latency issues

[Linus Lüssing]

On Mon, Jul 25, 2011 at 05:35:49AM +0200, Linus Lüssing wrote:
> On Sat, Jul 23, 2011 at 01:07:31PM +0200, Marco Tedaldi wrote:
> > Hello Linus
> > 
> > greetings from openwireless st. gallen (still using olsr)
> 
> Hey, that sounds familiar :) - you probably know Stefan Braun,
> don't you? Either I've missed an email for him or... could you
> maybe bump him for me, about the slides of his presentation about
> tahoe-lafs :)?
> 
> > 
> > Am 23.07.2011 03:10, schrieb Linus Lüssing:
> > > Hi everyone,
> > > 
> > > I've recently started looking at Tahoe-LAFS and I'm currently
> > > trying to get a feeling of how it works. The use-case I'm
> > > currently aiming at is to have an ftpd and httpd (proftpd +
> > > lighttpd) running on a distributed file system, where anyone can
> > > just add and contribute to the storage capacity. Furthermore I'm
> > > going to use it within an open, public, decentral wireless+vpn
> > > mesh network (e.g. using the mesh routing protocol
> > > B.A.T.M.A.N.-Advanced and the VPN software tinc).
> > 
> > I'm also very interested to hear how it works in your case. We tried it
> > here. It worked, but it was really slow. So now I'm connected to
> > volunteergrid2 because I really want to use the storage. But I see no
> > problem for me to contribute to a second grid inside our mesh here.
> > 
> > I think that tahoe can really benefit the users in community networks. I
> > think that tahoe would have to become more robust in cases where the
> > connection is not stable. As of now, it just seems to drop the
> > connection after a certain amount of time and wait for user interaction.
> > 
> > Keep me updated of what results you are getting. I think, the open mesh
> > networks and the open storage network (you decide yourself how open it
> > really is) fit really well. And if there is a nice user interface (like
> > the no-hasle interface of dropbox for example) in the future, i see
> > really great uses.
> 
> Yes, and together with the early payment integration ideas, like
> having a way to integrate it with bitcoin, that might actually
> help against several attacks, like spam, storage DDoSing or
> selfish users a public grid would face otherwise. And together
> with a decentral concept for the currently central introducer
> node, I bet it would go in the direction of THE one and only
> public grid (though there are still some things I'm probably missing,
> sorry, I'm quite knew to tahoe-lafs :) ).
> 
> Anyway, are you connected to dn42 in St. Gallen? We should
> currently be connected to it here at Freifunk Lübeck (though I
> haven't done any tests of it yet, done not if it actually works
s/done not if/don't know if/

> here :D). If you are or could get connected, maybe we could
> connect our tahoe-lafs nodes for the testing purpose?
> 
> You should be able to reach our introducer within dn42 at
> 10.130.0.16:
> https://krtek.asta.uni-luebeck.de/meutewiki/MetaMeuteMesh/StorageGrid
> (though if it is reachable within dn42, it's probably better to
> move such an entry to the dn42 wiki later - after having verified
> that it works as expected, which is not the case yet)

PS: tahoe-lafs is currently running in the VPN only though, as
stated in the email about the test results. But you should be able to
ping 10.130.0.1 and might be able to ping 10.130.0.16.

> 
> > 
> > best regards
> > 
> > Marco
> 
> Cheers, Linus
> 
> > _______________________________________________
> > tahoe-dev mailing list
> > tahoe-dev at tahoe-lafs.org
> > http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
> > 
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev