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

STUN Implementation #272

Open
Scraft opened this issue Jul 11, 2019 · 0 comments
Open

STUN Implementation #272

Scraft opened this issue Jul 11, 2019 · 0 comments

Comments

@Scraft
Copy link

Scraft commented Jul 11, 2019

I am looking for the smallest client-side library for establishing a STUN connection between two peers. I already have a messaging server, and already have a TURN style fallback for when STUN cannot be established. However, it isn't clear to me whether libsourcey provides a simple way to make the STUN attempt? I am looking for something along the line of:

stun-server.cpp
// implementation of a server which facilitates with connecting peers

stun-client.cpp
// peer A. make an offer via messaging server.
// peer B. accept the offer and send the answer via messaging server.
// peer A. make connection attempt via stun-server
// peer B. make connection attempt via stun-server
// ....
// peer A + peer B. either establish a connection or know STUN isn't possible

It sounds like there used to be a full ICE example, and also there is talk that any ICE stuff now is done via WebRTC. I wish to deploy on devices where build size and runtime code footprint is somewhat important, so I would love to avoid having huge dependencies to achieve a STUN connection between peers.

If libsourcey doesn't provide a STUN only solution but does provide a full ICE solution (outside of WebRTC) I'd also be interested in that as a starting point. Right now it seems like a bit of a minefield for being able to just connect two peers.

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

1 participant