I see this from time to time as well. Here's another example:
Oct 17 23:02:44.000 [notice] Our IP Address has changed from 52.64.142.121 to [CORRECT IP]; rebuilding descriptor (source: 86.59.21.38).
52.64.142.121 appears to be an instance on Amazon's EC2. I don't run any nodes on EC2. 86.59.21.38 resolves to tor.noreply.org.
I'm unable to find any occurrences of this happening from Faravahar, however the issue seems to be fairly common. What's going on?
On Thu, Oct 22, 2015 at 1:48 PM, Pascal Terjan pterjan@gmail.com wrote:
On 22 October 2015 at 19:22, Logforme m7527@abc.se wrote:
I run the relay Logforme (855BC2DABE24C861CD887DB9B2E950424B49FC34)
Saw this in yesterday's log file: Oct 22 03:17:55.000 [notice] Our IP Address has changed from 84.219.173.60 to 154.35.32.5; rebuilding descriptor (source: 154.35.175.225). Oct 22 03:17:55.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Oct 22 03:17:56.000 [notice] Performing bandwidth self-test...done. Oct 22 03:26:55.000 [notice] Our IP Address has changed from 154.35.32.5 to 84.219.173.60; rebuilding descriptor (source: 194.109.206.212).
84.219.173.60: <- My real IP address 154.35.32.5: faravahar.rabbani.jp <- No idea 154.35.175.225: faravahar.redteam.net <- Authority server 194.109.206.212: tor.dizum.com <- Better authority server
I just got something strange too:
Oct 22 20:42:24.000 [notice] Guessed our IP address as 77.206.60.235 (source: 154.35.175.225). Oct 22 20:42:25.000 [notice] Our IP Address has changed from 77.206.60.235 to 149.18.2.82; rebuilding descriptor (source: 199.254.238.52).
faravahar guess my ip wrongly to be 77.206.60.235 which is a French IP totally unrelated to my connection
So if I read it right my relay asked the authority server Faravahar what my IP address is and got the wrong answer. 9 minutes later my relay asked another authority server and got the right answer. My relay show an uptime starting from this time and if the relay did a full restart it meant all the circuits got dropped? Inconvenient for users.
My relay have "restarted" like this a few times the last weeks (only Tor daemon "restarting", not the machine). Don't know if Faravahar is behind the other "restarts". This time I just caught it in the log file before it got archived.
Is this a know issue with Faravahar? If so, should it be fixed? _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays