[tor-bugs] #3664 [Torouter]: Tor web interface for the DreamPlug

Tor Bug Tracker & Wiki torproject-admin at torproject.org
Sat Jul 30 13:30:35 UTC 2011


#3664: Tor web interface for the DreamPlug
----------------------+-----------------------------------------------------
 Reporter:  runa      |          Owner:  hellais
     Type:  task      |         Status:  new    
 Priority:  normal    |      Milestone:         
Component:  Torouter  |        Version:         
 Keywords:            |         Parent:         
   Points:            |   Actualpoints:         
----------------------+-----------------------------------------------------

Comment(by runa):

 Replying to [comment:1 hellais]:
 > I would like to know what the exact requirements for this web interface
 should be. What I deduce would be necessary is:
 >
 > main page:
 >   The main page contains an overview of the current status of the Tor
 router. Status if it is connected properly to Tor or not, and general
 information on the current status of the network. If it is the first time
 that the user connects to the Torouter then it loads the wizard.

 The devices we ship will be pre-configured and ready to go, so I'm
 wondering if including a wizard will be a bit too much. The devices will
 be for tech users who know what they are doing, so having a web interface
 that allows users to change the default config should be enough.

 The main page can show the status of services such as the Tor bridge, the
 Tor wifi or the normal wifi, whether or not there are any package updates
 for the system, if eth0 and eth1 are up, if the firewall is up (and maybe
 also the firewall rules) etc.

 I think that showing all of the services listed above on one single page
 will be messy, so I suggest you pick the most important ones (like the
 status of the Tor bridge).

 > wizard:
 >   Guides the user through the steps of configuring the Torouter. @runa,
 @jake you would need to tell me exactly what the steps required should be.
 An example would be
 >    step 1: The user is asked how he will connect to the internet. He
 chooses DHCP or static or whatever.
 >    step 2: The user is asked how to configure his wifi network. ESSID,
 channel, etc.
 >    step 3: He is asked how to configure Tor.
 >   .. and so on. As I said I am not sure how you envisioned this. What
 are your ideas?

 By default, the device will be using DHCP to connect to the network, Tor
 will be running as a public bridge, the Tor wireless network will be
 disabled and the firewall will use some standard rules.

 Users should be able to edit the configuration for the services listed
 above. This includes (I'm sure I've forgotten something, please don't see
 this as the complete list):

 1. Use of DHCP or static IP to connect to the network
 2. Option to enable (or disable) the transparent Tor wireless network
 3. Option to enable (or disable) the normal wireless network
 4. Option to configure Tor as (private) bridge or (exit) relay

 > status:
 >   A detailed status page, containing more info than the main page.
 [insert specs for "detailed information" here]

 At a minimum, we should show the Tor log (n last lines or something like
 that) on this page. If there are things you can't list on the main page,
 you might be able to put it here.

 > config:
 >   The advanced configuration interface. A good value for
 customizability/not_breakability should be found. By this I mean what kind
 of users are Torouter users? A good compromise between what they can do
 and what they can't do to avoid breaking stuff should be found [insert
 specs for what should be customizable]
 >
 > Is there anything else?

 How about having a web interface with the following set of tabs:

 1. Main page (like we've discussed so far)
 2. Network (with everything network)
 3. Firewall (showing the current rules and allows users to set new rules)
 4. Tor (configure Tor as (private) bridge or (exit) relay), include option
 to see the log etc

 The configuration options available should be the minimum necessary to get
 a service up a running; i.e. if you want to configure Tor to do lots of
 magic stuff, you can, but you'll need to edit the Tor config file
 manually.

 How does this sound?

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


More information about the tor-bugs mailing list