All,
I am working on a pure Golang relay implementation.
https://github.com/mmcloughlin/pearl/
I have thus far been testing locally with chutney (
https://gitweb.torproject.org/chutney.git). The project is not complete by
any stretch, but I believe I am close to the point where it can handle Tor
On 10/23/2017 6:12 PM, teor wrote:
On 24 Oct 2017, at 09:08, s7r wrote:
it looks like your relay has a measured by authority 'bastet' of
355. That is not a big value. The other authorities measured this:
278;
355;
367;
803;
So it looks like the speed was pretty much the same for the measure
(don't take this information as granted this was a quick 'n dirty thing)
David Goulet:
> Since July 2017
It appears to have started earlier than July if you graph metrics' csv
file for better granularity. Maybe somewhere in mid May 2017 (maybe when
tor 0.2.9.x -> 0.3.0 started to spread? -> corre
> On 24 Oct 2017, at 09:08, s7r wrote:
>
> it looks like your relay has a measured by authority 'bastet' of
> 355. That is not a big value. The other authorities measured this:
>
> 278;
> 355;
> 367;
> 803;
>
> So it looks like the speed was pretty much the same for the measurements
> performe
Trey Nolen wrote:
>
>> First of all, thanks for running a relay.
>>
>> Based on my experience, what usually happens is that the provider of
>> your VPS observed during a period of time you used more than N mbps
>> constantly and all the time, so they capped your VPS at some KB/s limit.
>> There a
No, not yet. I was planning on setting up Atlas but haven't had a
chance. This was a little test server we had spun up for various
projects and we decided to just run a node on it. However, we plan
on keeping it going now, if we can get it running so that it
actually
Stephane Thevenot:
> BTW is the atlas webserver running ? database backend problem ?
onionoo (atlas backend) has currently some issues, the maintainer and
admins are looking into it
https://trac.torproject.org/projects/tor/ticket/23929
--
https://mastodon.social/@nusenu
twitter: @nusenu_
s
On 10/23/2017 04:36 PM, nusenu wrote:
>
> Trey Nolen:
>> I'm new to running a Tor relay and started one about a month ago. I've
>> got 50 Mbps dedicated to it and at first it climbed in traffic pretty
>> steadily until it got to around 25-30 Mbps being used. Since then, it
>> has declined ste
I'm not trhotling VPS when renting them :) for real !!
BTW is the atlas webserver running ? database backend problem ?
https://atlas.torproject.org/#search/208.94.110.37
Le 2017-10-23 17:34, s7r a écrit :
> Hi,
>
> Trey Nolen wrote:
>
>> I'm new to running a Tor relay and started one ab
> First of all, thanks for running a relay.
>
> Based on my experience, what usually happens is that the provider of
> your VPS observed during a period of time you used more than N mbps
> constantly and all the time, so they capped your VPS at some KB/s limit.
> There are performance monitoring s
Hi,
Trey Nolen wrote:
> I'm new to running a Tor relay and started one about a month ago. I've
> got 50 Mbps dedicated to it and at first it climbed in traffic pretty
> steadily until it got to around 25-30 Mbps being used. Since then, it
> has declined steadily and is down to about 350 KBps n
Trey Nolen:
> I'm new to running a Tor relay and started one about a month ago. I've
> got 50 Mbps dedicated to it and at first it climbed in traffic pretty
> steadily until it got to around 25-30 Mbps being used. Since then, it
> has declined steadily and is down to about 350 KBps now (yes,
I'm new to running a Tor relay and started one about a month ago. I've
got 50 Mbps dedicated to it and at first it climbed in traffic pretty
steadily until it got to around 25-30 Mbps being used. Since then, it
has declined steadily and is down to about 350 KBps now (yes, I'm
keeping the units
On 23 Oct (22:49:55), rasptor 4273 wrote:
> My relay has gone off the consensus.
> Fingerprint: E7FFF8C3D5736AB87215C5DB05620103033E69C3
Interesting. And it is still running as of now without any problems? Can you
give me the IP/ORPORT tuple?
You think you can add this to your torrc and then HUP
My relay has gone off the consensus.
Fingerprint: E7FFF8C3D5736AB87215C5DB05620103033E69C3
Alias: rasptor4273
Am running Tor 0.2.5.14 on Debian, Raspberry Pi 2B. I upgraded to that
version on September 3rd.
I grepped through these:
https://collector.torproject.org/archive/relay-descriptors/consens
> Was it picked up by any alerts earlier, especially those two big and
> short-term drops?
I assume you mean the bridges line, they didn't remain unnoticed [1] and
you can find their explanation here:
https://metrics.torproject.org/news.html
[1]
https://lists.torproject.org/pipermail/metrics-tea
nusenu:
>> As some of you know, TDP did a little suite of shell scripts based on
>> OONI data to look at diversity statistics:
>
> I think you mean onionoo (not OONI).
Yes. Sloppy on details when thinking conceptually sometimes :)
>
>> In other words, daily reports would be run on, say, bw con
> As some of you know, TDP did a little suite of shell scripts based on
> OONI data to look at diversity statistics:
I think you mean onionoo (not OONI).
> In other words, daily reports would be run on, say, bw consensus by
> country, and if there was some statistically significant change over N
David Goulet:
> Hello everyone!
>
> Since July 2017, there has been a steady decline in relays from ~7k to now
> ~6.5k. This is a bit unusual that is we don't see often such a steady behavior
> of relays going offline (at least that I can remember...).
>
> It could certainly be something normal h
On 23 Oct (09:37:31), Eli wrote:
> I can state the reason I stopped hosting my exit relay was due to tor rpm
> package not being up to date for CentOS 7. The last available version was
> considered out of date and no longer supported. So instead of running a
> relay that was potentially detrimenta
I can state the reason I stopped hosting my exit relay was due to tor rpm
package not being up to date for CentOS 7. The last available version was
considered out of date and no longer supported. So instead of running a relay
that was potentially detrimental to the health of the tor network I sh
Hello everyone!
Since July 2017, there has been a steady decline in relays from ~7k to now
~6.5k. This is a bit unusual that is we don't see often such a steady behavior
of relays going offline (at least that I can remember...).
It could certainly be something normal here. However, we shouldn't r
22 matches
Mail list logo
