[Commotion-dev] Torouter on Commotion

[Ben West]

Commotion is presently tracking current OpenWRT Attitude Adjustment, so the
OS layer for OpenWRT devices should be fine.

In lieu of the limited CPU/RAM/flash resources on the OpenWRT nodes, and
especially in lieu of the question about possibly integrating Tor as an app
that a user may select via the Luci web UI, what might Tor integration
require of *all* nodes on a particular mesh, including those where Tor
isn't installed?

That is, if your repeater node, where Tor has been installed, wants to send
Tor traffic to another node on that mesh that is >1 hop away, or or it
wants to send Tor traffic to the Internet thru a gateway node that does not
have a full Tor installation, what could these non-Tor-capable nodes do to
at least forward the traffic correctly?

On Wed, May 22, 2013 at 11:53 AM, Stephanie Alarcon <steph.alarcon at gmail.com
> wrote:

> One other note, if I recall correctly, the makefile for Tor in OpenWRT
> downloads whatever the current stable release is.  I think.  But I have a
> pretty clear memory that it did not specify a particular or out-of-date
> version.  You should check the makefile to make sure I'm not lying to you.
>
>
> On 05/22/2013 12:32 PM, Stephanie Alarcon wrote:
>
>> Hey all,
>>
>> My apologies for not being forthcoming with good documentation of what I
>> worked on and found out about running Tor on Commotion.  Griffin and I
>> have plans to talk today or tomorrow so I can do a braindump.  This is
>> good incentive for me to sit down and summarize my work as promised, and
>> I'll get going on that this week or next.  I had some pressing home
>> repair issues that kept me away from my desk, but now those dragons are
>> mostly at bay and I'm flexible Wednesdays through Fridays.
>>
>> My recommendations for further work can be summed up by this haiku:
>>
>> Access Labs router:
>> Nice work, hard to get in touch.
>> It runs great, but how??
>>
>> On 05/20/2013 06:08 PM, Dan Staples wrote:
>>
>>> Updating the OpenWRT Tor package to the latest stable versions would be
>>> a benefit for everyone :)
>>>
>>> And making a LuCI interface could be useful, but there would be more to
>>> it than that. Did you talk to Stephanie about what she implemented?
>>> When we discussed the possibility of using Tor in Commotion, there were
>>> some factors brought up for consideration:
>>>
>>> 1. How would the end user use it? Would it be a specific access point
>>> on Commotion-OpenWRT that provided a transparent proxy through the Tor
>>> network?
>>> 2. If so, how do we manage the information leak risks that would
>>> otherwise be addressed by using the Tor browser bundle?
>>> 3. If we provide a transparent proxy to the Tor network, how do we
>>> handle local traffic for mesh-only services?
>>> 4. How would this be implemented in Commotion client software (android,
>>> linux, mac, windows)?
>>>
>>> Dan
>>>
>>> On Mon 20 May 2013 11:22:16 AM EDT, Griffin Boyce wrote:
>>>
>>>> So after a lengthy discussion with someone involved with Torouter, he
>>>> identified some outstanding features/issues
>>>>
>>>>    * Torouter doesn't have a user interface, which makes
>>>>      use/configuration difficult
>>>>    * No one is updating the OpenWRT package (though it is working, the
>>>>      tor binary needs occasional updates)
>>>>    * Current OpenWRT implementation is just "TransPort, DNSPort and a
>>>>      few iptables rules"
>>>>
>>>> Not sure if this would be considered an app or a feature, but what do
>>>> you all think?  Nat mentioned that making a generic luci interface to
>>>> configure tor likely wouldn't be too difficult.
>>>>
>>>> ~Griffin
>>>>
>>>>
>>>> ______________________________**_________________
>>>> Commotion-dev mailing list
>>>> Commotion-dev at lists.chambana.**net <Commotion-dev at lists.chambana.net>
>>>> https://lists.chambana.net/**mailman/listinfo/commotion-dev<https://lists.chambana.net/mailman/listinfo/commotion-dev>
>>>>
>>>
>>> --
>>> Dan Staples
>>>
>>> Open Technology Institute
>>> https://commotionwireless.net
>>> ______________________________**_________________
>>> Commotion-dev mailing list
>>> Commotion-dev at lists.chambana.**net <Commotion-dev at lists.chambana.net>
>>> https://lists.chambana.net/**mailman/listinfo/commotion-dev<https://lists.chambana.net/mailman/listinfo/commotion-dev>
>>>
>>>
>>
>>
>
> --
> stephalarcon.org
>
> ______________________________**_________________
> Commotion-dev mailing list
> Commotion-dev at lists.chambana.**net <Commotion-dev at lists.chambana.net>
> https://lists.chambana.net/**mailman/listinfo/commotion-dev<https://lists.chambana.net/mailman/listinfo/commotion-dev>
>
>


-- 
Ben West
http://gowasabi.net
ben at gowasabi.net
314-246-9434
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-dev/attachments/20130522/bb29774f/attachment.html>