Opened 11 years ago

Last modified 7 years ago

#900 closed defect (Duplicate)

Tor can't detect right IP

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

Description

Hi,

Tor sometimes cannot figure out the right IP address.
Below two extracts of the logfile.
I don't know when the IP usually changes but the manual of my provider says the IP will change once a day.

Setting:

  • In my torrc I don't have set the property "Address". (Didn't use it due to my misconfigured local caching DNS service.)
  • OS is Ubuntu 8.04

The IP in line 1 is the correct one. The other IP is an old one which was given from my provider yesterday evening:
---snip---
Jan 01 18:01:05.463 [notice] Guessed our IP address as 84.189.106.167.
Jan 01 18:01:11.270 [notice] Our IP Address has changed from 84.189.106.167 to 84.189.109.75; rebuilding descriptor.
Jan 01 18:01:11.573 [notice] Our IP Address has changed from 84.189.109.75 to 84.189.106.167; rebuilding descriptor.
Jan 01 18:01:13.102 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Jan 01 18:01:13.102 [notice] Now checking whether ORPort 84.189.106.167:65001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Jan 01 18:01:17.021 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Jan 01 18:01:17.728 [notice] Our IP Address has changed from 84.189.106.167 to 84.189.109.75; rebuilding descriptor.
Jan 01 18:21:17.681 [warn] Your server (84.189.109.75:65001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
---snap---
(I deleted some text from the logfile to make it short.)

Yesterday Tor "detected" also IP changes (which didn't occurr).
But yesterday the last detected change was the right one:
---snip---
Dec 31 21:35:31.981 [notice] Guessed our IP address as 84.189.109.75.
Dec 31 21:35:37.695 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Dec 31 21:35:37.695 [notice] Now checking whether ORPort 84.189.109.75:65001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Dec 31 21:35:50.928 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 31 21:36:33.666 [notice] Our IP Address has changed from 84.189.109.75 to 84.189.64.90; rebuilding descriptor.
Dec 31 21:36:34.298 [notice] Our IP Address has changed from 84.189.64.90 to 84.189.109.75; rebuilding descriptor.
Dec 31 21:37:40.280 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 31 21:38:39.613 [notice] Performing bandwidth self-test...done.
Dec 31 21:56:53.884 [notice] Our IP Address has changed from 84.189.109.75 to 84.189.64.90; rebuilding descriptor.
Dec 31 21:57:40.471 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 31 22:08:04.792 [notice] Our IP Address has changed from 84.189.64.90 to 84.189.109.75; rebuilding descriptor.
Dec 31 22:08:07.394 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 31 22:09:06.998 [notice] Our IP Address has changed from 84.189.109.75 to 84.189.64.90; rebuilding descriptor.
Dec 31 22:10:08.520 [notice] Our IP Address has changed from 84.189.64.90 to 84.189.109.75; rebuilding descriptor.
Dec 31 22:10:10.362 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 31 22:10:11.790 [notice] Our IP Address has changed from 84.189.109.75 to 84.189.64.90; rebuilding descriptor.
Dec 31 22:21:00.810 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 31 22:32:31.874 [notice] Our IP Address has changed from 84.189.64.90 to 84.189.109.75; rebuilding descriptor.
Dec 31 22:32:56.426 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
---snap---

Regards, Jörg

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

Child Tickets

Change History (6)

comment:1 Changed 11 years ago by bsdtechie

If you are running a tor server with bandwidth rates lower than 50 KBytes, additionally you could advertise a DirPort
(ie. "DirPort 9030" in your torrc). Tor network will ignore the advertised DirPort, but for whatever reasons the IP
changes will be recognised by the tor network.

The solution works also on servers with bandwidth rates more than 50 kBytes, but - surprise - the server is advertising
a DirPort. Sometimes this is not the intention of the operator.

System: FreeBSD 6.4, Tor 0.2.0.32

comment:3 Changed 11 years ago by nickm

Can you try this with the latest 0.2.1.x-alpha, and paste the relevant parts of the log with that? The debugging
output from the 0.2.1.x series should be far more useful in tracking this down.

comment:4 Changed 11 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:5 Changed 11 years ago by arma

flyspray2trac: bug closed.
duplicate of 827

comment:6 Changed 7 years ago by nickm

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