[tor-relays] Faravahar messing with my IP address
sina at redteam.net
Thu Oct 22 18:38:15 UTC 2015
Dear Relay Operator,
I am the operator of Faravahar, It has been having some network issues,
specifically very long latency. But this is the first time I hear of an issue like this.
220.127.116.11 is Faravahr's older IP addresses which was replaced with and
18.104.22.168 is the new IP (current).
There are iptable rules forwarding the traffic from OLD IP to the new one
for the clients that have not updated yet.
Are you running the latest version of tor software?
I'll be sure to keep an eye on this email and open a ticket as needed.
Thank you for reporting the issue and running a relay.
All the best,
"Be the change that you wish to see in the world." - Mahatma Gandhi
----- On Oct 22, 2015, at 11:22 AM, Logforme m7527 at 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
> 22.214.171.124 to 126.96.36.199; rebuilding descriptor (source:
> 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 188.8.131.52
> to 184.108.40.206; rebuilding descriptor (source: 220.127.116.11).
> 18.104.22.168: <- My real IP address
> 22.214.171.124: faravahar.rabbani.jp <- No idea
> 126.96.36.199: faravahar.redteam.net <- Authority server
> 188.8.131.52: tor.dizum.com <- Better authority server
> 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 at lists.torproject.org
More information about the tor-relays