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-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WH2lF-0007cO-Qm for bitcoin-development@lists.sourceforge.net; Sat, 22 Feb 2014 02:56:17 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.177 as permitted sender) client-ip=74.125.82.177; envelope-from=ronald.hoffman6@gmail.com; helo=mail-we0-f177.google.com; Received: from mail-we0-f177.google.com ([74.125.82.177]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WH2lE-0005sN-O4 for bitcoin-development@lists.sourceforge.net; Sat, 22 Feb 2014 02:56:17 +0000 Received: by mail-we0-f177.google.com with SMTP id t61so3059987wes.22 for ; Fri, 21 Feb 2014 18:56:10 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.13.5 with SMTP id d5mr5598872wic.54.1393037770435; Fri, 21 Feb 2014 18:56:10 -0800 (PST) Received: by 10.227.60.4 with HTTP; Fri, 21 Feb 2014 18:56:10 -0800 (PST) Date: Fri, 21 Feb 2014 21:56:10 -0500 Message-ID: From: Ronald Hoffman To: bitcoin-development@lists.sourceforge.net Content-Type: multipart/alternative; boundary=001a11c23fba77319804f2f5e19e X-Spam-Score: -0.3 (/) 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 (ronald.hoffman6[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit (ronald.hoffman6[at]gmail.com) 0.0 WEIRD_PORT URI: Uses non-standard port number for HTTP 0.0 NORMAL_HTTP_TO_IP URI: Uses a dotted-decimal IP address in URL 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 X-Headers-End: 1WH2lE-0005sN-O4 Subject: [Bitcoin-development] getpeerinfo results 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: Sat, 22 Feb 2014 02:56:18 -0000 --001a11c23fba77319804f2f5e19e Content-Type: text/plain; charset=ISO-8859-1 I noticed that the 'services' field appears to be garbled in the latest source code level from github. Bitcoind is connected to my Java node server at 127.0.0.1:8333. I thought I was sending a bad 'version' message but I get the correct results using 0.8.6. So it appears that something changed in 0.9.0. Here is bitcoin-cli talking to bitcoind (0.9.0) $ bitcoin-cli getpeerinfo [ { "addr" : "127.0.0.1:8333", "services" : "0000000164x", "lastsend" : 1393036635, "lastrecv" : 1393036635, "bytessent" : 100169, "bytesrecv" : 53633565, "conntime" : 1393036133, "pingtime" : 0.00000000, "version" : 70002, "subver" : "/JavaBitcoin:1.0/", "inbound" : false, "startingheight" : 287125, "banscore" : 0, "syncnode" : true } ] Here is the same bitcoin-cli talking to bidcoind (0.8.6) $ bitcoin-cli getpeerinfo [ { "addr" : "127.0.0.1:8333", "services" : "00000001", "lastsend" : 1393037165, "lastrecv" : 1393037165, "bytessent" : 77494, "bytesrecv" : 13054, "conntime" : 1393037135, "version" : 70002, "subver" : "/JavaBitcoin:1.0/", "inbound" : false, "startingheight" : 287126, "banscore" : 0, "syncnode" : true } ] Ron --001a11c23fba77319804f2f5e19e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I noticed that the 'services' field appears to be = garbled in the latest source code level from github. =A0Bitcoind is connect= ed to my Java node server at 127.0.0.1:83= 33. =A0I thought I was sending a bad 'version' message but I ge= t the correct results using 0.8.6. =A0So it appears that something changed = in 0.9.0.

Here is bitcoin-cli talking to bitcoind (0.9.0)
$ bitcoin-cli getpeerinfo
[
=A0 =A0 {
=A0 =A0 =A0 =A0 "addr" : "127.0.0.1:8333",
=A0 =A0 =A0 =A0 "services" : "0000000164x",
<= div>=A0 =A0 =A0 =A0 "lastsend" : 1393036635,
=A0 =A0 = =A0 =A0 "lastrecv" : 1393036635,
=A0 =A0 =A0 =A0 "= bytessent" : 100169,
=A0 =A0 =A0 =A0 "bytesrecv" : 53633565,
=A0 =A0 = =A0 =A0 "conntime" : 1393036133,
=A0 =A0 =A0 =A0 "= pingtime" : 0.00000000,
=A0 =A0 =A0 =A0 "version" = : 70002,
=A0 =A0 =A0 =A0 "subver" : "/JavaBitcoin:= 1.0/",
=A0 =A0 =A0 =A0 "inbound" : false,
=A0 =A0 =A0 =A0= "startingheight" : 287125,
=A0 =A0 =A0 =A0 "bansc= ore" : 0,
=A0 =A0 =A0 =A0 "syncnode" : true
<= div>=A0 =A0 }
]

Here is the same bitcoin-cli talking to bidcoind (0.8.6)

$ bitcoin-cli getpeerinfo
[
= =A0 =A0 {
=A0 =A0 =A0 =A0 "addr" : "127.0.0.1:8333",
=A0 =A0 =A0 =A0 "services" : "00000001",
=A0 =A0 =A0 =A0 "lastsend" : 1393037165,
=A0 =A0 =A0 = =A0 "lastrecv" : 1393037165,
=A0 =A0 =A0 =A0 "byte= ssent" : 77494,
=A0 =A0 =A0 =A0 "bytesrecv" : 13054,
=A0 =A0 =A0 =A0 &q= uot;conntime" : 1393037135,
=A0 =A0 =A0 =A0 "version&qu= ot; : 70002,
=A0 =A0 =A0 =A0 "subver" : "/JavaBitc= oin:1.0/",
=A0 =A0 =A0 =A0 "inbound" : false,
=A0 =A0 =A0 =A0 "startingheight" : 287126,
=A0 =A0= =A0 =A0 "banscore" : 0,
=A0 =A0 =A0 =A0 "syncnode= " : true
=A0 =A0 }
]

Ron
--001a11c23fba77319804f2f5e19e--