Status-backend nodes are only able to connect to the bootstrap node (nwaku:v0.37.1-beta), but they don’t discover between them.
If we check bootstrap logs, we observe it logs its own information the same number of times that nodes are connecting to it, and also a Received WakuMetadata request, same as in a working scenario previously described:
# (repeated)
node info topics="waku node" tid=7 file=waku_node.nim:202
# (repeated per status-backend peer id)
Received WakuMetadata request topics="waku metadata" tid=7 file=protocol.nim:86 remoteClusterId=some(16) remoteShards="[128, 32, 64, 256]" localClusterId=16 localShards=[] peer=16U*nno7Dn
If we check status-backend logs, we observe:
DEBUG GethStatusBackend.StatusNode.protocol waku/nwaku.go:925 peer stats {"peersCount": 1, "stats": {"isOnline":true,"peers":{"16Uiu2HAmSZ8ZEY5uMM7vUhDgKot2Pdne78vwJo8HS3ztaVLu2BW7":{"protocols":["/ipfs/id/1.0.0","/libp2p/autonat/1.0.0","/libp2p/circuit/relay/0.2.0/hop","/vac/waku/metadata/1.0.0","/ipfs/ping/1.0.0","/vac/waku/filter-push/2.0.0-beta1","/vac/waku/peer-exchange/2.0.0-alpha1"],"addresses":["/ip4/10.42.154.73/tcp/60000","/ip4/10.42.154.73/tcp/60000"]}}}}
WARN GethStatusBackend.StatusNode.protocol waku/nwaku.go:333 invalid peer multiaddress {"ma": "enr:-LO4QNFwHd2PE8neUssL8k0lKlR0J0icDBgIV3cat1wq1iugBGd9n02mmL9hKvtxOrHQcwEf2-t1Zo3d7f9hQFce0yACgmlkgnY0gmlwhAoqmkmKbXVsdGlhZGRyc4oACAQKKppJBupggnJzhwAQAgAgAECJc2VjcDI1NmsxoQPOg2kc2hkiqHuqnK_nHC3uTCu-4sQWsbRaTu3qJKucyIN0Y3CC6mCDdWRwgiMohXdha3UyAA", "error": "failed to parse multiaddr \"enr:-LO4QNFwHd2PE8neUssL8k0lKlR0J0icDBgIV3cat1wq1iugBGd9n02mmL9hKvtxOrHQcwEf2-t1Zo3d7f9hQFce0yACgmlkgnY0gmlwhAoqmkmKbXVsdGlhZGRyc4oACAQKKppJBupggnJzhwAQAgAgAECJc2VjcDI1NmsxoQPOg2kc2hkiqHuqnK_nHC3uTCu-4sQWsbRaTu3qJKucyIN0Y3CC6mCDdWRwgiMohXdha3UyAA\": must begin with /"}
WARN GethStatusBackend.StatusNode.protocol waku/nwaku.go:1372 could not write on connection changed channel
<aside> 💡
Bootstrap peer id: 16Uiu2HAmSZ8ZEY5uMM7vUhDgKot2Pdne78vwJo8HS3ztaVLu2BW7
Bootstrap ip: 10.42.154.73
This node peer id: 16Uiu2HAm6uZH4sLV1PSM9oHvptZn8tffkibuZf9ZMdGKQdgZ1pwu
This node ip: 10.42.120.183
</aside>
If we check nWaku bootstrap logs, we observe:
INF Dialing multiple peers topics="waku node peer_manager" tid=98 file=peer_manager.nim:352 numOfPeers=1 nodes=@[16Uiu2HAmSZ8ZEY5uMM7vUhDgKot2Pdne78vwJo8HS3ztaVLu2BW7]
DBG Dialing peer topics="libp2p dialer" tid=98 file=dialer.nim:147 peerId=16U*Lu2BW7 addrs="[/ip4/10.42.154.73/tcp/60000]"
DBG Expanded address and hostname topics="libp2p dialer" tid=98 file=dialer.nim:162 expandedAddress=/ip4/10.42.154.73/tcp/60000 hostname=10.42.154.73 resolvedAddresses="[/ip4/10.42.154.73/tcp/60000]"
DBG Dial successful topics="libp2p dialer" tid=98 file=dialer.nim:98 peerId=16U*Lu2BW7
DBG starting sendNonPriorityTask topics="libp2p pubsubpeer" tid=98 file=pubsubpeer.nim:587 p=16U*Lu2BW7
DBG created new pubsub peer topics="libp2p pubsub" tid=98 file=pubsub.nim:415 peerId=16U*Lu2BW7
DBG identify: info sent topics="libp2p identify" tid=98 file=identify.nim:155 conn=16U*Lu2BW7:696b94993eecf4e49ce1371f info="(peerId: 16Uiu2HAm6uZH4sLV1PSM9oHvptZn8tffkibuZf9ZMdGKQdgZ1pwu, listenAddrs: [/ip4/0.0.0.0/tcp/44123], addrs: [/ip4/10.42.120.183/tcp/44123], protocols: [/ipfs/id/1.0.0, /libp2p/autonat/1.0.0, /libp2p/circuit/relay/0.2.0/hop, /vac/waku/metadata/1.0.0, /vac/waku/relay/2.0.0, /vac/waku/rendezvous/1.0.0, /ipfs/ping/1.0.0, /vac/waku/lightpush/3.0.0, /vac/waku/lightpush/2.0.0-beta1, /vac/waku/filter-subscribe/2.0.0-beta1, /vac/waku/filter-push/2.0.0-beta1, /vac/waku/peer-exchange/2.0.0-alpha1], protoVersion: ipfs/0.1.0, agentVersion: nwaku-v0.37-with-ffi)"
DBG identify: info received topics="libp2p identify" tid=98 file=identify.nim:184 conn=16U*Lu2BW7:696b94993eecf4e49ce1371d pubkey=some(s...0f73)) addresses=/ip4/10.42.154.73/tcp/60000 protocols=/ipfs/id/1.0.0,/libp2p/autonat/1.0.0,/libp2p/circuit/relay/0.2.0/hop,/vac/waku/metadata/1.0.0,/ipfs/ping/1.0.0,/vac/waku/filter-push/2.0.0-beta1,/vac/waku/peer-exchange/2.0.0-alpha1 observable_address=some(/ip4/10.42.120.183/tcp/48812) proto_version=ipfs/0.1.0 agent_version=nwaku-v0.37.1-beta signedPeerRecord=None
INF Received WakuMetadata request topics="waku metadata" tid=98 file=protocol.nim:86 remoteClusterId=some(16) remoteShards=[] localClusterId=16 localShards="[128, 32, 64, 256]" peer=16U*Lu2BW7
INF Finished dialing multiple peers topics="waku node peer_manager" tid=98 file=peer_manager.nim:379 successfulConns=1 attempted=1
DBG Could not establish send connection topics="libp2p pubsubpeer" tid=98 file=pubsubpeer.nim:331 description="failed dial existing: Unable to select sub-protocol. Selected: . Available: @[\"/vac/waku/relay/2.0.0\", \"/meshsub/1.2.0\", \"/meshsub/1.1.0\", \"/meshsub/1.0.0\", \"/meshsub/1.2.0\", \"/meshsub/1.1.0\", \"/meshsub/1.0.0\"]"
Basically, we can check that the connection between the node and the bootstrap node is made, but apparently fails because it can not select sub-protocols, since the selected list looks empty in the last log line, highlighted in red:
DBG Could not establish send connection topics="libp2p pubsubpeer" tid=98 file=pubsubpeer.nim:331
"failed dial existing: Unable to select sub-protocol. Selected: . <--- EMPTY
Available: @[\"/vac/waku/relay/2.0.0\", \"/meshsub/1.2.0\", \"/meshsub/1.1.0\", \"/meshsub/1.0.0\", \"/meshsub/1.2.0\", \"/meshsub/1.1.0\", \"/meshsub/1.0.0\"]"
Connection looks like is rejected, and nodes cannot discover between them.