[tahoe-dev] Newbie problems

Denis Cheong denis at denisandyuki.net
Tue Feb 5 13:09:59 UTC 2013


I will take responsibility for the pubgrid at tahoe.koo storage node assuming that's the online one you're referring to.

This node is behind Internet facing NAT (no port forwarding possible) and is now using pagekite to expose its tub port. If somebody else has a permanent pagekite proxy it can use then it may be able to stay online last past the 31 day free trial subscription.


On 05/02/2013, at 11:52 PM, Paul Rabahy <prabahy at gmail.com> wrote:

> Excellent. I'm not sure if I'll be able to get PRabahyWork to actually work or not. It looks like we have another 2 storage nodes that have connected (1 is currently online). I also see that an additional file has been added to the public directory. Looks like we are good to go!
> 
> 
> On Tue, Feb 5, 2013 at 12:35 AM, Oleksandr Drach <luckyredhot at gmail.com> wrote:
>> Dear Paul,
>> I do confirm that PRabahy storage node is online/connected now.
>> PRabahyWork storage node is offline.
>> Thanks!
>> 
>> On Feb 5, 2013 1:19 AM, "Paul Rabahy" <prabahy at gmail.com> wrote:
>>> Do you mind checking again if PRabahy is online/connected? I made the necessary changes to the firewall.
>>> 
>>> 
>>> On Mon, Feb 4, 2013 at 9:25 AM, Oleksandr Drach <luckyredhot at gmail.com> wrote:
>>>> Dear All,
>>>> We need not only public introducer but also few storage nodes for it.
>>>> At the moment there is no storage node connected.
>>>> 
>>>> Thanks!
>>>> 
>>>> Sincerely,
>>>> Oleksandr Drach,
>>>> 
>>>> e-mail: luckyredhot at gmail.com.
>>>> 
>>>> 
>>>> 2013/2/4 Paul Rabahy <prabahy at gmail.com>
>>>>> It actually looks like I have the introducer setup correctly, but my storage nodes still need some work. You should be able to connect, but just not access any storage.
>>>>> 
>>>>> 
>>>>> 
>>>>> On Mon, Feb 4, 2013 at 9:06 AM, Paul Rabahy <prabahy at gmail.com> wrote:
>>>>>> I volunteer to become "Test Grid Wrangler". I setup a new introducer and hooked up a storage node to it. https://tahoe-lafs.org/trac/tahoe-lafs/wiki/TestGrid has been updated with the new introducer furl and public test directory.
>>>>>> 
>>>>>> It still appears that I need to setup some more port forwarding or something because I cannot connect to it from outside my LAN. I'll try to do that this evening (Eastern Timezone).
>>>>>> 
>>>>>> @Till, I haven't seen a setting for this. My main thought is that if a person was trying to abuse the system they could just break the file into many small chunks and upload them all. Hopefully once the accounting project is finished we will be able to set per-user storage limits.
>>>>>> 
>>>>>> @Eric, Agreed. The test grid was the first place I went to quickly try out Tahoe-LAFS. Without it, I believe that I would have lost interest and tried to find a different product.
>>>>>> 
>>>>>> @Greg, My plan is to have a public introducer, but each user will have to setup their own node. If another person sets up a public WUI, I don't know if there is much I will be able to do about it. We can cross that bridge if/when we come to it.
>>>>>> 
>>>>>> 
>>>>>> On Mon, Feb 4, 2013 at 8:37 AM, Greg Troxel <gdt at ir.bbn.com> wrote:
>>>>>>> 
>>>>>>> "erpo41 at gmail.com" <erpo41 at gmail.com> writes:
>>>>>>> 
>>>>>>> > I liked the test grid when I was just getting started. If I had had to set
>>>>>>> > up my own introducer and server and client just to try it out, I probably
>>>>>>> > would have passed. I definitely would not have set up multiple VMs to play
>>>>>>> > with different values of n and h.
>>>>>>> >
>>>>>>> > To prevent abuse, we could just set the expiration time for files to 48
>>>>>>> > hours.
>>>>>>> 
>>>>>>> My impression is that the cause of the abuse (not fair, I know) is the
>>>>>>> public gateway.  Once you need to set up a client to use it, the effort
>>>>>>> becomes too high compared to other file distribution methods.  I found
>>>>>>> the pubgrid very useful when getting started, and the public WUI not
>>>>>>> really that useful.
>>>>>>> 
>>>>>>> _______________________________________________
>>>>>>> tahoe-dev mailing list
>>>>>>> tahoe-dev at tahoe-lafs.org
>>>>>>> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> tahoe-dev mailing list
>>>>> tahoe-dev at tahoe-lafs.org
>>>>> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>>>> 
>>>> 
>>>> _______________________________________________
>>>> tahoe-dev mailing list
>>>> tahoe-dev at tahoe-lafs.org
>>>> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>>> 
>>> 
>>> _______________________________________________
>>> tahoe-dev mailing list
>>> tahoe-dev at tahoe-lafs.org
>>> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>> 
>> _______________________________________________
>> tahoe-dev mailing list
>> tahoe-dev at tahoe-lafs.org
>> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
> 
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20130206/82dcf6ce/attachment-0001.html>


More information about the tahoe-dev mailing list