Another update.
Nothing to report.
None of the exits I changed to guard changed their consensus weight.
I spun up a brand new guard relay last week, and it also is stuck at 20.
So, my one relay that was an exit but then put to guard which was then
reverted back to exit is - dun dun dun - a compl
Further update:
I changed two other affected relays to guard last night.
The consensus weight didn't budge at all and bandwidth usage was
negligible, so I've deleted all my onion keys for those two relays.
So these relays are starting fresh. We'll see how it goes. I'm going to
wait until I get s
A quick update regarding my guard-that-was-exit.
This relay, when it was an exit relay, never got past consensus weight
of 20. When I changed it to guard, the consensus weight immediately
jumped, and bandwidth was finally starting to be used. As usual, it
took a few days for full usage, but it did
Ok, even my node
(https://atlas.torproject.org/#details/FE4033D750831C32A957174ADD11E40F558A14A9)
after 7 days is not yet measured.
But what happens to Tor Network with all these nodes (> 1000) with
consensus=20?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Speak Freely:
From my ex
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Speak Freely:
>> From my experience, this happens only with exit relays. Changing
>> from
> an exit relay to a guard fixes the problem immediately.
>
> I've seen past threads that mentioned deleting your id key would
> fix the problem, but that ne
>From my experience, this happens only with exit relays. Changing from
an exit relay to a guard fixes the problem immediately.
I've seen past threads that mentioned deleting your id key would fix
the problem, but that never fixed it for me. But that is also
counter-intuitive given that going from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Speak Freely:
> It seems like the most pertinent task would be to fix the problem,
> not display it.
>
> Just saying...
I agree.
Do we know already which relays are affected and why?
teor asked in the trac entry as well.
https://trac.torproject.
It seems like the most pertinent task would be to fix the problem, not
display it.
Just saying...
Matt
Speak Freely
nusenu:
> In the light of this thread I made an onionoo (-> atlas) feature
> request to display the Unmeasured=1 flag on atlas (eventually).
>
> https://trac.torproject.org/proj
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
In the light of this thread I made an onionoo (-> atlas) feature
request to display the Unmeasured=1 flag on atlas (eventually).
https://trac.torproject.org/projects/tor/ticket/16020
-BEGIN PGP SIGNATURE-
iQIcBAEBCgAGBQJVVHtkAAoJEFv7XvVCEL
I'll be shutting down 5 of my unmetered 100mbit relays until they are fixed.
Matt
Speak Freely
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Thanks for the response Moritz. L Brandt
On 5/10/2015 11:26 PM, Moritz Bartl wrote:
Hi,
This is a known problem; the bandwidth authorities need to be worked on.
See for example
https://trac.torproject.org/projects/tor/ticket/13450
https://trac.torproject.org/projects/tor/ticket/4359
There's
Hi,
This is a known problem; the bandwidth authorities need to be worked on.
See for example
https://trac.torproject.org/projects/tor/ticket/13450
https://trac.torproject.org/projects/tor/ticket/4359
There's no timeline set yet on when this will be fixed.
On 05/10/2015 09:48 PM, Marcus Wahle wr
Same problem with my relay
(https://atlas.torproject.org/#details/FE4033D750831C32A957174ADD11E40F558A14A9).
If i loof at collected data at collector.torproject i see: Bandwidth=20
Unmeasured=1
Best regards,
--
ML.Tor.Node
Hey I have almost the same problem with my relay
(https://atlas.
I had a look at
https://collector.torproject.org/recent/relay-descriptors/consensuses/2015-05-10-19-00-00-consensus
There you can find 874 relays with the „flag“ "Bandwidth=20 Unmeasured=1“…
I don’t think this is normal…
Can anybody have a look at this?!
Best regards,
Marcus
> Am 10.05.2015 um
Hey I have almost the same problem with my relay
(https://atlas.torproject.org/#details/DABC2440E9EAAEDB23F150CF95656405917A7829)
I stuck to Consensus Weight: 20 since over one week. If I look at the
"collected data“ I se the „unmetered = 1“ comment. :(
Any Ideas how to fix this? Is this the nor
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
yes
I have experienced the same problem on my exit relay:
DDC6C968B3DFD156C97FD71808758D251B66DBB2
My relay lost the stable flag due to a inadvertent shut-down a few days
back.
LB
On 5/9/2015 1:38 PM, Neel Chauhan wrote:
Hi,
I have a Tor relay
(https://atlas.torproject.org/#details/342587
Hi,
I have a Tor relay
(https://atlas.torproject.org/#details/342587A287603040A49BB364D72EAC0B6BC3D71A)
running from a FreeBSD server at my house on with a 5 megabit upstream
connection.
I have seen that lately, Tor's "Consensus Weight" value on this relay has
not been going anywhere above (or bel
18 matches
Mail list logo
