Re: bridge relay: "DirPort unreachable"

[Gitano <0xb8968b9e9190@xxxxxxxxxxxxxx>]

Roger Dingledine wrote:

>> ---><8
>> May 31 11:53:47.477 [warn] Your server (*.*.*.*:80) has not managed to
>> confirm that its DirPort is reachable. Please check your firewalls,
>> ports, address, /etc/hosts file, etc.
>> ---><8
> 
> Are you running something else on port 80? Like, say, a webserver?

Yes, a small webserver is installed as a hidden service, but is
listening on address 127.0.0.1 only. Connect to the hidden service over
Tor is working perfect.

>> ---><8
>> May 31 11:53:23.284 [debug] connection_dir_client_reached_eof():
>> Received response from directory server '*.*.*.*:80': 404 "Not found"
>> May 31 11:53:23.285 [info] connection_dir_client_reached_eof(): Received
>> server info (size 0) from server '*.*.*.*:80'
>> May 31 11:53:23.285 [info] connection_dir_client_reached_eof(): Received
>> http status code 404 ("Not found") from server '*.*.*.*:80' while
>> fetching  . I'll try again soon.
>> ---><8
>>
>> What does this mean?
> 
> It means your Tor client tried to do a self-test on its advertised DirPort
> (port 80 of whatever Address you're advertising), and it didn't get an
> answer it expected. Perhaps something else is listening there instead?

No - port 80 ist 'NATed' to port 9030 and port 443 to 9001 in my
DSL-Router. The advertised DirPort ist 80 but bound to 0.0.0.0:9030 as
you can see in my origin posting ('/etc/tor/torrc').

   WAN ---->[DSL-Router]-------->[m0n0wall]-------->[Tor/Web server]
      443/80   (NAT)    9001/9030          9001/9030

In the m0n0wall-log I can see the request from e.g. 64.34.166.71 to port
9030 of my Tor bridge. But there is no "/tor/server/authority.z" on the
box and the answer '404' seems to be plausible.

Now, I stopped the webserver for a while, but no change:

May 31 22:53:47.378 [warn] Your server (*.*.*.*:80) has not managed to
confirm that its DirPort is reachable.

This warning comes every 20 minutes.