Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WH7dj-0002yz-0H for bitcoin-development@lists.sourceforge.net; Sat, 22 Feb 2014 08:08:51 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.44 as permitted sender) client-ip=209.85.214.44; envelope-from=laanwj@gmail.com; helo=mail-bk0-f44.google.com; Received: from mail-bk0-f44.google.com ([209.85.214.44]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WH7di-0000gd-2E for bitcoin-development@lists.sourceforge.net; Sat, 22 Feb 2014 08:08:50 +0000 Received: by mail-bk0-f44.google.com with SMTP id r7so1297317bkg.31 for ; Sat, 22 Feb 2014 00:08:43 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.205.101.5 with SMTP id cy5mr2551727bkc.151.1393056523756; Sat, 22 Feb 2014 00:08:43 -0800 (PST) Received: by 10.205.75.72 with HTTP; Sat, 22 Feb 2014 00:08:43 -0800 (PST) In-Reply-To: References: Date: Sat, 22 Feb 2014 09:08:43 +0100 Message-ID: From: Wladimir To: Ronald Hoffman Content-Type: multipart/alternative; boundary=f46d041c611640579204f2fa3fad X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.0 NORMAL_HTTP_TO_IP URI: Uses a dotted-decimal IP address in URL 0.0 WEIRD_PORT URI: Uses non-standard port number for HTTP 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: 1WH7di-0000gd-2E Cc: Bitcoin Dev Subject: Re: [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 08:08:51 -0000 --f46d041c611640579204f2fa3fad Content-Type: text/plain; charset=UTF-8 On Sat, Feb 22, 2014 at 3:56 AM, Ronald Hoffman wrote: > 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. > This warrants an issue on github: https://github.com/bitcoin/bitcoin/issues/new > Here is bitcoin-cli talking to bitcoind (0.9.0) > > $ bitcoin-cli getpeerinfo > [ > { > "addr" : "127.0.0.1:8333", > "services" : "0000000164x", > What git revision are you testing with? Built with what compiler on which platform? Do all peers in getpeerinfo show up garbled, or just yours? Does it literally show as "164x"? I just tried getpeerinfo locally and all my peers show as: ""services" : "00000001" as expected. Wladimir --f46d041c611640579204f2fa3fad Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On S= at, Feb 22, 2014 at 3:56 AM, Ronald Hoffman <ronald.hoffman6@gma= il.com> wrote:
I noticed that the 'services' fie= ld appears to be garbled in the latest source code level from github. =C2= =A0Bitcoind is connected to my Java node server at 127.0.0.1:8333. =C2=A0I thought I was sendi= ng a bad 'version' message but I get the correct results using 0.8.= 6. =C2=A0So it appears that something changed in 0.9.0.

This warrants an issue on github:=C2=A0https://github.com/b= itcoin/bitcoin/issues/new
=C2=A0
Here is bitcoin-cli talking to bitcoind (0.9.0)

$ bitcoin-cli getpeerinfo
[
=C2= =A0 =C2=A0 {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 "addr" : "= ;127.0.0.1:8333&quo= t;,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 "services" : "0000000164x&q= uot;,

What git revision are you= testing with? Built with what compiler on which platform?

Do all peers in getpeerinfo show up garbled, or just yours? Does i= t literally show as "164x"?

I just tried getpeerinfo locally and all my peers show = as: ""servic= es" : "00000001"=C2=A0as expected.

Wladimir

--f46d041c611640579204f2fa3fad--