Issues with Tor connection

nsm_nikhil · 2009-03-16 02:17:01

Hi,

First here is my network information.

I'm in university, where there is a direct connection to the internet. But the firewall blocks all outgoing ports except 80 and 443. In addition they seem to be preventing CONNECT calls over HTTP to tunnel other protocols.

I'm trying to use Tor. In my Torrc i set the following options

## CONFIGURED FOR ARCHLINUX               

## Last updated 22 July 2005 for Tor 0.1.0.13.
## (May or may not work for older or newer versions of Tor.)
#                                                           
## See the man page, or http://tor.eff.org/tor-manual.html, for more
## options you can use in this file.                                
#                                                                   
# On Unix, Tor will look for this file in someplace like "~/.tor/torrc" or
# "/etc/torrc"                                                            
#                                                                         
# On Windows, Tor will look for the configuration file in someplace like  
# "Application Data\tor\torrc" or "Application Data\<username>\tor\torrc" 
#                                                                         
# With the default Mac OS X installer, Tor will look in ~/.tor/torrc or   
# /Library/Tor/torrc                                                      

# Set the Tor Circuit Build time to find faster tor servers, increments of seconds
CircuitBuildTimeout 2                                                             
# connections while Tor is not in use.                                            
KeepalivePeriod 60                                                                
# Force Tor to consider whether to build a new circuit every NUM seconds.         
NewCircuitPeriod 15                                                               
# Set How many entry guards we should we keep at a time                           
NumEntryGuards 8                                                                  


## Replace this with "SocksPort 0" if you plan to run Tor only as a
## server, and not make any local application connections yourself.
SocksPort 9050 # what port to open for local application connections
SocksBindAddress 127.0.0.1 # accept connections only from localhost 
#SocksBindAddress 192.168.0.1:9100 # listen on a chosen IP/port too 

## Entry policies to allow/deny SOCKS requests based on IP address.
## First entry that matches wins. If no SocksPolicy is set, we accept
## all (and only) requests from SocksBindAddress.                    
#SocksPolicy accept 192.168.0.1/16                                   
#SocksPolicy reject *                                                

## Allow no-name routers (ones that the dirserver operators don't
## know anything about) in only these positions in your circuits.
## Other choices (not advised) are entry,exit,introduction.      
AllowUnverifiedNodes middle,rendezvous                           

## Logs go to stdout at level "notice" unless redirected by something
## else, like one of the below lines. You can have as many log lines as
## you want.                                                           
##                                                                     
## Send all messages of level 'notice' or higher to /var/log/tor/notices.log
#Log notice file /var/log/tor/notices.log                                   
## Send only debug and info messages to /var/log/tor/debug.log              
#Log debug-info file /var/log/tor/debug.log                                 
## Send ONLY debug messages to /var/log/tor/debug.log                       
#Log debug-debug file /var/log/tor/debug.log                                
## To use the system log instead of Tor's logfiles, uncomment these lines:  
Log notice syslog                                                           
## To send all messages to stderr:                                          
#Log debug stderr                                                           

## Uncomment this to start the process in the background... or use
## --runasdaemon 1 on the command line.                           
RunAsDaemon 1                                                     
User tor                                                          
Group tor                                                         

## Tor only trusts directories signed with one of these keys, and
## uses the given addresses to connect to the trusted directory  
## servers. If no DirServer lines are specified, Tor uses the built-in
## defaults (moria1, moria2, tor26), so you can leave this alone unless
## you need to change it.                                              
#DirServer 18.244.0.188:9031 FFCB 46DB 1339 DA84 674C 70D7 CB58 6434 C437 0441
#DirServer 18.244.0.114:80 719B E45D E224 B607 C537 07D0 E214 3E2D 423E 74CF  
#DirServer 86.59.21.38:80 847B 1F85 0344 D787 6491 A548 92F9 0493 4E4E B85D   

## The directory for keeping all the keys/etc. By default, we store
## things in $HOME/.tor on Unix, and in Application Data\tor on Windows.
DataDirectory /var/lib/tor                                              

## The port on which Tor will listen for local connections from Tor controller
## applications, as documented in control-spec.txt.  NB: this feature is      
## currently experimental.                                                    
#ControlPort 9051                                                             

############### This section is just for location-hidden services ###

## Look in .../hidden_service/hostname for the address to tell people.
## HiddenServicePort x y:z says to redirect a port x request from the 
## client to y:z.                                                     

#HiddenServiceDir /var/lib/tor/hidden_service/
#HiddenServicePort 80 127.0.0.1:80            

