I think I'm suppling the ServerTransport parameters incorrectly. the log seems to indicate it is listening on the wrong ports for obfs2 and obfs3.
Since it was the only compiled package I saw for Windows with obfs support, I downloaded the tor-pluggable-transports-browser-2.4.11-alpha-2.
I am using the following .torrc --
Address *obfuscated*
AvoidDiskWrites 1
BridgeRelay 1
LearnCircuitBuildTimeout 0
CircuitBuildTimeout 60
ClientTransportPlugin websocket exec flashproxy-client --register :0 :56833 *[not useful, I realize]*
ContactInfo *obfuscated*
ControlPort 9051
CookieAuthentication 1
DataDirectory *obfuscated*
DirPort 0
DirReqStatistics 0
ExitPolicy reject *:*
GeoIPFile *obfuscated*/geoip
GeoIPv6File *obfuscated*/geoip6
HardwareAccel 1
ServerTransportPlugin obfs2,obfs3 exec pyobfsproxy managed
ServerTransportListenAddr obfs2,obfs3 0.0.0.0:56831 0.0.0.0:56832
Log notice stdout
Nickname *obfuscated*
NumCPUs 4
ORPort 56830
RelayBandwidthBurst 97280
RelayBandwidthRate 71680
SocksListenAddress 127.0.0.1
SocksPort 9050
I get the following log messages on starting Tor:
[Notice] Tor v0.2.4.11-alpha (git-fcd9248387249d68) running on Windows 7 with Libevent 2.0.21-stable and OpenSSL 1.0.0k.
[Notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
[Notice] This version is not a stable Tor release. Expect more bugs than usual.
[Notice] Read configuration file "*obfuscated*\torrc".
[Notice] Opening Socks listener on 127.0.0.1:9050
[Notice] Opening Control listener on 127.0.0.1:9051
[Notice] Opening OR listener on 0.0.0.0:56830
[Notice] Parsing GEOIP IPv4 file *obfuscated*/geoip.
[Notice] Parsing GEOIP IPv6 file *obfuscated*/geoip6.
[Notice] Your Tor server's identity key fingerprint is '*obfuscated* *obfuscated*'
[Notice] We now have enough directory information to build circuits.
[Notice] Bootstrapped 80%: Connecting to the Tor network.
[Notice] New control connection opened.
[Notice] Bootstrapped 85%: Finishing handshake with first hop.
[Notice] Registered server transport 'obfs3' at '0.0.0.0:60093'
[Notice] Registered server transport 'obfs2' at '0.0.0.0:60094'
[Notice] Bootstrapped 90%: Establishing a Tor circuit.
[Notice] Tor has successfully opened a circuit. Looks like client functionality is working.
[Notice] Bootstrapped 100%: Done.
I have ports 56830, 56831, 56832, and 56833 forwarded to this machine from my router/nat.
I get connections on my ORPort 56830 -- though in 2-3 days, not a single client. Seems to be directory exchanges (?) or my own Tor Browser use. Isn't 2-3 days long enough to be discovered?
Looks like it is listening on 60093 and 60094 for obfs3 and obfs2 instead of the intended 56832 and 56831 (the ports I have forwarded) for the purpose.
Any help? Is it just a syntax error on my part (I tried using two lines for the ServerTransportListenAddr but one was automatically deleted after editing in Vidalia), or am I further off-track?
Thanks a bundle :) Asa