NodeJS-LibP2P: Listening on WebRTC-Direct MultiAddr #2038
Replies: 1 comment
-
As mentioned here there is currently a draft PR to add this, but the underlying library would need to add an option to disable config validation first |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Previously asked on the LibP2P forums: https://us06web.zoom.us/j/8280739255?pwd=d3RzRXUrakhiUHFTS2J0VHB3TU4rUT09
Hello,
I’ve spent a few days, off and on trying to figure out why I can’t seem to get my node.js-libp2p node to advertise a webrtc-direct listening multiaddr. Recently had a discussion over in the IPFS discord with another new dev who pointed me to this pull request.
At the top, the pull request's OP states that “Listening private-to-public” is not supported, and I’m just kinda wondering why that might be? Is there something technically limiting about node.js that prevents this?
Beta Was this translation helpful? Give feedback.
All reactions