Advertised/Measured bandwidth is too low. Only the top XX% (I think
10-20%, I don't remember off-hand) of nodes (by bandwidth) are eligible
to become guard nodes. At the moment, that works out that your node
needs to have at least ~2MBps bandwidth to be be eligible for the guard
flag.
On
Hi,
this is actually a question to BWauth ops.
even though the new onionoo measured flag data is not* yet completely
rolled out (since it has to be deployed for a week to assign the flag
to all relays), I would have a question since the data says that
all relays in the previously detected AWS
We're not punishing on purpose, that's for sure. DirAuths may not
vote on a relay to exclude it from the consensus, or may vote to give
it BadExit, but BWAuths have no such mechanism, and I guess you'll
just have to take the words of the individual operators to not do
something as evil as try and
On 18.08.2015 17:09, Tor Tor wrote:
That explains it, thanks. Related question. arm often reports
throughput around 1 Mbit/s. Why is my measured bandwidth only 110
Kbit/s on blutmagie.de? (My connection is advertised as 10 Mbit and
always gets over 1 Mbit).
On Tue, Aug 18, 2015 at 07:43:15AM -0400, 12xBTM wrote:
Advertised/Measured bandwidth is too low.
This is true.
Only the top XX% (I think
10-20%, I don't remember off-hand) of nodes (by bandwidth) are
eligible to become guard nodes. At the moment, that works out that
your node needs to have
