It has hit me again aswell, consensus dropped from 40,000+ to 20 after
serving 100+ mbit daily to the Tor network:
06/12/2015 621.04 GiB | 692.11 GiB |1.28 TiB | 127.49
Mbit/s
06/13/2015 565.29 GiB | 629.45 GiB |1.17 TiB | 116.00
Mbit/s
06/14/2015 649.90 GiB |
Matt,
135 Kb/s measured, I'm currently pushing data at 40Mbit in/out (limit is
80 Mbit with burst to 120 Mbit).
On 21.05.2015 11:14 PM, Speak Freely wrote:
Hey NOC,
Nah I had the same experience with *1* relay. Following the same
pattern, none of the other relays have left 20. I'm now at 162
After changing my exit node to a regular node it jumped from 20 to 7000
rating. I changed it back to exit and it jumped to 9000 and stayed on
that value. This was a few days ago.
Right now I've seen an increase to 17000. I assume this is due to the
new authorities? I'm glad that my node is bei
hey,
can you do me a favor and remove the exit status of your relay and turn
it into a regular node? I experienced the same problem as you:
https://atlas.torproject.org/#details/3D7E274A87D9A89AF064C13D1EE4CA1F184F2600
but ever since I removed the exit-flag I am generating some consensus
rat
my relay changed from 20 to 2080 overnight. I wonder if it will change
any more.
On 23.04.2015 08:29 PM, Speak Freely wrote:
Alright, I'm about to lose my mind.
My consensus weight on atlas already jumped from 20 to 207 on the relay
I changed from an exit to middle.
So... Super-duper.
Matt
Congrats, I'm still running on 20 :')
On 23.04.2015 08:29 PM, Speak Freely wrote:
Alright, I'm about to lose my mind.
My consensus weight on atlas already jumped from 20 to 207 on the relay
I changed from an exit to middle.
So... Super-duper.
Matt
Speak Freely
_
PM, Speak Freely wrote:
Most dearest Network Operations Center,
As the problem has yet to go away, I decided to bring back from the
dead
this thread.
The problem still persists, my consensus weight never leaves 20.
- I have deleted the ID
- I have changed the IP address
- I had the relay offlin
Hello,
currently there is no solution bar deleting your ID.
The most relevant threads:
https://lists.torproject.org/pipermail/tor-relays/2015-January/006225.html
https://lists.torproject.org/pipermail/tor-relays/2015-January/006055.html
There is also no ETA on when this will be fixed.
On 18.
t my knowledge about that is
far
below the average. So I hope someone with more knowledge is reviewing
this case and post a solution or declare it as a general probleme and
write a bug report.
~Josef
Am 31.01.2015 um 22:35 schrieb Network Operations Center:
2)
This link has been posted:
http://f
2)
This link has been posted:
http://freehaven.net/~arma/moria1-v3-status-votes
which is a collection of all 9 BWauth nodes. Currently there is nothing
a node operator can do bar deleting his keys. Atleast no other solution
has been posted in this thread.
On 31.01.2015 10:23 PM, starlight.201
This has already been done. And I was under the impression that things
would be changing soon. I still find it weird that the network is
ignoring several nodes.
On 31.01.2015 09:23 PM, starlight.201...@binnacle.cx wrote:
At 20:54 1/31/2015 +0100, you wrote:
Consensus weight of my relays and t
Ah I see, thanks for taking the time investigating this. If there is
something I need to do to help, please let me know.
On 21.01.2015 01:22 PM, Karsten Loesing wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/01/15 11:54, Network Operations Center wrote:
My dropping consensus
My dropping consensus overlaps exactly with the blue line on that graph
time-wise. The 1 Month Graph shows this pretty well.
https://atlas.torproject.org/#details/3D7E274A87D9A89AF064C13D1EE4CA1F184F2600
It feels as if I am almost completely dependent on that blue node,
although since one need
edine wrote:
On Tue, Jan 20, 2015 at 11:44:46AM +0100, Network Operations Center
wrote:
Thank you!
https://atlas.torproject.org/#details/3D7E274A87D9A89AF064C13D1EE4CA1F184F2600
The votes from the directory authorities for the last consensus period
are here:
http://freehaven.net/~arma/moria1-v3-s
Thank you!
https://atlas.torproject.org/#details/3D7E274A87D9A89AF064C13D1EE4CA1F184F2600
On 20.01.2015 09:10 AM, Karsten Loesing wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/01/15 21:04, Network Operations Center wrote:
Yes, fraction dropped from 0,2% to 0.72%
Please
Yes, fraction dropped from 0,2% to 0.72%
On 19.01.2015 08:45 PM, Karsten Loesing wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/01/15 20:14, Bram de Boer wrote:
Sebastian wrote:
One theory might be that the addition of a new bwauth has
shifted which vote gets picked for the co
I concur. Maybe it's worth to also post to the bugtracker?
On 19.01.2015 08:14 PM, Bram de Boer wrote:
Sebastian wrote:
One theory might be that the addition of a new bwauth has shifted
which vote gets picked for the consensus. It's conceivable that
bwauths rate relays which are placed topologi
Hello,
You are not alone with this issue (
https://lists.torproject.org/pipermail/tor-relays/2015-January/006055.html
). The weirdest part is, that consensus is fixed to exactly 20 and on
Jan 06, on both nodes yours and mine the weight spiked up for a short
amount and then dropped back to 20.
, Issue 15
Date: Mon, 05 Jan 2015 11:05:49 +
Message: 3
Date: Mon, 05 Jan 2015 11:36:59 +0100
From: Network Operations Center
To: tor-relays@lists.torproject.org
Subject: Re: [tor-relays] Help - My relay consensus has been stripped
backto 20
Message-ID
Mine just jumped to 18,000, again I'd like to stress that I have not
changed anything in my torrc:
https://atlas.torproject.org/#details/3D7E274A87D9A89AF064C13D1EE4CA1F184F2600
On 04.01.2015 11:13 PM, bigbud...@safe-mail.net wrote:
Message: 3
Date: Sat, 03 Jan 2015 02:30:55 +0100
From: Sebas
My relay has also been set to 20 and I don't have any suspicious log
entries either. I think the best is to wait for a response from a dev?
On 04.01.2015 11:13 PM, bigbud...@safe-mail.net wrote:
Message: 3
Date: Sat, 03 Jan 2015 02:30:55 +0100
From: Sebastian Urbach
To:
Subject: Re: [tor-rel
21 matches
Mail list logo
