bug/regression: filter subscribe on a pubsubtopic from a different cluster id freezes

[fbarbu15]

Not sure if this is a real use case but it:

• worked in the past for the same config (started failing last night)
• works if both nodes are nwaku
• works if both nodes are go-waku

In the logs I see 2024-03-14T12:28:55.190Z �[35mDEBUG�[0m basichost basic/basic_host.go:341 failed to fetch local IPv6 address {"node": "16Uiu2HAm9g4A7CTaxjNPW6is3NvtjBZph8kkpckKv6gfWb8JJaV4", "error": "no route found for ::"} when the issue reproduces

To Reproduce

docker run -i -t -p 45114:45114 -p 45115:45115 -p 45116:45116 -p 45117:45117 -p 45118:45118 harbor.status.im/wakuorg/nwaku:latest --listen-address=0.0.0.0 --rest=true --rest-admin=true --websocket-support=true --log-level=TRACE --rest-relay-cache-capacity=100 --websocket-port=45116 --rest-port=45114 --tcp-port=45115 --discv5-udp-port=45117 --rest-address=0.0.0.0 --nat=extip:172.18.170.168 --peer-exchange=true --discv5-discovery=true --cluster-id=0 --metrics-server=true --metrics-server-address=0.0.0.0 --metrics-server-port=45118 --metrics-logging=true --relay=true --filter=true --nodekey=30348dd51465150e04a5d9d932c72864c8967f806cce60b5d26afeca1e77eb68

docker network connect --ip 172.18.170.168 waku 364e39ef054bf668756192fdfb1338174f3aaa4f42196f2299ac240393eed9ce

docker run -i -t -p 34903:34903 -p 34904:34904 -p 34905:34905 -p 34906:34906 -p 34907:34907 harbor.status.im/wakuorg/go-waku:latest --listen-address=0.0.0.0 --rest=true --rest-admin=true --websocket-support=true --log-level=DEBUG --rest-relay-cache-capacity=100 --websocket-port=34905 --rest-port=34903 --tcp-port=34904 --discv5-udp-port=34906 --rest-address=0.0.0.0 --nat=extip:172.18.170.19 --peer-exchange=true --discv5-discovery=true --cluster-id=0 --min-relay-peers-to-publish=1 --rest-filter-cache-capacity=50 --relay=false --discv5-bootstrap-node=enr:-LO4QDzCALDTPwhj7gayHA1egQQc2qEFh_a4EwIy5k5w0E1oYpmeghm5xOeze8QSp8kh8LlOjgkd6CXU502LkcQMLWoBgmlkgnY0gmlwhKwSqqiKbXVsdGlhZGRyc4wACgSsEqqoBrA83QOCcnOFAAABAACJc2VjcDI1NmsxoQM3Tqpf5eFn4Jztm4gB0Y0JVSJyxyZsW8QR-QU5DZb-PYN0Y3CCsDuDdWRwgrA9hXdha3UyBQ --filternode=/ip4/172.18.170.168/tcp/45115/p2p/16Uiu2HAmGNtM2rQ8abySFNhqPDFY4cmfAEpfo9Z9fD3NekoFR2ip

docker network connect --ip 172.18.170.19 waku dae5673c80b265ce5dfc9490762987c7f674a7c4a041769b6b48d5b7357dd9d0

curl -v -X POST "http://127.0.0.1:45114/relay/v1/subscriptions" -H "Content-Type: application/json" -d '["/waku/2/rs/2/2"]'

Response status code: 200. Response content: b'OK'

curl -v -X POST "http://127.0.0.1:34903/filter/v2/subscriptions" -H "Content-Type: application/json" -d '{"requestId": "23549488-e331-41f1-8351-3bf684a4cc26", "contentFilters": ["/test/1/waku-filter/proto"], "pubsubTopic": "/waku/2/rs/2/2"}'

Just freezes here until the client times out

Expected behavior
I would expect either to work or a valid error.
docker_logs.zip

Added logs also when both nodes are go-waku and the test passes
docker_logs_when_both_nodes_are_gowaku_and_test_passes.zip