Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1R0r2v-0006zr-2O for bitcoin-development@lists.sourceforge.net; Tue, 06 Sep 2011 08:30:17 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.83.47 as permitted sender) client-ip=74.125.83.47; envelope-from=shadders.del@gmail.com; helo=mail-gw0-f47.google.com; Received: from mail-gw0-f47.google.com ([74.125.83.47]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1R0r2r-0003lF-6H for bitcoin-development@lists.sourceforge.net; Tue, 06 Sep 2011 08:30:17 +0000 Received: by gwb11 with SMTP id 11so3790467gwb.34 for ; Tue, 06 Sep 2011 01:30:07 -0700 (PDT) Received: by 10.150.2.6 with SMTP id 6mr3661856ybb.266.1315297806371; Tue, 06 Sep 2011 01:30:06 -0700 (PDT) Received: from [10.1.1.50] (155.88-67-202.dynamic.dsl.syd.iprimus.net.au [202.67.88.155]) by mx.google.com with ESMTPS id o3sm394675ybk.21.2011.09.06.01.30.03 (version=SSLv3 cipher=OTHER); Tue, 06 Sep 2011 01:30:05 -0700 (PDT) Message-ID: <4E65DA06.9060403@gmail.com> Date: Tue, 06 Sep 2011 18:29:58 +1000 From: Steve User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.21) Gecko/20110831 Thunderbird/3.1.13 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <4E65CEE6.7030002@gmail.com> In-Reply-To: <4E65CEE6.7030002@gmail.com> Content-Type: multipart/alternative; boundary="------------050305000509000308060609" X-Spam-Score: -1.1 (-) 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (shadders.del[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -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 0.0 T_TO_NO_BRKTS_FREEMAIL To: misformatted and free email service -0.5 AWL AWL: From: address is in the auto white-list X-Headers-End: 1R0r2r-0003lF-6H Subject: Re: [Bitcoin-development] Building a node crawler to map network X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list Reply-To: shadders.del@gmail.com List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Sep 2011 08:30:17 -0000 This is a multi-part message in MIME format. --------------050305000509000308060609 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit > > While I'm asking questions I'll add one more regarding the getaddr > message. Talking to myself here. I just sent this message then found this brilliant set of articles in the Dev & Tech forum which answers the question very nicely: *https://bitcointalk.org/index.php?topic=41722.0 * Anyway just as an FYI I've been running v0.0.0.0.0.0.0.0.1 for about an hour. It's only running 10 concurrent connections due to girlfriend complaining she couldn't watch youtube but here's some early results. New nodes: 19319 // node address discovered but no contact attempt made yet Contacted nodes: 754 Uncontactable nodes: 3253 Limbo nodes: 9 //not as exciting as it sounds, just nodes with connect in progress Total nodes: 23335 // about 5000 from initial IRC discover, the rest are from getaddr Versions: { 300=1, 31900=7, 31902=1, 32000=2, 32001=7, 32002=22, 32100=100, 32200=24, 32300=277, 32400=317, 32500=2} Fails: { ConnectException: Connection refused=377, IOException: Socket is disconnected=87, SocketException: Network is unreachable=2, ProtocolException: Error deserializing message =1, NoRouteToHostException: No route to host=115, SocketException: Connection reset=149, SocketTimeoutException: connect timed out=2521} --------------050305000509000308060609 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

While I'm asking questions I'll add one more regarding the getaddr message.

Talking to myself here.  I just sent this message then found this brilliant set of articles in the Dev & Tech forum which answers the question very nicely: https://bitcointalk.org/index.php?topic=41722.0

Anyway just as an FYI I've been running v0.0.0.0.0.0.0.0.1 for about an hour.  It's only running 10 concurrent connections due to girlfriend complaining she couldn't watch youtube but here's some early results.

New nodes: 19319 // node address discovered but no contact attempt made yet
Contacted nodes: 754
Uncontactable nodes: 3253
Limbo nodes: 9 //not as exciting as it sounds, just nodes with connect in progress
Total nodes: 23335 // about 5000 from initial IRC discover, the rest are from getaddr

Versions: {
300=1,
31900=7,
31902=1,
32000=2,
32001=7,
32002=22,
32100=100,
32200=24,
32300=277,
32400=317,
32500=2}

Fails: {
ConnectException: Connection refused=377,
IOException: Socket is disconnected=87,
SocketException: Network is unreachable=2,
ProtocolException: Error deserializing message =1,
NoRouteToHostException: No route to host=115,
SocketException: Connection reset=149,
SocketTimeoutException: connect timed out=2521}


--------------050305000509000308060609--