On Sunday 09 November 2014 04:11:27 coderman wrote: > > I would really like to see this happen. To me it seems your goals are > > slightly different tough. Torouter tries to provide public wifi (without > > risks for the operator), run bridge (and other) nodes and create hidden > > services (see https://trac.torproject.org/projects/tor/wiki/doc/Torouter ). > perhaps it would be useful to break this project into two parts, > a. client or bridge only portable router (pocket sized) > b. dedicated Tor router/relay machine for fixed use. > perhaps c. could be "common requirements for ALL Tor routers" which > apply to both types of use above.
That's actually quite a good idea and in reality it could probably be based on exactly the same OpenWrt source. OpenWrt compiles just fine for ARM processors as well as MIPS based Routers. Something like this: https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/open-source-hardware https://www.olimex.com/Products/SOM/AM3352/AM3352-SOM-EVB/open-source-hardware Would run an OpenWrt build with Tor as Relay/Exit just fine. And I would be quite OK if the Relay/Exit version required some technical skills for installation (as in was not available as a ready flashed plug-and-go device). > i would be willing to help work on these requirements and concerns, if > the https://trac.torproject.org/projects/tor/wiki/doc/Torouter page is > the right place to do it... My own area of expertise is mainly the embedded Linux part and some solid network/unix foundation, but yes - I'd be happy to help and as mentioned earlier whatever source produced or maintained on Github currently I'd be quite happy to move to a torproject server if that is preferred. -- Lars Boegild Thomsen https://reclaim-your-privacy.com Jabber/XMPP: [email protected]
signature.asc
Description: This is a digitally signed message part.
-- tor-talk mailing list - [email protected] To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
