> On 25 Jan 2017, at 09:43, nusenu wrote:
>
> If you run an exit with IPv6 connectivity consider allowing IPv6 exiting
> as well, currently only ~12% of tor exit capacity allows also IPv6.
>
> https://trac.torproject.org/projects/tor/ticket/21269#comment:3
We found two
On 19/01/17 18:12, nusenu wrote:
> If you plan to grow further it can be handy to preemptively create relay
> keys so you don't have to touch all relays every time you add a new one.
Is there a guide on how this can be done? - for the benefit of other
relay operators who might want to do
>> Could you explain please why names like torworld.org, torservers.net,
>> online de, etc. are not aggregated in one position on
>> https://raw.githubusercontent.com/ornetstats/stats/master/o/main_exit_operators.txt
>
>
> https://github.com/ornetstats/stats writes:
>> Relays are aggregated
Thx Ivan for your support.
I got an eye on the logs and everything around.
ps: updated to 2.9.9 some hours ago... looks like ok for now.
Ivan Markin :
> There is nothing wrong at your side. You're probably experiencing the
> same issue as in ticket I've mentioned earlier. "a memory leakage
>
Hi Monkey Pet,
On Mon, Jan 23, 2017 at 05:57:42PM -0800, Monkey Pet wrote:
> I received the following email from my ISP, the IP belongs to the tor exit
> node. I am wondering if the DHS is sending it out to all tor exit nodes?
We receive Avalanche e-mails via our ISP, too. It started in early
Petrusko:
>> Probably there is a memory leakage somewhere that makes everything fail
>> and get process eventually killed by OS.
> You're right Ivan,
> my bad !
> Swap has grown quickly and has been full... Ok, it was a test with
> another instance... so I'll kill this other instance :(
There is