Delivery-Date: Wed, 24 Dec 2014 12:35:44 -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 D7B0E1E0100
	for <archiver@seul.org>; Wed, 24 Dec 2014 12:35:42 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 5C8CB325BD;
	Wed, 24 Dec 2014 17:35:41 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 4EC5B325BC
 for <tor-talk@lists.torproject.org>; Wed, 24 Dec 2014 17:35:23 +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 D5bOTAvfepOU for <tor-talk@lists.torproject.org>;
 Wed, 24 Dec 2014 17:35:23 +0000 (UTC)
Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com
 [IPv6:2607:f8b0:400d:c01::235])
 (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 2E2FA3254E
 for <tor-talk@lists.torproject.org>; Wed, 24 Dec 2014 17:35:20 +0000 (UTC)
Received: by mail-qc0-f181.google.com with SMTP id m20so6123921qcx.12
 for <tor-talk@lists.torproject.org>; Wed, 24 Dec 2014 09:35:17 -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
 :content-type:content-transfer-encoding;
 bh=rotL8ff0q4UIbF/OYsYxhje4ZmAOoec+iOVZrbfO6Ik=;
 b=TOlj7mV4aeSsT9Ik1PjgXn+4A7d1RfV74jcF2CXRLTF0Bb2R0/om3M548VsSwMICP6
 Xt6TWoyOFrRKvC1vAFYOjoMuBr76ckTADOLY9odv5bIgi6vfcSKEcR4xGnxo4I2tV7sM
 EibqKsKX5fqXbIDV7apoJQzJ8HNOXXniXX8fM=
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:content-type:content-transfer-encoding;
 bh=rotL8ff0q4UIbF/OYsYxhje4ZmAOoec+iOVZrbfO6Ik=;
 b=OvPqULrTEhjGz2p0hMGCBnuIUKewLzPXrBBVd/Bjv17VLkHbcD3AJSdchduF5QaP2o
 7EpGf5O219n8Rtd6duelMTzMm3B8BMM6PIeXimaXcX+05D356eubQvZA36Lgt4xg6zSC
 3+nCJlestwmHFhsjn1UKnTgFs0jrqIsl3zQ7aE5gl0Agash+WvM8ZVCcqqw2QA2HsAf/
 /VmKuEoO0VcKKfokwqfNb/ZWPYBnkxeAXSekyLbz3/j89BgUK8hOtbf1DAmqbfaeP/oz
 MPQrj+oa1qxLtGYLvodFVpV9zE3Oi82nz/d4i6SfOGrtcxD7dng1SCiEnbYnVkyPSM3Y
 LInQ==
X-Gm-Message-State: ALoCoQmuPSrOH7Y7dpv8kHvhULMinTj8aNvEkJ4MFD0r/fTCZJV0PRQxqVSl0QU0owQzTOiymgrD
X-Received: by 10.224.74.70 with SMTP id t6mr5071292qaj.15.1419442517717;
 Wed, 24 Dec 2014 09:35:17 -0800 (PST)
Received: from mistakeNot.sonsorol.net (gw-bos.sonsorol.net. [50.247.195.121])
 by mx.google.com with ESMTPSA id
 p69sm5697220qga.27.2014.12.24.09.35.16
 for <tor-talk@lists.torproject.org>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Wed, 24 Dec 2014 09:35:16 -0800 (PST)
Message-ID: <549AF951.4060204@sonsorol.org>
Date: Wed, 24 Dec 2014 12:35:13 -0500
From: Chris Dagdigian <dag@sonsorol.org>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
Subject: [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>


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

