On 7 July 2015 at 09:04, Carlin Bingham wrote:
> I just want to chime in with my own consensus weight problem.
>
> FF1678164E0FFF1DACA45E3DCDE16E49FF1374BE has been running for over 70
> days and still has a consensus of 20, I don't think it has ever changed
> since it was started.
>
> Looking at
I just want to chime in with my own consensus weight problem.
FF1678164E0FFF1DACA45E3DCDE16E49FF1374BE has been running for over 70
days and still has a consensus of 20, I don't think it has ever changed
since it was started.
Looking at the consensus it is unmeasured=1 by every authority.
Any id
Hey Josh,
(The following is the only sentence that matters in this email)
I was just curious about the statement that it "takes a full 2 weeks for
the new-relay cap to be aged-out".
(The following is only background information in case you were curious,
because it's been a hell of a long standi
Hi Matt,
Which relays are you have issues with?
Kind Regards,
Joshua Lee Tucker
@tuckerwales
http://tucker.wales
> On 6 Jul 2015, at 19:41, Speak Freely wrote:
>
> Starlight,
>
> I created this relay on Friday, shortly after you told me to be patient.
>
> https://atlas.torproject.org/#deta
Starlight,
I created this relay on Friday, shortly after you told me to be patient.
https://atlas.torproject.org/#details/41C526E3C1441A3CDE9B605002643B94F3750E8C
Uptime: 3 days 23 hours
CW: 1100 (yesterday it was at 740)
It gained consensus after 48 hours, but you said it would take 2 weeks?
Ho
Takes a full two weeks for the
new-relay cap to be aged-out.
Patience.
At 13:33 7/2/2015 +, Speak Freely wrote:
>
>I did as s7r suggested, updated to 0.2.7.1-alpha-dev,
>and changed fingerprints.
>
>And we're still crippled by CW of 20.
>(Yes, yes, I know. The relay has gone back
>to stage 1
I did as s7r suggested, updated to 0.2.7.1-alpha-dev, and changed
fingerprints.
And we're still crippled by CW of 20.
(Yes, yes, I know. The relay has gone back to stage 1/3 because the
fingerprints changed.)
Uptime: > 48 hours
Upload/download : 2.1GB, works out to a blazingly fast speed of 12.1
On 2015-06-29 17:51, Speak Freely wrote:
Hello,
First of all, I love Tor. I love Tor Browser, and I love running
relays.
When the problems are solved, I will most likely spin up more relays.
I'm leaving my fastest relay running, as a method of checking the
status
for myself. The rest have a
Rah rah rah... Emailed Aaron directly by accident.
Here's the email:
Hello,
First of all, I love Tor. I love Tor Browser, and I love running relays.
When the problems are solved, I will most likely spin up more relays.
I'm leaving my fastest relay running, as a method of checking the status
On 2015-06-19 17:59, Speak Freely wrote:
Yeah, I've given up. I won't be renewing most of my relays this month.
:(
Matt
Speak Freely
Hi Matt,
Sorry that you have had so much trouble with your relays being
underutilized. I am now working to fix/refactor Tor's Bandwidth
Authority system as a
Yeah, I've given up. I won't be renewing most of my relays this month. :(
Matt
Speak Freely
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
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 |
I looked at
https://atlas.torproject.org/#details/D60B02A13F5D9CAFD6EC27A5332C5FEF5B769105
/ 4FreeSpeech for the latest vote:
moria: w Bandwidth=3012 Measured=1890
maatuska: w Bandwidth=3012 Measured=3820
gabelmoo: w Bandwidth=3012
longclaw: w Bandwidth=3012
consensus: w Bandwidth=20 Unmeasured
Zero progress on this, so I thought I'd pop it up again.
I'm only pointing this out because it's interesting, not because I think
anyone will do anything about it. It may be interesting to someone
looking into the diversity of consensus weights given a small subset
from two providers, that is all.
Actually I remembered a third relay having problems.
On Friday last week my provider asked me to rate limit one of my relays
because it was pumping a lot of data. (Unmetered does have its limits,
and I fully appreciate how my provider handled it) I changed the
RelayBandwidth from 100Mbit to 50Mbit
Just thought I'd throw it out there.
About 5 days ago I setup a new relay - it's consensus weight is still at 20.
Then, I noticed a relay I've been running for about a month all of
sudden lost all of it's consensus weight. It was ~17000, now at 20. It's
uptime is 25 days, and has downloaded 4.8TB
16 matches
Mail list logo