#HiddenServiceDir /var/lib/tor/other_hidden_service/
#HiddenServicePort 80 127.0.0.1:80                  
#HiddenServicePort 22 127.0.0.1:22                  
#HiddenServiceNodes moria1,moria2                   
#HiddenServiceExcludeNodes bad,otherbad             

################ This section is just for servers #####################

## NOTE: If you enable these, you should consider mailing your identity
## key fingerprint to the tor-ops, so we can add you to the list of    
## servers that clients will trust. See                                
## http://tor.eff.org/doc/tor-doc.html#server for details.             

## Required: A unique handle for this server
#Nickname ididnteditheconfig                

## The IP or fqdn for this server. Leave commented out and Tor will guess.
#Address noname.example.com                                               

## Contact info that will be published in the directory, so we can
## contact you if you need to upgrade or if something goes wrong. 
## This is optional but recommended.                              
#ContactInfo Random Person <nobody AT example dot com>            
## You might also include your PGP or GPG fingerprint if you have one:
#ContactInfo 1234D/FFFFFFFF Random Person <nobody AT example dot com> 

## Required: what port to advertise for tor connections
#ORPort 9001                                           
## If you want to listen on a port other than the one advertised
## in ORPort (e.g. to advertise 443 but bind to 9090), uncomment
## the line below. You'll need to do ipchains or other port forwarding
## yourself to make this work.                                        
#ORBindAddress 0.0.0.0:9090                                           

## Uncomment this to mirror the directory for others (please do)
#DirPort 9030 # what port to advertise for directory connections
## If you want to listen on a port other than the one advertised
## in DirPort (e.g. to advertise 80 but bind 9091), uncomment the line
## below. You'll need to do ipchains or other port forwarding yourself
## to make this work.
#DirBindAddress 0.0.0.0:9091

## A comma-separated list of exit policies. They're considered first
## to last, and the first match wins. If you want to *replace*
## the default exit policy, end this with either a reject *:* or an
## accept *:*. Otherwise, you're *augmenting* (prepending to) the
## default exit policy. Leave commented to just use the default, which is
## available in the man page or at http://tor.eff.org/documentation.html
##
## Look at http://tor.eff.org/faq-abuse.html#TypicalAbuses
## for issues you might encounter if you use the default exit policy.
##
## If certain IPs and ports are blocked externally, e.g. by your firewall,
## you should update your exit policy to reflect this -- otherwise Tor
## users will be told that those destinations are down.
##
#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports but no more
#ExitPolicy accept *:119 # accept nntp as well as default exit policy
#ExitPolicy reject *:* # middleman only -- no exits allowed

ReachableDirAddresses *:80
ReachableORAddresses *:443

But Tor is unable to connect. Here is the log

Tor[5442]: No current certificate known for authority moria1; launching request.
Tor[5442]: No current certificate known for authority tor26; launching request.
Tor[5442]: No current certificate known for authority dizum; launching request.
 Tor[5442]: No current certificate known for authority ides; launching request.
Tor[5442]: No current certificate known for authority gabelmoo; launching request.
 Tor[5442]: No current certificate known for authority dannenberg; launching request.
Tor[5442]: Your application (using socks4 to port 80) is giving Tor only an IP address. Applications t
hat do DNS resolves themselves may leak information. Consider using Socks4A (e.g. via privoxy or socat) instead. For more inf
ormation, please see http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS.
Tor[5442]: Application request when we're believed to be offline. Optimistically trying directory fetc
hes again.

I can't find any documentation about this issue.

Thanks.

sistematico · 2009-03-16 03:34:10

## Tor only trusts directories signed with one of these keys, and
## uses the given addresses to connect to the trusted directory
## servers. If no DirServer lines are specified, Tor uses the built-in
## defaults (moria1, moria2, tor26), so you can leave this alone unless
## you need to change it.
#DirServer 18.244.0.188:9031 FFCB 46DB 1339 DA84 674C 70D7 CB58 6434 C437 0441
#DirServer 18.244.0.114:80 719B E45D E224 B607 C537 07D0 E214 3E2D 423E 74CF
#DirServer 86.59.21.38:80 847B 1F85 0344 D787 6491 A548 92F9 0493 4E4E B85D

Try uncomment this...
Maybe tor need this address
Sorry for my very bad english, i am from Brazil, add me in GTalk if you need more support.

sistematico@gmail.com

Good luck!

Arch Linux

#1 2009-03-16 02:17:01

Issues with Tor connection

#2 2009-03-16 03:34:10

Re: Issues with Tor connection

Board footer