-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thanks for the eloquent response. Many good points made and apologies if
my comments came across as being critical of the Tor development
community. I have no plans to take down the relays I'm running any time
soon -- bwauth hiccups or not. Regard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Julian
Thanks for your contribution to Tor!
Please keep them running, as much as you can. We already struggle to
(at least partially) solve the issue for the short term, by launching
more bandwidth authorities. On the long term, some research
I have a non-exit relay that has been up and running with 100% uptime on
a 15mbps circuit for going on 20 days that is still unmeasured.
I also have an exit node on a 100mbps un-metered link that I brought
online 7 days ago and purchased specifically to donate to Tor that is
still unmeasured b
Hey,
I still have the problem, that my relay (non-exit) is "not measured". I tried
to set up a new ID but this doesn’t work. The relay ist still not measured
since one week. (12FD624EE73CEF37137C90D38B2406A66F68FAA2)
I don’t know much about the DA, but I checked that only two of nine have
measu
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
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 16200 and
averaging ~30mb/s.
4 still in limbo. What's also interesting is I setup a non-exit and it
also will not get past 20.
What does arm say your measured spee
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
Roger Dingledine writes:
> On Mon, May 18, 2015 at 09:02:27PM +, nusenu wrote:
>> now even DocTor starts to complain
>>
>> https://lists.torproject.org/pipermail/tor-consensus-health/2015-May/005772.html
>From what I've seen, there were only two messages from DocTor about
this (Mon May 18 0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> At least partially, the balance of measured/unmeasured should be
> fixed in the new few days.
Thanks for the pre-info, appreciated.
-BEGIN PGP SIGNATURE-
iQIcBAEBCgAGBQJVW6NQAAoJEFv7XvVCELh0/18P/2dsv6o5DFwCqCid41nYaksG
FNmgX8WqvOBGhcNng
On Mon, 18 May 2015, Roger Dingledine wrote:
I've even been pondering crazy hacks at this point like exporting moria1's
bwauth file to a second dir auth, so it gets to vote twice and we're more
likely to have the required minimum of three opinions for each relay.
Are the existing bwauths down,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is splitting the bwauth data into a seperate consensus of some
description a possibility and have a few people run them without
needing to be a dirauth? That would mean lesser responsibility is
placed on bwauth ops and perhaps the load or task could be
On Tue, May 19, 2015 at 12:27:12AM +0300, s7r wrote:
> Hi nusenu,
>
> Again thanks for keeping an eye on things. At least partially, the
> balance of measured/unmeasured should be fixed in the new few days.
>
> To relay operators, in the mean time, please bare for few more days
> and sorry for th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi nusenu,
Again thanks for keeping an eye on things. At least partially, the
balance of measured/unmeasured should be fixed in the new few days.
To relay operators, in the mean time, please bare for few more days
and sorry for the inconvenience, I
On Mon, May 18, 2015 at 09:02:27PM +, nusenu wrote:
> now even DocTor starts to complain
>
> https://lists.torproject.org/pipermail/tor-consensus-health/2015-May/005772.html
Yep. moria1's bwauth seems to be working fine, so I'm the only one
paying attention to the thread here, and also the on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
now even DocTor starts to complain
https://lists.torproject.org/pipermail/tor-consensus-health/2015-May/005772.html
-BEGIN PGP SIGNATURE-
iQIcBAEBCgAGBQJVWlNjAAoJEFv7XvVCELh0hPgP/36ZVrI6ec+5iplyNWN8xklx
RfAeKoDLrQD2FGB7bud1nDQB3EZrnVqnjIWMO
On Thu, May 14, 2015 at 08:01:19PM +, nusenu wrote:
> Dear Tor BW Authories,
>
> we'd like to bring the following issue to your attention.
> Since the last two weeks the amount of unmeasured relays is steadily
> rising [1].
Hello nusenu,
Thanks for the kick.
For other statistics, each hour
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> Graph showing the last 5 months:
> https://trac.torproject.org/projects/tor/attachment/ticket/13450/unmeasured_relaycount.png
you
>
can also see that the adv. bw. is going down since the beginning
of the month:
https://metrics.torproject.org/ba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Tor BW Authories,
we'd like to bring the following issue to your attention.
Since the last two weeks the amount of unmeasured relays is steadily
rising [1].
unmeasured relays on 2015-05-01: 387
unmeasured relays today: 1087 (and growing)
Gra
18 matches
Mail list logo
