Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XCTqE-00026E-LI for bitcoin-development@lists.sourceforge.net; Wed, 30 Jul 2014 13:22:50 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.213.180 as permitted sender) client-ip=209.85.213.180; envelope-from=jgarzik@bitpay.com; helo=mail-ig0-f180.google.com; Received: from mail-ig0-f180.google.com ([209.85.213.180]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XCTqC-0005Z3-MU for bitcoin-development@lists.sourceforge.net; Wed, 30 Jul 2014 13:22:50 +0000 Received: by mail-ig0-f180.google.com with SMTP id l13so2886558iga.13 for ; Wed, 30 Jul 2014 06:22:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc :content-type; bh=jx3bf/4AM7Y9KPsjfjrelf9bxDqxH5N61dd/12bDrLE=; b=JDRJilbDQwxCh7prJErWhTKaIxMm34MLJzZw9Ib9W+3JH+8HzSf2wsxasQXSmwmRgY f8c0lQlUwBCHG0YczD1Oou/Uij07nymmbsWz4JG7AKJt5HxWHHldOH/+LZhyqq3uEdnS JpKtu5rLH9EJv3QK877+1PzqzysWIdLjBlum3TT+tCNCBpIeGIMbEjBxXvu7GfUee9wQ mQf5O0tSysP9lDv3c7YoDKopLOKoERXuRP/I1lhIOTSKh/uMCE5q+mB8xlmgpVHvI0c/ SWlN0n8Q1eYrKMeiQkv8SKbm18rRnheLSv4SWVeewimUdTWYHsTpb5hgdlB3bRHcuv97 aERQ== X-Gm-Message-State: ALoCoQmLoA17KZtfbKTxW77r4J7s0c3FrB0Eko/jTOj6rPvxQcb17WzdPhhSl98bz7ZBbc/zgFEy X-Received: by 10.50.50.198 with SMTP id e6mr53407292igo.1.1406726563343; Wed, 30 Jul 2014 06:22:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.10.78 with HTTP; Wed, 30 Jul 2014 06:22:23 -0700 (PDT) From: Jeff Garzik Date: Wed, 30 Jul 2014 09:22:23 -0400 Message-ID: To: Bitcoin Dev Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1XCTqC-0005Z3-MU Subject: [Bitcoin-development] Abusive and broken bitcoin seeders 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: Wed, 30 Jul 2014 13:22:50 -0000 Seeing this on one of my public nodes: 2014-07-30 13:13:26 receive version message: /getaddr.bitnodes.io:0.1/: version 70001, blocks=313169, us=162.219.2.72:8333, peer=11847 2014-07-30 13:13:33 receive version message: /getaddr.bitnodes.io:0.1/: version 70001, blocks=290000, us=162.219.2.72:8333, peer=11848 2014-07-30 13:14:21 receive version message: /getaddr.bitnodes.io:0.1/: version 70001, blocks=313169, us=162.219.2.72:8333, peer=11849 That is abusive, taking up public slots. There is no reason to connect so rapidly to the same node. Other seeders are also rapidly reconnect'ers, though the time window is slightly more wide: 2014-07-30 13:09:35 receive version message: /bitcoinseeder:0.01/: version 60000, blocks=230000, us=162.219.2.72:8333, peer=11843 2014-07-30 13:12:42 receive version message: /bitcoinseeder:0.01/: version 60000, blocks=230000, us=162.219.2.72:8333, peer=11846 The version message helpfully tells me my own IP address but not theirs ;p -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/