Re: [tor-relays] debugging unbound on 'torexit' failing DNS queries (solved)

I can kinda answer that. I run an exit node that happily does 200-250mbit/s according to netdata accounting and my monitoring regularly pegs it at nearly 200k connections. Usually 100-150k. On Sun, Jan 21, 2018 at 4:06 PM, nusenu wrote: > > > Quintin: >> Ah, thats it.

[tor-relays] Exit Flag Requires 80 and 443 (was: connlimit: better to use "DROP" or "REJECT --reject-with tcp-reset"?)

> On 21 Jan 2018, at 22:34, Toralf Förster wrote: > > On 01/11/2018 02:10 AM, teor wrote: >> So if you're going to do this, please set a much higher limit than 2. >> I would suggest at least 4, but 10 or more is better. >> >> You might be able to set it higher if you

Re: [tor-relays] Become a Fallback Directory Mirror

Hi, If it is not too late, I would like to volunteer the relay 32828476F4F84E15C42B4C360A5CD8DE4C3C2BE7. Rhea On Sun, Jan 21, 2018 at 1:45 PM teor wrote: > Hi, > > > On 22 Jan 2018, at 05:01, Fabian A. Santiago > wrote: > > January 8, 2018

Re: [tor-relays] Become a Fallback Directory Mirror

> On 22 Jan 2018, at 11:33, Rhea Tor wrote: > > If it is not too late, I would like to volunteer the relay > 32828476F4F84E15C42B4C360A5CD8DE4C3C2BE7. It's never too late - we rebuild the list every 6-12 months. We're tracking changes for the next list. Yours is here:

Re: [tor-relays] kelihos infection

This is like when I got the helpful notification saying that my exit relay was running Windows XP and I ought to upgrade it. You can, if you feel like it, write back explaining that your exit node happens to have been used to forward traffic on behalf of a computer that happens to be infected

[tor-relays] kelihos infection

Hello fellow relay operators, I have received word from my ISP that they detected malicious traffic from my account. I'm running the exit node "cave" with reduced exit policy, https://atlas.torproject.org/#details/3875c9c843d33762fa733bcaf128f26a10bc75e7 The information received from my ISP