Happened again tonight: Nov 04 05:23:43.000 [notice] Our IP Address has changed from 84.219.173.60 to 185.99.185.61; rebuilding descriptor (source: 154.35.175.225). Nov 04 05:23:43.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Nov 04 05:23:43.000 [notice] Our IP Address has changed from 185.99.185.61 to 84.219.173.60; rebuilding descriptor (source: 154.35.175.225). Nov 04 05:23:43.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
84.219.173.60 <- My real IP address 185.99.185.61 <- Holland? 154.35.175.225 <- faravahar.redteam.net Not even a second between getting the wrong IP and then getting the correct one back, but enough to restart the relay. After seeing this I upgraded to the latest version 0.2.7.4-rc and on the restart it again used Faravahar to (correctly) guess the IP: Nov 04 07:47:49.000 [notice] Guessed our IP address as 84.219.173.60 (source: 154.35.175.225). On 2015-10-22 20:38, SiNA Rabbani wrote: > 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. > > 154.35.32.5 is Faravahr's older IP addresses which was replaced with and > 154.35.175.225 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. > > _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
