From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UOsYu-0004Pi-G7 for bitcoin-development@lists.sourceforge.net; Sun, 07 Apr 2013 16:35:24 +0000 X-ACL-Warn: Received: from olivere.de ([85.214.144.153] helo=mail.olivere.de) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1UOsYo-0005q4-Kd for bitcoin-development@lists.sourceforge.net; Sun, 07 Apr 2013 16:35:24 +0000 Received: from ip-81-210-197-250.unitymediagroup.de ([81.210.197.250]:37902 helo=[192.168.88.245]) by mail.olivere.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1UOsYh-0008Tj-Vg; Sun, 07 Apr 2013 18:35:12 +0200 Message-ID: <5161A03E.2040802@olivere.de> Date: Sun, 07 Apr 2013 18:35:10 +0200 From: Oliver Egginger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4 MIME-Version: 1.0 To: Scott Howard References: <51618612.9010603@olivere.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -2.4 (--) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -2.4 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1UOsYo-0005q4-Kd Cc: Bitcoin Development Subject: Re: [Bitcoin-development] DOS-Attacks on bitcoin-client? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Apr 2013 16:35:24 -0000 Am 07.04.2013 17:22, schrieb Scott Howard: > Many new users have started using the reference client which downloads > the whole blockchain from peers. Yes I have made a clean start because of the the new database structure. > There currently isn't a throttling > mechanism [1] so it's possible to quickly eat up your bandwidth. You > can try QoS on your router or use the -nolisten command line flag. You > will still relay transactions, just not serve the whole blockchain. I see. I successfully have downloaded the Blockchain again. Thus, it should not occur again now. If it does, I'll be back again. :-) Thank you for your quick help. regards Oliver