[tor-bugs] #2370 [Torouter]: Torouter basic Web UI for OpenWRT

Tor Bug Tracker & Wiki torproject-admin at torproject.org
Fri Mar 4 00:06:30 UTC 2011


#2370: Torouter basic Web UI for OpenWRT
-------------------------------+--------------------------------------------
 Reporter:  cyphunk            |          Owner:  ioerror
     Type:  enhancement        |         Status:  new    
 Priority:  normal             |      Milestone:         
Component:  Torouter           |        Version:         
 Keywords:  openwrt, torouter  |         Parent:         
   Points:                     |   Actualpoints:         
-------------------------------+--------------------------------------------

Comment(by fermenthor):

 Replying to [comment:6 ioerror]:
 > > - Tor configuration specifies which zones to use for the proxy
 (instead of a single interface);
 > In Tor? Or in OpenWRT's firewalling setup?
 in /etc/config/tor - toroptions.sh creates TransListenAddress parameters
 for all interfaces in the specified zone; firewall.sh creates iptables
 entries for these zones (which is very easy since firewall operates on
 zones). And i do think that all iptables related options would be handled
 by the firewall process, but i had a few problems with it. I'll look at it
 more.

 > > - No torrc is created when Tor starts - all options are passed on
 command line (maybe Tor should be patched to use /etc/config/tor as its
 config file?);
 > Tor can simply be passed the config file as a startup option with  '-f
 /etc/config/tor'
 Yes, but /etc/config/tor is in the uci format to make it compatible with
 the rest of the configuration system. So by patching tor, i mean make it
 read options from that kind of a file instead of using wrappers
 (toroptions.sh)

 > > - /etc/firewall.user is not used - instead, both firewall and tor call
 /etc/tor/firewall.sh on their restarts;
 > What are the practical differences here? Why not integrate the changes
 into the main /etc/firewall.user file?
 Originally, i did have it in firewall.user but decided to use a separate
 file because, if there are more processes trying to modify contents of
 firewall.user, it would be a mess. My solution simply drops a static
 script and uses the uci interface to tell the firewall to run it.

 > Do you want to integrate this into the tor-alpha package on OpenWRT and
 upload it as a patch? We can simply make the new tor-alpha package depend
 on LuCI if we want...
 Yes, we should check it in under the alpha package. Did you decide that we
 should not have a separate torgui package? In that case, there's no reason
 to depend on LuCI. It will work just fine without the UI and be
 configurable by command line uci tools like the rest of the system (though
 it will just install a few unnecessary lua files).

 Note that I used the country flag icons from Vidalia - I wonder if it
 requires a special copyright notice.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2370#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list