Multiple stun server & stun server credentials about libdatachannel HOT 5 CLOSED

Also supporting TURN server with #14

from libdatachannel.

• You are right, when multiple STUN servers are specified, it uses one of the resolvable ones randomly. This behavior is acceptable according to RFC 8445, but it's different from the behavior of browsers implementing WebRTC, which consists in gathering candidates from all the STUN servers, allowing to address specific topologies with hosts between cascading NATs. Anyway, I don't see how to replicate the behavior of browsers with libnice for now.

• I didn't implement STUN server credentials because as far as I know, STUN servers on the public Internet never have authentication. Credentials are typically for TURN servers, which are not supported.

from libdatachannel.

Some firewalls blocks all UDP communication.
I would love to use TCP ports for ICE communication and also for data channel.

Can we enable this option?

g_object_set(G_OBJECT(mNiceAgent.get()), "ice-tcp", FALSE, nullptr);

I made some tests and it looks OK.

from libdatachannel.

Sure, in that case could you please add an option enableIceTcp (with default false) to do so in Configuration?
Also, to do everything cleanly you would need to handle TCP candidates in Candidate::resolve() (it should use SOCK_STREAM and IPPROTO_TCP).

from libdatachannel.

ICE TCP support added in #16

from libdatachannel.