Relay traffic went to ~zero
Hi all, I have been running my relay for about a year now and about two weeks ago my relay traffic went close to zero [1]. Any ideas as to why? Is it my ISP silently throttling my ORport after founding out I run a relay? Is it some misconfiguration on my part? My consensus weight went down from ~400 to 10, over the last few days. [1]: http://imgur.com/YOMxU66 [2]: https://atlas.torproject.org/#details/1673C036756D2800D2BD0F7C20DEE3FB934F9C... [3]: http://torstatus.blutmagie.de/router_detail.php?FP=1673c036756d2800d2bd0f7c2... Cheers, -- Jan ______________________________________________________ /\ # PGP: 362056ADA8F2F4E421565EF87F4A448FE68F329D /__\ # https://neuromancer.sk /\ /\ # Eastern Seaboard Phishing Authority /__\/__\ #
Hey Jan, Humm, about ORPort, you can try easily to change it in your torrc configuration file (+firewall rules may be?) If you have nothing else running on this server (ex: webserver), you can try to "hide" Tor traffic by using commons ports like 80 or 443... 17/04/2017 11:35, Jan Jancar :
Hi all, I have been running my relay for about a year now and about two weeks ago my relay traffic went close to zero [1].
Any ideas as to why? Is it my ISP silently throttling my ORport after founding out I run a relay? Is it some misconfiguration on my part? My consensus weight went down from ~400 to 10, over the last few days.
[1]: http://imgur.com/YOMxU66 [2]: https://atlas.torproject.org/#details/1673C036756D2800D2BD0F7C20DEE3FB934F9C... [3]: http://torstatus.blutmagie.de/router_detail.php?FP=1673c036756d2800d2bd0f7c2...
Cheers,
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-- Petrusko C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5
I see on Atlas you have changed ORPort. And it can be nice to update your Tor version 0.2.9.9 to current 0.2.9.10 ;) -- Petrusko C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5
On 04/21/2017 07:31 AM, Petrusko wrote:
I see on Atlas you have changed ORPort. And it can be nice to update your Tor version 0.2.9.9 to current 0.2.9.10 ;)
I would, but I run Arch Linux, well Arch Linux ARM on that machine, and 0.2.9.10 is still in testing [1][2]. [1]: https://www.archlinux.org/packages/community/x86_64/tor/ [2]: https://archlinuxarm.org/packages/armv6h/tor Cheers, -- Jan ______________________________________________________ /\ # PGP: 362056ADA8F2F4E421565EF87F4A448FE68F329D /__\ # https://neuromancer.sk /\ /\ # Eastern Seaboard Phishing Authority /__\/__\ #
On 2017-04-21 at 11:44, Jan Jancar wrote:
I would, but I run Arch Linux, well Arch Linux ARM on that machine, and 0.2.9.10 is still in testing [1][2].
[1]: https://www.archlinux.org/packages/community/x86_64/tor/ [2]: https://archlinuxarm.org/packages/armv6h/tor
Cheers,
Hi Jan, you can use the Arch Build System [1] on Arch Linux to retreive the PKGBUILD files of testing packages without using the testing repository for pacman. That's how I am using 0.2.9.10 on my exit with Arch Linux without switching to the testing packages completely. Best, Michael [1] https://wiki.archlinux.org/index.php/Arch_Build_System
Hi all, I have been running my relay for about a year now and about two weeks ago my relay traffic went close to zero [1].
Any ideas as to why?
You relay's traffic went to ~zero because of problems with a tor network bandwidth scanner that (also) decides how much traffic you will get. Maatuska's bandwidth scanner is down since 2017-04-14 07:00. Maatuska's bw scanner is the bw authority with the highest measurements for many relays, if it no longer provides data your mean measured value and consensus weight will fall. For details see the last measurement vote by maatuska before it's scanner went offline: 2017-04-14 06:00:00 longclaw=28 moria1=22 gabelmoo=26 Faravahar=33 maatuska=40 afte maatuska went offline: 2017-04-14 07:00:00 maatuska=None longclaw=28 gabelmoo=26 Faravahar=33 moria1=22 2017-04-14 08:00:00 moria1=22 Faravahar=33 longclaw=28 gabelmoo=26 maatuska=None Using data from collector.torproject.org I created an easy to search/grep output file that contains all bwauth votes for all relays between 2017-04-01 and 2017-04-19. You can simply grep/search for your relay(s) nickname or fingerprint to see if maatuska was the mean value or above the mean value for your relay before it went offline. If it was, you are affected by its downtime. https://github.com/nusenu/tor-network-observations/tree/master/bwauthvotes (this file is big: ~29MB compressed, ~464MB uncrompressed) File format: date nickname/fingerprint measurement-votes
On 04/21/2017 02:45 PM, nusenu wrote:
Hi all, I have been running my relay for about a year now and about two weeks ago my relay traffic went close to zero [1].
Any ideas as to why?
You relay's traffic went to ~zero because of problems with a tor network bandwidth scanner that (also) decides how much traffic you will get.
Maatuska's bandwidth scanner is down since 2017-04-14 07:00. Maatuska's bw scanner is the bw authority with the highest measurements for many relays, if it no longer provides data your mean measured value and consensus weight will fall.
For details see the last measurement vote by maatuska before it's scanner went offline:
2017-04-14 06:00:00 longclaw=28 moria1=22 gabelmoo=26 Faravahar=33 maatuska=40
afte maatuska went offline: 2017-04-14 07:00:00 maatuska=None longclaw=28 gabelmoo=26 Faravahar=33 moria1=22 2017-04-14 08:00:00 moria1=22 Faravahar=33 longclaw=28 gabelmoo=26 maatuska=None
Right, I noticed some news of a bwauth being down. However that only went down at 2017-04-14. When I check the logs you provided, and grep for each bwauths measures for my relay I get the following significant jumps down: 2017-04-06 08:00:00 Faravahar=519 2017-04-06 09:00:00 Faravahar=102 2017-04-09 04:00:00 gabelmoo=203 2017-04-09 05:00:00 gabelmoo=78 2017-04-05 18:00:00 longclaw=337 2017-04-05 19:00:00 longclaw=103 2017-04-07 02:00:00 maatuska=197 2017-04-07 03:00:00 maatuska=95 2017-04-08 14:00:00 moria1=358 2017-04-08 15:00:00 moria1=55 all at around 6th - 9th. Which leads me to believe maatuska's bwauth going down is only a partial cause of my (zero) traffic. I don't really know what else I can do, I changed my ORport, restarted my relay, will upgrade as 0.2.9.10 reaches `community` on Arch Linux and hope it recovers.
Using data from collector.torproject.org I created an easy to search/grep output file that contains all bwauth votes for all relays between 2017-04-01 and 2017-04-19.
You can simply grep/search for your relay(s) nickname or fingerprint to see if maatuska was the mean value or above the mean value for your relay before it went offline. If it was, you are affected by its downtime.
https://github.com/nusenu/tor-network-observations/tree/master/bwauthvotes (this file is big: ~29MB compressed, ~464MB uncrompressed)
File format: date nickname/fingerprint measurement-votes
Thanks for the data! Cheers, -- Jan ______________________________________________________ /\ # PGP: 362056ADA8F2F4E421565EF87F4A448FE68F329D /__\ # https://neuromancer.sk /\ /\ # Eastern Seaboard Phishing Authority /__\/__\ #
participants (5)
-
Jan Jancar -
Michael Armbruster -
nusenu -
Petrusko -
tor