Skip to content

Concurrent dials to the same peer with duplicated multiaddrs #3209

Closed

Description

@stormshield-pj50

Summary

Useless concurrent dials when a peer is found with two identical multiaddrs in the DHT: one with a peerid, and the other without a peerid.

Expected behaviour

When dialing a peer, identical multiaddrs (that only differ with the presence of the peerid) should be filtered out in order to prevent useless concurrent dials to the same peer.

Actual behaviour

Two identical mutliaddrs filled by the DHT:

/ip4/10.10.0.1/tcp/80
and
/ip4/10.10.0.1/tcp/80/QmXXXXXXXX

are concurrently dialed twice.

Possible Solution

Maybe check uniqueness of multiaddrs without peerid

Version

  • libp2p version (version number, commit, or branch): 0.49

Would you like to work on fixing this bug?

No

Activity

  1. thomaseizinger commented on Dec 8, 2022

    @thomaseizinger
    Contributor

    Thanks for the report! I agree that it makes sense to do some better filtering here.

  2. linked a pull request that will close this issuerefactor(swarm): express dial logic linearly #3253on Dec 22, 2022
  3. thomaseizinger commented on Dec 22, 2022

    @thomaseizinger
    Contributor

    Needs a test before we can consider this closed.

  4. thomaseizinger commented on Sep 20, 2023

    @thomaseizinger
    Contributor

    @stormshield-pj50 Does this still occur?

  5. stormshield-pj50 commented on Sep 20, 2023

    @stormshield-pj50
    ContributorAuthor

    @stormshield-pj50 Does this still occur?

    Not any more, that's fixed. You can close the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions