Multiaddrs with peer ID are not considered dialable #2001
Labels
effort/hours
Estimated to take one or several hours
exp/beginner
Can be confidently tackled by newcomers
good first issue
Good issue for new contributors
A multiaddr can optionally contain the peer ID, i.e.
../p2p/<peer-ID>
. When such multiaddrs are added to the libp2p host peerstore, they are not considered to be dialable, and filtered onhost.Connect
resulting inno good addresses
error.For example, the following test fails with error
no good addresses
:While this one succeeds:
The only difference being that the multiaddr added to peerstore in the first test contained peer ID.
In the specific case above, looks like the address is being filtered by
CanDial
ofTcpTransport
which uses this matcher.Is this behaviour expected and or documented? Otherwise, it seems surprising that a valid multiaddr being successfully added to the peerstore and yet no good address are found on connection.
The text was updated successfully, but these errors were encountered: