Delivery-Date: Mon, 04 Jan 2016 11:17:11 -0500
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.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_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 2137D1E01B4;
	Mon,  4 Jan 2016 11:17:10 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id E4F3238CB8;
	Mon,  4 Jan 2016 16:17:04 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 29FF238CAD
 for <tor-talk@lists.torproject.org>; Mon,  4 Jan 2016 16:17:01 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
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 MM5534eZCu3F for <tor-talk@lists.torproject.org>;
 Mon,  4 Jan 2016 16:17:01 +0000 (UTC)
Received: from mail-qg0-x233.google.com (mail-qg0-x233.google.com
 [IPv6:2607:f8b0:400d:c04::233])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 0937F38B61
 for <tor-talk@lists.torproject.org>; Mon,  4 Jan 2016 16:16:58 +0000 (UTC)
Received: by mail-qg0-x233.google.com with SMTP id o11so257374746qge.2
 for <tor-talk@lists.torproject.org>; Mon, 04 Jan 2016 08:16:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sonsorol.org; s=google;
 h=message-id:date:from:user-agent:mime-version:to:subject:references
 :in-reply-to:content-type:content-transfer-encoding;
 bh=1KnfplKueZ3YvzXJ7J3kuNpig3Q9rg/vRniRVAoCoYI=;
 b=fARZayQO5K+TFdhAoIWMpeKteWDT4XElqpjdj8HzsjGF9APpfZp2rQBUsgIpvUq6Fp
 FH1/JYdyT+hEmCmQ9G5kAVTCdpbRIv6MeDj17CuumyMWhsQgh74/bMnbH0wbJa/tJGZ6
 V4CQvIuahRxx4vNr8Y3mn2VqItnKSVDgfI3XI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to
 :subject:references:in-reply-to:content-type
 :content-transfer-encoding;
 bh=1KnfplKueZ3YvzXJ7J3kuNpig3Q9rg/vRniRVAoCoYI=;
 b=mf9aIJ4Mq8pNlplA4mYrZyayHBHLGdGN5UAjMQZxedz+jOYLWqz1WMJaB+3izBTqML
 DHx64DDeM4UR6rAe11CMtu7QxX6ImplwHNLcM8c3HiHixqdOZZQ6UzdE6IbESbVdU28u
 C2w8hcCE2s1hdh4V6w35PXfQBenCxfwJ9bufFZVMT5/l3TRlctMOiYtnRx9mf4gOMal/
 1OHqHAj3XzS+ZDcigwCmxh49o7qeSLISr/MuaCydwBvWxCyRTNKlbw2U9lpI2sKQcuL5
 ufZQVXVTS86ueW+7c4QCU9emO0cP48I8wF/VdCvKsplrSO2Txgn7Qd6huKdpHDXP1Z4s
 5Yfg==
X-Gm-Message-State: ALoCoQkZb1JgOwR8RDm+ofFkt/V6Y+XqhY56LDHT0R2xdy/awSUIw/aQ27+l6vrSaRgTd2PcZ4EOnBcRRxh4O38x5GjcO8At9w==
X-Received: by 10.140.163.198 with SMTP id j189mr124613360qhj.36.1451924215462; 
 Mon, 04 Jan 2016 08:16:55 -0800 (PST)
Received: from mistakeNot.local ([50.153.132.21])
 by smtp.googlemail.com with ESMTPSA id t77sm40090852qhb.3.2016.01.04.08.16.53
 for <tor-talk@lists.torproject.org>
 (version=TLSv1/SSLv3 cipher=OTHER);
 Mon, 04 Jan 2016 08:16:54 -0800 (PST)
Message-ID: <568A9AF4.6090700@sonsorol.org>
Date: Mon, 04 Jan 2016 11:16:52 -0500
From: Chris Dagdigian <dag@sonsorol.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <568A833D.6060507@jluehr.de>
In-Reply-To: <568A833D.6060507@jluehr.de>
Subject: Re: [tor-talk] Bandwidth / RAM: When does it make sense to operate
 a tor relay (non-exit)
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Quick reply ...

  - I run a tor exit node with a raspberry PI 2 model B. The prior 
generation struggled a bit to run under load but the 2B works fine
- Experience has been fantastic; tor builds and run just fine from 
source and my only outages were upstream or power related over the last year

> Jan Luehr <mailto:tor-list@jluehr.de>
> January 4, 2016 at 9:35 AM
> Hello folks,
>
> I tried to bring this up at last years 32c3 relay operators meetup, but
> I didn't get much feedback. Thus, I'm asking here ;-).
>
> -> Who is running a tor-relay on embedded hardware (such as rasperri pi,
> etc.). at home. What's your experience?
> -> What platform are you using (rasperri pi?).
> -> What is the minimum bandwith for a tor-relay (non-exit), that does
> make sense? Are "slow" ADSL2+ connections (16Mbit/s down / 1 MBit/s up)
> suitable?
> -> What's is your experience?
>
> We're trying to build a small relay in our hackerspace and - depending
> on what makes sense at all - give a small workshop on crafting a tor
> relay on cheap hardware.
>
> Thanks in advance
> Jan

-- 
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

