Hi,
I am running an exit-relay and noticed a couple of odd things:
1. Last months, the node seems to be slow in using the full capacity.
- Back in April, I changed the relay's configuration to allow the relay to use all the bandwidth it could take. As a result, within a week or two the bandwidth consumption went up to 50 Mbps. In the months of May to July, I had to limit the capacity of the node again. Mid-July I reverted to the same configuration from April. However, the node was a lot slower to pick up the full capacity. [1]
- So, the question is: why is it so much slower maximising the full bandwidth? The configuration from mid-July onwards is identical to the one in April. The only thing that has changed is in mid-August, when I moved to relay into a LXC container. However, that doesn't explain the slow pickup in mid-July to mid-August.
- And yes, I am aware of the Roger's blogpost. That does explain why the node may be slow to pick up traffic, but it doesn't explain why it was a lot faster in doing so in April then in mid-July.
2. Since Friday there is a considerable drop in the traffic.
- Last Friday, around 23:00 hours CET the traffic dropped to about a third of it's usage the days before. Since then, there have been some increase from time to time, but the average is still half or even less than before Friday. There was no change in configuration.
I don't have the time to investigate these issues myself. However, if someone wants to look into this, let me know and I am more than happy to provide the details needed.
[1] https://rejo.zenger.nl/tmp/94.142.240.243_10-year.png [1] https://rejo.zenger.nl/tmp/94.142.240.243_10-week.png
On 2014-10-29 09:41, Rejo Zenger wrote: [..]
- So, the question is: why is it so much slower maximising the full bandwidth? The configuration from mid-July onwards is identical to the one in April. The only thing that has changed is in mid-August, when I moved to relay into a LXC container. However, that doesn't explain the slow pickup in mid-July to mid-August.
Note that LXC likely does not give you the security properties that you expect.
issue this in your container to shutdown the host: echo b > /proc/sysrq-trigger
There is a bug open on this: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/645625
- And yes, I am aware of the Roger's blogpost. That does explain why the node may be slow to pick up traffic, but it doesn't explain why it was a lot faster in doing so in April then in mid-July.
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
Nor in: https://torstatus.blutmagie.de/
Though there is: https://torstatus.blutmagie.de/router_detail.php?FP=aa0d167e03e298f9a8cd50f4...
https://atlas.torproject.org/#details/AA0D167E03E298F9A8CD50F448B81FBD7FA80D...
Is "Tor 0.2.5.9-rc" not outdated? You might be missing some features there.
I see similar issues with other nodes btw, eg: https://atlas.torproject.org/#details/BDB26EF60A419089CA3AA0891AF1681455285D...
Though that is not an exit, which gives it a completely different metric.
Are you also sure that coloclue likes you playing exit? (I can only assume so ;)
Greets, Jeroen
++ 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.
tor-relays@lists.torproject.org