[tor-bugs] #13537 [Vidalia]: Unexpected behaviour of Tor v0.2.5.8-rc embedded with vidalia v0.2.21

[Tor Bug Tracker & Wiki]

#13537: Unexpected behaviour of Tor v0.2.5.8-rc embedded with vidalia v0.2.21
--------------------------+------------------------------
     Reporter:  TORqueue  |      Owner:
         Type:  defect    |     Status:  new
     Priority:  normal    |  Milestone:  Tor: unspecified
    Component:  Vidalia   |    Version:  Tor: 0.2.5.8-rc
   Resolution:            |   Keywords:  vidalia v0.2.21
Actual Points:            |  Parent ID:
       Points:            |
--------------------------+------------------------------

Comment (by TORqueue):

 Replying to [comment:3 teor]:
 > That is strange behaviour from the consensus.
 > How many relays are running on that public IP?
 > Are there or have there ever been relays with that name?
 >
 > It may be that tor is incorrectly reporting uptime and downtime, but
 otherwise working. It's hard to tell.

 The name of relay is unique.
 I had an old non-exit relay last week with other name (for testing
 purpose) on my public IP 109.103.57.102
 I had running for months an old non-exit relay on other public IP, but I
 changed my ISP and I lost the old TOR DATA files.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13537#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online