Timeline for Tor relay (arm monitor) doesn't seem to follow Tor settings (torrc)
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 13, 2014 at 9:30 | comment | added | Birb | Since I never managed to get my relay fixed, I've decided to shut it down completely for the time being. It didn't solve my question (unless of course I need to wait a month or whatever before I can see the average numbers match up), but it was very useful. ...and thanks for that. :) | |
| Aug 5, 2014 at 23:16 | history | edited | Jens Kubieziel | CC BY-SA 3.0 |
corrected my answer
|
| Aug 5, 2014 at 15:52 | comment | added | Birb | OK, so, 16 hours later the current speeds and torrc as arm reads it can be seen in the updated question. The avg speeds are still 3 times higher than permitted, but at least the burst rate seems to behave somewhat nicely (not shown, but observed after snapshot was taken). | |
| Aug 4, 2014 at 22:55 | comment | added | Birb |
It says on the man-page for RelayBandwidthRate that "Relayed traffic currently is calculated to include answers to directory requests, but that may change in future versions. (Default: 0)". Do you know if this has changed since the man-page was written? I will try to set the other parameter, see what happens and report back when I wake up or get back from work.
|
|
| Aug 4, 2014 at 20:19 | history | answered | Jens Kubieziel | CC BY-SA 3.0 |