Different chain networks should not route each other's p2p node information to each other.

[gguoss]

2019-03-04 15:23:44.419 INFO Banned PeerId(QmdU82FC39tj6YUFsie2cC3LLjqWEqA6C7N5piWb8XTjWX) (#5, Dialer { address: "/ip4/47.96.97.52/tcp/31127" }, None).

There are some different p2p information in network/node.json.

[bkchr]

CC @tomaka

[tomaka]

Right now the network is differentiated based on the protocol_id in the chain spec:

substrate/core/service/src/chain_spec.rs

Line 92 in f429a0c

pub protocol_id: Option<String>,

Unfortunately, if you don't specify this value, it will default to sub. All the chains that use sub will conflict with each other and get these "banned peer" messages.

Later I'd like to try switch to a different discovery mechanism that allows knowing which chain a node belongs to when discovering it.
cc libp2p/rust-libp2p#942

[tomaka]

Progress report: #5045 is the first step towards fixing this.
We need a transition period during which nodes support both the old Kademlia and the one-DHT-per-chain. Then later we can finish this by removing the old Kademlia.

[tomaka]

#5993 removed the old Kademlia.
The last step is #5825

[tomaka]

Fixed in #6549