[Galene] Re: Heads-up: built-in TURN server

["Michael Ströder" <michael@stroeder.com>]

On 1/19/21 12:05 AM, Toke Høiland-Jørgensen wrote:
> Juliusz Chroboczek <jch@irif.fr> writes:
> 
>>> What about when the external TURN server is on a different IP, so Galene
>>> has no problem starting up the internal one, but it's firewalled off to
>>> clients can't connect to it? In that case presumably it'll just be
>>> another TURN candidate offered to clients which will fail?
>>
>> The external TURN server will be tried first, so the latency of successful
>> connections will not increase.  You'll just take more time to fail.
> 
> Right, OK.
> 
>>> (I think Firefox emits a warning recommending a max of two candidates)?
>>
>> Yeah, I'm not sure why.  I see no reason for that in the ICE spec, but
>> perhaps Firefox are doing proprietary magic.
>>
>> At any rate, I'd expect somebody who goes through the trouble of setting
>> up an instance of coturn to be willing to add a command-line option to
>> Galène.  I'd like to understand why you and Michael appear to disagree,
>> perhaps I'm missing something obvious.
> 
> Sure, I can add it, of course :)
> 
> It's just a bit of extra work; 
> [..]
> Just to be clear, I think turning on the TURN server by default is
> totally fine to make it easier to deploy Galene! It's only the "override
> user config" aspect I'm objecting to (and it's not a terribly strong
> objection, at that).

Toke summarized my own feelings, maybe just an emotional over-reaction
against opening an unneeded service port. ;-)

Just go ahead with whatever you consider appropriate.

Ciao, Michael.