I have been running a Tor relay on a BeagleBone Black since last August. It’s been reset twice. Once after Heartbleed, which effectively destroyed the uptime calculation since it looks like a new relay. The other was when I accidentally unplugged it.
On the various Tor mailing lists people have reported difficulties running on a Raspberry Pi. The Pi just doesn’t have the horsepower IMHO to handle the number of connections a relay receives. It will probably do fine as Bridge as Roger Dingledine suggests.
Also, raspian is not debian. The BBB uses actual arhmf so it is fully compatible with the debian ecosystem. See this post for more details.
However, I’ve been fine with my relay on the BBB for some time so I’d figured I’d post my
Log notice file /var/log/tor/notices.log RunAsDaemon 1 ControlPort 9051 CookieAuthentication 1 ORPort 443 NoListen ORPort XXX.XXX.XXX.XXX:52333 NoAdvertise Nickname CHANGEME MaxAdvertisedBandwidth 200 KB RelayBandwidthRate 520 KB RelayBandwidthBurst 640 KB ContactInfo <tor AT datko dot net> GPG: BF35C7AC ExitPolicy reject *:* # no exits allowed DisableDebuggerAttachment 0
Line 6 is the internal port of the BBB relay, the external port (to my home router) is 443. Therefore you must forward port 443 to port 52333 in this case. Also, replace the XXX with your internal BBB IP.
MaxAdvertisedBandwith field may not be doing what you/I think. See this bug. However, it has worked for me.
The nickname is not my relay’s nickname since I really don’t want to advertise my IP address, although it is essentially well-known because I run a relay. For home users, I would recommend running a bridge as I had problems with Hulu with my non-exit relay.
Follow the instructions from the Tor Project on installing the experimental branch for debian.
The pcDuino3 looks like it has the specs to act as relay, but I’m a BeagleBone fan 😉