[Feature Request] Add STUN/TURN server support for NIC enumeration

[ValorZard]

If you want to use str0m for a client side application, you'll run into the problem of str0m not having STUN/TURN support built-in.

Fortunately, there are a few libraries that deal with that:

• https://github.com/sancane/rustun
• https://github.com/ystreet/librice

Maybe you could add support for using those in a crate feature or something?

[thomaseizinger]

In my experience, STUN is an extremely simple protocol and you can roll your own client using stun-codec quite easily.

TURN is the really difficult one. However, how you want to use TURN also depends a lot on your usecase. For example, what are the policies around keeping allocations alive, which allocations do you want to make. Same with channels. How do you deal with retries? What about buffering? How do you deal with dual-sockets?

I think there is value in a sans-IO TURN client but I do think it will be quite difficult to come up with a good abstraction.

For reference, here is oursv https://github.com/firezone/firezone/blob/main/rust/connlib/snownet/src/allocation.rs

[Razzwan]

One more suggestion. What about partnership with https://github.com/mycrl/turn-rs?

I used this library instead of coturn and I think I got almost everything in coturn with better performance