Delivery-Date: Wed, 24 Dec 2014 12:57:00 -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.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,URIBL_BLOCKED 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 B38631E0502
	for <archiver@seul.org>; Wed, 24 Dec 2014 12:56:58 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 964AE32629;
	Wed, 24 Dec 2014 17:56:55 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id E108B320BD
 for <tor-talk@lists.torproject.org>; Wed, 24 Dec 2014 17:56:51 +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 gkoT25n9hxC1 for <tor-talk@lists.torproject.org>;
 Wed, 24 Dec 2014 17:56:51 +0000 (UTC)
Received: from mail-qg0-x229.google.com (mail-qg0-x229.google.com
 [IPv6:2607:f8b0:400d:c04::229])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id B4EE7319CD
 for <tor-talk@lists.torproject.org>; Wed, 24 Dec 2014 17:56:51 +0000 (UTC)
Received: by mail-qg0-f41.google.com with SMTP id e89so4235197qgf.14
 for <tor-talk@lists.torproject.org>; Wed, 24 Dec 2014 09:56:49 -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=HqbpnJUix36zT9u5/OaiTeCiLptzp9ECebbe9EOXzTY=;
 b=IH468+jqP+h4VfcknA0L3s5Q0xci5N3jzLz404bi7R9J0oDoHeD+kkS6A1m9EijiCQ
 q4W285Lz75LfL/N6+yH7pkofc7YxGHcrGzJ9Z7Xcb68qW6iQai9NI10vNnHkr1xiFOQm
 NID+t4Ucq3jBK0r9VxfuwrdXw5TVEi4WnLY84=
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=HqbpnJUix36zT9u5/OaiTeCiLptzp9ECebbe9EOXzTY=;
 b=axnpnzzcz7AnmOtyq1/EbXOPN4d0RXxs/0iYhQeFMYCrc+ppb4qDsIAE2ZcNFJcQ5U
 2PwOVWAOJ5SQKWYtkW793z/ngR958n0YEom5ZUYNYglkvZVDwSlw9By9IGndXZD6pU0O
 bwPk/j3hAwZZ/jBYJ5sUauELAgrPgjuvohdd4l95Ag87qLcJZ7jjyrXgPUoOHFTyi5QN
 zlfz+UmcsrAZ3V+vv/qywEBV7X5PQKffdfEgJ6rgmqLf0duakvjRa2zbXyMmoWoQClby
 7sRs9Yz6WnEhiMVK27D9c1nXVDvvIdSJmTp7thttT8iuDiw7MzORJF8uO9189mLyTJkh
 RYeQ==
X-Gm-Message-State: ALoCoQluRQ+cPBRnLgE1QSpQmkgi4TabhY2z156+RBwELynnNeZg/8JyAwqMeUKVRJqs6figTofY
X-Received: by 10.229.130.65 with SMTP id r1mr56554724qcs.16.1419443809444;
 Wed, 24 Dec 2014 09:56:49 -0800 (PST)
Received: from mistakeNot.sonsorol.net (gw-bos.sonsorol.net. [50.247.195.121])
 by mx.google.com with ESMTPSA id
 u49sm15674778qgd.26.2014.12.24.09.56.48
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Wed, 24 Dec 2014 09:56:48 -0800 (PST)
Message-ID: <549AFE5E.5080908@sonsorol.org>
Date: Wed, 24 Dec 2014 12:56:46 -0500
From: Chris Dagdigian <dag@sonsorol.org>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: Colin Mahns <colinmahns@riseup.net>, tor-talk@lists.torproject.org
References: <549AF951.4060204@sonsorol.org>
 <CADB15E0-7FE6-4196-88D2-D16EAAC6FB75@riseup.net>
In-Reply-To: <CADB15E0-7FE6-4196-88D2-D16EAAC6FB75@riseup.net>
Subject: Re: [tor-talk] running a stable exit node on a Raspberry Pi B+ (can
 it	handle it?)
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>



Colin Mahns wrote:
> I wouldn't recommend using a rPi for a Tor bridge/relay. It's far too 
> underpowered in my mind to be useful for anyone. If anything, it might 
> harm the network by introducing slow hops. A spare computer or a VPS 
> would be better here.
>
> As far as your bandwidth settings those seem fine, you should be able 
> to see connections taking place in arm if the relay is functioning.

Much appreciated! Oddly enough the standard tools don't seem to show the 
rPi server struggling much at all  tor seems to take 7-20% of cpu-- 
running 'arm' seems to add an equal amount of load as the tor daemon 
itself. I'm actually thinking that running 'arm' constantly in a 
terminal status window may be bogging down the rPi but I'd like to 
figure out some logging/debug magic to 'prove' to myself that I've got 
an underwhelming box.

If I can trace performance problems to the rPi I'll happily swap in 
another dedicated box as a replacement.

Thanks!



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

