Commotion is presently tracking current OpenWRT Attitude Adjustment, so the OS layer for OpenWRT devices should be fine.<br><br>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 <i>all</i> nodes on a particular mesh, including those where Tor isn't installed?<br>
<br>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?<br>
<br><div class="gmail_quote">On Wed, May 22, 2013 at 11:53 AM, Stephanie Alarcon <span dir="ltr"><<a href="mailto:steph.alarcon@gmail.com" target="_blank">steph.alarcon@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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.<div class="HOEnZb">
<div class="h5"><br>
<br>
On 05/22/2013 12:32 PM, Stephanie Alarcon wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey all,<br>
<br>
My apologies for not being forthcoming with good documentation of what I<br>
worked on and found out about running Tor on Commotion. Griffin and I<br>
have plans to talk today or tomorrow so I can do a braindump. This is<br>
good incentive for me to sit down and summarize my work as promised, and<br>
I'll get going on that this week or next. I had some pressing home<br>
repair issues that kept me away from my desk, but now those dragons are<br>
mostly at bay and I'm flexible Wednesdays through Fridays.<br>
<br>
My recommendations for further work can be summed up by this haiku:<br>
<br>
Access Labs router:<br>
Nice work, hard to get in touch.<br>
It runs great, but how??<br>
<br>
On 05/20/2013 06:08 PM, Dan Staples wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Updating the OpenWRT Tor package to the latest stable versions would be<br>
a benefit for everyone :)<br>
<br>
And making a LuCI interface could be useful, but there would be more to<br>
it than that. Did you talk to Stephanie about what she implemented?<br>
When we discussed the possibility of using Tor in Commotion, there were<br>
some factors brought up for consideration:<br>
<br>
1. How would the end user use it? Would it be a specific access point<br>
on Commotion-OpenWRT that provided a transparent proxy through the Tor<br>
network?<br>
2. If so, how do we manage the information leak risks that would<br>
otherwise be addressed by using the Tor browser bundle?<br>
3. If we provide a transparent proxy to the Tor network, how do we<br>
handle local traffic for mesh-only services?<br>
4. How would this be implemented in Commotion client software (android,<br>
linux, mac, windows)?<br>
<br>
Dan<br>
<br>
On Mon 20 May 2013 11:22:16 AM EDT, Griffin Boyce wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So after a lengthy discussion with someone involved with Torouter, he<br>
identified some outstanding features/issues<br>
<br>
* Torouter doesn't have a user interface, which makes<br>
use/configuration difficult<br>
* No one is updating the OpenWRT package (though it is working, the<br>
tor binary needs occasional updates)<br>
* Current OpenWRT implementation is just "TransPort, DNSPort and a<br>
few iptables rules"<br>
<br>
Not sure if this would be considered an app or a feature, but what do<br>
you all think? Nat mentioned that making a generic luci interface to<br>
configure tor likely wouldn't be too difficult.<br>
<br>
~Griffin<br>
<br>
<br>
______________________________<u></u>_________________<br>
Commotion-dev mailing list<br>
<a href="mailto:Commotion-dev@lists.chambana.net" target="_blank">Commotion-dev@lists.chambana.<u></u>net</a><br>
<a href="https://lists.chambana.net/mailman/listinfo/commotion-dev" target="_blank">https://lists.chambana.net/<u></u>mailman/listinfo/commotion-dev</a><br>
</blockquote>
<br>
--<br>
Dan Staples<br>
<br>
Open Technology Institute<br>
<a href="https://commotionwireless.net" target="_blank">https://commotionwireless.net</a><br>
______________________________<u></u>_________________<br>
Commotion-dev mailing list<br>
<a href="mailto:Commotion-dev@lists.chambana.net" target="_blank">Commotion-dev@lists.chambana.<u></u>net</a><br>
<a href="https://lists.chambana.net/mailman/listinfo/commotion-dev" target="_blank">https://lists.chambana.net/<u></u>mailman/listinfo/commotion-dev</a><br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
<br>
-- <br>
<a href="http://stephalarcon.org" target="_blank">stephalarcon.org</a><br>
<br>
______________________________<u></u>_________________<br>
Commotion-dev mailing list<br>
<a href="mailto:Commotion-dev@lists.chambana.net" target="_blank">Commotion-dev@lists.chambana.<u></u>net</a><br>
<a href="https://lists.chambana.net/mailman/listinfo/commotion-dev" target="_blank">https://lists.chambana.net/<u></u>mailman/listinfo/commotion-dev</a><br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Ben West<div><a href="http://gowasabi.net" target="_blank">http://gowasabi.net</a><br><a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a><br>
314-246-9434<br></div>