[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

RE: torcp problem

To: <or-talk@xxxxxxxxxxxxx>
Subject: RE: torcp problem
From: "evb" <dsmntl@xxxxxxx>
Date: Thu, 2 Mar 2006 18:25:58 -0700
Delivered-to: archiver@seul.org
Delivered-to: or-talk-outgoing@seul.org
Delivered-to: or-talk@seul.org
Delivery-date: Thu, 02 Mar 2006 20:26:04 -0500
In-reply-to: <20060303011027.GX31440@eecs.harvard.edu>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
Thread-index: AcY+XuXO7WQNS1ocT9OCglf6ENpwpQAAaZxA


:
:ORPort is the port on which Tor listens for new OR connections 
:(this is the Tor data plane).
:

Ok, that's how I thought it was before Ashton responded.  So what is Ashton
telling me I did wrong?

As it stands now:

1.  OR port set to "ORPort 8001" in torrc and uncommented.
2.  Control port set to 9051 in torrc, and now uncommented.
3.  GUI Control port set to 9051.
4.  Nickname set to "Nickname Eraserhead" in torrc.
5.  FW set to accept inbound connections on tcp 8001.

Still it doesn't work.

Eric


:ControlPort is the port on which Tor listens for new 
:controller connections (e.g. connections from TorCP).
:
:I believe that the socket accepting OR connections binds to 
:0.0.0.0 by default, in which case it MUST NOT have the same 
:value as ControlPort.
:Also, the ControlPort specified in torrc MUST match what TorCP 
:thinks that it is.
:
:Geoff
:

References:
- Re: torcp problem
  - From: Geoffrey Goodell

Prev by Author: RE: torcp problem
Next by Author: AW: Firefox extension: TorButton
Previous by thread: Re: torcp problem
Next by thread: Re: torcp problem
Index(es):
- Author
- Thread