From: "Michael Ströder" <michael@stroeder.com>
To: galene@lists.galene.org
Subject: [Galene] Re: Heads-up: built-in TURN server
Date: Tue, 19 Jan 2021 00:39:19 +0100 [thread overview]
Message-ID: <9365dbfd-11c7-7cf0-046d-951fa8fa541d@stroeder.com> (raw)
In-Reply-To: <87lfcprgl4.fsf@toke.dk>
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.
next prev parent reply other threads:[~2021-01-18 23:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 21:26 [Galene] " Juliusz Chroboczek
2021-01-18 21:38 ` [Galene] " Toke Høiland-Jørgensen
2021-01-18 21:44 ` Juliusz Chroboczek
2021-01-18 21:54 ` Toke Høiland-Jørgensen
2021-01-18 22:03 ` Michael Ströder
2021-01-18 22:04 ` Juliusz Chroboczek
2021-01-18 22:27 ` Toke Høiland-Jørgensen
2021-01-18 22:37 ` Juliusz Chroboczek
2021-01-18 23:05 ` Toke Høiland-Jørgensen
2021-01-18 23:39 ` Michael Ströder [this message]
2021-01-19 0:22 ` Juliusz Chroboczek
2021-01-19 11:47 ` Toke Høiland-Jørgensen
2021-01-19 11:52 ` Juliusz Chroboczek
2021-01-19 12:12 ` Toke Høiland-Jørgensen
2021-01-19 12:37 ` Michael Ströder
2021-01-19 12:48 ` Juliusz Chroboczek
2021-01-19 13:07 ` Toke Høiland-Jørgensen
2021-01-19 8:33 ` Rémi Nollet
2021-01-19 11:00 ` Gabriel Kerneis
2021-01-19 11:21 ` Juliusz Chroboczek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9365dbfd-11c7-7cf0-046d-951fa8fa541d@stroeder.com \
--to=michael@stroeder.com \
--cc=galene@lists.galene.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox