++ 29/10/14 10:15 +0100 - Jeroen Massar:
There are some weird properties in trying to do full-bandwidth. Deterministic it for sure is not.
The IP is not mentioned in atlas: https://atlas.torproject.org/#search/94.142.240.243
Nope. That is the IP-address of the switch in front of the node. The IP-address of the node is 94.142.245.231. The fingerprint is, as you have figured out already, AA0D167E03E298F9A8CD50F448B81FBD7FA80D56.
Is "Tor 0.2.5.9-rc" not outdated? You might be missing some features there.
Fixed. It's now running 0.2.5.10.
Are you also sure that coloclue likes you playing exit? (I can only assume so ;)
Yes. Anyway, I can't explain i) why the node was picking up speed so fast during April, both before and after Heartbleed and why it is so slow picking up speed in mid-July and 2) why there is a sudden drop in traffic since Friday. As said before, I don't have the time (and lacking expertise to do this efficiently) to investigate these issues. If anyone else is interested, I am more than happy to help - of course. -- Rejo Zenger E rejo@zenger.nl | P +31(0)639642738 | W https://rejo.zenger.nl T @rejozenger | J rejo@zenger.nl OpenPGP 1FBF 7B37 6537 68B1 2532 A4CB 0994 0946 21DB EFD4 XMPP OTR 271A 9186 AFBC 8124 18CF 4BE2 E000 E708 F811 5ACF