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

[tor-relays] Need help to set up Tor + Router: ORPort and DirPort unreachable



Hi

I am running tor 0.2.4.20 from official RPM repositories on my local
machine (Fedora 20). I can use it to surf the web and
https://check.torproject.org/ (besides others) tells me that tor is
running. I had the same problem with 0.2.3.25 from fedora's own
repository.

According to `netstat -tulpen` tor listens on 0.0.0.0:9001,
0.0.0.0:9030, and Control port + Socks port.
I configured my Router to port-forward 9001 and 9030 for both TCP+UDP
and IPv4+IPv6. How can I test that this worked?

I am running a local firewall but it does not seem to matter whether it
is enabled or disabled.

Is there anything else I could be missing? 

Regards
Chris
Jan 20 13:48:17.000 [notice] Tor 0.2.4.20 (git-9543df3899e84df2) opening log file.
Jan 20 13:48:17.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Jan 20 13:48:17.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Jan 20 13:48:17.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
Jan 20 13:48:17.000 [notice] We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later, but with a version of OpenSSL that apparently lacks accelerated support for the NIST P-224 and P-256 groups. Building openssl with such support (using the enable-ec_nistp_64_gcc_128 option when configuring it) would make ECDH much faster.
Jan 20 13:48:17.000 [notice] Your Tor server's identity key fingerprint is 'genodeftest 78B04BF06777F68FDF42D900DFA8EB045F43E103'
Jan 20 13:48:18.000 [warn] parse error: internal NUL character.
Jan 20 13:48:18.000 [warn] Unparseable microdescriptor
Jan 20 13:48:19.000 [notice] We now have enough directory information to build circuits.
Jan 20 13:48:19.000 [notice] Bootstrapped 80%: Connecting to the Tor network.
Jan 20 13:48:19.000 [notice] Guessed our IP address as 88.217.180.55 (source: 194.109.206.212).
Jan 20 13:48:20.000 [notice] Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor.
Jan 20 13:48:20.000 [notice] Bootstrapped 85%: Finishing handshake with first hop.
Jan 20 13:48:20.000 [notice] Bootstrapped 90%: Establishing a Tor circuit.
Jan 20 13:48:21.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Jan 20 13:48:21.000 [notice] Bootstrapped 100%: Done.
Jan 20 13:48:21.000 [notice] Now checking whether ORPort 88.217.180.55:9001 and DirPort 88.217.180.55:9030 are reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Jan 20 13:57:24.000 [notice] New control connection opened.
Jan 20 14:08:20.000 [warn] Your server (88.217.180.55:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Jan 20 14:08:20.000 [warn] Your server (88.217.180.55:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Jan 20 14:28:20.000 [warn] Your server (88.217.180.55:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Jan 20 14:28:20.000 [warn] Your server (88.217.180.55:9030) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays