-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
ipfs p2p listen and foward should show actual port when listening on 0 #5523
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
Comments
I think we should use: func (l *localListener) ListenAddress() ma.Multiaddr {
return l.listener.Multiaddr()
} |
We could also just set |
@Stebalien Should |
I agree. We should prevent that. |
License: MIT Signed-off-by: Overbool <[email protected]>
License: MIT Signed-off-by: Overbool <[email protected]>
Ah yes, for |
License: MIT Signed-off-by: Overbool <[email protected]>
Also, launching two |
License: MIT Signed-off-by: Overbool <[email protected]>
License: MIT Signed-off-by: Overbool <[email protected]>
;wq Signed-off-by: Overbool <[email protected]> License: MIT Signed-off-by: Overbool <[email protected]>
License: MIT Signed-off-by: Overbool <[email protected]>
;wq Signed-off-by: Overbool <[email protected]> License: MIT Signed-off-by: Overbool <[email protected]>
Version information:
master
Type:
Enhancement
Description:
ipfs p2p forward
andipfs p2p listen
commands take a listen-address or a target address. It works with/ip4/127.0.0.1/tcp/0
butipfs p2p ls
does still show 0 instead of the actual port it bound to (which should be a random available one). This can only be discovered withlsof
or similar (I think).Ideally,
p2p ls
should list the bind-address with the actual port.The text was updated successfully, but these errors were encountered: