[Ethereum] Parity: How to view connected Peers alternative to ‘admin’ keyword

parity

As we know we cannot use admin, which works on geth, on Parity.

For example I want to retrieve information such as enode-id, ip-address, used port of each connected peer.

parity_netPeers (https://github.com/paritytech/parity/wiki/JSONRPC-parity-module#parity_netpeers) returns some information without newline, it become difficult see detect the peers connected.

curl --data '{"method":"parity_netPeers","params":[],"id":1,"jsonrpc":"2.0"}' -H "Content-Type: application/json" -X POST localhost:8545

Example:

Here there is actually 2 connected peers but it returns many more information.

{"jsonrpc":"2.0","result":{"active":2,"connected":2,"max":25,"peers":[{"caps":[],"id":"575bbc154d3c37c35d5f91a42813641fef4389bc288c0e50cf2ab1cbbde014287b93d3748336ff02c99a11e7d58ab54868933c7a9804c36a071078cb9a586ca8","name":"","network":{"localAddress":"77.23.7.15:39741","remoteAddress":"Handshake"},"protocols":{"eth":null,"les":null}},{"caps":["eth/63","eth/62"],"id":"4d331051d8fb471c87a9351b36ffb72bf445a9337727d229e03c668f99897264bf11e1b897b1561f5889825e2211b06858139fa469fdf73c64d43a567ea72479","name":"Geth/v1.5.9-stable-a07539fb/linux/go1.7.1","network":{"localAddress":"77.13.17.145:35507","remoteAddress":"13.40.17.95:3000"},"protocols":{"eth":{"difficulty":null,"head":"3060e08b5cd0b90adb3c464342f6df13482361e8ef09724d7525cae48abbaf59","version":63},"les":null}},{"caps":[],"id":"13d6cc66f445072d2e389c5d47d1557543ec9f96237576a38072a5b76b67ba445050641219e1f42c1443a7287fab6cb3f4c078fa886520cbf3577ac23f5e0cad","name":"","network":{"localAddress":"77.13.17.15:44079","remoteAddress":"Handshake"},"protocols":{"eth":null,"les":null}},{"caps":[],"id":null,"name":"","network":{"lo
…`

Best Answer

Install JQ, a command-line JSON processor. It's like sed for JSON.

Run this

curl -s --data '{"method":"parity_netPeers","params":[],"id":1,"jsonrpc":"2.0"}' \
-H "Content-Type: application/json" -X POST localhost:8545 \
| jq '.result.peers[] | .id, .network'

Add the name of the key preceded by a comma after .network and before the single quote to add anything else to the output.

Related Solutions

[Ethereum] Adding private network peers to Parity

Not sure if I get your question correctly. Assuming you have a private network running with 5 clients on network ID 13337 and myGenesis.json chain configuration.

enode://0000..0001@192.168.178.101:36541
enode://0000..0002@192.168.178.102:36542
enode://0000..0003@192.168.178.103:36543
enode://0000..0004@192.168.178.104:36544
enode://0000..0005@192.168.178.105:36545

Add these nodes to a file, let's say myPrivateNetwork.txt, one entry per line:

enode://0000..0001@192.168.178.101:36541
enode://0000..0002@192.168.178.102:36542
enode://0000..0003@192.168.178.103:36543
enode://0000..0004@192.168.178.104:36544
enode://0000..0005@192.168.178.105:36545

And subsequently, run Parity with --chain myGenesis.json --network-id 13337 --reserved-peers myPrivateNetwork.txt --reserved-only. Or add it to the config file:

[parity]
chain = "myGenesis.json"

[network]
id = 13337
reserved_only = true
reserved_peers = "./myPrivateNetwork.txt"

This will establish a private network containing only your nodes:

--reserved-peers FILE        Provide a file containing enodes, one per line.
                             These nodes will always have a reserved slot on top
                             of the normal maximum peers. (default: None)
--reserved-only              Connect only to reserved nodes. (default: false)

Adding reserved peers also works from the Web3 console by issuing:

api.parity.addReservedPeer('enode://0000..0007@192.168.178.107:36547')

Note, that you have to enable the parity json rpc api.

You can also run a private development chain with parity --chain dev.

[Ethereum] “Active” vs. “Connected” Peers

Active versus connected is just a terminology question: Active means, they are actively synchronizing the chain, a 0 basically means you are already fully synchronized (or have no peers at all). Connected are all peers which you are listing to for new blocks and transactions, ideally this should be not 0.

You say, you have two nodes with 0/1/25 and one with 0/2/25, so your (virtual) peer-to-peer network looks like this:

[0/1/25] --- [0/2/25] --- [0/1/25]

So you have one node connected to the other two nodes, while they are not connected to a ring. Try to add all three enode addresses to a reserved peers file and pass this to all of your nodes:

--reserved-peers FILE          Provide a file containing enodes, one per line.
                               These nodes will always have a reserved slot on top
                               of the normal maximum peers. (default: None)

Best Answer

Related Solutions

[Ethereum] Adding private network peers to Parity

[Ethereum] “Active” vs. “Connected” Peers

Related Topic