Turncat does not include SNI header when using TURN/TLS about stunner

[dnlwgnd]

Currently no resources, but we're accepting PRs!

fair enough!
would it be as simple as constructing a turns:// url instead of a turn://? I might be able to add that.

[rg0now]

Fixed in 246913f

[rg0now]

We have ended up taking this as a feature request and implemented it right away. You can now use --sni=my-server-name on the turncat command line to set the SNI. This should be useful for testing.

Closing this as fixed now in cleaning up open issues for the imminent release of v1, but I'd like to ask you to answer a quick question before abandoning this issue: are you planning to set the SNI for testing only, or do you actually intend to use turncat in production?

[dnlwgnd]

wow thanks will check that out!.
I currently want to test with turncat as the most simple scenario and to see wether routing packets through a standard reverse proxy is feasible.

production workload would be webrtc, and I know this is far from ideal. onlyunfortunately it seems very difficult to open up even a single udp port in our firewalls. with turn/tls I would be able to reuse existing pathways.

I also tested with your fork of the mediasoup-demo. this does not currently support the TLS transport at all as it seems.
would you be able to add the option for tls transport (while SNI would be required as well) to the demo?

[rg0now]

I also tested with your fork of the mediasoup-demo. this does not currently support the TLS transport at all as it seems.
would you be able to add the option for tls transport (while SNI would be required as well) to the demo?

Currently no resources, but we're accepting PRs!