bug: cannot reach my node running in my shard

[plopezlpz]

Problem

I run a nwaku node in the following shards: 32, 64, 128, 256 and 101.

This node connects to the fleet nodes fine. Shard 101 is not known by any other node in the fleet.

I run status-desktop with no changes, it connects fine to nodes in the fleet. I create a community to be in shard 101 and I don't see any connection to the nwaku node on 101.

My assumption is that my status-desktop would discover that nwaku node in shard 101 indirectly through other nodes connected to to that node.

Expected behavior

My assumption is that my status-desktop would discover that nwaku node in shard 101 indirectly through other nodes connected to to that node. Maybe this assumption is wrong.
I can make this work just updating the bootstrapt node to my status-desktop app

[plopezlpz]

@chaitanyaprem FYI

[plopezlpz]

This is the log of my nwaku node
my.log

[gabrielmer]

If I understand correctly, status-desktop is connected to a node that doesn't support shard 101 and when trying to send a message in that shard it just rejects it instead of helping it find a node that does support shard 101. If that's the case, it seems to me that it's fine. But I might be missing something.

[plopezlpz]

@gabrielmer yes, that's the case, I was unsure if that was fine or a bug.

[gabrielmer]

I think it's fine but let's see what @chaitanyaprem says just to make sure :)

[plopezlpz]

also this is the config of my nwaku node:

log-level = "DEBUG"
relay = true
filter = true
store = true
lightpush = true
keep-alive = true
max-connections = 150
peer-exchange = true
pubsub-topic = ["/waku/2/rs/16/32","/waku/2/rs/16/64", "/waku/2/rs/16/101", "/waku/2/rs/16/128", "/waku/2/rs/16/256"]
metrics-logging = false
cluster-id = 16
discv5-discovery = true
discv5-udp-port = 9000
discv5-bootstrap-node = ["enr:-QEOuEAuAK49evunDoidpHqcmeVqZz73wt4jwHnHJlmCVBFj6EdIbZ9uH5BnCYKOEPJTns2QJKUR2XLtWyzIspPAfJF9AYJpZIJ2NIJpcISnYxMvim11bHRpYWRkcnO4YAAtNihib290LTAxLmRvLWFtczMuc2hhcmRzLnRlc3Quc3RhdHVzaW0ubmV0BnZfAC82KGJvb3QtMDEuZG8tYW1zMy5zaGFyZHMudGVzdC5zdGF0dXNpbS5uZXQGAbveA4Jyc4sAEAQAIABAAIABAIlzZWNwMjU2azGhAt60bRUEoHNuLlnsM12sU2PIQwBwfLIJ8a_ZPEY2-Rnkg3RjcIJ2X4N1ZHCCIyiFd2FrdTIN"]
discv5-enr-auto-update = true
rest = true
rest-admin = true
rest-port = 8645

[chaitanyaprem]

If I understand correctly, status-desktop is connected to a node that doesn't support shard 101 and when trying to send a message in that shard it just rejects it instead of helping it find a node that does support shard 101. If that's the case, it seems to me that it's fine. But I might be missing something.

This is not about node connections at libp2p level. This has to do more with discoveryv5 where-in status-desktop should have received the node with shard 101 from the bootstrap node.