From mboxrd@z Thu Jan 1 00:00:00 1970 From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1611011143; bh=676SgCrKWiEsK5jWEwioCU9hBCZHMLbik1OkyfkDzVg=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=W1EaVkFgv5LybdQCyGkrAiWOFAQhRTqivmLxSAskQLXRgFLMgYRmZMj83K+CcNrh7 G6xFqUpR9ekKcF2YHGDOzBFBwAn77Ged5nERy6pCqqf6YbcCT+lJUZ3xeZqQq61N7U hO6Gw5kiXnYiOEAGFhm7pRPpLu3QWaSpcxNGr9bcCTUv2wHXu/kPscnVx/6TQ89Lag 7flvk+A2ZlHqhhR4A3NMk4JyPrOy5rysZx1OkqSnoYcVIU8xLwukGvjXT8K51L93Tl oNgNVJtvOWGgoxDzABMtFn4gIDRmBcGbELNh9f4tD70Ee2P2pf0p5z5CF7u0fKiUdY 8aUfd1m/DkWWw== To: Juliusz Chroboczek In-Reply-To: <87eeihyipm.wl-jch@irif.fr> References: <87sg6yx7gy.wl-jch@irif.fr> <87zh16q61v.fsf@toke.dk> <87pn21yl6t.wl-jch@irif.fr> <87wnw9rjw7.fsf@toke.dk> <87mtx5yk96.wl-jch@irif.fr> <87o8hlridf.fsf@toke.dk> <87eeihyipm.wl-jch@irif.fr> Date: Tue, 19 Jan 2021 00:05:43 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87lfcprgl4.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID-Hash: 5DTI6MLFVHB7BOM4H55XLTE4MTECUFDG X-Message-ID-Hash: 5DTI6MLFVHB7BOM4H55XLTE4MTECUFDG X-MailFrom: toke@toke.dk X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header CC: galene@lists.galene.org X-Mailman-Version: 3.3.2 Precedence: list Subject: [Galene] Re: Heads-up: built-in TURN server List-Id: =?utf-8?q?Gal=C3=A8ne_videoconferencing_server_discussion_list?= Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: Juliusz Chroboczek 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=C3=A8ne. I'd like to understand why you and Michael appear to disagr= ee, > perhaps I'm missing something obvious. Sure, I can add it, of course :) It's just a bit of extra work; specifically, I have to go in and update the systemd unit file on update, and if I wasn't paying attention to the mailing list I would likely have missed this addition and end up running with a "broken" config. And also, from a "least surprise" PoV I think it's a bit odd to second-guess the user: if I configured a list of TURN servers, I would expect that that is the list that would be used, and not have it amended without an explicit opt-in. 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