js-libp2p icon indicating copy to clipboard operation
js-libp2p copied to clipboard

Tracking Issue - WebRTC direct in Node.js

Open 2color opened this issue 1 year ago • 2 comments

Background

WebRTC-direct is currently only supported in browsers as mentioned in package.

This is a tracking issue for adding support for WebRTC-direct in Node.js, which would allow browsers to dial Node.js directly (without circuit relay and signalling) without needing for a TLS certificate as in the case of WebSockets.

Dependencies

This require changes to both https://github.com/murat-dogan/node-datachannel and https://github.com/paullouisageneau/libdatachannel to allow SDP Munging.

Related PRs/issues:

### Tasks
- [ ] https://github.com/paullouisageneau/libjuice/pull/243
- [ ] https://github.com/paullouisageneau/libdatachannel/pull/1172
- [ ] https://github.com/paullouisageneau/libdatachannel/pull/1201
- [ ] https://github.com/paullouisageneau/libdatachannel/pull/1204
- [ ] https://github.com/murat-dogan/node-datachannel/pull/257
- [ ] https://github.com/murat-dogan/node-datachannel/pull/256
- [ ] https://github.com/libp2p/go-libp2p/issues/2827

2color avatar Jun 07 '24 11:06 2color

There is good news when all of the above PRs are applied:

image

achingbrain avatar Jun 07 '24 14:06 achingbrain

I am trying to use webRTC in an exclusive node.js environment (no browser nodes). I created issue #2702 and wanted to link to it here, as it might be relevant to this discussion.

christroutner avatar Sep 13 '24 16:09 christroutner

Closed by #2583

achingbrain avatar Feb 12 '25 15:02 achingbrain