-
Notifications
You must be signed in to change notification settings - Fork 534
/webrtc-direct listener breaks Status page #2176
Copy link
Copy link
Closed
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upeffort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekexp/expertHaving worked on the specific codebase is importantHaving worked on the specific codebase is importantkind/bugA bug in existing code (including security flaws)A bug in existing code (including security flaws)
Description
Activity
Metadata
Metadata
Assignees
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upeffort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekexp/expertHaving worked on the specific codebase is importantHaving worked on the specific codebase is importantkind/bugA bug in existing code (including security flaws)A bug in existing code (including security flaws)
Type
Projects
- StatusShow more project fieldsDone
Describe the bug
This is the same problems as #2033 but for
/webrtc-directTo Reproduce
"/ip4/0.0.0.0/udp/4002/webrtc-direct"toAddresses.Swarmipfs config Swarm.Transports.Network.WebRTCDirect --json trueSee Release Notes for more info: https://github.com/ipfs/kubo/blob/master/docs/changelogs/v0.24.md
Expected behavior
Show
/webrtc-direct(spec) listeners returned byipfs.idWhile at it, also make sure
/webrtc(spec) is supported as well (not in kubo yet, but will be added in near future).To avoid a big refactor, a fix similar to
patches/multiaddr+8.1.2.patchfrom #2057 would be sufficient for solving the problem at hand.Add codes for
webrtc-directandwebrtchttps://github.com/multiformats/multiaddr/blob/master/protocols.csv