[tor-relays] Running Obfsproxy on a Raspberry Pi

[Richard Budd]

Saw your P.S. as I finished my reply.
I've got 2gig of swap on the SD card, so even if it's slow memory maybe
that helps my system.
Richard


On Sat, Jun 1, 2013 at 5:08 PM, Richard Budd <rotorbudd at gmail.com> wrote:

> I've had no problems with the stock raspbian. However I've only got 720kb
> going thru it as a Obs. bridge. I'm constrained by the cable upload limits
> more than anything else.
> As far as running it on family members connections, I would likely have it
> set even lower, and I could just SSH into it to keep it up.
> If you ever get a good set of optimizations please let us know. I think
> anything we can do to make the Pi something close to a "Plug and Play"  set
> up would help to get it adopted by the average user.
>
>
>
> On Sat, Jun 1, 2013 at 4:56 PM, <torsion at ftml.net> wrote:
>
>> **
>> On Sat, Jun 1, 2013, at 12:43 PM, Richard Budd wrote:
>>
>> Don't know how common this is but I've had a Pi running for 35 days 6
>> hours (so far). With over 80GB transferred on my half assed comcast cable
>> connection.
>> Not bad for $25 a credit card sized board sitting in a cardboard box in
>> my broom closet.
>>  I think I'm going to give one to everyone of my family members
>> preloaded with Tor. Plug it into their cable router and let it run.
>> That would be another 4 bridges added to the total. If we could get
>> another 100 people to do this it it might be a good way to add capacity
>> with very little cost or power use.
>>
>>
>> Be warned, I've found that if you run a Pi as a relay and give it enough
>> bandwidth, bursts of circuit creation can cause it to crash or freeze.
>> This was dedicating about 1Mbps to it.  As a bridge it'd likely be just
>> fine, and this was something I considered as well.  If your relatives can't
>> service it though you might consider rigging something that would
>> powercycle it once a day in case it locks up.  I use electromechanical
>> timers with 15-min increments for this purpose with an ancient laser
>> printer and dodgy (but free) WAP.
>>
>> I've found a number of optimizations to config files (mainly in kernel
>> networking settings) that vastly reduce the number of lockups on a Pi
>> that's relaying 1Mbps, but so far haven't eliminated them, they're mostly
>> caused by huge bursts of circuit creation.  Unfortunately I've had no time
>> to work on this in recent weeks and am just about to travel for a week, but
>> I was considering trying to write some kind of iptables "clamping" script,
>> or otherwise figure out the right combination of .torrc and iptables limits
>> to keep the Pi from crashing when this kind of network activity occurs.
>>
>> I see these circuit creation storms on my much bigger relays, too, but
>> since they're running on much bigger machines, they've never caused a
>> crash.  The Pi is quite a bit more limited.  Nobody on the list has made a
>> stab at explaining this behavior yet.
>>
>>
>>
>> _______________________________________________
>> tor-relays mailing list
>> tor-relays at lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20130601/662bbf47/attachment-0001.html>