Delivery-Date: Wed, 24 Dec 2014 12:51:37 -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,UNPARSEABLE_RELAY,
	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 CE48B1E0100
	for <archiver@seul.org>; Wed, 24 Dec 2014 12:51:35 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id BA77F3234A;
	Wed, 24 Dec 2014 17:51:32 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id DA4EA3230E
 for <tor-talk@lists.torproject.org>; Wed, 24 Dec 2014 17:51:29 +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 AtlrkGATUSs4 for <tor-talk@lists.torproject.org>;
 Wed, 24 Dec 2014 17:51:29 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id A29423220B
 for <tor-talk@lists.torproject.org>; Wed, 24 Dec 2014 17:51:29 +0000 (UTC)
Received: from plantcutter.riseup.net (plantcutter-pn.riseup.net [10.0.1.121])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.riseup.net (Postfix) with ESMTPS id F16BA40DE4;
 Wed, 24 Dec 2014 17:51:26 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1419443487; bh=hnIK8A63BuPtCMT0UsSG199x0gHJ7ovlDInSIWqDmYE=;
 h=In-Reply-To:References:Subject:From:Date:To:From;
 b=lfVxR6H/QA0CBRwJBSV5Z8Lu6JpZidqN4pLyyFkBSFITs1OrszZW4STLR5NCHrnDO
 jglDafEGweHQU7iawCMg+EsA9e+4c6Ra9fW5ZgyQw3bOBXeSLsev/1e32a1pJusrns
 Y0M4Z29D4uMVCi7yW1Pf9V9m03rmyp7P7lkWBxeg=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: colinmahns) with ESMTPSA id 5B39E20395
In-Reply-To: <549AF951.4060204@sonsorol.org>
References: <549AF951.4060204@sonsorol.org>
MIME-Version: 1.0
From: Colin Mahns <colinmahns@riseup.net>
Date: Wed, 24 Dec 2014 17:51:22 +0000
To: tor-talk@lists.torproject.org,Chris Dagdigian <dag@sonsorol.org>
Message-ID: <CADB15E0-7FE6-4196-88D2-D16EAAC6FB75@riseup.net>
X-Virus-Scanned: clamav-milter 0.98.5 at mx1
X-Virus-Status: Clean
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
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-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>

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. 

On December 24, 2014 12:35:13 PM EST, Chris Dagdigian <dag@sonsorol.org> wrote:
>
>I'm running a brand new US exit node on a dedicated B+ model Raspberry 
>Pi server (relay nickname:
>sonsorolDotNet ) configured per all the guides and running the reduced 
>exit policy.
>
>Trying to avoid being one of the new folks who obsess about flag status
>
>but  the relay lost the Stable flag sometime yesterday despite being up
>
>and running nonstop. I want to make sure it's not because I've tuned 
>badly or because the B+ server is underpowered for what it needs to do.
>
>Tried to set torrc conservatively at first for bandwidth:
>> RelayBandwidthRate 800 KB
>> RelayBandwidthBurst 1600 KB
>
>The 'arm' utility says average up/down traffic is 1Mb/sec
>
>Log data:
>> Dec 24 14:35:33.000 [notice] Heartbeat: Tor's uptime is 9 days 17:55 
>> hours, with 332 circuits open. I've sent 58.85 GB and received 60.64
>GB.
>> Dec 24 14:35:33.000 [notice] Average packaged cell fullness: 97.712%
>> Dec 24 14:35:33.000 [notice] TLS write overhead: 2%
>> Dec 24 14:35:33.000 [notice] Circuit handshake stats since last time:
>
>> 17845/2749463 TAP, 7845/8431 NTor.
>
>The only interesting system log entry recently:
>> [839721.095364] TCP: TCP: Possible SYN flooding on port 9030. Sending
>
>> cookies.  Check SNMP counters.
>
>Looking for pointers/tips/data on:
>
>1. Can the raspberry pi B+ handle exit relay duties or is it
>potentially 
>underpowered?
>
>2. Best logging/debug tips to dive into stability or connection issues 
>with the tor service?
>
>3. raspberrian or torcc tuning tips from people with similar setups
>
>
>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
-- 
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

