Opened 11 years ago

Last modified 7 years ago

#709 closed defect (Fixed)

Setting DirPort when acting as bridge will give false Warnings

Reported by: knappo Owned by: arma
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.2.1.0-alpha
Severity: Keywords:
Cc: knappo, nickm, arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

If you config your Tor to work as a bridge and also set up a DirPort you will get warnings like this:
"Warning: Your server (IP:DirPort) has not managed to confirm that its DirPort is reachable.
Please check your firewalls, ports, address, /etc/hosts file, etc."

It was independently confirmed that the port is reachable and this message is wrong.
Setting a different DirPort does of course only alter the message but it still appears.
This behaviour was seen in 28-rc and 2.1.1-alpha under WinXP Pro SP3 (but could be there for some time).

It is right that setting up a DirPort on a bridge is senseless but the Warning is just wrong and should be redone.

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (7)

comment:1 Changed 11 years ago by arma

From or-talk post on Dec 28 2008:

starting my Tor-Server as a bridge (with a clean /var/lib/tor/) I get:

Dec 28 20:06:03.406 [notice] Tor 0.2.1.9-alpha (r17777) opening log file.
Dec 28 20:26:07.562 [warn] Your server (87.122.2.241:9030) has not
managed to confirm that its DirPort is reachable. Please check your
firewalls, ports, address, /etc/hosts file, etc.

The debug.log shows:
###
Dec 28 19:43:23.953 [notice] Now checking whether ORPort
87.122.2.241:443 and DirPort 87.122.2.241:9030 are reachable... (this
may take up to 20 minutes -- look for log messages indicating success)
Dec 28 19:43:23.960 [info] connection_ap_make_link(): Making internal
anonymized tunnel to 87.122.2.241:9030 ...
Dec 28 19:43:43.534 [debug] connection_dir_client_reached_eof():
Received response from directory server '87.122.2.241:9030': 404 "Not found"
Dec 28 19:43:43.534 [info] connection_dir_client_reached_eof(): Received
server info (size 0) from server '87.122.2.241:9030'
Dec 28 19:43:43.534 [info] connection_dir_client_reached_eof(): Received
http status code 404 ("Not found") from server '87.122.2.241:9030' while
fetching "/tor/server/authority.z". I'll try again soon.
###

Starting my Tor-Server as a relay (# BridgeRelay 1), all works well:
###
Dec 28 19:33:32.091 [notice] Now checking whether ORPort
87.122.2.241:443 and DirPort 87.122.2.241:9030 are reachable... (this
may take up to 20 minutes -- look for log messages indicating success)
Dec 28 19:33:32.098 [info] connection_ap_make_link(): Making internal
anonymized tunnel to 87.122.2.241:9030 ...
Dec 28 19:33:53.771 [debug] connection_dir_client_reached_eof():
Received response from directory server '87.122.2.241:9030': 200 "OK"
Dec 28 19:33:53.771 [info] connection_dir_client_reached_eof(): Received
server info (size 1177) from server '87.122.2.241:9030'
###

Nothing else has been changed except 'BridgeRelay 1' and cleaning up
'/var/lib/tor/'!

comment:2 Changed 11 years ago by arma

The big hint is that it only happens when Tor has to guess your IP address
based on directory hints. If Tor can learn your IP address from your hostname
or the Address field, then the complaint doesn't happen.

comment:3 Changed 11 years ago by arma

In particular, see update_router_descriptor_downloads()

comment:4 Changed 11 years ago by arma

Here it is:

if (for_unencrypted_conn) {

/* Remove anything whose purpose isn't general. */

When we ask ourselves for /tor/server/authority to test dirport
reachability, we take it away at the last minute because we consider
it too sensitive to serve. So the test gets a 404 and fails.

comment:5 Changed 11 years ago by arma

Fixed in r17945.

comment:6 Changed 11 years ago by arma

flyspray2trac: bug closed.

comment:7 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.