Opened 14 years ago

Last modified 7 years ago

#286 closed defect (Fixed)

Reachability testing looks for wrong ORPort and DirPort after a setconf from the controller

Reported by: edmanm Owned by: arma
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.1.1.18-rc
Severity: Keywords:
Cc: edmanm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

If I tell Tor that I want to change my ORPort and DirPort right after starting Tor, via the control port,
Tor will close the old listeners and open new listeners properly; however, it seems to start doing its
reachability testing on the old ports.

Apr 19 18:45:39:555 [Notice] Tor v0.1.1.18-rc. This is experimental software. Do not rely on it for strong anonymity.
Apr 19 18:45:39:975 [Notice] Initialized libevent version 1.1a using method poll. Good.
Apr 19 18:45:39:977 [Notice] connection_create_listener(): Opening OR listener on 0.0.0.0:9001
Apr 19 18:45:39:980 [Notice] connection_create_listener(): Opening Directory listener on 0.0.0.0:9031
Apr 19 18:45:39:983 [Notice] connection_create_listener(): Opening Socks listener on 127.0.0.1:9050
Apr 19 18:45:39:984 [Notice] connection_create_listener(): Opening Control listener on 127.0.0.1:9051
Apr 19 18:45:40:414 [Notice] Your Tor server's identity key fingerprint is 'adrastea BC82 02BC AEF3 ED5E 55F3 8E68 CAA7 B445 2056 39CE'
Apr 19 18:45:41:387 [Notice] We now have enough directory information to build circuits.
Apr 19 18:45:41:981 [Notice] retry_listeners(): Closing OR listener on 0.0.0.0:9001
Apr 19 18:45:41:984 [Notice] connection_create_listener(): Opening OR listener on 0.0.0.0:9000
Apr 19 18:45:41:986 [Notice] retry_listeners(): Closing Directory listener on 0.0.0.0:9031
Apr 19 18:45:41:989 [Notice] connection_create_listener(): Opening Directory listener on 0.0.0.0:9030
Apr 19 18:45:41:991 [Notice] options_act_reversible(): Closing old OR listener on 0.0.0.0:9001
Apr 19 18:45:41:992 [Notice] options_act_reversible(): Closing old Directory listener on 0.0.0.0:9031
Apr 19 18:45:42:336 [Notice] retry_listeners(): Closing OR listener on 0.0.0.0:9001
Apr 19 18:45:42:338 [Notice] connection_create_listener(): Opening OR listener on 0.0.0.0:9000
Apr 19 18:45:42:341 [Notice] retry_listeners(): Closing Directory listener on 0.0.0.0:9031
Apr 19 18:45:42:343 [Notice] connection_create_listener(): Opening Directory listener on 0.0.0.0:9030
Apr 19 18:45:42:345 [Notice] options_act_reversible(): Closing old OR listener on 0.0.0.0:9001
Apr 19 18:45:42:347 [Notice] options_act_reversible(): Closing old Directory listener on 0.0.0.0:9031
Apr 19 18:45:44:089 [Notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Apr 19 18:45:44:092 [Notice] Now checking whether ORPort xx.xxx.xx.xxx:9001 and DirPort xx.xxx.xx.xxx:9031 are
reachable... (this may take up to 20 minutes -- look for log messages indicating success)

In the example above, my ORPort and DirPort were previously 9001 and 9031, respectively. Vidalia started Tor,
used SETCONF to set the new ORPort and DirPort to be 9000 and 9030, respectively, and then issued a SAVECONF.
netstat tells me that Tor really was listening on the new ports I had asked, but the reachability
testing seems to be looking for the old ports 9001 and 9031.

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (4)

comment:1 Changed 14 years ago by arma

I just fixed this in latest CVS. Can you test and see if it is still broken for you?

comment:2 Changed 14 years ago by arma

Closing on the theory that Matt says it works now.

comment:3 Changed 14 years ago by arma

flyspray2trac: bug closed.

comment:4 Changed 7 years ago by nickm

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