I have been a regular user of the Tor browser bundle for quite sometime. Lately, I switched to a faster connection and I have been wondering if I should be running my own Tor-relay. I took the plunge and ran into couple of issues.
I used Vidalia to setup Tor, gave it a nick and a contact email and all that. The opening of the ports is where I am facing an issue.
To my knowledge the OR (onion router) port is by default 9001 and the other port which the tutorial says is optional is the directory port which is by default 9030.
I opened them both on my cisco router, but I keep noticing the same error in the log file.
[Sat Dec 14 11:24:06 2013] Server Port Reachability Test Failed - Your relay's server port is not reachable by other Tor clients. This can happen if you are behind a router or firewall that requires you to set up port forwarding. If x.x.x.x:9001 is not your correct IP address and server port, please check your relay's configuration. [Sat Dec 14 11:24:06 2013] Directory Port Reachability Test Failed - Your relay's directory port is not reachable by other Tor clients. This can happen if you are behind a router or firewall that requires you to set up port forwarding. If x.x.x.x:9030 is not your correct IP address and directory port, please check your relay's configuration.
Here are the contents of the torrc file.
AvoidDiskWrites 1 ContactInfo ControlPort 9151 DataDirectory /home/x/Downloads/tor-browser_en-US/Data/Tor DirPort 9030 DirReqStatistics 0 ExitPolicy reject *:* GeoIPFile ./Data/Tor/geoip HashedControlPassword Log notice stdout Nickname ORPort 9001 RelayBandwidthBurst 10485760 RelayBandwidthRate 5242880 SocksListenAddress 127.0.0.1 SocksPort 9050
One last thing I would like to add, while pasting these log-files, I noticed that the IP-address that is mentioned is not my external IP-address, what I am missing?
One more thing I would like to add is I also port-forward another port for my bit-torrent client and its working with out any problem.
The problem as pointed out by weasel, is that the Tor process is not able to bind to the correct external address, manually specifying the correct external address seems to be the solution.