Opened 11 years ago

Last modified 7 years ago

#883 closed defect (Duplicate)

Tor doesn't publish the new IP address when it changes

Reported by: ultravelours Owned by:
Priority: Low Milestone: 0.2.1.x-final
Component: Core Tor/Tor Version: 0.2.0.31
Severity: Keywords:
Cc: ultravelours, nickm, mavior, arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I set up a Tor relay using "Tor v0.2.0.32 (r17346)" from Debian backports on Debian Etch (for some reason I can only
choose 0.2.0.31 from the menu above). This relay is running on a low end NAS on MIPSel hardware behind a NAT router
which gets a new IP address every 24h. It is configured not be an exit node and I don't have a directory server running.

I had no problems with the previous version 0.1.2.19 I compiled myself, that one worked and filled the assigned
bandwidth.

But with the current version the daemon does recognize that it is reachable with a new IP address, but it doesn't seem
to publish it. The port 9001 is reachable from the outside, the logfiles say so and I tested it with telnet. From the
logs I get:

Dec 03 06:28:15.017 [notice] Tor 0.2.0.32 (r17346) opening new log file.
Dec 03 17:23:38.755 [notice] Performing bandwidth self-test...done.
Dec 04 05:00:57.797 [notice] Your IP address seems to have changed to 92.227.177.214. Updating.
Dec 04 05:01:09.459 [notice] I learned some more directory information, but not enough to build a circuit: We have only 269/1132 usable descriptors.
Dec 04 05:01:10.668 [notice] We now have enough directory information to build circuits.
Dec 04 05:01:29.227 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 04 05:01:47.985 [notice] Performing bandwidth self-test...done.
Dec 04 06:28:15.747 [notice] Received reload signal (hup). Reloading config.

But although the log says "updating", it doesn't do so. Status pages like https://torstatus.blutmagie.de/ don't list
the server after a change of ip address. In the config file I used a CNAME for my dyndns hostname which does work and
resolves to the IP address that Tor detects.

When I restart the Tor service, evrerything is fine again, at startup it publishes the correct IP address, the Status
pages pick that up and I get the traffic according to the bandwith setting in my torrc.

[Automatically added by flyspray2trac: Operating System: Other Linux]

Child Tickets

Change History (5)

comment:1 Changed 11 years ago by ultravelours

Sorry for the bad formatting. I thought that long lines would be wrapped to fit without me manually having to add line
breaks - and I can't modify that anymore.

comment:2 Changed 11 years ago by limcoretor

Hi, btw, I was under impression that tor works better when opening also other ports then just 9001 for the outside.
9030 and 9031 .. I was under impression that without them open my node was not really visible. But perhaps I am wrong.

comment:3 Changed 10 years ago by arma

I think this is a duplicate of bug 827, which I've (finally) fixed. The
fix should come out in 0.2.1.14-rc, shortly.

I'm going to mark this bug as a duplicate. Please file a new one if
0.2.1.14-rc still has problems for you. :)

comment:4 Changed 10 years ago by arma

flyspray2trac: bug closed.
duplicate of 827

comment:5 Changed 7 years ago by nickm

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