Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

swarm.connect() should override Dial blacklisting #2424

Closed
lidel opened this issue Sep 3, 2019 · 2 comments
Closed

swarm.connect() should override Dial blacklisting #2424

lidel opened this issue Sep 3, 2019 · 2 comments
Assignees
Labels
exp/expert Having worked on the specific codebase is important kind/bug A bug in existing code (including security flaws) kind/wontfix P3 Low: Not priority right now status/ready Ready to be worked topic/libp2p Topic libp2p

Comments

@lidel
Copy link
Member

lidel commented Sep 3, 2019

  • Version: v0.37.1
  • Platform: web, node
  • Subsystem: swarm.connect()

Type: Bug

Severity: Medium

Description:

It is impossible to manually retry connection if PeerID got blacklisted from dialling.
The only way is to wait for blacklisting to expire or stop and start node.

Steps to reproduce the error:

  1. set up go-ipfs somewhere
  2. shut it down (needs to be offline)
  3. call swarm.connect() with mutiaddr of the node that is offline, get expected connection error
  4. start go-ipfs
  5. try to connect to it, call swarm.connect() again
  6. get error:

dial-is-blacklisted-2019-09-03--14-12-59
js-ipfs in Brave with TCP transport enabled (ipfs/ipfs-companion#716)

This feels like a bug.

Expected result

Manual swarm connect should override any automated blacklisting, making it possible to connect as soon as remote node is up, without waiting for blacklisting to expire.

@lidel lidel added the kind/bug A bug in existing code (including security flaws) label Sep 3, 2019
@jacobheun
Copy link
Contributor

May not directly be related, but the resolution should help here, is dialing addresses in libp2p libp2p/js-libp2p#451, instead of peers. I've started working on that and will work on making it so that when libp2p receives an address dial request it clears the deny list for the peer. (Ideally we'll have addresses be denied in the future, instead of peers)

@alanshaw alanshaw added exp/expert Having worked on the specific codebase is important topic/libp2p Topic libp2p P3 Low: Not priority right now status/ready Ready to be worked labels Oct 21, 2019
@SgtPooki SgtPooki self-assigned this May 17, 2023
@SgtPooki SgtPooki moved this to 🥞 Todo in js-ipfs deprecation May 17, 2023
@SgtPooki SgtPooki moved this from 🥞 Todo to 🏃‍♀️ In Progress in js-ipfs deprecation May 25, 2023
@SgtPooki
Copy link
Member

js-ipfs is being deprecated in favor of Helia. You can learn more about this deprecation and read the migration guide.

Please feel to reopen with any comments by 2023-06-02. We will do a final pass on reopened issues afterwards (see #4336).

@github-project-automation github-project-automation bot moved this from 🏃‍♀️ In Progress to ✅ Done in js-ipfs deprecation May 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
exp/expert Having worked on the specific codebase is important kind/bug A bug in existing code (including security flaws) kind/wontfix P3 Low: Not priority right now status/ready Ready to be worked topic/libp2p Topic libp2p
Projects
No open projects
Status: Done
Development

No branches or pull requests

4 participants