Delivery-Date: Mon, 06 Oct 2014 04:58:45 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 4E9141E0A95;
	Mon,  6 Oct 2014 04:58:44 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id A43932F087;
	Mon,  6 Oct 2014 08:58:40 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 4EFED2BC12
 for <tor-talk@lists.torproject.org>; Mon,  6 Oct 2014 08:58:37 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id ypZtldXW9P8M for <tor-talk@lists.torproject.org>;
 Mon,  6 Oct 2014 08:58:37 +0000 (UTC)
Received: from mail.ncf.ca (mail.ncf.ca [206.47.12.45])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 3153B2B597
 for <tor-talk@lists.torproject.org>; Mon,  6 Oct 2014 08:58:37 +0000 (UTC)
Received: from mail.ncf.ca (localhost [127.0.0.1])
 by mail.ncf.ca (Postfix) with ESMTP id 221AA9F1BB
 for <tor-talk@lists.torproject.org>; Mon,  6 Oct 2014 04:58:35 -0400 (EDT)
Received: from [172.16.2.5] (206-248-162-75.dsl.teksavvy.com [206.248.162.75])
 (using TLSv1 with cipher AES128-SHA (128/128 bits))
 (No client certificate requested) (Authenticated sender: fr223)
 by mail.ncf.ca (Postfix) with ESMTPSA id DA1319F19B
 for <tor-talk@lists.torproject.org>; Mon,  6 Oct 2014 04:58:34 -0400 (EDT)
References: <CAM+RCEg_xRY8uQfEzKtwN2d5sk5bCXnYWyxvcNPPb2wSkb+mNg@mail.gmail.com>
 <CAM+RCEgYBRKV9iXijsFf4i8=RuFT4HbVRUK_ZfHsbA8Q3qwQDg@mail.gmail.com>
 <5432471B.1000909@web.de>
In-Reply-To: <5432471B.1000909@web.de>
Mime-Version: 1.0 (Apple Message framework v1085)
Message-Id: <DC323F89-FA2B-46DA-A3EA-81B584AD2C95@ncf.ca>
From: stn <stn@ncf.ca>
Date: Mon, 6 Oct 2014 04:58:24 -0400
To: tor-talk@lists.torproject.org
X-Mailer: Apple Mail (2.1085)
X-NCF-Filtered: By ProxSMTP on pallando Mon Oct  6 04:58:35 2014 -0400 (EDT)
Subject: Re: [tor-talk] tor browser speed.
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

hi
i've been informed running a bridge  relay/node requires 24/7 uptime so i'm building a "Box" to run at home dedicated to a tor bridge.

it takes more than a week for a node to start to integrate into the network and every time the node goes down i think you start again.

but you can run one via torcloud. i run two of them (https://cloud.torproject.org/)
originally i opened a torcloud node to offer bandwidth to the torproject while i built my home torbox from old hardware but ...

torcloud is inexpensive (for 1 year at least) and likely more reliable than a home ISP connection  (at least more reliable than my connection in canada).
this way i can donate bandwidth both from home and via "the cloud".  if one goes down the other still runs.  

additionally cloud + home offers network diversity.

i can't gurantee you will reach the speeds you desire however amazon's cloud services are designed to be steady and reliable.  again  better than my home ISP connection in terms of uptime.

torcloud is an official torproject release.
cf
https://cloud.torproject.org/

i quite like it.  the torproject has a preconfigured image you install after starting your amazon cloud computing account.     

i am not an expert but have been through the process twice so can offer help if you run into problems.   


i have yet to pay any fees after running for one month but torcloud cap is currently $3 USD/month under the amazon cloud computing "Free" plan (free up to 15GB networking bandwidth and torlcoud caps at 40GB usage/month).

once your torcloud bridge is running you can connect to it by manually entering your bridge node IP in place of a list of bridges tor gives you.

bridge writeup here
https://www.torproject.org/docs/bridges.html.en







On Oct 6, 2014, at 3:39 AM, Hartmut Haase wrote:

> Does that mean my PC has to run all day long? Normally I use it about 4 hours a day only.
>> The safest and easiest way is to run a middle node.
> How do I do that?

-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

