Re: Tor 0.1.1.20 servers no longer handle dynamic IPs?

[Jens Lechtenboerger <snooped@xxxxxxxxx>]

Roger Dingledine <arma@xxxxxxx> writes:

> Hi folks,
>
> It seems that Tor 0.1.0.17 correctly handled people running servers
> with dynamic IP addresses:
> http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#DynamicIP

I've always had trouble running a server with dynamic IP address.
(With 0.1.0.17 I had to remove the client directory in ~/.tor to
establish circuits through my node.  This does not seem to work any
longer...)

Actually, I don't think that my server ever supported a single
circuit for somebody else so far.

> I've gotten a report that Tor 0.1.1.20 does not -- when the IP address
> changes, Tor notices, but then it never finds itself reachable. Only
> restarting the process fixes it.

I'm afraid restarting doesn't help either:

Jun 02 19:37:55.791 [notice] Tor 0.1.1.20 opening log file.
Jun 02 19:37:55.992 [notice] Your Tor server's identity key fingerprint is 'snoopy 9A14 D7E6 9161 B19A DDAE 1FC7 FB3B 0C07 D45D 5E2E'
Jun 02 19:37:56.641 [notice] We now have enough directory information to build circuits.
Jun 02 19:37:58.470 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Jun 02 19:37:58.470 [notice] Now checking whether ORPort 80.143.133.238:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Jun 02 19:57:56.372 [warn] second_elapsed_callback(): Your server (80.143.133.238:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Jun 02 20:17:56.072 [warn] second_elapsed_callback(): Your server (80.143.133.238:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Jun 02 20:37:56.268 [warn] second_elapsed_callback(): Your server (80.143.133.238:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Jun 02 20:38:57.453 [notice] resolve_my_address(): Your IP seems to have changed. Updating.
Jun 02 20:58:56.788 [warn] second_elapsed_callback(): Your server (169.132.13.103:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Jun 02 21:09:27.230 [notice] resolve_my_address(): Your IP seems to have changed. Updating.
Jun 02 21:26:19.490 [notice] hibernate_begin(): Interrupt: will shut down in 30 seconds. Interrupt again to exit now.
Jun 02 21:26:49.527 [notice] Tor 0.1.1.20 opening log file.
Jun 02 21:26:49.630 [notice] Your Tor server's identity key fingerprint is 'snoopy 9A14 D7E6 9161 B19A DDAE 1FC7 FB3B 0C07 D45D 5E2E'
Jun 02 21:26:49.819 [notice] consider_hibernation(): Clean shutdown finished. Exiting.
Jun 02 21:26:50.080 [notice] We now have enough directory information to build circuits.
Jun 02 21:26:51.778 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Jun 02 21:26:51.778 [notice] Now checking whether ORPort 80.143.133.238:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Jun 02 21:46:50.400 [warn] second_elapsed_callback(): Your server (80.143.133.238:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Jun 02 22:06:50.974 [warn] second_elapsed_callback(): Your server (80.143.133.238:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.

> Please help me track this down,

What do you need?

Jens