[tor-talk] running a stable exit node on a Raspberry Pi B+ (can it handle it?)

Chris Dagdigian dag at sonsorol.org
Wed Dec 24 17:35:13 UTC 2014

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 

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


More information about the tor-talk mailing list