Re: [tor-relays] Recent wave of abuse on Tor guards

2017-12-21 Thread Felix
Am 22-Dec-17 um 08:25 schrieb niftybunny: > Still under heavy attack even with the MaxMemInQueues and 0.3.2.8-rc. I > need 2 xeons to push 30 mbit as a guard/middle … Do you want to share some information: Type i) (memory exhaustion by too many circuits) What is the memory(top) per tor and its

Re: [tor-relays] Recent wave of abuse on Tor guards

2017-12-21 Thread niftybunny
Still under heavy attack even with the MaxMemInQueues and 0.3.2.8-rc. I need 2 xeons to push 30 mbit as a guard/middle … Markus > On 22. Dec 2017, at 00:25, teor wrote: > > > On 22 Dec 2017, at 10:08, Roger Dingledine wrote: > (Connection refused;

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

2017-12-21 Thread Aneesh Dogra
D8972986BE19E0287770DF51C47C630A53DC6E97 Thanks -Aneesh On Fri, Dec 22, 2017 at 4:51 AM, Franklin Bynum wrote: > 78E2BE744A53631B4AAB781468E94C52AB73968B > ___ > tor-relays mailing list > tor-relays@lists.torproject.org >

Re: [tor-relays] IPv6 Issue with Relay

2017-12-21 Thread Conrad Rockenhaus
Thank you. It’s always the small things, huh? :D Conrad > On Dec 21, 2017, at 6:12 PM, teor wrote: > > >> On 22 Dec 2017, at 09:13, Conrad Rockenhaus wrote: >> I’ve confirmed that the following entries are in torrc: ORPort 9001

Re: [tor-relays] IPv6 Issue with Relay

2017-12-21 Thread teor
> On 22 Dec 2017, at 09:13, Conrad Rockenhaus wrote: > >>> I’ve confirmed that the following entries are in torrc: >>> >>> ORPort 9001 >>> ORPort [2600:1f14:ede:d601:e107:1a4b:ba3:803]:9001 >>> IPv6Exit 1 >> ... >> Also, you have set IPv6Exit, but Relay Search says: >>

Re: [tor-relays] Recent wave of abuse on Tor guards

2017-12-21 Thread teor
On 22 Dec 2017, at 10:08, Roger Dingledine wrote: >>> (Connection refused; CONNECTREFUSED; count 18; recommendation warn; >>> host DAC825BBF05D678ABDEA1C3086E8D99CF0BBF112 at 185.73.220.8:443) >>> >>> So - I get loads of CONNECTREFUSED whilst coming up (presumably because >>> of

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

2017-12-21 Thread Franklin Bynum
78E2BE744A53631B4AAB781468E94C52AB73968B ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] first impression with 0.3.2.8-rcant a fast exit relay

2017-12-21 Thread Toralf Förster
With 0.3.2.7-rc the command /usr/sbin/iftop -B -i eth0 -P -N -n -m 320M showed every then and when (few times in a hour) for 10-20 sec a traffic value of nearly 0 bytes for the short-term period (the left of the 3 values). Usuaally I do poberve between 6 and 26 MByte/sec. With the Tor

Re: [tor-relays] Recent wave of abuse on Tor guards

2017-12-21 Thread Roger Dingledine
On Thu, Dec 21, 2017 at 10:11:47PM +0100, Felix wrote: > It's currently good to be restrictive. May-be a *per ip* limit of 20 > (slow DoS) and a *per ip* rate of 1 per sec (fast DoS) is good. I'm getting up to speed on this issue (been absent for some days). My current thought is that these are

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

2017-12-21 Thread Anders Burmeister
Hi Tim, Be my guest 775B0FAFDE71AADC23FFC8782B7BEB1D5A92733E EFEACD781604EB80FBC025EDEDEA2D523AEAAA2F 484A10BA2B8D48A5F0216674C8DD50EF27BC32F3 1938EBACBB1A7BFA888D9623C90061130E63BB3F Best Regards Anders Burmeister Sent with [ProtonMail](https://protonmail.com) Secure Email. > Original

Re: [tor-relays] IPv6 Issue with Relay

2017-12-21 Thread Conrad Rockenhaus
On Dec 21, 2017, at 3:01 AM, teor wrote:On 21 Dec 2017, at 16:33, Conrad Rockenhaus wrote:Hello,One of the relays that I brought online yesterday, ConradsAWSExit (Hash 1B47E33F9D422CC97BD2DDA1F082BFF2FC58E79A) is showing up on Atlas that the IPv6 OR is

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

2017-12-21 Thread John Ricketts
Tim, Oh.. and C5A53BCC174EF8FD0DCB223E4AA929FA557DEDB2 John L. Ricketts, Ph.D. Quintex Alliance Consulting (325) 262-3488 Cell/Signal -Original Message- From: tor-relays [mailto:tor-relays-boun...@lists.torproject.org] On Behalf Of teor Sent: Wednesday, December 20, 2017 5:51 PM

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

2017-12-21 Thread John Ricketts
Tim, 0077BCBA7244DB3E6A5ED2746E86170066684887 041646640AB306EA74B001966E86169B04CC88D2 155D6F57425F16C0624D7641E4EB1B47C6F0 1AE949967F82BBE7534A3D6BA77A7EBE1CED4369 1DB25DF59DAA01B5BE3D3CEB8AFED115940EBE8B 1E5136DDC52FAE1219208F0A6BADB0BA62587EE6 2ED4D25766973713EB8C56A290BF07E06B85BF12

Re: [tor-relays] Recent wave of abuse on Tor guards

2017-12-21 Thread teor
Hi, You can block inbound connections if you like, but it's only a partial mitigation for the attack. > On 22 Dec 2017, at 06:42, mick wrote: > > So: My logs show Tor staying up for around 10 minutes at a time before > rebooting with the following sort of entries: > ... > Dec

Re: [tor-relays] Ongoing DDoS on the Network - Status

2017-12-21 Thread David Goulet
On 21 Dec (22:15:00), Felix wrote: > > If you are running a relay version >= 0.3.2.x (currently 281 relays in the > > network), please update as soon as you can with the latest tarball or latest > > git tag. > Update as well if HSDir is still present? The network might loose the > rare ones. If

Re: [tor-relays] Ongoing DDoS on the Network - Status

2017-12-21 Thread Felix
> If you are running a relay version >= 0.3.2.x (currently 281 relays in the > network), please update as soon as you can with the latest tarball or latest > git tag. Update as well if HSDir is still present? The network might loose the rare ones. -- Cheers, Felix

Re: [tor-relays] Recent wave of abuse on Tor guards

2017-12-21 Thread Felix
Hi mick > And I run 0xbaddad - EA8637EA746451C0680559FDFF34ABA54DDAE831 a guard > (though whether it stays a guard depends. It keeps falling over.) Still guard > (As an aside, I'd be very > grateful for any feedback from other relay operators who /have/ added > iptables "connlimit" rules. What

Re: [tor-relays] Ongoing DDoS on the Network - Status

2017-12-21 Thread David Goulet
On 20 Dec (11:21:57), David Goulet wrote: > Hi everyone! > > I'm David and I'm part of the core development team in Tor. A few minutes ago > I just sent this to the tor-project@ mailing list about the DDoS the network > is currently under: > >

Re: [tor-relays] Recent wave of abuse on Tor guards

2017-12-21 Thread mick
On Wed, 20 Dec 2017 17:22:54 +0100 fco...@wardsback.org allegedly wrote: > Hi > > I'm the happy maintainer of wardsback : > B143D439B72D239A419F8DCE07B8A8EB1B486FA7 And I run 0xbaddad - EA8637EA746451C0680559FDFF34ABA54DDAE831 a guard (though whether it stays a guard depends. It keeps falling

Re: [tor-relays] restarting tor service after AccountingMax has been reached

2017-12-21 Thread Fabian A. Santiago
On December 21, 2017 4:26:11 AM EST, Sebastian Hahn wrote: > >> On 20. Dec 2017, at 22:46, Fabian A. Santiago > wrote: so how i first noticed was when i couldn't browse to my dirport >readme html page after a tor restart. are you

Re: [tor-relays] restarting tor service after AccountingMax has been reached

2017-12-21 Thread Sebastian Hahn
> On 20. Dec 2017, at 22:46, Fabian A. Santiago > wrote: >>> so how i first noticed was when i couldn't browse to my dirport readme html >>> page after a tor >>> restart. are you saying when it normally hibernates, that page goes down >>> too? >> >> Yes. >> >>

Re: [tor-relays] IPv6 Issue with Relay

2017-12-21 Thread teor
> On 21 Dec 2017, at 16:33, Conrad Rockenhaus wrote: > > Hello, > > One of the relays that I brought online yesterday, ConradsAWSExit (Hash > 1B47E33F9D422CC97BD2DDA1F082BFF2FC58E79A) is showing up on Atlas that the > IPv6 OR is unreachable. > > The other relay is

Re: [tor-relays] IPv6 Issue with Relay

2017-12-21 Thread Toralf Förster
On 12/21/2017 06:33 AM, Conrad Rockenhaus wrote: > Hello, > > One of the relays that I brought online yesterday, ConradsAWSExit (Hash > 1B47E33F9D422CC97BD2DDA1F082BFF2FC58E79A) is showing up on Atlas that the > IPv6 OR is unreachable. Just a guess: IPv6 needs ICMPv6, so you should have