It seems that there are some mistakes,Like SocksPolicy reject *:*,waht about SocksPolicy accept *:* At 2012-02-23 04:53:24,"Christian Kujau" <li...@nerdbynature.de> wrote: >Hi, > >I'm running a Tor bridge for some days now (after shutting down an exit >node, due to too many DMCA complaints) but it's hardly getting any >traffic: > > Heartbeat: Tor's uptime is 1 day 11:59 hours, with 2 circuits open. > I've sent 7.34 MB and received 24.86 MB. > >I feel like it's configured wrongly, though the log file does not report >any errors: > >Tor 0.2.3.12-alpha-dev (git-81fe3e438b39cd14) opening log file. >No AES engine found; using AES_* functions. >This version of OpenSSL has a slow implementation of counter mode; not using >it. >OpenSSL OpenSSL 0.9.8o 01 Jun 2010 looks like version 0.9.8m or later; I will >try SSL_OP to enable renegotiation >Your Tor server's identity key fingerprint is xxxx >Configured hibernation. This interval begins at 2012-02-21 00:00:00 and ends >at 2012-02-22 00:00:00. We have no prior estimate for bandwidth, so we will >start out awake and hibernate when we exhaust our quota. >Parsing GEOIP file /opt/tor/share/tor/geoip. >Configured to measure statistics. Look for the *-stats files that will first >be written to the data directory in 24 hours from now. >This version of Tor (0.2.3.12-alpha-dev) is newer than any recommended >version, according to the directory authorities. Recommended versions are: >0.2.1.32,0.2.2.35,0.2.3.10-alpha,0.2.3.11-alpha,0.2.3.12-alpha >Reloaded microdescriptor cache. Found 2910 descriptors. >We now have enough directory information to build circuits. >Bootstrapped 80%: Connecting to the Tor network.Heartbeat: Tor's uptime is >0:00 hours, with 4 circuits open. I've sent 0 kB and received 0 kB. >Bootstrapped 85%: Finishing handshake with first hop. >Bootstrapped 90%: Establishing a Tor circuit. >Guessed our IP address as x.x.x.x (source: x.x.x.x). >Tor has successfully opened a circuit. Looks like client functionality is >working. Bootstrapped 100%: Done. >Now checking whether ORPort x.x.x.x:9001 is reachable... (this may take up to >20 minutes -- look for log messages indicating success) >Self-testing indicates your ORPort is reachable from the outside. Excellent. >Publishing server descriptor. >Performing bandwidth self-test...done. > >I've forwarded port 9001/tcp from the internet-facing router to the >machine where tor is running, of course. > >My torrc looks like this: > >----------- >SocksListenAddress 127.0.0.1:9050 >SocksPolicy accept 127.0.0.1 >SocksPolicy reject *:* >Log notice file /var/log/tor/notices.log >RunAsDaemon 1 >DataDirectory /var/lib/tor >ControlPort 9051 >ControlListenAddress 127.0.0.1:9051 >HashedControlPassword xxx >ORPort 9001 >Nickname xxx >RelayBandwidthRate 100 KB >RelayBandwidthBurst 250 KB >AccountingMax 4 GB >AccountingStart day 00:00 >ContactInfo xxx >ExitPolicy reject *:* >BridgeRelay 1 >----------- > >I've also installed a bridge in an Amazon EC2 with the TorCloud project >and here I have the same problem: > > Heartbeat: Tor's uptime is 23:59 hours, with 0 circuits open. > I've sent 2.44 MB and received 13.41 MB. > >Network-wise things seem to look fine: > > Feb 21 20:42:17.000 [notice] Self-testing indicates your ORPort is > reachable from the outside. Excellent. Publishing server descriptor. > >The torrc for the EC2 bridge: > >------- >Nickname xxx >ContactInfo xxx >SocksPort 0 >ORPort 9001 >ORListenAddress 0.0.0.0:9001 >BridgeRelay 1 >AccountingStart week 1 10:00 >AccountingMax 10 GB >ExitPolicy reject *:* >------ > >Any ideas on how to get the bridge going? > >Thanks, >Christian. >-- >BOFH excuse #161: > >monitor VLF leakage >_______________________________________________ >tor-talk mailing list >tor-talk@lists.torproject.org >https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
_______________________________________________ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
