Skip to content
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

Multiple Connections over a single port #584

Closed
keverw opened this issue Dec 10, 2019 · 1 comment
Closed

Multiple Connections over a single port #584

keverw opened this issue Dec 10, 2019 · 1 comment

Comments

@keverw
Copy link

keverw commented Dec 10, 2019

I'm doing research for a project and figured webrtc between server to server would be an interesting use case, or client to server mixing the audio of multiple users into a single connection per client. However running it in a system where you only wanted to open up a few ports, for example kubernetes instead of all 60,000+ ports.

There's a project in Go discussing this too pion/webrtc#639

Then in the past this was mentioned for this project too, but looked like settled on defining a range of port, not just running multiple connections over a single port. #354

Seems like the other idea for a workaround could be running a TURN server though, but seems to defeat the idea of servers going point to point... and then you could mix and match, some services could run outside of the firewall while some run outside of the firewall but still be able to connect.

@markandrus
Copy link
Member

Hi @keverw, probably this is more feasible in a project like pion/webrtc or rawrtc/rawrtc. node-webrtc is just bindings over the webrtc.org implementation. Anything not implemented there won't be implemented here. You could check the webrtc.org bug tracker for feature requests, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants