> On 25 Oct 2017, at 08:35, rasptor 4273 wrote:
>
> However there's also a lot of this in that file:
> Oct 24 16:55:45.000 [warn] Your server (24.132.17.230:9001) has not managed
> to confirm that its ORPort is reachable. Please check your firewalls, ports,
> address, /etc/hosts file, etc.
> O
My IP/ORPORT is 24.132.17.230:9001.
My relay is still running. arm shows traffic going through and several
circuits on the connections page. And from my notices.log file:
Oct 24 16:35:45.000 [notice] Heartbeat: It seems like we are not in the
cached consensus.
Oct 24 16:35:45.000 [notice] Heartbea
Hey,
And on the road, you will be able to see "the man who is wearing the Tor
Operator -Level 2- Tshirt" :)
Cheers ;)
> It seems to me that it might be better to have a reward for the first stage
> of running a relay(s) at a couple of months and another reward for much
> longer, faster or finan
Thanks for the encouragement Nagaev :)
Yes I am very aware of Tom van der Woerdt's previous work, and I am
attempting to avoid some of the problems he faced. This implementation is
pure Go, so I will not have cgo-based issues at least.
As I said the project is still far from complete. It implemen
Hey
Thanks for doing that! It came many times to my mind.
There were efforts on implementing Tor relay in Golang before, by
Tom van der Woerdt:
https://github.com/tvdw/gotor
Have you looked at the project?
In his blog post
https://tvdw.eu/blog/2015/01/24/implementing-a-tor-relay-from-scratch/
To
On 2017-10-24 03:30, nusenu wrote:
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? -> correlate it with the relays
by version graph)
I had a dead relay afte
