[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Huh?
Andrew wrote:
TorOp schrieb:
And what's this about?
Jan 27 10:08:00.373 [Notice] Our IP Address has changed from
69.119.206.101 to 212.112.242.159; rebuilding descriptor.
Jan 27 10:08:01.595 [Notice] Self-testing indicates your ORPort is
reachable from the outside. Excellent. Publishing server descriptor.
Jan 27 10:08:46.068 [Notice] Our IP Address has changed from
212.112.242.159 to 69.119.206.101; rebuilding descriptor.
Jan 27 10:08:51.206 [Notice] Self-testing indicates your ORPort is
reachable from the outside. Excellent. Publishing server descriptor.
That seems to be a (rare) issue with the new alpha versions. A similar
log has been posted to this list not too long ago (john smith: unusual
connection activity?).
Note that *both* IPs point to a tor-node: Zippy
(MybKsCAd5bQuzF48aFY3JyuOjxs IGJmo96Yu7liu1Y9xM8jSEV82Jk) and maximator
(+pyyTwuDM1sEKAOFYKJM2GYdF2c /zMSZTixMZpKvzJjBa0siBJ8O1U), both of which
were set up today according to the directory
http://moria.seul.org:9032/tor/status/authority
You were/are not by any chance running a second tor server by the name
of maximator? If not, developement must be made aware of this issue.
Regards,
Andrew
No, I'm only running one node, and the name has always been Zippy.
I am running on a part-time basis, about 14 hours a day, but that's the
way I've always run it.