[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-relays] Faravahar messing with my IP address



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

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@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays