Unexpected nodes on blockchain

+1 vote

I set up a 4 node multichain blockchain using VMware. I don't know if I did something different along the line while working with it but recently I used getpeerinfo on one of the nodes and got a response with 6 nodes three of which were the other multichain nodes running on the vmware (as can be seen in the addr field) but the other three entries showed the vmware host system as nodes using the same ipaddr but different ports even though i didn't set up multichain on the vmware host, although i used json-rpc from the host system at some point.

Is there something I am missing?


asked Jan 5, 2017 by Rosevelt

1 Answer

+2 votes

Please take a look at the incoming fields of the getpeerinfo response, and compare to the IP addresses you're seeing. We've seen cases where two nodes connect to each other in both directions, leading to duplicate entries, and that sounds like the case here. There's no harm in this, except the confusing output from the getpeerinfo API, and a very minor efficiency hit. 

Can you please also confirm which version of MultiChain you're currently using?

answered Jan 5, 2017 by MultiChain
Thanks for your response.

I can't find an "incoming" field for the getpeerinfo response. The MultiChain version running is Build 1.0 alpha 24 protocol 10006.
Sorry - I meant "inbound", not "incoming". That distinguishes between connections that were initiated by this node (inbound=false) and those initiated by others (inbound=true).
FYI you may also see this issue resolved in a more recent version.