public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Scott Howard <showard314@gmail.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] DOS-Attacks on bitcoin-client?
Date: Sun, 7 Apr 2013 11:22:32 -0400	[thread overview]
Message-ID: <CANg8-dC2FX-9QFE_Bq6djTiEsvvD+0Cc2Vy0Ofzk54DVrdVuxA@mail.gmail.com> (raw)
In-Reply-To: <51618612.9010603@olivere.de>

On Sun, Apr 7, 2013 at 10:43 AM, Oliver Egginger <bitcoin@olivere.de> wrote:
> Hello,
>
> I'm using your bitcoin-qt client (version 0.8.1). Normally everything is
> working pretty fine, but sometimes it seems that other nodes produce an
> enormous amount of traffic. I have not had the time to investigate
> thoroughly yet. I only have briefly viewed with tshark.
>
> So far I have just restarted the client in the hope that it no longer
> connects with the 'evil' node. This usually works quite well.
>
> Is anything about DOS-Attacks known to you?

Many new users have started using the reference client which downloads
the whole blockchain from peers. 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.

[1] https://github.com/bitcoin/bitcoin/issues/273



  reply	other threads:[~2013-04-07 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-07 14:43 [Bitcoin-development] DOS-Attacks on bitcoin-client? Oliver Egginger
2013-04-07 15:22 ` Scott Howard [this message]
2013-04-07 16:35   ` Oliver Egginger
2013-04-08  5:42 ` Jeff Garzik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANg8-dC2FX-9QFE_Bq6djTiEsvvD+0Cc2Vy0Ofzk54DVrdVuxA@mail.gmail.com \
    --to=showard314@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox