-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ipfs p2p forward
should accept full multiaddresses as target (not only /ipfs/<peerID>)
#5524
Comments
ipfs p2p forward
should accept full multiaddresses as target (not only ipfs)ipfs p2p forward
should accept full multiaddresses as target (not only /ipfs/<peerID>)
If no one grabs this soon, I'll do that in a spare moment |
Hey @magik6k @Stebalien , can i help you do for this?I am interested in this issue.
Can you explain it to me?Thx a lot.I am confusing about this. And as i known, we can use command |
@kjzz you're right, it already takes a full multiaddress and adds it to the peerstore before forwarding so that should work. What doesn't work is resolving |
Thx for replying @hsanjuan , so you mean that we should support command such as |
@kjzz yes, in principle, but we have some discussion about how painful it is to manually resolve in several places etc. #5535 (comment) maybe hold off a bit, as ideally this should be taken care of directly at libp2p-level. |
Version information:
master
Type:
Feature
Description:
ipfs p2p forward
takes an*/ipfs/<peerID>
multi-address as target.This assumes the given peer is routable.However, sometimes it would be useful to do
ipfs p2p forward <proto> /dnsaddr/mypeer
or. In these case, the command shouldipfs p2p forward <proto> /ip4/1.2.4.5/tcp/23131/ipfs/<peerID>
automatically add the peer addresses to the peerstore so that they can be connected (right now, a manualresolve the addresses.swarm connect
is required in advance).This simplifies connecting to libp2p peers which are not part of the ipfs network or, particularly, the ipfs dht.The text was updated successfully, but these errors were encountered: