public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Wladimir <laanwj@gmail.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Abusive and broken bitcoin seeders
Date: Wed, 30 Jul 2014 15:50:30 +0200	[thread overview]
Message-ID: <CA+s+GJDUbm7Z9FeQr1otuEPXn0RRq+KL=kS3GJT3j3TeWz_n5Q@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0O1EP8aUn4KLbo3OvzjgVfF8onrMjNnkRAnuWHwbofWBQ@mail.gmail.com>

> The version message helpfully tells me my own IP address but not theirs ;p

Try -logips. Logging peer IPs was disabled by default after #3764.

BTW I'm seeing the same abusive behavior. Who is running these? Why do
the requests need to be so frequent?

Wladimir



  reply	other threads:[~2014-07-30 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30 13:22 [Bitcoin-development] Abusive and broken bitcoin seeders Jeff Garzik
2014-07-30 13:50 ` Wladimir [this message]
2014-07-30 13:57   ` Pieter Wuille
2014-07-30 21:03     ` Neil Fincham
2014-07-31 10:37       ` Mike Hearn
2014-07-31 12:59         ` Jameson Lopp
2014-07-30 22:53 ` Addy Yeow

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='CA+s+GJDUbm7Z9FeQr1otuEPXn0RRq+KL=kS3GJT3j3TeWz_n5Q@mail.gmail.com' \
    --to=laanwj@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=jgarzik@bitpay.com \
    /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