Re: [tor-dev] Your server has not managed to confirm that its ORPort is reachable

[Roger Dingledine <arma@xxxxxxx>]

On Fri, May 17, 2013 at 11:11:33PM -0700, Christian Kujau wrote:
> Hm, an hour later it succeeded:
> 
> May 17 20:40:43.000 [warn] Your server (...:9001) has not managed to confirm that its ORPort is reachable.
> May 17 21:00:43.000 [warn] Your server (...:9001) has not managed to confirm that its ORPort is reachable.
> May 17 21:20:43.000 [warn] Your server (...:9001) has not managed to confirm that its ORPort is reachable.
> May 17 21:38:01.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.

Your relay launches reachability tests every 20 minutes, and it counts
you as reachable if anybody succeeds at connecting (and making a Tor
circuit) from the outside. In this case it sure looks like somebody
else had your bridge address and connected to it -- perhaps the bridge
directory authority doing its own reachability test, or perhaps some
user who got your address from bridgedb.

My first thought is to look at the "..." that you left out, and see if
it's guessing its address wrong (and thus launching the reachability
test to the wrong place).

--Roger

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