Dirserver believes your ORPort is unreachable

Peter Palfrader peter at palfrader.org
Mon Sep 12 19:28:53 UTC 2005


On Mon, 12 Sep 2005, Eugene Armstead wrote:

> Sep 12 13:10:08.655 [notice] Now checking whether ORPort 216.161.59.50:9001 and DirPort 216.161.59.50:9030 are reachable... (this may take several minutes)
> Sep 12 13:10:09.814 [notice] Your ORPort is reachable from the outside. Excellent. Publishing server descriptor.

> Sep 12 13:10:15.740 [warn] connection_dir_client_reached_eof(): http status 400 ("Dirserver believes your ORPort is unreachable") response from dirserver '86.59.5.130:80'. Malformed server descriptor?
> Sep 12 13:10:30.912 [notice] Your DirPort is reachable from the outside. Excellent.

And here is, where tor26 disagrees:

weasel at asteria:~$ timeout 30 telnet 216.161.59.50 9030
Trying 216.161.59.50...
Timeout: aborting command ``telnet'' with signal 9
zsh: killed     timeout 30 telnet 216.161.59.50 9030


weasel at asteria:~$ tcptraceroute 216.161.59.50 9030 -f 23
Selected device eth0, address 86.59.5.130, port 45551 for outgoing packets
Tracing the path to 216.161.59.50 on TCP port 9030, 30 hops max
23  clsp-dsl-gw04-68.clsp.qwest.net (67.42.184.68)  148.759 ms  307.900 ms  149.594 ms
24  matrix.armsteadent.com (216.161.59.62)  188.300 ms  187.890 ms  201.563 ms
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *


Either you are throwing away the SYN packets after matrix, or somebody
in between is throwing away your syn+ack replies.

It's interesting to note that it works for several other computers, even
some that are nearby (but on other logical network ranges).

Check, if your firewalls are blocking stuff?
-- 
 PGP signed and encrypted  |  .''`.  ** Debian GNU/Linux **
    messages preferred.    | : :' :      The  universal
                           | `. `'      Operating System
 http://www.palfrader.org/ |   `-    http://www.debian.org/



More information about the tor-talk mailing list